Hi,
you shound unmount the partition first. Then you can check it. See e2fschk for more details: e2fschk -p -v /dev/sda1. (http://www.cyberciti.biz/tips/repairing-linux-ext2-or-ext3-file-system.html). Find another Linux machine to check the disk on it (it works even with linux runing on vmware where you can connect your drive using a sata to usb converter e.g. http://www.amazon.com/Drive-Adapter-Converter-Optical-External/dp/B002OV1VJW
I would also recommend to check the hard drive surface to recove bad blocks if any: http://hddreg.com/about
Thanks,
Sergey
|
Hello, The boot disk of my NSLU2 with SlugOS 5.3 has several errors. I still can boot. I tried to fix the errors by running fsck when the disk was attached to a Ubuntu desktop, without success. I am afraid serveral files are corrupted. I cannot connect from my Windows desktop to samba anymore. Is there a way to re-TURNUP creating a new bootdrive? I'm not a Linux expert, so be gentle on me, please! The log says: Mar 11 11:30:59 (none) user.notice kernel: scsi 1:0:0:0: Direct-Access SAMSUNG HD154UI PQ: 0 ANSI: 2 CCS Mar 11 11:30:59 (none) user.notice kernel: sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) Mar 11 11:30:59 (none) user.notice kernel: sd 1:0:0:0: [sdb] Write Protect is off Mar 11 11:30:59 (none) user.debug kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 38 00 00 Mar 11 11:30:59 (none) user.err kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Mar 11 11:30:59 (none) user.notice kernel: sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) Mar 11 11:30:59 (none) user.notice kernel: sd 1:0:0:0: [sdb] Write Protect is off Mar 11 11:30:59 (none) user.debug kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 38 00 00 Mar 11 11:30:59 (none) user.err kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Mar 11 11:30:59 (none) user.info kernel: sdb: sdb1 sdb2 sdb3 sdb4 Mar 11 11:30:59 (none) user.notice kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Mar 11 11:30:59 (none) user.debug kernel: usb-storage: device scan complete Mar 11 11:30:59 (none) user.alert kernel: journal_bmap: journal block not found at offset 6156 on sda1 Mar 11 11:30:59 (none) user.err kernel: JBD: bad block at offset 6156 Mar 11 11:30:59 (none) user.alert kernel: journal_bmap: journal block not found at offset 6156 on sda1 Mar 11 11:30:59 (none) user.err kernel: JBD: bad block at offset 6156 Mar 11 11:30:59 (none) user.err kernel: JBD: Failed to read block at offset 6150 Mar 11 11:30:59 (none) user.warn kernel: JBD: recovery failed Mar 11 11:30:59 (none) user.err kernel: EXT3-fs: error loading journal. Mar 11 11:30:59 (none) user.info kernel: kjournald starting. Commit interval 5 seconds Mar 11 11:30:59 (none) user.warn kernel: EXT3-fs warning (device sda1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure Mar 11 11:30:59 (none) user.warn kernel: EXT3-fs warning (device sda1): ext3_clear_journal_err: Marking fs in need of filesystem check. Mar 11 11:30:59 (none) user.warn kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended Mar 11 11:30:59 (none) user.info kernel: EXT3 FS on sda1, internal journal Mar 11 11:30:59 (none) user.info kernel: EXT3-fs: recovery complete. Mar 11 11:30:59 (none) user.info kernel: EXT3-fs: mounted filesystem with ordered data mode. Mar 11 11:30:59 (none) user.info kernel: kjournald starting. Commit interval 5 seconds After a short time I see this when I dmesg: Aborting journal on device sda1. ext3_abort called. EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only Regards, Jos.
|
No comments:
Post a Comment