Page: 1, 2  Next

trouble with kernel 2.6.31-4.slh.1-686
manilg
Status: Interested
Joined: 03 Nov 2009
Posts: 14
Reply Quote
After installing the new sidux-kernel with smxi my system couldn´t start again: It stops and after some minutes I get the error message, that the root partiton coldn´t be found and /dev/uuid/f3479161-afa7-4f48-9198-860b14755d87 is unknow. Older kernel find the root partition.
What can I do?
Thank you

manilg
Back to top
drb
Status: Contributor
Joined: 09 Jul 2009
Posts: 130
Reply Quote
That's quite an old kernel. smxi installed 2.6.31-5.slh.2 here some time ago.
Back to top
manilg
Status: Interested
Joined: 03 Nov 2009
Posts: 14
Reply Quote
I also installed 2.6.31-5.slh.2 same problem

manilg
Back to top
drb
Status: Contributor
Joined: 09 Jul 2009
Posts: 130
Reply Quote
I'd use a LiveCD to check out the UUID and then edit fstab accordingly. Why the older kernel works, I don't know,
Back to top
manilg
Status: Interested
Joined: 03 Nov 2009
Posts: 14
Reply Quote
When using a live-CD ther is no UUID in fstab

manilg
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Just boot into system using older kernel, then:

ls -l /dev/disk/by-uuid

to get the uuid information.

I do NOT use uuid, because it's not nearly as user friendly as Labels, when I assign a label I know it will not change or alter or fail, and I put that label into fstab and menu.lst and resume data if applicable.
Back to top
manilg
Status: Interested
Joined: 03 Nov 2009
Posts: 14
Reply Quote
:: Quote ::

ls -l /dev/disk/by-uuid
insgesamt 0
lrwxrwxrwx 1 root root 10 4. Nov 2009 20888DFA888DCEAA -> ../../sda1
lrwxrwxrwx 1 root root 10 4. Nov 2009 c4a2eb4e-cf87-473c-8683-af3fd4725110 -> ../../sda3
lrwxrwxrwx 1 root root 10 4. Nov 2009 e1ab8f6e-cc9e-4733-86d4-ed097b6a0884 -> ../../sda6
lrwxrwxrwx 1 root root 10 4. Nov 2009 EC61-C8FD -> ../../sda5
lrwxrwxrwx 1 root root 10 4. Nov 2009 f3479161-afa7-4f48-9198-860b14755d87 -> ../../sda2


and

:: Quote ::

cat /boot/grub/menu.lst | grep UUID
# kopt=root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet
kernel /boot/vmlinuz-2.6.31-5.slh.2-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
kernel /boot/vmlinuz-2.6.31-4.slh.2-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
kernel /boot/vmlinuz-2.6.29-4.slh.1-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
kernel /boot/vmlinuz-2.6.29-0.slh.1-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
kernel /boot/vmlinuz-2.6.28-2.slh.2-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
kernel /boot/vmlinuz-2.6.28-0.slh.10-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
kernel /boot/vmlinuz-2.6.27-8.slh.1-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791




:: Quote ::

cat /etc/fstab | grep /
# /etc/fstab - static information about the filesystems - fstab(5)
# /etc/fstab is only read by programs, and not written; it is the duty of the
/dev/disk/by-uuid/20888DFA888DCEAA /media/disk1part1 ntfs auto,users,ro,dmask=0022,fmask=0133,nls=utf8 0 0
UUID=f3479161-afa7-4f48-9198-860b14755d87 / ext3 defaults,errors=remount-ro,noatime 0 1
UUID=c4a2eb4e-cf87-473c-8683-af3fd4725110 /home ext3 defaults,auto,users,rw,exec,noatime 0 2
/dev/disk/by-uuid/EC61-C8FD /media/disk1part5 vfat auto,users,rw,quiet,umask=000,shortname=lower 0 0
#/dev/sr0 /media/cdrom udf,iso9660 noauto,ro,users 0 0
/dev/fd0 /media/fd0 auto noauto,rw,users 0 0


UUID is correct, (sda2 is the root partition) and I only can use the kernel until 26.28-2.

manilg
Back to top
aus9
Status: Assistant
Joined: 21 Sep 2008
Posts: 358
Location: Australia
Reply Quote
hi

maybe its not the uuid at all?

how about posting your hard drive /boot/grub/menu.lst

I am wondering if its because you have a borked grub file?
Namely a wrong attempt to set the boot partition to something that does not have the balance of grub files on them?

I could show you how to use grub in trouble-shooter mode?
www.linuxquestions.org/questions/linux-software-2/discussion-new-grub-trouble-shooter-278748/

but I no longer maintain it as I now use grub2
Back to top
manilg
Status: Interested
Joined: 03 Nov 2009
Posts: 14
Reply Quote
Hi,

here is my complete menu.lst

:: Quote ::

