Announcement

**Qqmike** · Jul 14, 2007, 05:49 AM

Re: Another UUID problem

Well, Gandolf, I don’t yet have any real experience with the UUIDs either, but I do know you aren’t alone in your frustration here.

Here’s a GRUB How-To I wrote, covering very basic methods. Somewhere down below that first post is another standalone post containing a few tips about editing your boot menu.lst for UUIDs, "UUIDs (in Feisty’s filesystem table, fstab)" (along with some tips about Vista). That’s all I know about this subject so far. Basically, I just copied that UUID (from, in your case sda8) into the kernel line, replacing the sda8= with the UUID. That worked in one of my 7.04 partitions for me, that day, that is. Try that and see if your system is any happier. Of course, uncomment the sda8 UUID in fstab, as root, File-Save, File-Quit, and all those good practice precautions.

How To GRUB Methods - Toolkit
http://kubuntuforums.net/forums/inde...opic=3081671.0

Just curious, as other potential helpers might be, what exactly does that UUID message say?

**GANDOLF** · Jul 15, 2007, 04:19 AM

Re: Another UUID problem

Thank you for the reply.

As for messages:
At first it told me it could not find UUID=XXXXXXX, which made sense since the part. table was changed.

so I replaced all the uuid's with sda8.
with the pclinux grub the same message came up.

Now it gets a bit complicated.

I installed gutsy tribe 2 and put grub in (hd0).

Gutsy's grub put feisty in /dev/sda8 so when I tried to boot feisty I got this message: Kernal panic: not syncing: attempted to kill init

I then proceeded to do: ls -l /dev/disk/by-uuid/
and replaced the uuid for sda8 in both grubs (Gutsy, feisty) and changed both fstabs accordingly.

Now when I boot feisty I get something like this: cannot find /lib/modules/2.6.20-16 generic/xxxxxxx

After checking in sda8 I find the folder /lib/modules/2.6.20-16 with all the modules.

I am pretty much at a loss.

Here are copies of the feisty part of gutsy menu.lst and fstab in feisty and gutsy:

Menu.lst Gutsy and Feisty :
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda8.
title Feisty, kernel 2.6.20-16-generic (on /dev/sda8)
root (hd0,7)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 ro splash acpi=off
initrd /boot/initrd.img-2.6.20-15-generic
savedefault
boot

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda8.
title Feisty, kernel 2.6.20-16-generic (recovery mode) (on /dev/sda8)
root (hd0,7)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 ro single
initrd /boot/initrd.img-2.6.20-15-generic
savedefault
boot

Feisty fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
#/dev/sda8 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
# /dev/sda5
UUID=CCA0-D201 /Data vfat sync,umask=022,uid=1000,gid=1000,auto,rw,user 0 0
# /dev/sdb5
UUID=4675-5EA7 /Data2 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda6
UUID=309F-309F /Vmware vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda7
UUID=41b4e918-04c8-4670-86b4-95c755bd6bdd /home ext3 defaults 0 2
# /dev/sda1
UUID=20F0D241F0D21D3C /media/sda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda10
UUID=e4ad0ec7-05e6-4c82-bb2f-d907beb2be2f /media/sda10 ext3 defaults 0 2
# /dev/sda11
UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 /media/sda11 ext3 defaults 0 2
# /dev/sda9
UUID=b823d8b7-c080-4b95-8fcc-62e3ca91d8d7 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

Gutsy fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda11
UUID=4fac41e8-5bcc-4474-947a-7f6c7d9014bf / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5
UUID=CCA0-D201 /Data vfat sync,umask=022,uid=1000,gid=1000,auto,rw,user 0 0
# /dev/sdb5
UUID=4675-5EA7 /Data2 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda6
UUID=309F-309F /Vmware vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda7
UUID=41b4e918-04c8-4670-86b4-95c755bd6bdd /home ext3 defaults 0 2
# /dev/sda1
UUID=20F0D241F0D21D3C /media/sda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda10
UUID=e4ad0ec7-05e6-4c82-bb2f-d907beb2be2f /media/sda10 ext3 defaults 0 2
#/dev/sda8 /media/sda8 ext3 defaults 0 2
UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 /media/sda8 ext3 defaults 0 2
# /dev/sda9
UUID=b823d8b7-c080-4b95-8fcc-62e3ca91d8d7 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

What is wrong with this?

