Comment 18 for bug 198125

I too have experienced disk corruption following suspend to ram, which I use on my NAS storage server in conjunction with PowerNap. I have observed this working in both Lucid and Natty over the last year. In my experience, this problem is not limited to external drives. I have observed corruption of my boot drive on three different internal SATA controller cards in a Nehalem class X86 server. These include a

* Highpoint Rocket 620 PCIe add in card running Bios Version 1.1
* LSI MPT SAS controller running in IT mode on a Supermicro S8DA3 motherboard running MPTSAS BIOS v 6.30.00.00 2009_11_12
* Old Promise SATA300 PCI add in card

Note that I am using all 6 of the ICH10 SATA ports for a RAID5 array, so I do not know if this corruption ever occurs using the standard Intel ICH10 SATA ports. Perhaps that is why it is not reported more widely.

The corruption occurred most often when using the LSI SAS controller (about 1 in 5 boots). It occurs much less frequently on the Highpoint Rocket 620 card, but it just happened for the first time yesterday after about 2 months of testing.

I'm sorry I don't have fresh logs to post, but I had to get my system back on-line ASAP. I'll add logs the next time it happens if I can scrape them out of the corrupted filesystem.

This is a very serious problem, and I am baffled that it is marked Low priority. It doesn't get much more grave than when your boot drive gets corrupted every few months due to something not being right in the syncing of disks going into and out of suspend to ram.

If Ubuntu is serious about power management in the upcoming Precise release, this MUST be addressed.

Best Regards,

-Jim Heck