Kernel Panic + Intel SATA

Kernel Panic + Intel SATA

[Márcio Oliveira]

Hi there!

  I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel 
2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) and I 
am geting the following message when the computer boots:

Creating root device
mkrootdev: label / not found
Mounting root filesystem
mount: error 2 mouting ext3
Switchimg to new root
ERROR opening /dev/console!!!!: 2
switchroot: mount failed: 22
Kernel Panic - not syncing to kill init!

    I added the fdisk command to the initrd file and the init script 
executes it every boot to check if the kernel was recognizing the SATA 
disk. All partitions are listed in the boot process and the disk is 
recognized without problems, but the kernel still not able to mount the 
root partition:

scsi0: ata_piix
...
...
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0

Disk /dev/sda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
 
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1913    15361888+   7  HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2            6778        7296     4165560   12  Compaq diagnostics
Partition 2 does not end on cylinder boundary.
/dev/sda3            1914        1929      128520   83  Linux
/dev/sda4            1930        6777    38941560    5  Extended
/dev/sda5            1930        2843     7341673+  8e  Linux LVM
/dev/sda6            2844        3235     3148708+  83  Linux
/dev/sda7            3236        6777    28451083+   b  W95 FAT32
 
Partition table entries are not in disk order

   I also checked the initrd file and all seems ok.
   Thinks I made:

- compiled the kernel with ext3 modular support;
- compiled the kernel with ext3 built-in support;
- checked the modules loaded in the initrd;
- rebuilded and customized the initrd;
- checked if the SATA controller is recognized at boot time;
- tested fstab with and without "LABEL" partition name.

Any idea?

   Related Files:

/etc/fstab:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/sda6                 /                       ext3    
defaults        1 1
#LABEL=/                 /                       ext3    defaults        1 1
#LABEL=/boot             /boot                   ext3    defaults        1 2
/dev/sda3             /boot                   ext3    defaults        1 2
/dev/devpts             /dev/pts                devpts  gid=5,mode=620  0 0
/dev/shm                /dev/shm                tmpfs   defaults        0 0
/dev/proc               /proc                   proc    defaults        0 0
/dev/sys                /sys                    sysfs   defaults        0 0
/dev/VG00/usr           /usr                    ext3    defaults        1 2
/dev/VG00/var           /var                    ext3    defaults        1 2
/dev/VG00/swap          swap                    swap    defaults        0 0
/dev/sda7               /mnt/windows            vfat    user,defaults   0 0
/dev/hdc                /media/cdrecorder       auto    
pamconsole,exec,noauto,managed 0 0

/boot/grub/menu.lst

title Fedora Core (2.6.13-4)
        root (hd0,2)
        kernel /vmlinuz-2.6.13.4-ext3 ro root=LABEL=/ hda=noprobe 1
        initrd /initrd-2.6.13.4-ext3.img

*** I tested the root=LABEL=/ and root=/dev/sda6 kernel comand options.

Initrd file contents:

./sbin
./loopfs
./proc
./init
./sysroot
./bin
./bin/hotplug
./bin/nash
./bin/udev
./bin/fdisk
./bin/insmod
./bin/udevstart
./bin/modprobe
./dev
./dev/tty3
./dev/tty4
./dev/tty1
./dev/console
./dev/tty2
./dev/null
./dev/ram
./dev/systty
./sys
./lib
./lib/libc.so.6
./lib/ld-2.3.5.so
./lib/scsi_mod.ko
./lib/ld-linux.so.2
./lib/sd_mod.ko
./lib/libc-2.3.5.so
./lib/dm-mod.ko
./lib/ata_piix.ko
./lib/libata.ko
./etc
./etc/udev
./etc/udev/udev.conf

/init initrd file:

#!/bin/nash
mount -t proc /proc /proc
setquiet
echo Mounted /proc filesystem
echo Mounting sysfs
mount -t sysfs /sys /sys
echo Creating /dev
mount -o mode=0755 -t tmpfs /dev /dev
mknod /dev/console c 5 1
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mkdir /dev/pts
mkdir /dev/shm
echo Starting udev
/sbin/udevstart
echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
echo "Loading scsi_mod.ko module"
insmod /lib/scsi_mod.ko
echo "Loading sd_mod.ko module"
insmod /lib/sd_mod.ko
echo "Loading libata.ko module"
insmod /lib/libata.ko
echo "Loading ata_piix.ko module"
insmod /lib/ata_piix.ko
echo "Loading dm-mod.ko module"
insmod /lib/dm-mod.ko
sleep 10
/sbin/fdisk -l
sleep 10
/sbin/udevstart
echo Creating root device
mkrootdev /dev/root
echo Mounting root filesystem
mount -o defaults --ro -t ext3 /dev/root /sysroot
echo Switching to new root
switchroot --movedev /sysroot

