10-26-2009 12:10 PM
Just did the firmware update and it hosed my Windows 7 installation. The updater showed a successful firware update. Initially the computer booted just fine, but once I was within Windows it installed some drivers and asked for a reboot. That's when the trouble started. Now the drive won't boot Windows 7 anymore. I don't know if it's a Dell problem or Intel problem. The Dell BIOS claims a SMART error. I have a Dell XPS 8000.
10-28-2009 05:30 PM
Has anyone with bricked drives tried disabling SMART in the BIOS? Maybe this would allow booting back to Windows?
10-28-2009 05:34 PM
I don't know who gave that information. My Partition Starting Offset is 1, 048, 576 bytes. So?
10-28-2009 05:38 PM
ambizytl wrote:
I don't know who gave that information. My Partition Starting Offset is 1, 048, 576 bytes. So?
It was from another forum. It means that your drive is correctly aligned. Can you confirm that TRIM is active and your drive is fine please?
You can do this by running "fsutil behavior query DisableDeleteNotify" in a dos box. If DisableDeleteNotify = 0 then TRIM is active.
10-28-2009 05:46 PM
That confirms TRIM is enabled in Windows 7, which I know from before the update. I am the one who posted that information about checking for TRIM on this forum. I also know TRIM is working in the SSD by doing a benchmark test using AS SSD. The Seq Write is now 109.02 MB/s and my 4K write is back to like new performance--that is the best way to check for 160GB SSD drives to know if your TRIM in SSD is working, also for 80GB SSD but without the Seq Write figure being so high as the enhancement in the update is only for 160GB SSD
10-28-2009 05:50 PM
ambizytl wrote:
That confirms TRIM is enabled in Windows 7, which I know from before the update.
Yup and that's what I am trying to hypothesize:
Aligned SSD + TRIM enbaled or not = successful firmware update
Not aligned SSD + TRIM enabled = bricked drive
My drive is not aligned and I have TRIM disable and I am fine. My hypothesis could be way off but I haven't seen anything else that makes sense as to why it's appears to be a hit and miss update.