Dear Maxmillian,

After submitting this post to the bug reporting system, I realized that the
intention might have been to send it directly to you as mentioned in the
automated reply.

If you received the message twice becasue of this my apologies. I ams not sure
whether the bug should be closed. The kernel is still simply not bootable.

Kind regards
Hans Linkels

Unfortunately UUID does not work either.

This is what my /etc/fstab looks right now:
UUID=c1420be7-ac52-477b-b31d-820d809105dc / ext3
defaults,errors=remount-ro 0 1
UUID=e7307d00-7354-44d4-81d3-502a0a860b7c /home ext3 defaults
0 2
UUID=5c35c1c8-a5d5-4e9d-9655-55e4ea4fed9c /usr ext3 defaults
0 2
UUID=60bd51f9-d5b5-413a-b74a-b26a2fd96a46 /var ext3 defaults
0 2

And /boot/grub/menu.lst:
title Debian GNU/Linux, kernel 2.6.26-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-686
root=UUID=c1420be7-ac52-477b-b31d-820d809105dc ro
initrd /boot/initrd.img-2.6.26-1-686

title Debian GNU/Linux, kernel 2.6.22-3-k7
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-3-k7
root=UUID=c1420be7-ac52-477b-b31d-820d809105dc ro
initrd /boot/initrd.img-2.6.22-3-k7

The blkid on the machine looks like this:
/dev/hdc1: LABEL="boot" UUID="c1420be7-ac52-477b-b31d-820d809105dc"
SEC_TYPE="ext2" TYPE="ext3"
/dev/hdc3: TYPE="swap"
/dev/hdc5: LABEL="/usr" UUID="5c35c1c8-a5d5-4e9d-9655-55e4ea4fed9c"
SEC_TYPE="ext2" TYPE="ext3"
/dev/hdc6: UUID="e7307d00-7354-44d4-81d3-502a0a860b7c" SEC_TYPE="ext2"
/dev/hdc7: LABEL="/var" UUID="60bd51f9-d5b5-413a-b74a-b26a2fd96a46"
SEC_TYPE="ext2" TYPE="ext3"

These UUIDs were collected while running 2.6.22. Given the nature of UUIDs, I
expect that these do not change while running a different kernel.

Note that what you expect to be on one line actually IS on one line, the
editor inserted the breaks.

Now I have taken some pictures of the screen when the boot failure occurs. I
am linking here to the pictures because I have not found a way yet to paste
the screens into a text file in BusyBox. Copying is a PITA and error prone.
But let me know if linking to pictures is against the policy and I try to
copy the text to this message anyway.

What strikes me is that apparently /dev/disk/by-uuid/xxx is expected, but this
device doesn't exist.

Kernel 2.6.22 still boots without problems, even now I have replaced /dev/hdc
with UUID.


On Saturday 20 September 2008, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the linux-image-2.6-k7 package:
> #499575: linux-image-2.6-K7 Wait for root file system after upgrading from
> kernel 2.6.22 to 2.6-K7
> It has been closed by maximilian attems .
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact maximilian attems
> by replying to this email.


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact