Ah, thanks very much Endolith
What's happened is that when /boot was created, it wasn't properly
cleaned up so it's not possible for blkid to determine the filesystem
type (and thus the UUID)
Here's how to fix that:
sudo -s
(will give you a root shell)
# tar czf /boot.tar.gz /boot
# umo
On Fri, 2010-04-16 at 23:43 +, nomnex wrote:
> Scott, I am a subscriber to this bug. the same problem has happened to
> me. Please, take a look at bug 511963 (eventually mark it as duplicate
> of this bug, thanks)
>
For the sake of sanity, could you attach this tar file to bug 511963
instead
~> sudo blkid -p /dev/sda5
/dev/sda5: ambivalent result (probably more filesystems on the device)
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
~> sudo blkid
/dev/sda1: SEC_TYPE="msdos" LABEL="DELLUTILITY" UUID="07D4-0918" TYPE="vfat"
/dev/sda2: UUID="709CF04A9CF00C7A" LABEL="Windows XP" TYPE="ntfs"
/dev/sda3: LABEL="DELLPCRESTO" TYPE="vfat"
/dev/sda6: UUID="5497-3D7E" TYPE="vfat"
/dev/sda7: LABEL="Jaunty" UUID="57882a85-8d4c-4adc-84eb
Scott, I am a subscriber to this bug. the same problem has happened to
me. Please, take a look at bug 511963 (eventually mark it as duplicate
of this bug, thanks)
blkid.tar {blkid.txt, blkid -p /dev/sda5.txt}
** Attachment added: "blkid.tar"
http://launchpadlibrarian.net/44493929/blkid.tar
--
On Fri, 2010-04-16 at 22:37 +, Endolith wrote:
> To make it boot again, I changed the UUID to /dev/sda5. I don't know
> why the UUID stopped working.
>
Happy to try and debug for that for you. Could you run "sudo blkid" and
give the output?
Also "sudo blkid -p /dev/sda5"
Thanks
Scott
--
To make it boot again, I changed the UUID to /dev/sda5. I don't know
why the UUID stopped working.
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thanks for the report.
>From the information you've given, it simply looks like your /etc/fstab
is wrong; or your /boot is corrupted
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received t
edit: I made a mix-up between 2 different bugs... this comment cancel
comment #3 above.
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Endolith, look here
https://bugs.launchpad.net/ubuntu/+bug/511963
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
** Package changed: ubuntu => mountall (Ubuntu)
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
In /etc/fstab, I changed
UUID=338c820e-d3b1-42bc-8966-b89e212547b2 /boot ext2 relatime 0 2
to
/dev/sda5 /boot ext2 relatime 0 2
and it seems to work now. The UUID has been removed or something?
~> la /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 140 2010-01-16 02:55 ./
drwxr-xr-x
** Attachment added: "RESULTS1.txt"
http://launchpadlibrarian.net/37705542/RESULTS1.txt
--
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/505751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
13 matches
Mail list logo