**Qqmike** · Jul 15, 2007, 04:43 AM

Re: Another UUID problem

Hi GANDOLF. I don’t know, to be quick and honest about this. Obviously, it would seem the key is

“Now when I boot feisty I get something like this: cannot find /lib/modules/2.6.20-16 generic/xxxxxxx
After checking in sda8 I find the folder /lib/modules/2.6.20-16 with all the modules.”

But there’s some subtlety about what the message is saying. You’ve posted enough details that some of the pro’s may get a clue as to what these symptoms point at. I’ll be looking at this, too.

**GANDOLF** · Jul 15, 2007, 11:29 AM

Re: Another UUID problem

Thanks Qgmike

I just rebooted again into Feisty and after getting this message.
Fatal: cannot load /lib/modules/2.6.20-16 generic/xxxxxxx no such file or directory

I let it sit for a while 3-4 min) and up came this:
Done.
Begin: running /scripts/init-premount
Done.
Mounting root file system
Beginn: Running /scripts/local-top
Done.
Begin: waiting for root file system...
Then a bunch of stuff followed by:
Fatal:cannot load /lib/modules/2.6.20-16 generic/xxxxxxx no such file or directory
Alert! /dev/disk/by-uuid cd1e9366-437b-4d63-8e0b-6f7770091c19 does not exsist.
BusyBox v1.13 (debian 1.1.13-3ubuntu3) Builtin shell (ash)
enter 'help' for a list of built in commands
/bin/sh:can't access tty;job control turned off
(initramfs)

Just for the hell of it I'll post this as well:
ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2007-07-15 21:19 20F0D241F0D21D3C -> ../../sda1
lrwxrwxrwx 1 root root 10 2007-07-15 21:19 309F-309F -> ../../sda6
lrwxrwxrwx 1 root root 10 2007-07-15 21:19 41b4e918-04c8-4670-86b4-95c755bd6bdd -> ../../sda7
lrwxrwxrwx 1 root root 10 2007-07-15 21:19 4675-5EA7 -> ../../sdb5
lrwxrwxrwx 1 root root 11 2007-07-15 21:19 4fac41e8-5bcc-4474-947a-7f6c7d9014bf -> ../../sda11
lrwxrwxrwx 1 root root 10 2007-07-15 21:19 b823d8b7-c080-4b95-8fcc-62e3ca91d8d7 -> ../../sda9
lrwxrwxrwx 1 root root 10 2007-07-15 21:19 CCA0-D201 -> ../../sda5
lrwxrwxrwx 1 root root 10 2007-07-15 21:19 cd1e9366-437b-4d63-8e0b-6f7770091c19 -> ../../sda8
lrwxrwxrwx 1 root root 11 2007-07-15 21:19 e4ad0ec7-05e6-4c82-bb2f-d907beb2be2f -> ../../sda10

ANY ideas??

**penguin.ch** · Jul 15, 2007, 11:43 AM

Re: Another UUID problem

My guess: the inital RAM file system (initramfs) contains errors.
Therefore, you may try to recreate it: sudo update-initramfs -u

**GANDOLF** · Jul 16, 2007, 01:10 AM

Re: Another UUID problem

Okay but how? I tried it when booting feisty at the line (initramfs) but that didn't work. I am not very knowledgeable with the CLI so could you give me a pointer?

Thank you

**penguin.ch** · Jul 16, 2007, 01:59 AM

Re: Another UUID problem

Originally posted by Qqmike

But there’s some subtlety about what the message is saying. You’ve posted enough details that some of the pro’s may get a clue as to what these symptoms point at. I’ll be looking at this, too.

