DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've just compiled 188.8.131.52. It fails with the error below on boot:
/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.
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?
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)
Location: East Coast, USA (in "the great northeast")
Distribution: Custom / from source; Fedora, Debian, CentOS, Scientific; LFS.
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.