I installed kernel 2.6.30.5.slh through smxi but upon booting it hangs. How do I get the grub/menu.list to recognize and boot into this and future kernels? Like setting UUID

I'm running antiX strictly sid repos only. Here is my grub/menu.list

timeout 15
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title antiX at hda1, kernel 2.6.27-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-1-mepis-smp root=/dev/hda1 nomce quiet nosplash vga=791 resume=/dev/hda2
initrd /boot/initrd.img-2.6.27-1-mepis-smp
boot

title MEMTEST
kernel /boot/memtest86+.bin

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/hda1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(single-user mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.30-5.slh.1-sidux-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.30-5.slh.1-sidux-686 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.30-5.slh.1-sidux-686

title Debian GNU/Linux, kernel 2.6.30-5.slh.1-sidux-686 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.30-5.slh.1-sidux-686 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.30-5.slh.1-sidux-686

title Debian GNU/Linux, kernel 2.6.27-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-1-mepis-smp root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.27-1-mepis-smp

title Debian GNU/Linux, kernel 2.6.27-1-mepis-smp (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-1-mepis-smp root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.27-1-mepis-smp

title Debian GNU/Linux, kernel memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

Thankx in advance.
Robert
Back to top

You can't use /dev/hdxx syntax for modern libata kernels, you have to mount by either LABEL or UUID.

antix.freeforums.org/post11643.html#p11643

You have to replace all /dev/hdxy in /etc/fstab and /boot/grub/menu.lst with either LABEL=<partition label> or UUID=<partition uuid>

I'm hoping mepis fixes this problem in their default setup configurations, along with their problematic xorg.conf issue, by the next release, otherwise they are going to have more and more difficultly keeping end users over time.
Back to top

You might get away with just adding the UUid to the menu.lst and no need to edit fstab. (This works on my box with the liquorix kernel).
Changing hd to sd may also work.

To get the UUID's use the inxi script.

inxi -plu
Back to top

hi

Please read only if you have time and tolerate grub weirdos

Having seen quite a few forum postings on grub and UUID, I vote for people to change to LABEL altho e2label only works for ext2/3/4 and not for swap!

if anyone knows a way of labelling swap pls post?

anyhows I use UUID for swap and don't care as I have never seen mine being used...with my new computer. (I spent 5 years on a intel 440BX so feel I have done my yakka)

2)
a good live cd has gparted on it which has a graphical way of changing labels assuming you ensure they are not mounted before the attempt. It seems to be a front end to e3label.

3) while in live cd mode you can then mount your /boot parition or if its a sub-folder to / mount that and any separate / partition and edit your grub config file and fstab to show new entries

eg for fstab the beginning is of mine is

LABEL=root /.....blah blah etc

Yes I am a complex individual who can not remember sophicated labels so root is my choice...if I had a separate boot partition guess what it might be called? lol

and my grub legacy is
# kopt=root=LABEL=root ro quiet

(is used by grub-update to convert to my kernel line below the Debian script stuff)
kernel /boot/vmlinuz-2.6.30-1.slh.3-sidux-686 root=LABEL=root ro quiet vga=791

4) I had attempted to move to pure sid but for time reasons opted to install sidux 2009-02 xfce edition and then convert to LXDE with openbox and then of course smxi to update stuff.

but will go back to my beloved grub2 soonish but looking at my old online link I am not sure if grub2 respects LABEL?

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

sidux.com/index.php?module=Wikula&tag=grub2bak

regards gordy
Back to top

hi

an update is always good?

gparted can add labels at creation as per test in vbox.

and fstab and grub legacy editted to use labels for root and swap


Back to top

To create labels: techpatterns.com/forums/about1240.html&highlight=uuid+label
that post has most of the methods, all very easy to do.

You can also use sed to replace all occurances of the bad /dev/xxx with LABEL=<label>

ie, you change say: root=/dev/sda3
to: root=LABEL=my-root-stuff

in fstab, menu.lst. For suspend, sometimes you need to change the resume in menu.lst as well, and in one place in /etc too.

Labels are by far and away the easiest and safest way to handle mounts, and are also human readable and user friendly, and require relatively trivial scripting to handle in system install, so one has to be tempted to ask: why aren't they standard, especially if the scripting enforces complexity rules, like say: <boxname>-root-1 after checking that label does not exist on system.

Likewise, if Debian would stop formatting swap on every install, it would be trivial to add that as well to the default installer. But let's not hold our breaths...

In general, I would suggest you resist the urge to use short generic lables like swap root home and use machine specific stuff like main-root-1 or main-swap-1

this also makes search and replaces much easier, since searching for 'root' is going to destroy your system if you replace it with another string, but searching for mybox-root-1 will simply find and replace the labels that occur.
Back to top

hi techadmin

thanks for the link ...did not search for it.... silly me

I think you are agreeing label for swap is only available on creation

I shall check it out
Back to top

To create a Label for swap:

swapoff -a
mkswap -L <your label> /dev/xxxx
swapon -a
Back to top