[SOLVED] sandisk reader (not card) undetectable on linux only.

Haxsaw · 08-25-2020, 03:39 PM

Hi all pleased to meet you, this is my first post here and i am reasonably new to the linux world. I have very few commands in mind but do understand the principles of root, sudo and modifying with nano.
I am a long time Win user but recently installed Mint on an old Acer Aspire 6920. I also have a RPI3b+ running the official Pi OS.
As a gift i have a sandisk mobilemate (for the size on the RPI) with a 64gb sd card which is formatted with two 32 gb fat32 partitions. This was done on a win10 machine and I have been using it on my RPI and laptop without a problem since fathers-day.
After transferring the data from the card onto the win machine i decided to reformat the two partitions as before 2x32gb. Everything went well but on finalization i received a super fast error message and am no longer able to detect the reader on both the mint laptop or the RPI.
Windows does detect and mount it.
The card in another reader (RPI kit) does mount correctly on the Laptop an RPI.
Another card in the reader doesn't work either.

The following i will try to explain the best i can from a cra**y video on my phone of the error..

When i boot my laptop i get an error message libkmod: ERROR in the libkmod.conf file it seems to be rmmod and modprobe in the sdhci.conf it is ignoring the error on line 1,2,3 and 4

see image

I don't know enough to know if this is really linked to the reader but think it is.

If more info is needed to track this down let me know (with commands)

Thanks in advance to anyone who can help.

Code:

[  790.460084] usb 2-1: new high-speed USB device number 6 using ehci-pci
[  790.616560] usb 2-1: New USB device found, idVendor=1908, idProduct=0226
[  790.616564] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  790.805402] usb-storage 2-1:1.0: USB Mass Storage device detected
[  790.815099] scsi host5: usb-storage 2-1:1.0
[  790.815543] usbcore: registered new interface driver usb-storage
[  790.845459] usbcore: registered new interface driver uas
[  791.842201] scsi 5:0:0:0: Direct-Access     Generic  Mass-Storage     1.11 PQ: 0 ANSI: 2
[  791.843382] sd 5:0:0:0: Attached scsi generic sg2 type 0
[  792.688772] sd 5:0:0:0: [sdb] 124735488 512-byte logical blocks: (63.9 GB/59.5 GiB)
[  792.689631] sd 5:0:0:0: [sdb] Write Protect is off
[  792.689633] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[  792.690627] sd 5:0:0:0: [sdb] No Caching mode page found
[  792.690650] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[  792.704101]  sdb: sdb1 sdb2
[  792.708371] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 1180.353367] usb 2-1: USB disconnect, device number 6
[ 1180.416178] blk_partition_remap: fail for partition 1
[ 1180.416183] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty
[ 1180.452386] blk_partition_remap: fail for partition 2
[ 1180.452392] FAT-fs (sdb2): unable to read boot sector to mark fs as dirty
[ 1730.340176] usb 2-3: new high-speed USB device number 7 using ehci-pci
[ 1730.496597] usb 2-3: New USB device found, idVendor=1908, idProduct=0226
[ 1730.496605] usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1730.497199] usb-storage 2-3:1.0: USB Mass Storage device detected
[ 1730.503146] scsi host5: usb-storage 2-3:1.0
[ 1731.521237] scsi 5:0:0:0: Direct-Access     Generic  Mass-Storage     1.11 PQ: 0 ANSI: 2
[ 1731.522204] sd 5:0:0:0: Attached scsi generic sg2 type 0
[ 1732.233396] sd 5:0:0:0: [sdb] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
[ 1732.234375] sd 5:0:0:0: [sdb] Write Protect is off
[ 1732.234379] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 1732.235377] sd 5:0:0:0: [sdb] No Caching mode page found
[ 1732.235386] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 1732.242165]  sdb: sdb1 sdb2
[ 1732.245744] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 1732.497637] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 1733.195857] EXT4-fs (sdb2): recovery complete
[ 1733.197032] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
[ 3046.631051] usb 2-3: USB disconnect, device number 7
[ 3046.718294] blk_partition_remap: fail for partition 2
[ 3046.718299] Buffer I/O error on dev sdb2, logical block 557056, lost sync page write
[ 3046.718306] JBD2: Error -5 detected when updating journal superblock for sdb2-8.
[ 3046.718308] Aborting journal on device sdb2-8.
[ 3046.718311] blk_partition_remap: fail for partition 2
[ 3046.718313] Buffer I/O error on dev sdb2, logical block 557056, lost sync page write
[ 3046.718315] JBD2: Error -5 detected when updating journal superblock for sdb2-8.
[ 3452.921176] JFS: nTxBlock = 8192, nTxLock = 65536
[ 3453.105165] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 3463.368192] usb 2-1: new high-speed USB device number 8 using ehci-pci
[ 3463.524618] usb 2-1: New USB device found, idVendor=1908, idProduct=0226
[ 3463.524627] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3463.529523] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 3463.530479] scsi host5: usb-storage 2-1:1.0
[ 3464.545317] scsi 5:0:0:0: Direct-Access     Generic  Mass-Storage     1.11 PQ: 0 ANSI: 2
[ 3464.550066] sd 5:0:0:0: Attached scsi generic sg2 type 0
[ 3465.308749] sd 5:0:0:0: [sdb] 124735488 512-byte logical blocks: (63.9 GB/59.5 GiB)
[ 3465.309774] sd 5:0:0:0: [sdb] Write Protect is off
[ 3465.309778] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 3465.310752] sd 5:0:0:0: [sdb] No Caching mode page found
[ 3465.310760] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 3465.318772]  sdb: sdb1 sdb2
[ 3465.325791] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 3715.021480] usb 2-1: USB disconnect, device number 8
[ 5329.556241] usb 2-1: new high-speed USB device number 9 using ehci-pci