Re: Kernel Panic + Intel SATA

[linux-os (Dick Johnson)]

On Wed, 26 Oct 2005, [iso-8859-1] Márcio Oliveira wrote:

> Hi there!
>
>  I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel
> 2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) and I
> am geting the following message when the computer boots:
>
> Creating root device
> mkrootdev: label / not found

This label was no good it needs to be /dev/sda6 from your fstab
You will need to put the device name in /boot/*/*.conf lilo or
grub instead on "label"

> Mounting root filesystem
> mount: error 2 mouting ext3

Error 2 == ENOENT


> Switchimg to new root
> ERROR opening /dev/console!!!!: 2
> switchroot: mount failed: 22

Error 22 = EINVAL

> Kernel Panic - not syncing to kill init!
>
>    I added the fdisk command to the initrd file and the init script
> executes it every boot to check if the kernel was recognizing the SATA
> disk. All partitions are listed in the boot process and the disk is
> recognized without problems, but the kernel still not able to mount the
> root partition:
>
> scsi0: ata_piix
> ...
> ...
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>
> Disk /dev/sda: 60.0 GB, 60011642880 bytes
> 255 heads, 63 sectors/track, 7296 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>   Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1        1913    15361888+   7  HPFS/NTFS
> Partition 1 does not end on cylinder boundary.
> /dev/sda2            6778        7296     4165560   12  Compaq diagnostics
> Partition 2 does not end on cylinder boundary.
> /dev/sda3            1914        1929      128520   83  Linux
> /dev/sda4            1930        6777    38941560    5  Extended
> /dev/sda5            1930        2843     7341673+  8e  Linux LVM
> /dev/sda6            2844        3235     3148708+  83  Linux
> /dev/sda7            3236        6777    28451083+   b  W95 FAT32
>
> Partition table entries are not in disk order
>
>   I also checked the initrd file and all seems ok.
>   Thinks I made:
>
> - compiled the kernel with ext3 modular support;
> - compiled the kernel with ext3 built-in support;
> - checked the modules loaded in the initrd;
> - rebuilded and customized the initrd;
> - checked if the SATA controller is recognized at boot time;
> - tested fstab with and without "LABEL" partition name.
>
> Any idea?
>
>   Related Files:
>
> /etc/fstab:
>
> # This file is edited by fstab-sync - see 'man fstab-sync' for details
> /dev/sda6                 /                       ext3
> defaults        1 1
> #LABEL=/                 /                       ext3    defaults        1 1
> #LABEL=/boot             /boot                   ext3    defaults        1 2
> /dev/sda3             /boot                   ext3    defaults        1 2
> /dev/devpts             /dev/pts                devpts  gid=5,mode=620  0 0
> /dev/shm                /dev/shm                tmpfs   defaults        0 0
> /dev/proc               /proc                   proc    defaults        0 0
> /dev/sys                /sys                    sysfs   defaults        0 0
> /dev/VG00/usr           /usr                    ext3    defaults        1 2
> /dev/VG00/var           /var                    ext3    defaults        1 2
> /dev/VG00/swap          swap                    swap    defaults        0 0
> /dev/sda7               /mnt/windows            vfat    user,defaults   0 0
> /dev/hdc                /media/cdrecorder       auto
> pamconsole,exec,noauto,managed 0 0
>
> /boot/grub/menu.lst
>
> title Fedora Core (2.6.13-4)
>        root (hd0,2)
>        kernel /vmlinuz-2.6.13.4-ext3 ro root=LABEL=/ hda=noprobe 1
>        initrd /initrd-2.6.13.4-ext3.img
>
> *** I tested the root=LABEL=/ and root=/dev/sda6 kernel comand options.
>
> Initrd file contents:
>
> ./sbin
> ./loopfs
> ./proc
> ./init
> ./sysroot
> ./bin
> ./bin/hotplug
> ./bin/nash
> ./bin/udev
> ./bin/fdisk
> ./bin/insmod
> ./bin/udevstart
> ./bin/modprobe
> ./dev
> ./dev/tty3
> ./dev/tty4
> ./dev/tty1
> ./dev/console
> ./dev/tty2
> ./dev/null
> ./dev/ram
> ./dev/systty
> ./sys
> ./lib
> ./lib/libc.so.6
> ./lib/ld-2.3.5.so
> ./lib/scsi_mod.ko
> ./lib/ld-linux.so.2
> ./lib/sd_mod.ko
> ./lib/libc-2.3.5.so
> ./lib/dm-mod.ko
> ./lib/ata_piix.ko
> ./lib/libata.ko
> ./etc
> ./etc/udev
> ./etc/udev/udev.conf
>
> /init initrd file:
>
> #!/bin/nash
> mount -t proc /proc /proc
> setquiet
> echo Mounted /proc filesystem
> echo Mounting sysfs
> mount -t sysfs /sys /sys
> echo Creating /dev
> mount -o mode=0755 -t tmpfs /dev /dev
> mknod /dev/console c 5 1
> mknod /dev/null c 1 3
> mknod /dev/zero c 1 5
> mkdir /dev/pts
> mkdir /dev/shm
> echo Starting udev
> /sbin/udevstart
> echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
> echo "Loading scsi_mod.ko module"
> insmod /lib/scsi_mod.ko
> echo "Loading sd_mod.ko module"
> insmod /lib/sd_mod.ko
> echo "Loading libata.ko module"
> insmod /lib/libata.ko
> echo "Loading ata_piix.ko module"
> insmod /lib/ata_piix.ko
> echo "Loading dm-mod.ko module"
> insmod /lib/dm-mod.ko
> sleep 10
> /sbin/fdisk -l
> sleep 10
> /sbin/udevstart
> echo Creating root device
> mkrootdev /dev/root
> echo Mounting root filesystem
> mount -o defaults --ro -t ext3 /dev/root /sysroot
> echo Switching to new root
> switchroot --movedev /sysroot
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips).
Warning : 98.36% of all statistics are fiction.

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: Kernel Panic + Intel SATA

[Jeff Garzik]

Márcio Oliveira wrote:
> Hi there!
> 
>  I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel 
> 2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) and I 
> am geting the following message when the computer boots:

Can you try 2.6.14-rc5?

	Jeff

Re: Kernel Panic + Intel SATA

[Marcio Oliveira]

yes, I can. But, is there any modification in the 2.6.14-rc5 kernel 
version that will help in this issue?
thank you Jeff.
marcio.

> Jeff Garzik writes:
>
>> Márcio Oliveira wrote:
>>
>>> Hi there!
>>>  I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel 
>>> 2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) 
>>> and I am geting the following message when the computer boots:
>>
>>
>> Can you try 2.6.14-rc5?
>>     Jeff
>>  
>>
>
>

Re: Kernel Panic + Intel SATA

[Marcio Oliveira]

yes, I can. But, is there any modification in the 2.6.14-rc5 kernel 
version that will help in this issue?
thank you Jeff.
marcio.

>> Jeff Garzik writes:
>>
>>> Márcio Oliveira wrote:
>>>
>>>> Hi there!
>>>>  I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel 
>>>> 2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) 
>>>> and I am geting the following message when the computer boots:
>>>
>>>
>>>
>>> Can you try 2.6.14-rc5?
>>>     Jeff
>>>  
>>>
>>
>>
>
>

Re: Kernel Panic + Intel SATA

[Marcio Oliveira]

linux-os (Dick Johnson) wrote:

>On Wed, 26 Oct 2005, [iso-8859-1] Márcio Oliveira wrote:
>
>  
>
>>Hi there!
>>
>> I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel
>>2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) and I
>>am geting the following message when the computer boots:
>>
>>Creating root device
>>mkrootdev: label / not found
>>    
>>
>
>This label was no good it needs to be /dev/sda6 from your fstab
>You will need to put the device name in /boot/*/*.conf lilo or
>grub instead on "label"
>  
>
yeah, I try to boot it using "root=/dev/sda6" instead "root=LABEL=/" 
parameter, but the system still not booting...

