Well the problem has not been fixed. Here is the current indication:
Log of fsck -C -R -A -a
Fri Jul 6 08:50:24 2007
fsck 1.40-WIP (14-Nov-2006)
fsck.ext3: Unable to resolve 'UUID=e1298250-91d0-4524-8fea-abeffc04d4ec'
fsck died with exit status 8
Fri Jul 6 08:50:24 2007
----------------
As you can see from below this is rubbish:
[EMAIL PROTECTED]:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type>
<options> <dump> <pass>
proc /proc proc
defaults 0 0
# /dev/sda1
UUID=69eb4fab-f38b-43f7-8796-39734a877b89 / ext3
defaults,errors=remount-ro 0 1
# /dev/sda2
UUID=b800200b-197f-40e2-b27e-684b783e1bea none swap sw
0 0
# /dev/sdb2
UUID=101458e2-7316-4b2e-9550-f4354323c9d7 none swap sw
0 0
#/dev/Volume0/lvol0
UUID=e1298250-91d0-4524-8fea-abeffc04d4ec /home ext3
defaults 0 2
/dev/cdrom /media/cdrom0 udf,iso9660
user,noauto 0 0
Plus, of course I could reboot into the system perfectly after this "error"
--
Superblock not read at boot
https://bugs.launchpad.net/bugs/120285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
