[Bug 512647] Re: blkid fails to detect fat memory stick in camera phone

Phillip Susi psusi at ubuntu.com
Thu Oct 10 14:08:53 UTC 2013


** Changed in: util-linux (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/512647

Title:
  blkid fails to detect fat memory stick in camera phone

Status in “util-linux” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  New

Bug description:
  Binary package hint: libblkid1

  In karmic, my camera phone fails to automount when I plug it in via usb. This works in hardy. I think I have tracked this down, via reading the mount manpage, to the fact that mount cannot autodetect the filesystem type. Plugging in the device, dmesg shows the partitions on the device correctly:
  dmesg | tail
  [ 6537.240147] scsi 8:0:0:0: Direct-Access     Sony Eri Memory Stick     0000 PQ: 0 ANSI: 0
  [ 6537.241877] sd 8:0:0:0: Attached scsi generic sg1 type 0
  [ 6537.263077] sd 8:0:0:0: [sdb] 126912 512-byte logical blocks: (64.9 MB/61.9 MiB)
  [ 6537.268137] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6537.268150] sd 8:0:0:0: [sdb] Mode Sense: 00 6a 00 00
  [ 6537.268157] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6537.282079] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6537.282099]  sdb: sdb1
  [ 6537.312158] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6537.312180] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  However, this does not automount. If I try mounting manually, it fails:
  sudo mount /dev/sdb1 /mnt/t
  mount: you must specify the filesystem type

  If I specify the filesystem to be vfat, no problems.

  Reading the mount manpage, it tries to detect the filesystem type by using blkid and vol_id. In Hardy and Karmic, blkid does not detect the filesystem type:
  sudo blkid -p /dev/sdb1
  milli:~$ echo $?
  2

  Return code 2 from blkid, means "I don't know what filesystem that is". However, vol_id, which is no longer available in karmic, detects it and mount can automatically detect the and mount the device in Hardy:
  hardy:> sudo vol_id /dev/sdb1
  ID_FS_USAGE=filesystem
  ID_FS_TYPE=vfat
  ID_FS_VERSION=FAT12
  ID_FS_UUID=BABE-BABE
  ID_FS_UUID_ENC=BABE-BABE
  ID_FS_LABEL=
  ID_FS_LABEL_ENC=
  ID_FS_LABEL_SAFE=

  So it seems that blkid has been broken/incomplete for quite some time,
  but mount was working by using vol_id. Since vol_id is now gone,
  automounting of my camera phone is now broken.

  Hope this is enough info, let me know if you need more.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Jan 26 12:30:49 2010
  DistroRelease: Ubuntu 9.10
  HotplugNewDevices: /dev/sdb /dev/sdb1
  HotplugNewMounts:
   
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
  Package: gvfs 1.4.1-0ubuntu1
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: gvfs
  Symptom: storage
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-17-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/512647/+subscriptions



More information about the foundations-bugs mailing list