>  
>
>>Mounting root filesystem
>>mount: error 2 mouting ext3
>>    
>>
>
>Error 2 == ENOENT
>  
>

ENOENT? What it means?

>  
>
>>Switchimg to new root
>>ERROR opening /dev/console!!!!: 2
>>switchroot: mount failed: 22
>>    
>>
>
>Error 22 = EINVAL
>  
>

EINVAL? What it means?

>  
>
>>Kernel Panic - not syncing to kill init!
>>
>>   I added the fdisk command to the initrd file and the init script
>>executes it every boot to check if the kernel was recognizing the SATA
>>disk. All partitions are listed in the boot process and the disk is
>>recognized without problems, but the kernel still not able to mount the
>>root partition:
>>
>>scsi0: ata_piix
>>...
>>...
>>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>>
>>Disk /dev/sda: 60.0 GB, 60011642880 bytes
>>255 heads, 63 sectors/track, 7296 cylinders
>>Units = cylinders of 16065 * 512 = 8225280 bytes
>>
>>  Device Boot      Start         End      Blocks   Id  System
>>/dev/sda1   *           1        1913    15361888+   7  HPFS/NTFS
>>Partition 1 does not end on cylinder boundary.
>>/dev/sda2            6778        7296     4165560   12  Compaq diagnostics
>>Partition 2 does not end on cylinder boundary.
>>/dev/sda3            1914        1929      128520   83  Linux
>>/dev/sda4            1930        6777    38941560    5  Extended
>>/dev/sda5            1930        2843     7341673+  8e  Linux LVM
>>/dev/sda6            2844        3235     3148708+  83  Linux
>>/dev/sda7            3236        6777    28451083+   b  W95 FAT32
>>
>>Partition table entries are not in disk order
>>
>>  I also checked the initrd file and all seems ok.
>>  Thinks I made:
>>
>>- compiled the kernel with ext3 modular support;
>>- compiled the kernel with ext3 built-in support;
>>- checked the modules loaded in the initrd;
>>- rebuilded and customized the initrd;
>>- checked if the SATA controller is recognized at boot time;
>>- tested fstab with and without "LABEL" partition name.
>>
>>Any idea?
>>
>>  Related Files:
>>
>>/etc/fstab:
>>
>># This file is edited by fstab-sync - see 'man fstab-sync' for details
>>/dev/sda6                 /                       ext3
>>defaults        1 1
>>#LABEL=/                 /                       ext3    defaults        1 1
>>#LABEL=/boot             /boot                   ext3    defaults        1 2
>>/dev/sda3             /boot                   ext3    defaults        1 2
>>/dev/devpts             /dev/pts                devpts  gid=5,mode=620  0 0
>>/dev/shm                /dev/shm                tmpfs   defaults        0 0
>>/dev/proc               /proc                   proc    defaults        0 0
>>/dev/sys                /sys                    sysfs   defaults        0 0
>>/dev/VG00/usr           /usr                    ext3    defaults        1 2
>>/dev/VG00/var           /var                    ext3    defaults        1 2
>>/dev/VG00/swap          swap                    swap    defaults        0 0
>>/dev/sda7               /mnt/windows            vfat    user,defaults   0 0
>>/dev/hdc                /media/cdrecorder       auto
>>pamconsole,exec,noauto,managed 0 0
>>
>>/boot/grub/menu.lst
>>
>>title Fedora Core (2.6.13-4)
>>       root (hd0,2)
>>       kernel /vmlinuz-2.6.13.4-ext3 ro root=LABEL=/ hda=noprobe 1
>>       initrd /initrd-2.6.13.4-ext3.img
>>
>>*** I tested the root=LABEL=/ and root=/dev/sda6 kernel comand options.
>>
>>Initrd file contents:
>>
>>./sbin
>>./loopfs
>>./proc
>>./init
>>./sysroot
>>./bin
>>./bin/hotplug
>>./bin/nash
>>./bin/udev
>>./bin/fdisk
>>./bin/insmod
>>./bin/udevstart
>>./bin/modprobe
>>./dev
>>./dev/tty3
>>./dev/tty4
>>./dev/tty1
>>./dev/console
>>./dev/tty2
>>./dev/null
>>./dev/ram
>>./dev/systty
>>./sys
>>./lib
>>./lib/libc.so.6
>>./lib/ld-2.3.5.so
>>./lib/scsi_mod.ko
>>./lib/ld-linux.so.2
>>./lib/sd_mod.ko
>>./lib/libc-2.3.5.so
>>./lib/dm-mod.ko
>>./lib/ata_piix.ko
>>./lib/libata.ko
>>./etc
>>./etc/udev
>>./etc/udev/udev.conf
>>
>>/init initrd file:
>>
>>#!/bin/nash
>>mount -t proc /proc /proc
>>setquiet
>>echo Mounted /proc filesystem
>>echo Mounting sysfs
>>mount -t sysfs /sys /sys
>>echo Creating /dev
>>mount -o mode=0755 -t tmpfs /dev /dev
>>mknod /dev/console c 5 1
>>mknod /dev/null c 1 3
>>mknod /dev/zero c 1 5
>>mkdir /dev/pts
>>mkdir /dev/shm
>>echo Starting udev
>>/sbin/udevstart
>>echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
>>echo "Loading scsi_mod.ko module"
>>insmod /lib/scsi_mod.ko
>>echo "Loading sd_mod.ko module"
>>insmod /lib/sd_mod.ko
>>echo "Loading libata.ko module"
>>insmod /lib/libata.ko
>>echo "Loading ata_piix.ko module"
>>insmod /lib/ata_piix.ko
>>echo "Loading dm-mod.ko module"
>>insmod /lib/dm-mod.ko
>>sleep 10
>>/sbin/fdisk -l
>>sleep 10
>>/sbin/udevstart
>>echo Creating root device
>>mkrootdev /dev/root
>>echo Mounting root filesystem
>>mount -o defaults --ro -t ext3 /dev/root /sysroot
>>echo Switching to new root
>>switchroot --movedev /sysroot
>>
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at  http://www.tux.org/lkml/
>>
>>    
>>
>
>Cheers,
>Dick Johnson
>Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips).
>Warning : 98.36% of all statistics are fiction.
>
>****************************************************************
>The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>
>Thank you.
>  
>
   This is very strange, at the boot time the system can show the disk 
