which config files are responsible for mounting and detecting filesystems..

deepclutch · 11-26-2005, 03:03 PM

Very Happy Hello to All,
Will someone help me which configuration files are responsible for mounting/detecting correct partitions with Linux..afaik they are /etc/fstab and /etc/mtab..any other files...please help...

I have a problem with my debian sarge 3.1 with 2.6.14-1-686-smp kernel from unstable repo.
everything worked well until i reinstalled XP and sarge kernel panicked... due to rearranged/renamed partition table.
i will expalin briefly,earlier my root partn is at /dev/sda7 is now at /dev/sda8 and my swap partiton earlier at /dev/sda6 changed to /dev/sda7...so i edited mounted sarge partition /etc/fstab and /etc/matb to correct partition names..rescued grub,but sarge kernel panicked
again saying it cannot find ext3fs on /dev/sda7...while sda8 is the correct partiton to look for..Thanks please give a hint what should be wrong......

H2O-linux · 11-26-2005, 03:05 PM

etc/fstab

purelithium · 11-26-2005, 03:49 PM

Quote:

Originally posted by H2O-linux
etc/fstab

Read his post, fool! He already edited his fstab.

I would check to see if your edits took effect. Make sure you actually check that partition table with fdisk.

You shouldn't have to edit mtab, as that only takes effect once the fs is actually mounted. so don't mess with it, anything you change will just get overwritten once the partitions are properly mounted.

deepclutch · 11-26-2005, 04:23 PM

Thanks purelithium,i checked my debian partition with fdisk

Code:

fsck.ext3 /dev/sda8 -f
e2fsck 1.38 (30-Jun-2005)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda8: 140584/1343488 files (1.6% non-contiguous), 828552/2684855 blocks

how do i check superblocks ...i know that fsck.ext3 -b xxxx will do.but me silly,i don know about this superblocks,how to list or find them.....please help....

makuyl · 11-26-2005, 04:23 PM

I'd say the kernel panic comes from wrong root= in menu.lst. Perhaps double check that also.

deepclutch · 11-26-2005, 04:25 PM

@makuyl
i rechecked menu.lst for root value it is correct.

makuyl · 11-26-2005, 04:31 PM

Hmm, you might as well post the menu.lst

deepclutch · 11-26-2005, 04:42 PM

heres my menu.lst fyi i checked for superlocks error and fixed some

errors...but gain kernel panic

Code:

root@ubuntu:~# vim /mnt/debian/boot/grub/menu.lst

Code:

title           Debian GNU/Linux, kernel 2.6.14-1-686-smp (splashy)
root            (hd0,7)
kernel          /boot/vmlinuz-2.6.14-1-686-smp root=/dev/sda8 ro
#vga=786 quiet
initrd          /boot/initrd.img-2.6.14-1-686-smp
savedefault
boot

makuyl · 11-26-2005, 04:52 PM

You're right, looks ok. Perhaps reinstall grub then. Can't hurt anyway. Strange problem while afaict you've done everything correctly.

deepclutch · 11-26-2005, 04:55 PM

Thanks anyway..seems like i endup in a reinstall eh?..

makuyl · 11-26-2005, 05:09 PM

Well, reinstallation is rarely needed but if you backup /etc and some such it won't take long to get everything back. I'd still try running grub-install and do "grep root menu.lst" just to see you don't have a default root or groot (hdx,y) that might be messing things up.

deepclutch · 11-26-2005, 05:49 PM

Thanks...i will try that....waiting for 4 days to fix the problem.....

purelithium · 11-27-2005, 09:53 AM

I didn't mean checking your partitions with fdisk, I meant checking your partition table and making sure that the partition table listed by fdisk was the same as was listed in your fstab.

deepclutch · 12-03-2005, 03:25 PM

Yes.fstab is the same as fdisk -l lists.any one to help..me