X-25M 160GB noticeably slower

[erdemali]

are those old slides? the G2 X25-E uses super-capacitor for bbwc operation which changes ALOT when it comes to intel write.

If you'd like i could point this thread to an intel SSD Specialist who could share non-nda opinions. (aka intel employee) might take a while.

Are you saying this may not be applicable to new drives?
I didn't understand, sorry.

good way to put doubts in one's mind / clouds one's decisions.
Some hate to see others advanced and some love to see how they get advanced.

 

[Old Hippie]

Can this be done while keeping the data?

I doubt it.

 

[erdemali]

I doubt it.

I thought so.
Then there is no point for me to change the way I do it that works for me
and that I am comfortable with.

 

[Martimus]

are those old slides? the G2 X25-E uses super-capacitor for bbwc operation which changes ALOT when it comes to intel write.

If you'd like i could point this thread to an intel SSD Specialist who could share non-nda opinions. (aka intel employee) might take a while.

I would appreciate it if you did that.

 

[NiL8r87]

Wow, some fantastic information in this thread. Thanks alot everyone. I got alot more help than I ever expected

I'm going to give sub.mesa's recommendation a try. I'll let everyone know how it goes.

 

[NiL8r87]

I'm not sure if HDD Erase worked properly. When I ran the secure erase I get a "General Failure Writing Drive A" error, and it asks me to Abort, Retry, or Fail. Retry doesn't work, when I select fail it says there was an error writing the audit log or something to that effect, but it says that the drive was successfully wiped.

I restarted, and the computer tried to load windows but failed. I decided to insert the Windows 7 disk and check the status of the partition, it was listed as unallocated space. Oh, and the SSD firmware was still up to date. Again, not sure if the wipe was successful. Thoughts?

 

[Old Hippie]

When I ran the secure erase I get a "General Failure Writing Drive A" error

It gives me that error every time but still works fine....as you have experienced.

I dunno if "Drive A" is my absent floppy but the program works as intended.

 

[NiL8r87]

I see. I think I figured out why my comp tried to load windows. The 100MB system partition was somehow located on my Storage drive. And I guess the hdd erase wasn't supposed to reset the firmware. I suppose it worked then

 

[erdemali]

....................
....

 

[Martimus]

....................
....

Why did you take the results down? They were pretty interesting, even if they were only one point of data.

 

[erdemali]

Why did you take the results down? They were pretty interesting, even if they were only one point of data.

That was a stupid idea proving what's already proven by intel engineers.

 

[LokutusofBorg]

Actually, is this true for all SSD or just Intel? Forgot to ask that important question

One of Anand's latest SSD articles (the one comparing the newer Sandforce drives only reserving 13%) explains that the Intel and Sandforce controllers are dynamic, and use any free space. I took that as implying that other controllers don't do this, and will only use the area they know as "reserved". Could be wrong, but that's my take on it.

 

[IntelUser2000]

Can this be done while keeping the data?

Yes.

But to make it as a controller reserved space effective you need to run Secure Erase anyway so in a way, no.

 

[erdemali]

Yes.

But to make it as a controller reserved space effective you need to run Secure Erase anyway so in a way, no.

Thanks. I was hoping a dummy easy way.

 

[IntelUser2000]

Secure Erasing on my X25-M was extremely annoying.

1. My motherboard(DH55HC) has no floppy ports
2. You can't run the HDAT2 without using legacy IDE selection on BIOS. "Native" and AHCI does not work
3. Most of the newer motherboards, including the one I have, supports the ATA command which blocks the Secure Erase from working.

I had to find a computer that doesn't block the Secure Erase, has option to switch to legacy IDE and supports SATA, and use a bootable USB Flash drive in order to make it work. Not all USB flash drives can be made bootable either.

 

[erdemali]

Some are still having trouble understanding the points made.

For instance:
7% spare area ------> ~600Gb write ~= 4% wear
27% spare area -----> ~600Gb write ~= 1% wear

Not even mentioning dramatic increase in IOPS

That's it. I am not an SSD Manuf. Employee trying to convince people.
Use it the way you like and couple of years down the track buy another SSD.

 

[Old Hippie]

Secure Erasing on my X25-M was extremely annoying.

1. My motherboard(DH55HC) has no floppy ports
2. You can't run the HDAT2 without using legacy IDE selection on BIOS. "Native" and AHCI does not work
3. Most of the newer motherboards, including the one I have, supports the ATA command which blocks the Secure Erase from working.

I had to find a computer that doesn't block the Secure Erase, has option to switch to legacy IDE and supports SATA, and use a bootable USB Flash drive in order to make it work. Not all USB flash drives can be made bootable either.

I can and have done a secure erase with an Abit IP35 Pro and my Asus P6T thru a CD drive and the bootable ISO I linked earlier in the thread. Even though these boards had a BIOS lock the CD would recognize this and ask for a reboot to try and "fool" the lock.

Unless you have no optical drive I'm not sure why floppy ports or USB drives were needed.

Edit....I'm using a SATA CD drive in IDE mode.