partitions as I said, but cannot  mount it. I tryed to compile the 
following kernel versions: 2.6.12 (kernel.org), 2.6.11 (fedora core 4), 
2.6.12 (fedora core 4) and 2.6.13 (fedora core 4) and all of it shows 
the error message when the system is trying to mount the root partition 
at boot time. Any more idea about what should I do?

Thanks.
Marcio Oliveira.

Re: Kernel Panic + Intel SATA

[linux-os (Dick Johnson)]

On Wed, 26 Oct 2005, Marcio Oliveira wrote:

> linux-os (Dick Johnson) wrote:
>
>> On Wed, 26 Oct 2005, [iso-8859-1] Márcio Oliveira wrote:
>>
>>
>>
>>> Hi there!
>>>
>>> I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel
>>> 2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) and I
>>> am geting the following message when the computer boots:
>>>
>>> Creating root device
>>> mkrootdev: label / not found
>>>
>>>
>>
>> This label was no good it needs to be /dev/sda6 from your fstab
>> You will need to put the device name in /boot/*/*.conf lilo or
>> grub instead on "label"
>>
>>
> yeah, I try to boot it using "root=/dev/sda6" instead "root=LABEL=/"
> parameter, but the system still not booting...
>
>>
>>
>>> Mounting root filesystem
>>> mount: error 2 mouting ext3
>>>
>>>
>>
>> Error 2 == ENOENT
>>
>>
>
> ENOENT? What it means?

Was 'no such file', perhaps the device file was not created by `mkrootdev`
because it errored out???

This is all 'Fedora' stuff, not Linux stuff. You should upgrade
your 'mkinitrd' (or rewrite it) so it doesn't use Fedora-specific
stuff if you intend to install an un-patched kernel.


>
>>
>>
>>> Switchimg to new root
>>> ERROR opening /dev/console!!!!: 2
>>> switchroot: mount failed: 22
>>>
>>>
>>
>> Error 22 = EINVAL
>>
>>
>
> EINVAL? What it means?
>

Means 'wrong value'. Probably because the new root wasn't
mounted.

[SNIPPED...]


In the meantime do:

mknod /dev/sda6 b 8 6
mknod /dev/root b 8 6

.. in your initrd script. This should get you past the errors.


>>> mount -o mode=0755 -t tmpfs /dev /dev
>>> mknod /dev/console c 5 1
>>> mknod /dev/null c 1 3
>>> mknod /dev/zero c 1 5
>>> mkdir /dev/pts
>>> mkdir /dev/shm
>>> echo Starting udev
>>> /sbin/udevstart
>>> echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
>>> echo "Loading scsi_mod.ko module"
>>> insmod /lib/scsi_mod.ko
>>> echo "Loading sd_mod.ko module"
>>> insmod /lib/sd_mod.ko
>>> echo "Loading libata.ko module"
>>> insmod /lib/libata.ko
>>> echo "Loading ata_piix.ko module"
>>> insmod /lib/ata_piix.ko
>>> echo "Loading dm-mod.ko module"
>>> insmod /lib/dm-mod.ko
>>> sleep 10
>>> /sbin/fdisk -l
>>> sleep 10
>>> /sbin/udevstart
>>> echo Creating root device
>>> mkrootdev /dev/root
>>> echo Mounting root filesystem
>>> mount -o defaults --ro -t ext3 /dev/root /sysroot
>>> echo Switching to new root
>>> switchroot --movedev /sysroot

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips).
Warning : 98.36% of all statistics are fiction.

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: Kernel Panic + Intel SATA

[Alan Cox]

On Iau, 2005-10-27 at 08:49 -0400, linux-os (Dick Johnson) wrote:
> This is all 'Fedora' stuff, not Linux stuff. You should upgrade
> your 'mkinitrd' (or rewrite it) so it doesn't use Fedora-specific
> stuff if you intend to install an un-patched kernel.

Fedora is quite happy with an unpatched kernel, that is generally what I
am running for development on Fedora.

If you are using LVM2 or MD you just need to be sure you have the right
config options enabled (the Red Hat src.rpm is a good guide).

Alan

Re: Kernel Panic + Intel SATA

[Márcio Oliveira]

Alan Cox wrote:

>On Iau, 2005-10-27 at 08:49 -0400, linux-os (Dick Johnson) wrote:
>  
>
>>This is all 'Fedora' stuff, not Linux stuff. You should upgrade
>>your 'mkinitrd' (or rewrite it) so it doesn't use Fedora-specific
>>stuff if you intend to install an un-patched kernel.
>>    
>>
>
>Fedora is quite happy with an unpatched kernel, that is generally what I
>am running for development on Fedora.
>  
>
When I copiled the src fedora core 4 kernel 
(kernel-2.6.12-1.1456_FC4.src.rpm and kernel-2.6.13-1.1526_FC4.src.rpm), 
I got the same error messages.

>If you are using LVM2 or MD you just need to be sure you have the right
>config options enabled (the Red Hat src.rpm is a good guide).
>
>Alan
>  
>
I'm not using lvm or raid in the /root or the /boot partition. All 
partitions was made directly in the disk and formated with ext3 file 
system. I think all needed options was compiled in the new kernel, since 
I copied the /boot/config-2.6.12-1.1456_FC4 (config file from the kernel 
that works fine) and compiled the kernel.src.rpm without any 
modifications in the config file, and it still not working.

Any more ideas?

Thank you Alan.
Márcio Oliveira.

Re: Kernel Panic + Intel SATA

[Márcio Oliveira]

linux-os (Dick Johnson) wrote:

>On Wed, 26 Oct 2005, Marcio Oliveira wrote:
>
>  
>
>>linux-os (Dick Johnson) wrote:
>>
>>    
>>
>>>On Wed, 26 Oct 2005, [iso-8859-1] Márcio Oliveira wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>Hi there!
>>>>
>>>>I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel
>>>>2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) and I
>>>>am geting the following message when the computer boots:
>>>>
>>>>Creating root device
>>>>mkrootdev: label / not found
>>>>
>>>>
>>>>        
>>>>
>>>This label was no good it needs to be /dev/sda6 from your fstab
>>>You will need to put the device name in /boot/*/*.conf lilo or
>>>grub instead on "label"
>>>
>>>
>>>      
>>>
>>yeah, I try to boot it using "root=/dev/sda6" instead "root=LABEL=/"
>>parameter, but the system still not booting...
>>
>>    
>>
>>>      
>>>
>>>>Mounting root filesystem
>>>>mount: error 2 mouting ext3
>>>>
>>>>
>>>>        
>>>>
>>>Error 2 == ENOENT
>>>
>>>
>>>      
>>>
>>ENOENT? What it means?
>>    
>>
>
>Was 'no such file', perhaps the device file was not created by `mkrootdev`
>because it errored out???
>
>This is all 'Fedora' stuff, not Linux stuff. You should upgrade
>your 'mkinitrd' (or rewrite it) so it doesn't use Fedora-specific
>stuff if you intend to install an un-patched kernel.
>  
>
Dick, sorry about my newbie question: where can I find a mkinitrd source 
code to compile in my system?

