cant boot - kernel panic

khazdar · 2004-10-09 14:50:23

during boot i get this message:

ext3-fx error (device hde3): ext3_check_descriptors: block bitmap for group 164 not in group (block 5341184)!
ext3-fs: group descriptors corrupted !
ext2-fs error (device hde3): ext2_check_descriptors: block bitmap for group 164 not in group (block 5341184)!
ext2-fs: group descriptors corrupted!
udf-fs: no partition found (1)
xfs: bad magic number
xfs: sb validate failed
kernel panic: vfs: unable to mount root fs on unknown-block(0,0)

anyone known how to fix? i have a copy of knoppix that i can boot in to if there is a util that can fix this corruption. thanks!

-khaz

khazdar · 2004-10-09 15:25:32

i just ran fsck.ext3 and it fixed a bunch of errors. i am now able to mount /dev/hde3 under knoppix (couldnt mount it before) so i think this is a good sign. i'm about to reboot and find out.

-khaz

khazdar · 2004-10-09 16:34:36

well.. i still cant boot. this is what happens now:

starting udev daemon                                [failed]
activating swap                                         [swap]
mount root read-only                                [done]
checking filesystems                                  [busy]

fsck.ext3: no such file or directory while trying to open /dev/discs/disc0/part3

/dev/discs/disc0/part3:
the superblock could not be read or does not describe a correct ext2 filesystems. if the device is valid and it really contains an ext2 filesystem (can not swap or ufs or something else) then the suprerblock is corrupt and you might try running e2fsck with and alternate superblock.

and then it says give root password for maintence.

any ideas ??

-khaz[/code]

Mr Green · 2004-10-09 16:41:12

Are use using lilo or grub. ?

What kernel are you trying to boot .....?

Need a little more info to get an idea whats wrong .....

Could be something wrong in fstab ......

khazdar · 2004-10-09 16:48:56

I am using grub.

The kernel is 2.6.7

here is my fstab:

#
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /proc         proc      defaults            0      0
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0
tmpfs                  /tmp          tmpfs     defaults            0      0
#sysfs                 /sys          sysfs     defaults            0      0
usbfs               /proc/bus/usb    usbfs     defaults            0      0

/dev/cdroms/cdrom0     /mnt/cd   iso9660   ro,users,noauto,unhide   0      0
/dev/cdroms/cdrom0     /mnt/dvd  udf       ro,user,noauto,unhide   0      0
/dev/floppy/0         /mnt/fl   vfat      user,noauto,unhide      0      0

/dev/discs/disc0/part3 / ext3 defaults 0 1
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0

khazdar · 2004-10-09 20:44:50

i am able to boot now.... but my systems is screwed

i am guessing that when i ran fsck.ext3 it dumped some system files into the lost+found directory. while looking through the lost+found i noticed that my udev directory was there. i moved it back to the /etc dir and i can get logged in with out errors. but there 75 files and 15 directories in the lost+found directory. i tried to starting X and it complained that it couldn't find startx. i ran a updatedb and then a locate and startx was nowhere to be found. i tried re-install xorg and i got a message that said could not extract etc/X11/xkb/types/README: Operation not permitted. tried pacman -sf xorg, same thing. i tried removing the /etc/x11/xkb directory and it says this: could not extract etc/X11/xkb/types/README: Operation not permitted
i tried changing the permissions of README and it wont let me. even though i am root. it said could not extract etc/X11/xkb/types/README: Operation not permitted.

it is looking like i need to do a fresh install. do any of my ramblings make sense?

iphitus · 2004-10-10 04:43:12

As the filesystem was corrupted, it seems your best choice is to clean format the affected partitions then reinstall.

If you have an older computer, this might be the signs of your hard drive dying.

iphitus

khazdar · 2004-10-10 13:48:34

i re-installed arch. just putting the finishing touches on the system.

Mr Green · 2004-10-10 13:58:27

If its a new install then I would agree that reinstalling from scratch is a good idea ...

If on the other hand system had been set up for some time then something a little less drastic is in order

Anyway glad to hear you are back on track

Arch Linux

#1 2004-10-09 14:50:23

cant boot - kernel panic

#2 2004-10-09 15:25:32

Re: cant boot - kernel panic

#3 2004-10-09 16:34:36

Re: cant boot - kernel panic

#4 2004-10-09 16:41:12

Re: cant boot - kernel panic

#5 2004-10-09 16:48:56

Re: cant boot - kernel panic

#6 2004-10-09 20:44:50

Re: cant boot - kernel panic

#7 2004-10-10 04:43:12

Re: cant boot - kernel panic

#8 2004-10-10 13:48:34

Re: cant boot - kernel panic

#9 2004-10-10 13:58:27

Re: cant boot - kernel panic

Board footer