Kernel compile gone wrong

Jongi · 09-30-2007, 04:20 PM

I've just compiled 2.6.22.7. It fails with the error below on boot:

Code:

/bin/cat: : No such file or directory
Device /sys/block/hdd/hdd8/dev seems to be down
/bin/mknod: missing operand after 'b'
Special files require major and minor device numbers.
Try '/bin/mknod --help' for more information
mount: special device /dev/hdd8 does not exist
Switching root ...
/usr/lib/yaird/exec/run_init: current directory on the same filesystem as root: Success
Kernel panic - not syncing: Attempted to kill init

Is this the hdx to sdx filesystem change? Something else?

The system is lenny/sid and /dev/hdd8 is the root filesystem (on the 2.6.21 and prior kernels I have). I've used the same method of compiling I always have. And as per usual I use the config-2.6.18 file to base the compile on.

Jongi · 10-01-2007, 03:20 PM

Rather than open a new thread I thought I'd tack this here. If I am busy compiling a kernel and the power goes off. If I restart and start to compile, does it start from scratch or where it was when it was interrupted?

raskin · 10-01-2007, 03:56 PM

Probably yes, it is hdx->sdx. So you need at least to adjust you root= in kernel parameters and fstab. And if kernel build is interrupted it will lose some amount of work, but generally it will compile only the parts it hasn't compiled before crash. There are some chances to get defective kernel, though - if some file was not completely sync'ed to disk (unlikely, but it happens sometimes - though very rarely)

Jongi · 10-01-2007, 06:02 PM

Changed references in fstab to reflect the drives as sdx (got this from my FC7 install which has all the drives in sdx format). Still got the same error.

EDIT: Is there something in /var/log I can provide?

raskin · 10-01-2007, 10:52 PM

And what did you do with initrd?

Jongi · 10-02-2007, 10:52 AM

can you be a bit more specific with your question about initrd?

raskin · 10-02-2007, 11:14 AM

What does you bootloader config now say about initrd? Is it the same initrd as it was for the previous kernel?

Jongi · 10-02-2007, 11:23 AM

I use yaird (mkinitrd.yaird iirc). Is that what you are asking?

EDIT:

Code:

[root:/usr/src#] dpkg -i linux-image-2.6.22.7_jng5_i386.deb linux-headers-2.6.22.7_jng5_i386.deb 
Selecting previously deselected package linux-image-2.6.22.7. 
(Reading database ... 157070 files and directories currently installed.) 
Unpacking linux-image-2.6.22.7 (from linux-image-2.6.22.7_jng5_i386.deb) ... 
Done. 
Selecting previously deselected package linux-headers-2.6.22.7. 
Unpacking linux-headers-2.6.22.7 (from linux-headers-2.6.22.7_jng5_i386.deb) ... 
Setting up linux-image-2.6.22.7 (jng5) ... 
Running depmod. 
Finding valid ramdisk creators. 
Using /usr/sbin/mkinitrd.yaird to build the ramdisk. 
Running postinst hook script update-grub. 
Searching for GRUB installation directory ... found: /boot/grub 
Searching for default file ... found: /boot/grub/default 
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst 
Searching for splash image ... none found, skipping ... 
Found kernel: /boot/vmlinuz-2.6.22.7 
Found kernel: /boot/vmlinuz-2.6.21-2-686 
Found kernel: /boot/vmlinuz-2.6.18-4-686 
Updating /boot/grub/menu.lst ... done

2.6.21-2 and 2.6.18-4 are kernels got from repo

HowDoIProgramIt · 10-02-2007, 11:40 AM

Quote:

Originally Posted by Jongi

I use yaird (mkinitrd.yaird iirc). Is that what you are asking?

I think what he's saying is either (or both) "did you remember to fix all the other references you could potentially have in your boot sequence." / can initrd be found during the boot process - and/or - did you create an initrd that's appropriate for the new drive access scheme.

You're going to need drivers now that you didn't need when you were addressing the drives as IDE/ATA drivers. They have to be either compiled in to the kernel or added in to your initrd / initramfs. Your hardware didn't change physically, but the way you're accessing it did, so for all intents and purposes, it did change.

Hope that helps...

- Larry

Jongi · 10-02-2007, 01:24 PM

What would I need to change for the new drive access scheme to ensure that every thing is built in the proper way?

Jongi · 10-02-2007, 04:38 PM

http://forums.debian.net/viewtopic.p...8204ead927fd92

Looks like that's the issue. So I've changed my kernel-img.conf to look like this:

Code:

# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
ramdisk = /usr/sbin/mkinitrd /usr/sbin/mkinitramfs
postinst_hook = update-grub
postrm_hook   = update-grub
#ramdisk = /usr/sbin/mkinitrd.yaird

Hopefully this will work.

Jongi · 10-03-2007, 01:49 AM

Success !!!! \o/