fsck, e2fsck, mke2fs ?'s

blackx · 05-22-2003, 11:10 PM

I am booting my RH9 boot into rescue mode and trying to figure out how to run fsck, mke2fs -n to find the superblocks, and e2fsck -b to fix superblocks but its not finding the commands in the defualt /(root) and locate is not working.
I was under the understanding the partitions had to be unmounted to run the about commands on them.. is this true.
Do I have to mount my normal /root partition and chroot it?

michaelk · 05-23-2003, 07:24 AM

There isn't any path enviroment set in rescue mode.

Just use the cd command to navigate to /sbin or /bin.

kazuni · 05-23-2003, 07:27 AM

yeah, it's in one of those paths.

try to echo the $PATH (if u r running a shell) and see if paths are there, if they are, chances are u can just use "whereis fsck" or "which fsck". If not, check those paths (/sbin, /bin, /usr/bin, /usr/sbin/, etc)

oh and of course u have to be root, just run

/sbin/su

and login as root

hope that helps

blackx · 05-23-2003, 01:52 PM

That makes sense but here is a problem I am running into. I want to find the superblocks on / partition but get a error when I run:

mke2fs -n /dev/sda2

error:
/dev/sda2 is mounted: will not make a file system here.

I have booted off the RH9 cd1 -> linux rescue mode -> selected read only for /mnt/sysimage.
So I figured I need to umount /dev/sda1

umount /dev/sda2

error:
umount /dev/sda2 device or resource busy

umount /mnt/sysimage

error:
umount /dev/sda2 device or resource busy

Can someone educate me on what I am missing... sorry for the lamer question...

whansard · 05-23-2003, 01:56 PM

maybe the shell is cd'd into a directory on the hard
drive?

michaelk · 05-23-2003, 02:01 PM

Maybe because you are selecting read only for /mnt/sysimage.

Can you just boot to a command prompt in rescue mode not select or mount any partitions?

blackx · 05-23-2003, 02:02 PM

when you boot to rescue mode it puts you in a small linux root environment and your normal user /(root) environment is mounted to /mnt/sysimage in rw or ro mode depending on what you chose during the option menus that is unless you choose to skip linux partition detection.
I didnt run chroot on /mnt/sysimage ether and that is why I am confused...

"Maybe because you are selecting read only for /mnt/sysimage.
" why wouldnt let me umount it though?