jefro · 08-25-2020, 05:44 PM

Gparted may be of some use to see what might be learned. Other programs and I'd assume diskpart would do it also. I'd redo it with gparted and see if it works correctly.

Since you say another card fails do you mean you can't get any card to be usable even if it is windows 10? Of if you are saying only windows 10 then maybe some technical issue maybe even exfat or such.

I think I'd have made a zipped copy of the data on the sd card instead of using file by file. I could be wrong but I get the feeling some filesystem issue. ??

business_kid · 08-26-2020, 08:30 AM

Welcome to LQ, Haxsaw.

I'd try and separate what's working and what's not. If the card reader is not built in, I presume it's on the usb? I would be suspicious of cables, and things inserted in the card reader. Unless you get it pretty straight. things can go wrong. cables fail, particularly cables often folded or with small or worn plugs.

Open a terminal. Plug the offending reader(s) out. Then plug it in again. In the terminal, type

Code:

sudo dmesg |tail

and that will show you what the kernel found. Repeat with the sdcard. If you can, post the output.This is what I get when I plug an sdcard into the built in reader (last 3 lines)

Code:

[172801.514220] mmc0: new ultra high speed SDR50 SDXC card at address 5048
[172801.514459] mmcblk0: mmc0:5048 SD64G 58.1 GiB 
[172801.520991]  mmcblk0: p1 p2

The line in bold means it's read the sdcard and seen the partitions. The card reader should appear with 'sudo lsusb'

Code:

Bus 003 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller

Haxsaw · 08-26-2020, 09:28 AM

Hi Jefro & Hi business_kid

Thanks for the replies...
Firstly: the card does work in a different external USB reader on linux. The card is fine
Secondly: the reader (sandisk) that is not detected on linux is detected on windows. So the reader is working just not on linux

I have gparted the sd card again, new partitions and it's the same result
here are the results you asked for @business_kid, sorry but i have the distinct impression you know more about all this than I do.

$ sudo dmesg |tail

Code:

[   37.019628] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[   37.038456] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
[   38.570864] ACPI: \_SB.PCI0.PEGP.NVGA.MXMI: Excess arguments - Caller passed 2, method requires 1 (20170831/nsarguments-276)
[   38.570904] ACPI: \_SB.PCI0.PEGP.NVGA.MXMS: Excess arguments - Caller passed 2, method requires 1 (20170831/nsarguments-276)
[   38.572952] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[   38.573214] caller os_map_kernel_space+0x8d/0xb0 [nvidia] mapping multiple BARs
[   49.492119] Bluetooth: RFCOMM TTY layer initialized
[   49.492128] Bluetooth: RFCOMM socket layer initialized
[   49.492138] Bluetooth: RFCOMM ver 1.11
[  697.162811] perf: interrupt took too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79750

$ sudo lsusb

Code:

      
Bus 002 Device 004: ID 04f2:b044 Chicony Electronics Co., Ltd Acer CrystalEye Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0000:0538  
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 138a:0001 Validity Sensors, Inc. VFS101 Fingerprint Reader
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I am aware that fat32 is for cards less than 32gb. I have a 64gb sd with 2x32gb partitions. Could all this be down to a stupid formatting error? Like i said new'ish to linux, i have been trying to solve this for a week now and all search's point to solving card issues but not the reader.

