Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey,
I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site.
Now I tried to boot it, I ended up failing with this message:
Code:
Waiting 10 seconds for device /dev/sda1 ...
Root device '/dev/sda1' doesn't exist, Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/sda1'
Here is the important part of my menu.lst:
Code:
# Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/somelongid ro
initrd /kernel26.img
# my one
title mine
root (hd0,0)
kernel /vmlinuz root=/dev/sda1 ro
initrd /initrd.img
Note that on my first try, I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name
Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
Code:
[ 1.xx (kerneltime I guess)] VFS: Cannot open root device 'disk/by-uuid/blabla' or unknown-block(0,0)
[ 1.xx ] Please append a correct "root=" boot option; here are the available partitions:
[ 1.xx ] 0b00 1048575 sr0 driver:sr
[ 1.xx ] ekrnel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I am using a 2.6.38 Kernel running on VirtualBox, using ArchLinux with LXDE
What do you mean with more than one drive attached? I only got one harddrive, which was formatted during Arch installation int a /root, a swap and a rest partition.
No USB or CD media are in there.
What do you mean with more than one drive attached? I only got one harddrive, which was formatted during Arch installation int a /root, a swap and a rest partition.
No USB or CD media are in there.
I created initrd using
sudo mkinitcpio -k 2.6.22 -g /boot/initrd.img
The update to glibc-2.12.2-1 increases the minimum required kernel version to 2.6.27. This kernel version was chosen as it is currently the oldest kernel with longterm support upstream. Users of the Arch "kernel26" and "kernel26-lts" packages are unaffected by this change.
Those wanting to continue the use of an older kernel version will be required to rebuild the glibc package with the appropriate adjustment made to the "--enable-kernel" configuration option.
I got the source from kernel.org - it's stable and mainline.
I choose this way without PKGBuild b/c I want to work within the kernel (i.e. code new modules) and I wasn't sure whether I had to compile the whole kernel using PGKBUILD when I just made small changes.
Whenever I have encountered this situation, I've mis-configured the kernel either by not adding support for the drive or the file system that's on it. I recommend passing your hard drive manufacturer through `grep` on the kernel .config file. Alternatively, you could unpack the kernel source, if you haven't kept it around, copy the .config file to the tree and run `make {x,menu,old}config` and visually inspect all of these areas.
Looks like your boot commands should work, although I think you're using Lilo and that has been a long time for me. The "kernel panic" got my attention.
You could also search through the Linux From Scratch archives. There's been some discussion in the last few months about problems using Virtual Box. Since you're running Archlinux, you may also want to try the CLFS archives.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.