>
>  
>
>>>      
>>>
>>>>Switchimg to new root
>>>>ERROR opening /dev/console!!!!: 2
>>>>switchroot: mount failed: 22
>>>>
>>>>
>>>>        
>>>>
>>>Error 22 = EINVAL
>>>
>>>
>>>      
>>>
>>EINVAL? What it means?
>>
>>    
>>
>
>Means 'wrong value'. Probably because the new root wasn't
>mounted.
>
>[SNIPPED...]
>
>
>In the meantime do:
>
>mknod /dev/sda6 b 8 6
>mknod /dev/root b 8 6
>
>.. in your initrd script. This should get you past the errors.
>  
>
I made the changes you suggest in the initrd script and it was not able 
to create the necessary devices at boot time...
In the meantime I also installed a new mkinitrd (from fedora devel, 
version 5.0.8-1), but it still not working...

Any more ideas? When can I get the mkinitrd source code?

thanks Dick.
Márcio Oliveira

>
>  
>
>>>>mount -o mode=0755 -t tmpfs /dev /dev
>>>>mknod /dev/console c 5 1
>>>>mknod /dev/null c 1 3
>>>>mknod /dev/zero c 1 5
>>>>mkdir /dev/pts
>>>>mkdir /dev/shm
>>>>echo Starting udev
>>>>/sbin/udevstart
>>>>echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
>>>>echo "Loading scsi_mod.ko module"
>>>>insmod /lib/scsi_mod.ko
>>>>echo "Loading sd_mod.ko module"
>>>>insmod /lib/sd_mod.ko
>>>>echo "Loading libata.ko module"
>>>>insmod /lib/libata.ko
>>>>echo "Loading ata_piix.ko module"
>>>>insmod /lib/ata_piix.ko
>>>>echo "Loading dm-mod.ko module"
>>>>insmod /lib/dm-mod.ko
>>>>sleep 10
>>>>/sbin/fdisk -l
>>>>sleep 10
>>>>/sbin/udevstart
>>>>echo Creating root device
>>>>mkrootdev /dev/root
>>>>echo Mounting root filesystem
>>>>mount -o defaults --ro -t ext3 /dev/root /sysroot
>>>>echo Switching to new root
>>>>switchroot --movedev /sysroot
>>>>        
>>>>
>
>Cheers,
>Dick Johnson
>Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips).
>Warning : 98.36% of all statistics are fiction.
>
>****************************************************************
>The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>
>Thank you.
>  
>

