[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Kernel panic f7t3 and f7t4



Finally decided I need some help with this one.  I get a kernel panic on
several installs of f7t3: iso dvd, and 2 http installs from rawhide,
different snapshots.  Same issue with iso dvd install of f7t4.  All
appear to install normally to sdc which is a wd 160 gig pata.  Machine
also has 2 sata2 drives in raid 1 configuration running centos 5. Here
is hardware setup:
asus A8N-SLI
cpu amd 64 X2 4400+
2 gigs ram
2 maxtor sata2
1 wd pata

[root office bmcclure]# fdisk -l

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          13      104391   83  Linux
/dev/hda2              14        1925    15358140   83  Linux
/dev/hda3            1926       19457   140825790   83  Linux

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid
autodetect
/dev/sda2              14        3837    30716280   fd  Linux raid
autodetect
/dev/sda3            3838        3901      514080   fd  Linux raid
autodetect
/dev/sda4            3902       19457   124953570    5  Extended
/dev/sda5            3902       19457   124953538+  fd  Linux raid
autodetect

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   fd  Linux raid
autodetect
/dev/sdb2              14        3837    30716280   fd  Linux raid
autodetect
/dev/sdb3            3838        3901      514080   fd  Linux raid
autodetect
/dev/sdb4            3902       19457   124953570    5  Extended
/dev/sdb5            3902       19457   124953538+  fd  Linux raid
autodetect

Disk /dev/md1: 31.4 GB, 31453347840 bytes
2 heads, 4 sectors/track, 7679040 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/md3: 127.9 GB, 127952355328 bytes
2 heads, 4 sectors/track, 31238368 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md3 doesn't contain a valid partition table

Disk /dev/md2: 526 MB, 526319616 bytes
2 heads, 4 sectors/track, 128496 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md0: 106 MB, 106823680 bytes
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 doesn't contain a valid partition table

I understand the above hda drive is seen by f7 as sdc.

Here is the error message:

mount:could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot:mount failed: No such file or directory
Kernel panic - not syncing:Attempted to kill init!

Booting in linux rescue mode I get a screen full of garbage characters
and a "You have no linux partitions" error message and drops me to a
shell.  Running fdisk -l shows normal partitions for sdc.

I can mount the f7t4 partitions from centos 5 and all looks normal
AFAICT.

[root office bmcclure]# mount -t ext3 /dev/hda1 /mnt/fc7
[root office bmcclure]# ls -l /mnt/fc7
total 5894
-rw-r--r-- 1 root root   75847 Apr 21 21:34 config-2.6.20-1.3104.fc7
drwxr-xr-x 2 root root    1024 Apr 27 12:08 grub
-rw------- 1 root root 3029675 Apr 27 11:45 initrd-2.6.20-1.3104.fc7.img
drwx------ 2 root root   12288 Apr 27 06:33 lost+found
-rw-r--r-- 1 root root  929390 Apr 21 21:34 System.map-2.6.20-1.3104.fc7
-rw-r--r-- 1 root root 1951092 Apr 21 21:34 vmlinuz-2.6.20-1.3104.fc7
[root office bmcclure]# umount /dev/hda1
[root office bmcclure]# mount -t ext3 /dev/hda2 /mnt/fc7
[root office bmcclure]# ls -l /mnt/fc7
total 176
drwxr-xr-x   2 root root  4096 Apr 27 11:46 bin
drwxr-xr-x   2 root root  4096 Apr 27 06:35 boot
drwxr-xr-x   2 root root  4096 Apr 27 11:35 dev
drwxr-xr-x 102 root root 12288 Apr 27 11:51 etc
drwxr-xr-x   2 root root  4096 Apr 27 06:35 home
drwxr-xr-x  15 root root  4096 Apr 27 11:46 lib
drwx------   2 root root 16384 Apr 27 06:32 lost+found
drwxr-xr-x   2 root root  4096 Apr 17 07:46 media
drwxr-xr-x   2 root root  4096 Apr 17 07:46 mnt
drwxr-xr-x   2 root root  4096 Apr 17 07:46 opt
drwxr-xr-x   2 root root  4096 Apr 27 06:35 proc
drwxr-x---   2 root root  4096 Apr 27 11:51 root
drwxr-xr-x   2 root root 12288 Apr 27 11:46 sbin
drwxr-xr-x   2 root root  4096 Apr 27 11:35 selinux
drwxr-xr-x   3 root root  4096 Apr 27 11:45 srv
drwxr-xr-x   2 root root  4096 Apr 27 06:35 sys
drwxrwxrwt   2 root root  4096 Apr 27 11:51 tmp
drwxr-xr-x  13 root root  4096 Apr 27 11:40 usr
drwxr-xr-x  22 root root  4096 Apr 27 11:49 var

I have a feeling this is very simple but can't seem to put my finger on
it.  Any help much appreciated.

As an aside, I did an install on an old asus A7N8X wd pata drive and all
went well with no known issues.

Thanks agaain.
B.J.

CentOS 5.0, Linux 2.6.18-8.1.1.el5 x86_64 13:13:32 up 13 min, 1 user,
load average: 0.13, 0.14, 0.09


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]