Ubuntu
linux package

usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.

Bug #1424261 reported by Jarl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size.

Hardware:

sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB)
USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2)
SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY)

Here is the output from terminal:
Accessing it through USB card reader:
$ sudo fdisk -l /dev/sdb

Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Accessing it through sd card adapter and the built-int sd card reader:
$ sudo fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

My conclussion is that the driver for the usb card-reader.

I will attach the output of lsusb -v -d 090c:6200

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-30-generic 3.16.0-30.40
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jarl 4339 F.... pulseaudio
CurrentDesktop: KDE
Date: Sat Feb 21 21:27:53 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2
InstallationDate: Installed on 2013-11-27 (450 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP EliteBook 8730w
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-30-generic N/A
 linux-backports-modules-3.16.0-30-generic N/A
 linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago)
dmi.bios.date: 12/03/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PAD Ver. F.13
dmi.board.name: 30EC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.25
dmi.chassis.asset.tag: CNU01143H6
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8730w
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Jarl (jarl-dk) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Jarl (jarl-dk) wrote :

First time I tried to use thsi SD card reader was about a year ago (13.10) where I also had this problem (same hardware), and the situation has not changed (i.e. all kernels through Ubuntu 14.04 and now 14.10.

The reason I have not repported this before is lack of time of root-cause investigation. For quite some time I was mislead/confused by the 32GB limitation of the FAT file system and not-so-mature linux implementation of the exFAT file system.

So this problem did not just start happening, it has never worked correct for me.

> Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

Yes, I have try to use the v4.0-rc1 kernel downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/ with no effect the behaviour is identical. Therefore I add the tag 'kernel-bug-exists-upstream'.

tags: added: kernel-bug-exists-upstream
Jarl (jarl-dk)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-f.20
tags: added: saucy trusty
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jarl (jarl-dk) wrote :

It's no so easy to update the BIOS when Ubuntu is installed, working on it, hang on, I'll be there.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Jarl (jarl-dk) wrote :

I have now (finally) updated the BIOS to the latest F.20 (mentioned in comment #5). I have further upgraded to the latest ubuntu 15.10 with kernel Linux hermes 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

The hardware, the symptoms and the problem is still the same.

Changed in linux (Ubuntu):
status: Expired → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jarl (jarl-dk) wrote :

The output from `sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date` is

68PAD Ver. F.20
12/07/2011

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jarl, could you please test the latest upstream kernel (4.4-rc2) and advise to the results?

tags: added: latest-bios-f.20
removed: bios-outdated-f.20
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jarl (jarl-dk) wrote :

I have now tried with the latest rc5 kernel
`Linux hermes 4.4.0-040400rc5-generic #201512140221 SMP Mon Dec 14 02:23:36 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux`

The problem/symptoms are still the same.

Jarl

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jarl, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Ulf Hansson CC linux-mmc)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

tags: added: kernel-bug-exists-upstream-4.4-rc5
Changed in linux (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.