Re: Kernel Panic + Intel SATA

From: linux-os (Dick Johnson)
Date: Thu Oct 27 2005 - 10:21:09 EST



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@xxxxxxxxxxxx - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/