cat /boot/grub/menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-legacy-doc/.

# Deutsche Tastaturbelegung
setkey y z
setkey z y
setkey Y Z
setkey Z Y
setkey equal parenright
setkey parenright parenleft
setkey parenleft asterisk
setkey doublequote at
setkey plus bracketright
setkey minus slash
setkey slash ampersand
setkey ampersand percent
setkey percent caret
setkey underscore question
setkey question underscore
setkey semicolon less
setkey less numbersign
setkey numbersign backslash
setkey colon greater
setkey greater bar
setkey asterisk braceright

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default saved

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5

# Pretty colours
color cyan/blue white/blue
gfxmenu (hd0,1)/boot/message

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### 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=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet

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

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

## 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=vga=791

## 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.31-5.slh.2-sidux-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.31-5.slh.2-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
initrd /boot/initrd.img-2.6.31-5.slh.2-sidux-686

title Debian GNU/Linux, kernel 2.6.31-4.slh.2-sidux-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.31-4.slh.2-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
initrd /boot/initrd.img-2.6.31-4.slh.2-sidux-686

title Debian GNU/Linux, kernel 2.6.29-4.slh.1-sidux-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.29-4.slh.1-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
initrd /boot/initrd.img-2.6.29-4.slh.1-sidux-686

title Debian GNU/Linux, kernel 2.6.29-0.slh.1-sidux-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.29-0.slh.1-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
initrd /boot/initrd.img-2.6.29-0.slh.1-sidux-686

title Debian GNU/Linux, kernel 2.6.28-2.slh.2-sidux-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.28-2.slh.2-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
initrd /boot/initrd.img-2.6.28-2.slh.2-sidux-686

title Debian GNU/Linux, kernel 2.6.28-0.slh.10-sidux-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.28-0.slh.10-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
initrd /boot/initrd.img-2.6.28-0.slh.10-sidux-686

title Debian GNU/Linux, kernel 2.6.27-8.slh.1-sidux-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.27-8.slh.1-sidux-686 root=UUID=f3479161-afa7-4f48-9198-860b14755d87 ro quiet vga=791
initrd /boot/initrd.img-2.6.27-8.slh.1-sidux-686

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

### END DEBIAN AUTOMAGIC KERNELS LIST

title Windows 2K/XP/2003/Vista (sda1)
rootnoverify (hd0,0)
makeactive
chainloader +1

### ISO boot
title sidux 32bit von ISO
kernel (hd0,1)/sidux/vmlinuz boot=fll quiet vga=791 fromiso=/sidux/sidux.iso
initrd (hd0,1)/sidux/initrd.img


manilg
Back to top
aus9
Status: Assistant
Joined: 21 Sep 2008
Posts: 358
Location: Australia
Reply Quote
hi

firstly thanks for your patience...let me tell you that I am struggling but let confirm what we both know and work from there....= you do the work

(unless others can spot it)

1) is grub pointing to boot partition?
yes its (hd0,1) which in ls uuid is a match and is a match to fstab and a match to grub's kernel line....meaning your boot is a sub-folder to / and not on its own partition.

2) Do I have a suggestion on your current menu other than TechAdmins suggestion to move to root=LABEL=labelstring....YES

in grub menu you have these lines at top
# array will desync and will not let you boot your system.
default saved

Please consider changing to default (number)

eg
default 0

3) Does grub find the kernel and initrd?
Well the menu looks great to me but we can use grub at command mode to test.


You may need to write these down if you like? and no harm in trying

at grub menu press C for commands then issue commands and press enter at end of each line...you must get a response

:: Code ::

root (hd0,1)

-----response should be linux partition
:: Code ::

kernel /boot/vmlinuz (AND press tab key)

----response will be one of the following
a) nothing...because we have the wrong partiton or no kernel named vmlinuz*
b) one vmlinuz...which autocompletes)
c) multiple vmlinuz files

leaping ahead type a bit and tab from

kernel /boot/vmlinuz-2.6.31-5 (and press tab key) which should autocomplete your kernel bit.....then complete but use NO UUID

so its

kernel /boot/vmlinuz-2.6.31-5.slh.2-sidux-686 root=/dev/sda2 ro

:: Code ::

initrd /boot/initrd (AND PRESS TAB KEY) to get responses


---responses are
a) nothing as wrong partition or no initrd exists
b) one initrd....which autocompletes
c) multiple initrds and then type some more to complete line as

initrd /boot/initrd-2.6.31-5.slh.2-sidux-686

next line is

:: Code ::

boot


-------------------------
I would like to know what grub error numbers you see and write down the exact message please.

Leaping ahead..I can not see anything wrong with your legacy menu other than some minor fetish issues unique to me and that should not affect your booting.

-----------------------------------

Since you are here, can you confirm you had no issues using smxi please?
Back to top
Display posts from previous:   
Page: 1, 2  Next
All times are GMT - 8 Hours