Results 1 to 7 of 7
Hi,
I am unable to boot my server and it is causing "Kernel panic - not syncing: Attempted to kill init!". Here are my details:
I have a brand new ...
- 09-27-2010 #1Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
[SOLVED] EXT3-fs: unable to read superblock
Hi,
I am unable to boot my server and it is causing "Kernel panic - not syncing: Attempted to kill init!". Here are my details:
I have a brand new Dell PowerEdge T110 server with Quad-Core Xeon CPU and 2GB 1333MHz RAM. I have installed a hard disk (SATA, 7.2rpm) on this machine that I removed from another Dell PowerEdge T100 server with Dual-Core Xeon CPU that was running software RAID 1.
Now when I boot the new T110 server, it displays the following error messages:
Creating root device.
Mounting root filesystem.
EXT3-fs: unable to read superblock
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
I am running CentOs v5.5 x86-64. If I put the hard disk back into T100, it boots fine. I do not know why it is not working with T110 server. Please help!!!
- 09-28-2010 #2
i am not sure about that but as i understand your new system is Quad-Core Xeon CPU and another system is Dual-Core Xeon CPU so i think that the kernel parameter is not same for both system so it is not become compatible in other system .
- 09-29-2010 #3Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
You are very right. Do you any suggestions for kernel parameters that I can use so that the server boots successfully?
- 09-29-2010 #4
As i know that the kernel parameter is set automatically when we install the system . so if possible you try to fresh install the o.s or wait for any linux guru to reply . some useful link i given
HTML Code:http://www.mjmwired.net/kernel/Documentation
- 09-30-2010 #5
Are you using UUID in grub.conf and /etc/fstab or device names only?
Post the contents of /etc/fstab and /boot/grub/grub.conf file here.It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 09-30-2010 #6Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
Here are the outputs of fstab, grub.conf and fdisk:
$cat /etc/fstab
/dev/md3 / ext3 defaults 1 1
/dev/md4 /var ext3 defaults 1 2
/dev/md2 /home ext3 defaults 1 2
/dev/md1 /usr ext3 defaults 1 2
/dev/md0 /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sdb5 swap swap defaults 0 0
LABEL=SWAP-sda5 swap swap defaults 0 0
$cal /boot/grub/grub.conf
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.18-194.11.3.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.11.3.el5 ro root=/dev/md3
initrd /initrd-2.6.18-194.11.3.el5.img
$fdisk -l
Disk /dev/sda: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 127 1020096 fd Linux raid autodetect
/dev/sda2 128 12875 102398310 fd Linux raid autodetect
/dev/sda3 12876 15425 20482875 fd Linux raid autodetect
/dev/sda4 15426 19452 32346877+ 5 Extended
/dev/sda5 15426 15935 4096543+ 82 Linux swap /Solaris
/dev/sda6 15936 16445 4096543+ fd Linux raid autodetect
/dev/sda7 16446 16955 4096543+ fd Linux raid autodetect
In grub.conf, I have tried changing root=/dev/sda6 where sda6 is md4. Similarily, I have tried root=LABEL=/ but it did not help.
- 10-08-2010 #7Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
I tried all the suggestions that were posted so far. But no luck. Finally, I decided to do a fresh install on Cent Os on T110 server.


