> Evening. An ext2 fs on my wife's suse machine has
> decided to become rather stupid. Upon booting, errors
> are found with the fs and fschk is recommended.
I would boot from your rescue disk and run e2fsck
without mounting the boot LINUX drive, and I would
run it repeatedly.
I am using Reiserfs now and I am so happy, no trouble
so far. I am 100% LINUX and I keep two bootable drives
on my system at all time with mountpoints and /etc/fstab
ready to mount the other one, I haven't needed to for
over a year. (a 40 and a 20 gig.)
> Error reading block 65610 (Attempt to read block from
> filesystem resulted in shortread) while doing inode
> scan. Ignore Error?
>
> Upon specifying 'n', e2fsck exits. In other attempts
> to resolve this, I have told e2fsck to ignore the
> error, and it carries on about its way checking the fs
> and then exits without error. This doesn't fix much
> though as I am no better off upon recycling.
> I am assuming that there is not an error with the
> device since I can boot into a fat32 fs which is also
> on the hdd. Is this a corrupt ext2 fs that I have? Was
> booting fine last night.
--
73 (= Best Regards) de: Ron ka4inm@tampabay.rr.com
100% Slack. since July, 1997 (still free!) SENT D&T are UTC
Visit my HAM Web SITE at: http://www.qsl.net/ka4inm
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:26:52 EDT