You are not logged in.
Pages: 1
Hi there.
I'm performing a clean install in a desktop machine. I've managed to perform all steps in the menu but the "#7 Install bootloader"... After choosing grub, I've changed /mnt/boot/grub/menu.lst to the following:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/c4ea7498-b80a-4348-bb61-16583c6e9ae1 ro
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/c4ea7498-b80a-4348-bb61-16583c6e9ae1 ro
initrd /kernel26-fallback.img
My /boot partition is /dev/sda1.
After saving the file, the "boot device selection" menu is displayed. I'm choosing /dev/sda and two error messages are shown:
Error: Missing/Invalid root device:
Grub was NOT successfully installed.
Could you please help me? Thanks in advance.
Last edited by gandulfo (2009-11-08 19:05:51)
Offline
Well, if /boot is /dev/sda1 I'm assuming arch is on /dev/sda2 but you are defining your grub root as hd0,0 which is your boot, not your arch.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Also if in confusion remove by-uuid and just use /dev/sdaX naming scheme instead, much easier.
+1
UUIDs never made sense to me. Most people aren't changing hdds to the point of sda becoming sdb. If that is the case, simply use labels rather than UUIDs since a label is meaningful to you. For example, /dev/disk/by-uuid/c4ea7498-b80a-4348-bb61-16583c6e9ae1 doesn't tell me anything about the partition, but LABEL=Boot does!
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Well, if /boot is /dev/sda1 I'm assuming arch is on /dev/sda2 but you are defining your grub root as hd0,0 which is your boot, not your arch.
I don't think I agree. Grub's root command defines the partition where the kernel is to be found. That would normally be in the boot partition. Opposed to the root= argument in the kernel line, which should be the partition of the filesystem to be booted (they can be the same).
However, menu.lst doesn't seem to be the problem here (as it is only used at boot time), but the installation of the grub bootloader itself. Apparently, grub doesn't recognize /dev/sda as a valid device. You could try
fdisk -l
in a virtual console to verify.
Last edited by leepesjee (2009-11-07 14:43:12)
Offline
Sorry for the delay (a weekend in the forest, away from computers )
Changing /dev/by-uuid/... to /dev/sda1 has not solved the problem. The output of fdisk -l:
Device Boot Start End Blocks Id System
/dev/sda1 * ... 83 Linux
/dev/sda2 ... 82 Linux Swap / Solaris
/dev/sda3 ... 83 Linux
...
/dev/sda3 is /, formated using ext4. /dev/sda1 is /boot, formated with ext2. I've other partitions but I supose they don't apply to the case.
I don't know if could be significant that /var/log/pacman.log doesn't say anything about having installed grub...
Thanks for your suggestions!
Offline
Try to install grub manually: at the console, type 'grub'. Then at the grub prompt:
grub > root (hd0,0)
grub > setup (hd0)
grub > quit
This will probably fail - else it would have succeeded during installation. Let us know where it fails.
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
Thanks for your answer grey, but I just managed to install everything. Checking the pacman log, it was complaining about some files in /etc. I deleted them and installed all packages again. That solved everything.
Thanks again!!!
Offline
Pages: 1