[SOLVED] One small installation problem re boot/grub/menu.lst

red devil · 2008-09-19 13:14:52

Hi,
This is the first time I have installed Arch and I totally, totally love it.
I followed the Beginners Guide to the letter and everything went smoothly apart from one minor issue.
I am not able to launch Arch from the main 'Arch Linux' boot menu but it will start and run fine if I select the Arch Fallback option.
I have KDE4 running and all my applications installed etc, so there's just this one glitch that's stopping my Arch being absolutely perfect.
Below are what i thought might be the three most pertintent files - I wonder if an experienced Arch user could cast an eye over them and see where I am going wrong?
First, here's me GRUB menu.lst

# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 
root=/dev/disk/by-uuid/a4b6157c-8ee1-4673-a7a4-74eba4138cf2 ro
initrd /kernel26.img

# (1) Arch Linux
title  Arch Linux Fallback
root   (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/a4b6157c-8ee1-4673-a7a4-74eba4138cf2 ro
initrd /kernel26-fallback.img

# (1) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1

And then my Fstab

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0


#/dev/cdrom /media/cdrom   auto    ro,user,noauto,unhide   0      0
#/dev/cdrom1 /media/cdrom1   auto    ro,user,noauto,unhide   0      0
#/dev/dvd /media/dvd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd1 /media/dvd1   auto    ro,user,noauto,unhide   0      0
UUID=1ddddf6e-f6fc-4959-a37b-a39338783c57 /boot ext2 defaults 0 1
UUID=a4b6157c-8ee1-4673-a7a4-74eba4138cf2 / ext3 defaults 0 1
UUID=c21c5819-5645-411d-aa5c-0750de4963ac swap swap defaults 0 0
UUID=e82834bd-1de0-4275-97dd-00657c6ee836 /home ext3 defaults 0 1

and finally I did an fdisk -l to get my disk setup

bash-3.2# fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1           5       40162   83  Linux
/dev/sda2               6         136     1052257+  82  Linux swap / Solaris
/dev/sda3             137        1093     7687102+  83  Linux
/dev/sda4            1094        9729    69368670   83  Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8f9c798a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       19457   156288321    c  W95 FAT32 (LBA)

I found it odd that my menu.lst should identify my partitions by their UUID rather than the usual device name (sda1 etc), but I assumed this was something peculiar to Arch??
When I try to boot into the 'Arch Linux' entry, I get the following error message:

Booting 'Arch Linux'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz26
[linux-bzImage, setup=0x3000, size=0x188bf0]
root=/dev/disk/by-uuid/a4b6157c-8ee1-4673-a7a4-74eba4138cf2 ro
Error 11: Unrecognised device string

I have checked and the device string is the same in both the Arch Linux and the Arch Fallback menu.lst entries.
Can anyone help?
Cheers

Last edited by red devil (2008-09-22 13:59:03)

dav7 · 2008-09-19 13:21:40

title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 
> root=/dev/disk/by-uuid/a4b6157c-8ee1-4673-a7a4-74eba4138cf2 ro
initrd /kernel26.img

title  Arch Linux Fallback
root   (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/a4b6157c-8ee1-4673-a7a4-74eba4138cf2 ro
                  ^^
initrd /kernel26-fallback.img

Note the misalignment

-dav7

Last edited by dav7 (2008-09-19 13:22:14)

red devil · 2008-09-19 13:28:56

@ dav7 - thank you so much, that did the trick!
I did see the discrepancy but didn't realise the root=etc etc had to be on the same line as the kernel=... live and learn.. live and learn.
Arch is awesome, BTW - can't believe it has taken me so long to getting round to trying it.

Misfit138 · 2008-09-19 14:53:05

I don't use nano, but could this be an issue that nano -w may have avoided...I wonder...?

Mr.Elendig · 2008-09-19 15:11:40

Misfit138 wrote:

I don't use nano, but could this be an issue that nano -w may have avoided...I wonder...?

I made a bug report, it was closed with the reason being that nano was going to be rebuilt with nowrap as default. But then on the forum there were some complaints that it shoudn't and so on. Don't know what happened in the end

Misfit138 · 2008-09-19 15:52:20

Mr.Elendig wrote:

Misfit138 wrote:
I don't use nano, but could this be an issue that nano -w may have avoided...I wonder...?
I made a bug report, it was closed with the reason being that nano was going to be rebuilt with nowrap as default. But then on the forum there were some complaints that it shoudn't and so on. Don't know what happened in the end

Should the beginners' guide be updated to use nano -w everywhere it is used, perhaps?

dav7 · 2008-09-19 16:07:57

I personally like that idea a lot. Even when I use nano now, after months of having it installed, I still hit alt+l (or esc-l) to turn that terrible feature off. I've never used it once, and hate it. If the nano devs want a free bit of advice... rewrite the text wrapping system to *not modify the actual file*... I mean wow.

</rant>

-dav7

Mr.Elendig · 2008-09-19 17:41:07

Misfit138 wrote:

Mr.Elendig wrote:
Misfit138 wrote:
I don't use nano, but could this be an issue that nano -w may have avoided...I wonder...?
I made a bug report, it was closed with the reason being that nano was going to be rebuilt with nowrap as default. But then on the forum there were some complaints that it shoudn't and so on. Don't know what happened in the end
Should the beginners' guide be updated to use nano -w everywhere it is used, perhaps?

Problem is that the 2008.06 installer don't use -w, so if they opened and saved the file during install...... (something that is a good idea to do)

Shagbag · 2008-09-19 17:52:30

create a default alias in .bashrc for nano -w?

dav7 · 2008-09-20 07:24:10

ooo.

*taken aback by obvious simplicity*

*immediately sets that up*

-dav7

Mr.Elendig · 2008-09-20 11:21:30

Even better, turn on nowrap in .nanorc or whatever it's resource file is named.

Arch Linux

#1 2008-09-19 13:14:52

[SOLVED] One small installation problem re boot/grub/menu.lst

#2 2008-09-19 13:21:40

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#3 2008-09-19 13:28:56

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#4 2008-09-19 14:53:05

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#5 2008-09-19 15:11:40

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#6 2008-09-19 15:52:20

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#7 2008-09-19 16:07:57

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#8 2008-09-19 17:41:07

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#9 2008-09-19 17:52:30

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#10 2008-09-20 07:24:10

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

#11 2008-09-20 11:21:30

Re: [SOLVED] One small installation problem re boot/grub/menu.lst

Board footer