michaelk · 08-26-2020, 10:17 AM

It looks like that particular card reader is not being recognized. I suspect the card reader is the following. You can unplug the reader and see if it disappears.

Quote:

Bus 005 Device 002: ID 0000:0538

If the reader was recognized I would of expected something like the following from the output of dmesg.

Code:

[603647.414018] usb 2-2: new high-speed USB device number 27 using ehci-pci
[603647.540276] usb 2-2: New USB device found, idVendor=058f, idProduct=6366, bcdDevice= 1.00
[603647.540279] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[603647.540281] usb 2-2: Product: Mass Storage Device
[603647.540284] usb 2-2: Manufacturer: Generic
[603647.540286] usb 2-2: SerialNumber: 058F63666471
[603647.540570] usb-storage 2-2:1.0: USB Mass Storage device detected
[603647.540686] scsi host23: usb-storage 2-2:1.0

Have you tried plugging the device into another USB port? Could be a marginal port or the reader is not making a good connection.

I doubt it is a formatting error. If you had formatted in Windows it might of used exFAT or NTFS verus FAT32 but the reader should still be detected and you would of seen other errors.

Haxsaw · 08-26-2020, 12:49 PM

Quote:

Originally Posted by michaelk

It looks like that particular card reader is not being recognized. I suspect the card reader is the following. You can unplug the reader and see if it disappears.

If the reader was recognized I would of expected something like the following from the output of dmesg.

Code:

[603647.414018] usb 2-2: new high-speed USB device number 27 using ehci-pci
[603647.540276] usb 2-2: New USB device found, idVendor=058f, idProduct=6366, bcdDevice= 1.00
[603647.540279] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[603647.540281] usb 2-2: Product: Mass Storage Device
[603647.540284] usb 2-2: Manufacturer: Generic
[603647.540286] usb 2-2: SerialNumber: 058F63666471
[603647.540570] usb-storage 2-2:1.0: USB Mass Storage device detected
[603647.540686] scsi host23: usb-storage 2-2:1.0

Have you tried plugging the device into another USB port? Could be a marginal port or the reader is not making a good connection.

I doubt it is a formatting error. If you had formatted in Windows it might of used exFAT or NTFS verus FAT32 but the reader should still be detected and you would of seen other errors.

Hi Michael,
I tried what you said and the same line of code was still there, so without rebooting i moved the mouse to another port and in the same command window i started again and it became bus 003 device 17. So by deduction that line seems to be the mouse.
I then placed the card into another reader and it mounted and shows as GEMBIRD. The culprit reader is now in the old mouse port and this is the result.

$ sudo lsusb

Code:

Bus 002 Device 004: ID 04f2:b044 Chicony Electronics Co., Ltd Acer CrystalEye Webcam
Bus 002 Device 006: ID 1908:0226 GEMBIRD 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0000:0538  
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 138a:0001 Validity Sensors, Inc. VFS101 Fingerprint Reader
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Like you and after cross checking with 2 linux machines and a windows machine. Two readers and two cards i am thinking its the reader that's at fault and on linux only.
I don't know enough but could the error message i receive when i boot the laptop have something to do with it? I mentioned it in my first post, but only have a bad quality phone video of the message.

business_kid · 08-27-2020, 04:22 AM

Google for the module driving it. Mine uses the Realtek rts5129, but the module isn't called that

Code:

bash-5.0$ sudo grep rts /var/log/messages
Password: 
Aug 27 09:27:11 RoseViolet kernel: [    8.366572] usbcore: registered new interface driver rtsx_usb 
bash-5.0$ lsmod |grep rts
rtsx_usb_sdmmc         24576  0
rtsx_usb_ms            20480  0
memstick               16384  1 rtsx_usb_ms
mmc_core              159744  2 rtsx_usb_sdmmc,mmc_block
rtsx_usb               20480  2 rtsx_usb_sdmmc,rtsx_usb_ms

The logs don't refer to it as a cerd reader at all, and it's difficult to find, but it works. If you can't find it, grep for 'mmc' and you might find something.

Haxsaw · 08-27-2020, 01:04 PM

Quote:

Originally Posted by business_kid

Google for the module driving it. Mine uses the Realtek rts5129, but the module isn't called that

Code:

