Tim wrote:
> Denis,
>
>> dmsg shows Ext-3 fs error (stb1); remounting file system read only
>
> This is a pretty clear indication that either your drive is dying or you
> did something very bad to your filesystem (many hard reboots,
> accidential writes to the raw disk device, etc). I'm thinking the most
> likely is that your drive is dying, since EXT3 is pretty good about
> recovering from hard reboots.
>
> To help verify this, check through your dmesg/kernel logs for more
> drive failure information. For instance, the Linux kernel typically
> prints out something similar to the following when there are signs of
> hardware failures:
x...@r2d3:~$ dmesg | grep error
[ 30.788060] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not
found.
[ 37.592214] res 51/84:00:80:f6:4f/00:00:00:00:00/fe Emask 0x10 (ATA
bus error)
[ 37.592223] ata1.01: error: { ICRC ABRT }
[ 37.941575] res 51/84:00:80:f6:4f/00:00:00:00:00/fe Emask 0x10 (ATA
bus error)
[ 37.941584] ata1.01: error: { ICRC ABRT }
[ 38.290936] res 51/84:00:80:f6:4f/00:00:00:00:00/fe Emask 0x10 (ATA
bus error)
[ 38.290945] ata1.01: error: { ICRC ABRT }
[ 38.632007] res 51/84:00:80:f6:4f/00:00:00:00:00/fe Emask 0x10 (ATA
bus error)
[ 38.632015] ata1.01: error: { ICRC ABRT }
[ 39.996235] res 51/84:00:4f:7b:24/00:00:00:00:00/fc Emask 0x10 (ATA
bus error)
[ 39.996244] ata1.01: error: { ICRC ABRT }
[ 40.353895] res 51/84:00:4f:7b:24/00:00:00:00:00/fc Emask 0x10 (ATA
bus error)
[ 40.353903] ata1.01: error: { ICRC ABRT }
[ 40.703264] res 51/84:00:4f:7b:24/00:00:00:00:00/fc Emask 0x10 (ATA
bus error)
[ 40.703272] ata1.01: error: { ICRC ABRT }
[ 41.035996] res 51/84:00:4f:7b:24/00:00:00:00:00/fc Emask 0x10 (ATA
bus error)
[ 41.036004] ata1.01: error: { ICRC ABRT }
Is this ordinary, or should I be playing with the cables?
...
>
> To get more information about such errors, i suggest you use smartctl
> (a part of the smartmontools package on Debian) on the drive.
...
I will look into smartctl next.
> The lost+found folder is where orphaned files are placed after a fsck.
> Orphaned files are those which were not deleted normally, but were
> unlinked from their parent directory... in other words, files still on
> disk but were forgotten about. You should look through these files to
> see if anything of importance is there. Commonly they'll just be
> temporary files (perhaps generated by firefox and the like). I
> encourage you to use the "file" command on them to determine the file
> content type, then use an appropriate tool to open the ones you can.
> Note that you must have root privileges to look at files in this
> directory.
>
> Good luck,
> tim
I will also look at the orphaned files. Should I infer from your comments that
the presence of such files are likely NOT due to the crash?
Thanks for the ideas.
-Denis
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
