Re: e2fsck problem/interpretation

Tam <taminglis@xxxxxxxxx> writes:


This may depend on the distribution that you're using. For at least
some systems, 'touch /forcefsck && reboot' will do it.


Thats working now, thankyou Doug.


e2fcsk -y /dev/sdb1 will fix your your first problem. For the
second one you'll need to confirm that /dev/sdc2 actually has an
efs file system on it. Are you sure that it isn't a container
for an LVM volume?


Yup I'm sure.

Then which drive are those LVM volumes listed in /proc/partitions on?

That drive does in fact have Fedora 7 on it and the layout would
seem to confirm that. The drive in use now is sda. sda1 is quite
small with sda2 allocated the lions share of the space. sdc is very
simalair (the default layout created by the install process both
times). I used LVM back in the dark old days when it had to be
manually configured so im 100% sure its not the case. I can mount
sdc1 and find the following directories and files.

Dirs : Lost+Found, grub.
Files : config-2.6.21-1.3194.fc7, System.map-2.6.21-1.3194.fc7,
initrd-2.6.21-1.3194.fc7.img and vmlinuz-2.6.21-1.3194.fc7

Now you're talking about sdc1, while the error messages were about
sdc2. Which is it?

--
Måns Rullgård
mans@xxxxxxxxx
.