Bug 592183 - udisks reporting empty label on SDHC drive
udisks reporting empty label on SDHC drive
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: udisks (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-14 03:33 EDT by Michel Alexandre Salim
Modified: 2013-03-05 23:02 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-18 16:18:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michel Alexandre Salim 2010-05-14 03:33:35 EDT
Description of problem:
udisks does not read the correct partition label on a SDHC card inserted into a Google Nexus One phone. The same setup works fine with dosfslabel, and I've tried resetting the disk label and running fsck.

Version-Release number of selected component (if applicable):
udisks-1.0.1-1.fc13.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Plug phone through USB cable, turn on USB storage on phone
2. udisks --show-info /dev/sdd1 | grep label
3. sudo dosfslabel /dev/sdd1
  
Actual results:
Step #2 shows an empty label, thus the disk is mounted using its FAT volume ID. Step #3 correctly shows the label (in this case, NEXUS16G)

Expected results:
udisks should report the correct volume label. This worked fine a couple of days ago.

Additional info:
I just tested a small FAT16 partition I used to flash my computer's BIOS and on it, udisks works just fine.
Comment 1 Michel Alexandre Salim 2010-05-18 16:18:56 EDT
Turns out it was a disk on the verge of failure (after less than a month!). The disk was not even readable in Windows; I managed to get most of the data out, but after that it cannot even be formatted anymore.

Note You need to log in before you can comment on or make changes to this bug.