I'm having a strange problem I've never seen before. Sometimes my system crashes, and upon restart I am missing *at least* a handful of files. They are completely gone and untraceable. At first I forced fsck on reboot, and that helped recover some of them, but the problem continues. I have no clue even where to start tracing this. Can anyone help? The system is a new AMD Phenom on a SATA Seagate 1Tb disk. Ubuntu Ibex is the only OS loaded, on ext3 partitioned 5 ways. My system just crashed today, and now that I'm back up and running there is one file in particular that is completely gone. I haven't touched this file in months, and it just up and disappeared. I checked with Seagate to see if my drive was part of the recall, it's not. (so they say) HELP! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20090312/2f3d25a3/attachment.htm>
On Thu, 12 Mar 2009, James McKain [Gmail] wrote:> I'm having a strange problem I've never seen before. Sometimes my system > crashesWhat's wrong with this system that it sometimes just "crashes"?>, and upon restart I am missing *at least* a handful of files. They > are completely gone and untraceable. At first I forced fsck on reboot, and > that helped recover some of them, but the problem continues.Anything related in the logs, does fsck report anything during bootup?> My system just crashed today, and now that I'm back up and running there is > one file in particular that is completely gone. I haven't touched this file > in months, and it just up and disappeared.Did anything show up in /lost+found?> I checked with Seagate to see if my drive was part of the recall, it's not.Speaking of drive errors: did you test your drive, can you read from the beginning to the end of it without any errors? Christian. -- If you want to contact Bruce Schneier, just type his name into your shell prompt.
On Thursday 12 March 2009, James McKain [Gmail] wrote:> I'm having a strange problem I've never seen before. Sometimes my system > crashes, and upon restart I am missing *at least* a handful of files. They > are completely gone and untraceable. At first I forced fsck on reboot, and > that helped recover some of them, but the problem continues. I have no > clue even where to start tracing this. Can anyone help? The system is a > new AMD Phenom on a SATA Seagate 1Tb disk. Ubuntu Ibex is the only OS > loaded, on ext3 partitioned 5 ways. > > My system just crashed today, and now that I'm back up and running there is > one file in particular that is completely gone. I haven't touched this > file in months, and it just up and disappeared. > > I checked with Seagate to see if my drive was part of the recall, it's not. > (so they say)Test it using smart: # smartctl -T permissive -d ata -s on /dev/sda # smartctl -T permissive -d ata -t long /dev/sda && sleep 2h && smartctl -T permissive -d ata -l selftest /dev/sda If the output is all %00, then the drive is passing it's self test. If it's failing before it reached %00 (down form 100%) then it's failing.. get your stuff off asap. Tweeks Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com, and delete the original message. Your cooperation is appreciated.