Created attachment 44200 [details] udisks --dump output When connected Ipod is recognized by KDE as two devices: one is actual Ipod (works fine), another as a flash drive of the same size (is unmountable). Bug in KDE - https://bugs.kde.org/show_bug.cgi?id=267499 Ipod Classic 160Gb, Linux Mint 10 KDE x64 or Kubuntu Maverick x64. cat /proc/self/mountinfo 14 19 0:14 / /sys rw,nosuid,nodev,noexec,relatime - sysfs none rw 15 19 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc none rw 16 19 0:5 / /dev rw,relatime - devtmpfs none rw,size=1018120k,nr_inodes=254530,mode=755 17 16 0:11 / /dev/pts rw,nosuid,noexec,relatime - devpts none rw,gid=5,mode=620,ptmxmode=000 18 14 0:15 / /sys/fs/fuse/connections rw,relatime - fusectl fusectl rw 19 1 8:5 / / rw,relatime - ext4 /dev/disk/by-uuid/136ee63e-57c7-4f7e-a64d-3f60455caea3 rw,errors=remount-ro,barrier=1,data=ordered 21 14 0:7 / /sys/kernel/debug rw,relatime - debugfs none rw 22 14 0:10 / /sys/kernel/security rw,relatime - securityfs none rw 23 16 0:16 / /dev/shm rw,nosuid,nodev,relatime - tmpfs none rw 24 19 0:17 / /var/run rw,nosuid,relatime - tmpfs none rw,mode=755 25 19 0:18 / /var/lock rw,nosuid,nodev,noexec,relatime - tmpfs none rw 26 19 8:3 / /media/Data rw,nosuid,nodev,relatime - fuseblk /dev/sda3 rw,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 27 19 8:1 / /media/Windows rw,nosuid,nodev,relatime - fuseblk /dev/sda1 rw,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 28 19 8:7 / /home rw,relatime - ext4 /dev/sda7 rw,user_xattr,barrier=1,data=ordered 29 15 0:19 / /proc/sys/fs/binfmt_misc rw,nosuid,nodev,noexec,relatime - binfmt_misc binfmt_misc rw 20 19 8:17 / /media/ALEX'S\040IPOD rw,nosuid,nodev,relatime - vfat /dev/sdb1 rw,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,errors=remount-ro cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda5 during installation UUID=136ee63e-57c7-4f7e-a64d-3f60455caea3 / ext4 errors=remount-ro 0 1 # /home was on /dev/sda7 during installation # Commented out by Dropbox # UUID=16609324-4ae1-41e3-abfe-1d3e46715cce /home ext4 defaults 0 2 # /media/Data was on /dev/sda3 during installation UUID=7C2365321A9923CE /media/Data ntfs defaults,umask=007,gid=46 0 0 # /media/Windows was on /dev/sda1 during installation UUID=1080572080570C1A /media/Windows ntfs defaults,umask=007,gid=46 0 0 # swap was on /dev/sda6 during installation UUID=263f248a-a174-4f33-9321-9cc3839888f5 none swap sw 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0 UUID=16609324-4ae1-41e3-abfe-1d3e46715cce /home ext4 defaults,user_xattr 0 2 udisks version: 1.0.1+git20100614-3 gvfs: 1.6.4-0ubuntu1.1 libatasmart4: 0.17+git20100219-2 - is not installed
Created attachment 44201 [details] 'udevadm info --export-db output
Created attachment 44202 [details] udisks --monitor-detail
Created attachment 44203 [details] gvfs-mount -oi output
Created attachment 44204 [details] udevadm monitor --udev --property output
udev reports: E: DEVNAME=sdb1 E: ID_FS_TYPE=vfat E: ID_FS_USAGE=filesystem and E: DEVNAME=sdb E: ID_FS_TYPE=vfat E: ID_FS_USAGE=filesystem so udisks probably isn't at fault here (I assume the ID_FS_* properties are set by udev and used by udisks, if this assumption is wrong, disregard what I say) I think I've already seen the kernel(?) misidentifiying a filesystem on the block device on some iPods, but I can't remember the specifics.
So where do I go from here? :) This thing started happening after KDE 4.6 install, which started using udisks. Never happened in 4.5.
This is indeed a libblkid issue but I think it has been resolved. Otherwise please file a bug against util-linux (which is what provides libblkid). Thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.