An XD card from a camera is formatted in FAT12.
Dmesg shows it is seen but is not automounted.
As root, “mount -t auto …” works fine and I can access all files.
I examined /etc/fstab for clues why automount is not happening but was faced with a forest of UUIDs which my knowledge does not encompass.
Any way I can hint to the system to automount XD cards?
Hi
What size is the XD card, is this card in a reader or direct from the camera?
If via the camera, does it configure it’s self as USB storage or an MTP device?
Can you tail the log and connect the device (not mount) to see what it’s doing;
su -
journalctl -f
Card is 32 MB and the failure occurs on read through a system card reader.
Reading via USB cable through the camera is no problem.
Here is the follow from journalctl:
# journalctl -f
-- Logs begin at Tue 2015-11-10 05:18:21 EST. --
Jul 14 09:20:05 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=74 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=56853 DPT=161 LEN=54
Jul 14 09:20:06 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=74 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=56853 DPT=161 LEN=54
Jul 14 09:20:07 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=74 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=56853 DPT=161 LEN=54
Jul 14 09:20:38 linux-tqr4 su[6031]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Jul 14 09:20:38 linux-tqr4 su[6031]: gkr-pam: couldn't unlock the login keyring.
Jul 14 09:20:38 linux-tqr4 su[6031]: (to root) colin on pts/0
Jul 14 09:20:38 linux-tqr4 su[6031]: pam_unix(su:session): session opened for user root by colin(uid=1000)
Jul 14 09:20:47 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=11554 DF PROTO=TCP SPT=33380 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405B40402080A452176F20000000001030306)
Jul 14 09:20:48 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=11555 DF PROTO=TCP SPT=33380 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405B40402080A452177EC0000000001030306)
Jul 14 09:20:50 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=11556 DF PROTO=TCP SPT=33380 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405B40402080A452179E10000000001030306)
Jul 14 09:20:54 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=11557 DF PROTO=TCP SPT=33380 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405B40402080A45217DCC0000000001030306)
Jul 14 09:21:01 linux-tqr4 kernel: sd 6:0:0:0: [sdb] 64000 512-byte logical blocks: (32.8 MB/31.3 MiB)
Jul 14 09:21:01 linux-tqr4 kernel: sdb: sdb1
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 80 00 00 08 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63872
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 80 00 00 08 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63872
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb, logical block 7984, async page read
Jul 14 09:21:02 linux-tqr4 kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=fc:aa:14:39:35:25:00:09:6b:38:16:a1:08:00 SRC=192.168.0.141 DST=192.168.0.111 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=11558 DF PROTO=TCP SPT=33380 DPT=80 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405B40402080A452185A00000000001030306)
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 80 00 00 08 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63872
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 80 00 00 08 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63872
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb, logical block 7984, async page read
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 23 00 00 08 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63779
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 23 00 00 01 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63779
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63744, async page read
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 24 00 00 01 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63780
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63745, async page read
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
Jul 14 09:21:02 linux-tqr4 kernel: sd 6:0:0:0: [sdb] CDB: Read(10) 28 00 00 00 f9 25 00 00 06 00
Jul 14 09:21:02 linux-tqr4 kernel: blk_update_request: critical medium error, dev sdb, sector 63781
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63746, async page read
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63747, async page read
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63748, async page read
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63749, async page read
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63750, async page read
Jul 14 09:21:02 linux-tqr4 kernel: Buffer I/O error on dev sdb1, logical block 63751, async page read
I see here a reference to the login keyring. I am using auto login which results in the keyring not being automatically opened. However some applications when they find this lock in place then generate a dialog box to get access. That does not happen here, and does not happen when the camera is connected by cable.
Hi
So when you mount manually all is ok, maybe run fsck over it? If you copy all the files off, reformat device in the camera how does it go?
When you say mount via camera/usb cable it mounts automatically, but if use the reader it doesn’t?
Thanks for your suggestions.
I have two of these cards, both FAT12, both work in the camera and are available through USB cable.
Both were mountable manually with mount command using option “-t auto”.
I tried to run “dosfsck” on both with fix off, and both reported a dirty bit set, not cleanly unmounted.
I fixed one with the -a option. Now that card reports no errors from dosfsck.
But it still will not automount, and now it refuses to mount with “mount -t auto /dev…” as it did before.
In fact neither of the cards will mount manually, they both report that there is no entry in /etc/fstab to deal with the situation.
Another small detail, I ran gparted with one of the cards plugged in and gparted thought the formatting of the card was FAT16, not FAT12 determined by the system.
On Thu 14 Jul 2016 02:46:02 PM CDT, colbec wrote:
Thanks for your suggestions.
I have two of these cards, both FAT12, both work in the camera and are
available through USB cable.
Both were mountable manually with mount command using option “-t auto”.
I tried to run “dosfsck” on both with fix off, and both reported a dirty
bit set, not cleanly unmounted.
I fixed one with the -a option. Now that card reports no errors from
dosfsck.
But it still will not automount, and now it refuses to mount with “mount
-t auto /dev…” as it did before.
In fact neither of the cards will mount manually, they both report that
there is no entry in /etc/fstab to deal with the situation.
Hi
Can you re-format the cards in the camera?
What does journalctl -f indicate when trying to attach/manually
mount…?
For automounting it’s udisks and gvfs… wonder if FAT12 support has
been dropped…
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.26-21-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Apologies, the cards do mount manually, I had typo in mount command.
Noted your suggestion to reformat in the camera, will do that when I have investigated the fstab issue.
After formatting the card in the camera, the camera can read the card, the card can be mounted by openSUSE and I can write a file and delete it while mounted. But Gparted is not able to read the card at all; it thinks the card does not have a fs which it can recognize. Previously gparted was able to get FAT16 from it.
When deliberately formatted by gparted as FAT16, camera cannot read it.
I’m doubtful that the real format is FAT12 since this is a much earlier standard designed for cards smaller than this one.
The camera is a Fujifilm and since they invented the xd card format I guess they should know pretty well how to format it. They seem to be keeping the format nicely hidden so this might explain why there are some parts that work on Linux and others that do not cooperate well.
FWIW this problem just went away. The card now mounts correctly and is visible to the system as soon as I plug it in.
No action on my part to explain this, apart from regular Yast updates.