On 04/07/2011 10:53 AM, Adam Williamson wrote:
On Thu, 2011-04-07 at 10:38 -0500, Steven Stern wrote:
I rebooted to see if that would make the next try go better. The system required a manual fsck. It appears that the file system had several errors. I'm currently running another update that seems to be going well.
Now, I'm wondering what caused the disk errors.
Dollars to donuts, your disk's dying. Run smartctl on it, check the system logs, do some backups, check out your manufacturers return policy...
Adam: It's a brand new disk. I think what happened is that I was testing hibernate/suspend/poweroff stuff (because this is a laptop) and the repeated cycles led to some file system corruption, or I may have moved it from my desk to my bag before the disk and file system were completely shut down.
In any case, smartctl is running a long test against the drive right now.