Ok, I'm going to mark this bug as "Invalid" since an entry in the blkid
cache is not really udev's fault (since it uses vol_id anyway)
We have a meta-bug anyway about the fact we have both blkid and vol_id,
when we should have just one library; we're in discussions with both
upstreams about findin
Problem solved.
blkid and vol_id gave the same uuids, but there were some old entries in
blkid cache which I removed with "sudo blkid -g". Then I removed old
menu.lst and forced update-grub to regenerate it - now there are correct
uuids. update-grub normally didn't overwrite old menu.lst, I had to
Interesting... this may be that a UUID has stayed in the blkid cache (in
which case this is an e2fsprogs issue).
After cloning the partition and changing the UUID, try running vol_id on
the new partition - do you get the same UUID as blkid or a different
one? Do you get the new UUID or the old on
Reopening as per previous comment(s).
** Changed in: udev (Ubuntu)
Importance: Undecided => Medium
Status: Invalid => Triaged
--
Different UUID between udev and fstab
https://bugs.launchpad.net/bugs/110251
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I encountered this bug after upgrading from Ubuntu 8.04 to 8.10 (Alpha).
There are different uuids in GRUB's menu.lst and reported by /dev/disk
/by-uuid (and also fstab). I'm not sure what has changed? Maybe the way
kernel generates uuids for disks is different than the one done by grub
updating sc
Hmmm simply changing the status to invalid just doesn't solve the
issue.
I outlined above how to reproduce this bug. Clone a partiton, give it a new
label and UUID, and blkid yields nonsense.
This did not go away.
Ubuntu has moved to UUID-based mounting (which is a controversial issue in
it
Since the problem has gone away, no way to get more information from
you.
This is usually because the partition has had a filesystem previously,
and both metadata are available
** Changed in: udev (Ubuntu)
Status: New => Invalid
--
Different UUID between udev and fstab
https://bugs.launc
It seems I solved the problem. I merged two partitions, properly
installed Feisty Fawn and now ... I don't have my problem anymore. But I
guess there is a rare problem of UUID attribution but I could not tell
which one. Cheers, Debian / Ubuntu rocks.
--
Different UUID between udev and fstab
https
It seems I'm suffering from a different incarnation of the same bug:
After cloning my Feisty (sdb1) install to another partition (sda7) on the same
machine i ran reiserfstune -u `uuidgen` /dev/sda7 to give the clone a different
UUID. This was successful
When trying to edit the fstab of the clone
** Attachment added: "/boot/grub/menu.lst"
http://librarian.launchpad.net/7410706/menu.lst
--
Different UUID between udev and fstab
https://bugs.launchpad.net/bugs/110251
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
10 matches
Mail list logo