bash-5.0$ sudo grep rts /var/log/messages
Password: 
Aug 27 09:27:11 RoseViolet kernel: [    8.366572] usbcore: registered new interface driver rtsx_usb 
bash-5.0$ lsmod |grep rts
rtsx_usb_sdmmc         24576  0
rtsx_usb_ms            20480  0
memstick               16384  1 rtsx_usb_ms
mmc_core              159744  2 rtsx_usb_sdmmc,mmc_block
rtsx_usb               20480  2 rtsx_usb_sdmmc,rtsx_usb_ms

The logs don't refer to it as a cerd reader at all, and it's difficult to find, but it works. If you can't find it, grep for 'mmc' and you might find something.

I have tried formulating in google as many different ways i can and still can't find a reply, so based on your rts5129 i googled to get some idea of what i am supposed to be googling for and came across some 3rd party site and this https://github.com/asymingt/rts5139, obviously I didn't just go and install and to be honest i got lost at the last part of the install instructions. Sorry i don't know how to grep for stuff yet.

On the other hand i opened the file manager and then went into root and suddenly i could see the reader in the lefthand panel under devices. But it wouldn't mount.
AS YOU CAN SEE IN THE IMAGE there are two instances of the file manager open, one under root and the error message below it when trying to mount.

michaelk · 08-27-2020, 03:40 PM

A builtin card reader might require a driver as in the case of business_kid but your mobilemate which is a USB device should not.

I think the libkmod and sdhci.conf messages could be an error related to the Acer built in card reader.

At the moment I don't know why it isn't working...

Haxsaw · 08-27-2020, 09:33 PM

Quote:

Originally Posted by michaelk

A builtin card reader might require a driver as in the case of business_kid but your mobilemate which is a USB device should not.

I think the libkmod and sdhci.conf messages could be an error related to the Acer built in card reader.

At the moment I don't know why it isn't working...

Hi, I am still digging around, just done a complete install of mint 20 but that didn't change anything either. I just hope to find a solution.

While i was googling this thread came up as a suggestion, at least i thought it did. I followed it hoping for a new reply and discovered a duplicate post. I definitely didn't do that, i have no idea how it got there. You or admin can remove that if you like, i couldn't see how to.

sgosnell · 08-27-2020, 09:50 PM

The image shows that the error preventing mounting Box is "unknown filesystem type 'FAT32'. I don't know why that is happening on your system.

business_kid · 08-28-2020, 03:42 AM

Peopleare running away from fat* these days. afaik gdisk doesn't support it, windows doesn't support it so it's probably not in the kernel. Try cd'ing to /lib/modules/<kernel-version>, and run

Code:

find -name '*fat.ko'

Haxsaw · 08-28-2020, 08:38 AM

Quote:

Originally Posted by business_kid

Peopleare running away from fat* these days. afaik gdisk doesn't support it, windows doesn't support it so it's probably not in the kernel. Try cd'ing to /lib/modules/<kernel-version>, and run

Code:

find -name '*fat.ko'

I used

Code:

sudo nano /lib/modules/5.4.0-42-generic

and it replied

Code:

[ "/lib/modules/5.4.0-42-generic" is a directory ]

So i went into the file system and found a few sub directories and files based on modules. To many to open 1 by 1, but i did open the modules.dep out of curiosity and the closet i came finding your suggestion was this.

Code:

kernel/fs/fat/msdos.ko:

sgosnell · 08-28-2020, 08:54 AM

Since I don't have to deal with Windows, not ever, for anything, I format my SD cards as ext4. I would expect FAT32 support to be common, but I don't know anyone else's system. FAT32 works on mine, but I don't like it, so I don't use it.

Haxsaw · 08-28-2020, 11:02 AM

Quote:

Originally Posted by sgosnell

Since I don't have to deal with Windows, not ever, for anything, I format my SD cards as ext4. I would expect FAT32 support to be common, but I don't know anyone else's system. FAT32 works on mine, but I don't like it, so I don't use it.

We all have different stories, i started with windows years before i even knew linux existed, although i am regretting not having taken to linux sooner

sure you have to think a bit more and READ a lot more but with enough perseverance things slowly start to make sense.

I have just reformatted to ext4 but the result is the same. If it wasn't for the fact the reader mounts on windows I would have said the reader is dead. If it wasn't for the fact that the card mounts in another reader on both win and mint i would have said the card is dead.
I would like to think that i screwed something up within linux which is preventing the reader from being detected, but on the RPI i did nothing and that won't mount it either so, no i don't think i did anything wrong. the thing just stopped working on linux that's all i know.....It's really frustrating