> Add to your boot params: libata.force=noncq > It's not a guarantee to work, just helps quite a bit. Reading the comments above I dont see this helping much. > > Also are you running in any sort of RAID configuration? Yes, I am. I have four disks attached to the controller; on each pair of disks two partitions are in a RAID 1. > I found a new PSU > helped a little as well, had very few incidents up until yesterday... I dont see a reason to assume this is related to the PSU. This very thread more or less proves this is a either a bug in linux kernel or in firmware/hardware. > I still blame Seagate drives as being part of the problem. I just checked and it turns out I do actually have two Seagate Barracuda 7200.10 disks (I thought I had only Samsung). And it is indeed one of those that is causing problems. This is interesting. > > On Thu, Mar 31, 2011 at 14:36, Vasco