You said that you were using the new 2.4.17 kernel. Since you claimed to have forgotten that you were using ext3, is it possible that you forgot to include ext3 support into the new kernel? This problem that you're having is common among people who try to mount an ext2 fs as ext3 or vise versa. Check your fstab & then boot into single user mode & manually mount the FS. BTW, ext3 is backwards compatible with ext2. So although your supberblock excursion was not the best way to go, it should not have damaged anything so long as it didn't corrupt the fs itself. -Rob > begin Linux Pquter quotation: > > > When the system tried to come up, it couldnt mount root. It dropped > > me straight into single user mode. > > I'm not familiar with the newer versions of Red Hat, but how on Earth > did you get into single-user mode if you could not mount the root > filesystem? Perhaps the message said it could not *fsck* root? > > -- > ///////////////// | | The spark of a pin > <sneakums@zork.net> | (require 'gnu) | dropping, falling feather-like. > \\\\\\\\\\\\\\\\\ | | There is too much noise. > > > > _______________________________________________ > > Ext3-users@redhat.com > https://listman.redhat.com/mailman/listinfo/ext3-users > -- -Rob