Indeed: it reads /lib/modules/2.6.20-16 generic/* instead of /lib/modules/2.6.20-16-generic/* ...

which gives me another idea: maybe a sym]
sudo ln -s /lib/modules/2.6.20-16-generic '/lib/modules/2.6.20-16 generic'
[/code]

**penguin.ch** · Jul 16, 2007, 02:02 AM

Re: Another UUID problem

Originally posted by GANDOLF

Okay but how?

Good question ... maybe boot to the previous kernel and start over from there?

**GANDOLF** · Jul 16, 2007, 02:58 AM

Re: Another UUID problem

Thanks rider.
tried this:
Code:
sudo ln -s /lib/modules/2.6.20-16-generic '/lib/modules/2.6.20-16 generic'

don't kmow what it was supposed to do, but it changed nothing.

I still had the -15 version in /sda8/lib/modules so I changed both /grub/menu.list to:

title Feisty, kernel 2.6.20-15-generic (recovery mode) (on /dev/sda8)
root (hd0,7)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 ro single
initrd /boot/initrd.img-2.6.20-15-generic
savedefault
boot

and saved them.

at boot I still get:
Fatal:cannot load /lib/modules/2.6.20-16 generic/XXXXXX no such file or directory

Why is it looking for -16 when it is supposed to be booting -15?

I am getting tired of this BS so I have another question:

If I reinstall Feisty to sda8 will it screw up may uuid again so that I can't boot anything (like gutsy sda11 or pclinux sda10) anymore?
If so how do I get around this?

I mean gutsy is great so far, but beeing beta it won't stay stable until the final release will it?

Anyway I need vmware and I read somewhere elsethat it doesn't like the gutsy kernel as of yet.

again thank you.

I really hate uuid with a vengance.
It is probably great on a system that never changes. But I can't even change the size of my data partition without f..g my boot up.

**penguin.ch** · Jul 16, 2007, 04:22 AM

Re: Another UUID problem

Could you please mail to me the complete file /boot/initrd.img-2.6.20-16-generic (~ 6 MB)?
I would like to analyze this problem in more detail; maybe it's possible to clear the faults (?).

**Fintan** · Jul 16, 2007, 06:01 AM

Re: Another UUID problem

@Gandolf:
s...t happens, typos too.

I just read through your menu.lst:

Menu.lst Gutsy and Feisty :
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda8.
title Feisty, kernel 2.6.20-16-generic (on /dev/sda8)
root (hd0,7)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 ro splash acpi=off
initrd /boot/initrd.img-2.6.20-15-generic
savedefault
boot

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda8.
title Feisty, kernel 2.6.20-16-generic (recovery mode) (on /dev/sda8)
root (hd0,7)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cd1e9366-437b-4d63-8e0b-6f7770091c19 ro single
initrd /boot/initrd.img-2.6.20-15-generic
savedefault
boot

I may be wrong but it seems that:
initrd /boot/initrd.img-2.6.20-15-generic
should read:
initrd /boot/initrd.img-2.6.20-16-generic

I hope this helps and I agree with you about UUID's I have had my issues in the past

**Qqmike** · Jul 16, 2007, 06:50 AM

Re: Another UUID problem

Well, now.
I suppose that qualifies as a “subtlety.” So that make me right.
And it concerns the initial RAM file. So that makes UnicornRider right.
Hmmm . . . was this actually just meant to be a quiz?
Of course, I’m just joking, lest you mistake my often mistaken sense of humor, and let’s hope it fixes the problem.
(As an old girlfriend used to say, it may not be right, but it is correct.)

**GANDOLF** · Jul 16, 2007, 07:07 AM

Re: Another UUID problem

I do have a healthy sense of humor but no this was a serious mistake on my part

anyway it partly worked. Now I have to do Ctrl+D to get fully booted. It doesn't like something in my fstab. I'll try and post what the boot error says later. I have a lot of work to catch up on.

Thank you all for your patience with someone who is still learning.

The BS with UUID'S still remains >

Cheers
G

**GANDOLF** · Jul 17, 2007, 01:52 AM

Re: Another UUID problem

Well this is a synapsis of the error message I get:
/dev/hda8 is mounted.e2fsck: cannot continue. aborting

fsck dies with exit status 8

Alog is being saved in /var/log/fsck/checkfs
Please repair manually a maintenance shell will now be started.
CONTOL-D will terminate this shell and resume system boot.

I do fsck and get something about a last line in fstab. Whatever that means?

CTRL+D boots the system

Comment from me: why is it hda8 here and sda8 in fstab??

Here is /var/log/fsck/checkfs:
Log of fsck -C -R -A -a
Tue Jul 17 09:38:20 2007

fsck 1.40-WIP (14-Nov-2006)
/dev/hda7: clean, 17714/2611200 files, 362603/5213084 blocks
Edgy: clean, 86589/796544 files, 646440/1592435 blocks
/dev/hda8 is mounted. e2fsck: Cannot continue, aborting.

fsck died with exit status 8

Tue Jul 17 09:38:21 2007
----------------

So how do I repair what "manually"?

cheers
G