Re: Kernel Panic + Intel SATA

[linux-os (Dick Johnson)]

On Thu, 27 Oct 2005, [iso-8859-1] Márcio Oliveira wrote:

> linux-os (Dick Johnson) wrote:
>
>> On Wed, 26 Oct 2005, Marcio Oliveira wrote:
>>
>>
>>
>>> linux-os (Dick Johnson) wrote:
>>>
>>>
>>>
>>>> On Wed, 26 Oct 2005, [iso-8859-1] Márcio Oliveira wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hi there!
>>>>>
>>>>> I have a IBM ThinkPad t43 running Fedora Core  Linux 4 and kernel
>>>>> 2.6.12-1.146_FC4. I recompiled the kernel (2.6.13.4 - kernel.org) and I
>>>>> am geting the following message when the computer boots:
>>>>>
>>>>> Creating root device
>>>>> mkrootdev: label / not found
>>>>>
>>>>>
>>>>>
>>>>>
>>>> This label was no good it needs to be /dev/sda6 from your fstab
>>>> You will need to put the device name in /boot/*/*.conf lilo or
>>>> grub instead on "label"
>>>>
>>>>
>>>>
>>>>
>>> yeah, I try to boot it using "root=/dev/sda6" instead "root=LABEL=/"
>>> parameter, but the system still not booting...
>>>
>>>
>>>
>>>>
>>>>
>>>>> Mounting root filesystem
>>>>> mount: error 2 mouting ext3
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Error 2 == ENOENT
>>>>
>>>>
>>>>
>>>>
>>> ENOENT? What it means?
>>>
>>>
>>
>> Was 'no such file', perhaps the device file was not created by `mkrootdev`
>> because it errored out???
>>
>> This is all 'Fedora' stuff, not Linux stuff. You should upgrade
>> your 'mkinitrd' (or rewrite it) so it doesn't use Fedora-specific
>> stuff if you intend to install an un-patched kernel.
>>
>>
> Dick, sorry about my newbie question: where can I find a mkinitrd source
> code to compile in my system?
>

Fedora Development.

>>
>>
>>
>>>>
>>>>
>>>>> Switchimg to new root
>>>>> ERROR opening /dev/console!!!!: 2
>>>>> switchroot: mount failed: 22
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Error 22 = EINVAL
>>>>
>>>>
>>>>
>>>>
>>> EINVAL? What it means?
>>>
>>>
>>>
>>
>> Means 'wrong value'. Probably because the new root wasn't
>> mounted.
>>
>> [SNIPPED...]
>>
>>
>> In the meantime do:
>>
>> mknod /dev/sda6 b 8 6
>> mknod /dev/root b 8 6
>>
>> .. in your initrd script. This should get you past the errors.
>>
>>
> I made the changes you suggest in the initrd script and it was not able
> to create the necessary devices at boot time...
> In the meantime I also installed a new mkinitrd (from fedora devel,
> version 5.0.8-1), but it still not working...
>
> Any more ideas? When can I get the mkinitrd source code?
>

Fedora development.

Also, do what Alan said. You need to enable something (don't remember
what) when you compile the kernel. That lets the Fedora stuff work.

> thanks Dick.
> Márcio Oliveira
>
>>
>>
>>
>>>>> mount -o mode=0755 -t tmpfs /dev /dev
>>>>> mknod /dev/console c 5 1
>>>>> mknod /dev/null c 1 3
>>>>> mknod /dev/zero c 1 5
>>>>> mkdir /dev/pts
>>>>> mkdir /dev/shm
>>>>> echo Starting udev
>>>>> /sbin/udevstart
>>>>> echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
>>>>> echo "Loading scsi_mod.ko module"
>>>>> insmod /lib/scsi_mod.ko
>>>>> echo "Loading sd_mod.ko module"
>>>>> insmod /lib/sd_mod.ko
>>>>> echo "Loading libata.ko module"
>>>>> insmod /lib/libata.ko
>>>>> echo "Loading ata_piix.ko module"
>>>>> insmod /lib/ata_piix.ko
>>>>> echo "Loading dm-mod.ko module"
>>>>> insmod /lib/dm-mod.ko
>>>>> sleep 10
>>>>> /sbin/fdisk -l
>>>>> sleep 10
>>>>> /sbin/udevstart
>>>>> echo Creating root device
>>>>> mkrootdev /dev/root
>>>>> echo Mounting root filesystem
>>>>> mount -o defaults --ro -t ext3 /dev/root /sysroot
>>>>> echo Switching to new root
>>>>> switchroot --movedev /sysroot
>>>>>
>>>>>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips).
Warning : 98.36% of all statistics are fiction.

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

Re: Kernel Panic + Intel SATA

[Alan Cox]

> >If you are using LVM2 or MD you just need to be sure you have the right
> >config options enabled (the Red Hat src.rpm is a good guide).
> >
> >Alan
> >  
> >
> I'm not using lvm or raid in the /root or the /boot partition. All 
> partitions was made directly in the disk and formated with ext3 file 
> system. I think all needed options was compiled in the new kernel, since 
> I copied the /boot/config-2.6.12-1.1456_FC4 (config file from the kernel 
> that works fine) and compiled the kernel.src.rpm without any 
> modifications in the config file, and it still not working.

You also created a new initrd with mkinitrd ?

Re: Kernel Panic + Intel SATA

[Márcio Oliveira]

Alan Cox wrote:

>>>If you are using LVM2 or MD you just need to be sure you have the right
>>>config options enabled (the Red Hat src.rpm is a good guide).
>>>
>>>Alan
>>> 
>>>
>>>      
>>>
>>I'm not using lvm or raid in the /root or the /boot partition. All 
>>partitions was made directly in the disk and formated with ext3 file 
>>system. I think all needed options was compiled in the new kernel, since 
>>I copied the /boot/config-2.6.12-1.1456_FC4 (config file from the kernel 
>>that works fine) and compiled the kernel.src.rpm without any 
>>modifications in the config file, and it still not working.
>>    
>>
>
>You also created a new initrd with mkinitrd ?
>  
>
Yes, I created it. I also extracted the initrd image and compared it 
with a initrd that works fine (the initrd-2.6.12-1.1456_FC4.img initrd 
image provided by the kernel-2.6.12-1.1456_FC4.i386.rpm kernel package) 
and the images have the same files.

I got the mkinitrd-5.0.8-1 package and the 
kernel-devel-2.6.12-1.1456_FC4.i686.rpm package too. I compiled the 
mkinitrd package with the command:

# rpmbuild --rebuild mkinitrd-5.0.8-1.src.rpm
# rpm -ivh /usr/src/redhat/RPMS/i386/mkinitrd-5.0.8-1.i386.rpm

I also changed parameters in the kernel.spec file and recompiled it. The 
parameters was changed from:

%define buildsmp 1
...
%patch800 -p1

To:

%define buildsmp 0
...
# %patch800 -p1

(the nonint patch was generating error messages during the kernel rpm 
compilation)

# rpmbuild --target i686 -ba /usr/src/redhat/SPECS/kernel.spec
# rpm -ivh /usr/src/redhat/RPMS/i686/kernel-2.6.12.ext3-2.i686.rpm

After I finished the process, I booted the machine and got the same 
error message. I also rebuilt the initrd image and built a new 2.6.13 
fedora core src.rpm kernel, but it still not working... any more idea??

Thank you.

Márcio.