** Changed in: util-linux (Ubuntu Karmic)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/426027
Title:
/dev/disk/by-uuid doesn't exist in karmic kernels
To manage
Hybrid CD-ROMs still cannot be handled in Lucid Lynx.
Now (in Lucid Lynx) the device appears in the desktop (KDE)
devicemanager, but it still cannot be mounted. The only option that
appears is: copy with k3b
When starting this option, k3b opens, but cannot recognize the CD-
device.
In fact,
BTW:
What happens behind the desktops devicemanager when a device is inserted?
Where could I add mount options (such as -t iso9660)?
Where is the detection of the filesysem of a plugged-in USB-device?
I've been looking around for docs a long time, but it seems to have
changed several time
Lucid has a much newer util-linux
** Changed in: util-linux (Ubuntu Lucid)
Status: Triaged = Fix Released
--
/dev/disk/by-uuid doesn't exist in karmic kernels
https://bugs.launchpad.net/bugs/426027
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Downloaded the git version of util-linux-ng, compiled (without fallocate
because this fails due to absent fallocate64) and verified that the new
blkid correctly recognizes my root partition:
$ cd util-linux-ng/misc-utils
$ ./blkid /dev/sda1
/dev/sda1: UUID=f9526843-5dda-4683-9588-41b864812487
Will this ever be fixed in Karmic? Just upgraded from jaunty to karmic
and lost 4 hours trying to figure out how to boot my system, an Acer
travelmate 2480
--
/dev/disk/by-uuid doesn't exist in karmic kernels
https://bugs.launchpad.net/bugs/426027
You received this bug notification because you
I have the same issue after upgrading to karmic with a mixed fs cd-rom
containing rockridge, jolliet, hfs.
The cmd we use to create the image is (simplified):
$ mkisofs -A SwissStick $(EDITION_USERFRIENDLY) -J -r -V SwissStick
\
-cache-inodes
If the CD-ROM filesystem contains HFS and Joliet and Rock Ridge
(iso9660), it cannot decide whether it should be mounted as hfs or as
iso9660. In Ubuntu older than Karmic Koala, it used to mount iso9660,
which is exactly the behaviour we expect and wish: Different view on Mac
(HFS), Linux
I also converted from Jaunty to Karmic and had this problem too. I have
tried the work-around: replacing the UUID with /dev/sdaN which is my
/home partition. One thing I want to add is that I had to reboot a few
times before the machine (Dell Latitude D810) would boot. It is curious
that there is
I have this problem also. I added a second internal HDD to my desktop
computer and thought that UUIDs would be a better method than the
/dev/sdXY notation I'd been using, but I got the /dev/disk/by-uuid
doesn't exist message.
Blkid does work for me in Karmic, but for some reason Karmic sees my
I also converted from Janunty to Karmic and had this problem. I have
not tried the work around, but will shortly. One thing I want to add.
I was trying to upgrade a Dell as was the person who originally posted
the problem. Is there something unique to Dell BIOS or hardware that
might be
I've got a Fujitsu laptop and also experienced this problem, so I'd
doubt this has something to do with Dell hardware.
--
/dev/disk/by-uuid doesn't exist in karmic kernels
https://bugs.launchpad.net/bugs/426027
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have what looks to be the same problem, although for me the problem is
not on my boot drive but a secondary drive. How should I work around
it? Should I get the git version of blkid -- will this allow me to
mount?
Currently I cannot even though I know the UUID that worked before with
Jaunty
This bug also prevented my machine from booting when I upgraded to
Karmic. As a workaround, I added 'GRUB_DISABLE_LINUX_UUID=true' to my
boot parameters, and changed 'root=UUID=foo' to 'root=/dev/sda1'. This
allowed me to boot my machine.
--
/dev/disk/by-uuid doesn't exist in karmic kernels
PS -- Using the git version of blkid also worked for me. However, I
couldn't see a non-hazardous way of using that version of blkid to boot
(I would need to put it on the initramfs, right?), hence the above
workaround.
--
/dev/disk/by-uuid doesn't exist in karmic kernels
I was hit by the same problem when upgrading to Karmic today (detected
vfat and ext3). Git version also works here
# blkid -p /dev/sda1
/dev/sda1: ambivalent result (probably more filesystems on the device)
# ./blkid -p /dev/sda1
/dev/sda1: UUID=a7b855d8-8d49-494f-b24d-dfa26c4a5916 VERSION=1.0
Given that upstream has a fix for this, we should certainly apply this
to karmic via SRU.
** Also affects: util-linux (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Lucid)
Importance: Medium
Status: Confirmed
** Changed in: util-linux
Matt: could you please also post the output of karmic blkid and the git
blkid:
$ sudo su -
# BLKID_DEBUG=0x blkid -p /dev/sda1
--
/dev/disk/by-uuid doesn't exist in karmic kernels
https://bugs.launchpad.net/bugs/426027
You received this bug notification because you are a member of Ubuntu
Sure.
karmic:
# BLKID_DEBUG=0x blkid -p /dev/sda1
libblkid: debug mask set to 0x.
reseting blkid_probe
ready for low-probing, offset=0, size=0
-- starting probing loop [idx=-1]
linux_raid_member: call probefunc()
ddf_raid_member: call probefunc()
isw_raid_member: call probefunc()
OK. It's clear from the git log that vfat detection has had some love recently:
http://git.kernel.org/?p=utils/util-linux-ng/util-linux-ng.git;a=history;f=shlibs/blkid/src/superblocks/vfat.c;h=2ba7ded10166b7413583441b7a19478ead5ed4c9;hb=HEAD
I just wanted to make sure this is not a duplicate of
On Thu, 2009-10-15 at 02:08 +, Matt Drake wrote:
With util-linux-ng 2.16.1 there's no change, but with git it works:
$ sudo ./blkid -p /dev/sda1
/dev/sda1: UUID=466063b6-fb62-4ebd-aadd-073d7ab92472 VERSION=1.0
TYPE=ext2 USAGE=filesystem
While I understand that this won't make it
Thanks for your insight Scott.
With util-linux-ng 2.16.1 there's no change, but with git it works:
$ sudo ./blkid -p /dev/sda1
/dev/sda1: UUID=466063b6-fb62-4ebd-aadd-073d7ab92472 VERSION=1.0
TYPE=ext2 USAGE=filesystem
While I understand that this won't make it into karmic, is there a
chance
On Mon, 2009-10-12 at 19:20 +, Matt Drake wrote:
$ sudo blkid -p /dev/sda1
/dev/sda1: ambivalent result (probably more filesystems on the device)
I saw your comment on 433364 (which might be a duplicate of this bug
since my partition is ext2) that explained what this output means. I did
Could you now run blkid -p /dev/sda1 for me?
** Changed in: util-linux (Ubuntu)
Status: Confirmed = Incomplete
--
/dev/disk/by-uuid doesn't exist in karmic kernels
https://bugs.launchpad.net/bugs/426027
You received this bug notification because you are a member of Ubuntu
Bugs, which is
$ sudo blkid -p /dev/sda1
/dev/sda1: ambivalent result (probably more filesystems on the device)
I saw your comment on 433364 (which might be a duplicate of this bug
since my partition is ext2) that explained what this output means. I did
use jaunty's alternative installer for lpia to setup this
Please supply the output of running blkid
** Changed in: udev (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: udev (Ubuntu)
Importance: Undecided = Medium
--
/dev/disk/by-uuid doesn't exist in karmic kernels
https://bugs.launchpad.net/bugs/426027
You received this bug
Your udevdb records these symlinks:
/dev/sda:
S: disk/by-id/ata-STEC_ATA_DISK_vS020.1.0_STECD51608A10r88GBY3
S: disk/by-id/scsi-SATA_STEC_ATA_DISK_vSTECD51608A10r88GBY3
S: disk/by-path/pci-:00:1f.1-scsi-0:0:0:0
/dev/sda1:
S: disk/by-id/ata-STEC_ATA_DISK_vS020.1.0_STECD51608A10r88GBY3-part1
blkid gives no output at all.
I'm assuming from your comments that this bug is not in udev, but in blkid, so
I'm changing the package to util-linux
** Package changed: udev (Ubuntu) = util-linux (Ubuntu)
** Changed in: util-linux (Ubuntu)
Status: Incomplete = Confirmed
--
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/31467446/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/31467447/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/31467448/Dependencies.txt
**
** Changed in: udev (Ubuntu)
Status: New = Confirmed
--
/dev/disk/by-uuid doesn't exist in karmic kernels
https://bugs.launchpad.net/bugs/426027
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
30 matches
Mail list logo
