Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Solved] MicroSD issue

Need help with peripherals or devices?
Message
Author
Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

[Solved] MicroSD issue

#1 Post by Fossy »

Regarding a Kingston microSD 128GB card that I want to use as data storage just like I use a USB flash drive .

Can someone guide me , taking into account a mildly deficient computer/ICT knowledge , through a procedure that I can handle ?
Although my system (via the internal Sd card reader) recognizes the card I fail to put this card into use ... my system ignores all my amateur efforts/approach (with thanks of not asking what I've been doing so far) .

Image

Image

Some usefull info ?
lsusb : Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
inxi -Fxxxrza ( with plugged-in card) :

Code: Select all

 System:
  Kernel: 5.10.0-21-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64 
  root=UUID=2088088c-7f70-497b-9a18-b904cdc70e0b ro quiet splash 
  resume=UUID=eff123dc-db4b-4634-810e-9bdd3550f761 
  Desktop: Cinnamon 4.8.6 tk: GTK 3.24.24 dm: LightDM 1.26.0 
  Distro: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: ASUSTeK product: K54HR v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: K54HR v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: K54HR.204 date: 03/20/2012 
Battery:
  ID-1: BAT0 charge: 43.3 Wh condition: 50.2/57.2 Wh (88%) volts: 11.5/10.8 
  model: ASUSTek K53--52 type: Li-ion serial: N/A status: Discharging 
CPU:
  Info: Dual Core model: Intel Core i3-2350M bits: 64 type: MT MCP 
  arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
  L2 cache: 3 MiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18357 
  Speed: 798 MHz min/max: 800/2300 MHz Core speeds (MHz): 1: 798 2: 798 
  3: 798 4: 798 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: mmio_stale_data status: Unknown: No mitigations 
  Type: retbleed status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, 
  STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Seymour [Radeon HD 6400M/7400M Series] vendor: ASUSTeK 
  driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6760 class ID: 0300 
  Device-2: IMC Networks UVC VGA Webcam type: USB driver: uvcvideo 
  bus ID: 1-1.2:3 chip ID: 13d3:5710 class ID: 0e02 serial: <filter> 
  Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon 
  unloaded: fbdev,modesetting,vesa display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") 
  s-diag: 414mm (16.3") 
  Monitor-1: LVDS res: 1366x768 hz: 60 
  OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.10.0-21-amd64 LLVM 11.0.1) 
  v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:1c20 class ID: 0403 
  Sound Server: ALSA v: k5.10.0-21-amd64 
Network:
  Device-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe vendor: Foxconn 
  driver: rt2800pci v: 2.3.0 port: d000 bus ID: 03:00.0 chip ID: 1814:5390 
  class ID: 0280 
  IF: wlp3s0 state: up mac: <filter> 
  Device-2: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: ASUSTeK 
  driver: atl1c v: kernel port: 9000 bus ID: 05:00.0 chip ID: 1969:1083 
  class ID: 0200 
  IF: enp5s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 228.27 GiB used: 17.6 GiB (7.7%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37120G 
  size: 111.79 GiB block size: physical: 512 B logical: 512 B 
  speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: B1E1 scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 type: USB model: Multiple Card Reader 
  size: 116.48 GiB block size: physical: 512 B logical: 512 B 
  serial: <filter> rev: 1.00 
Partition:
  ID-1: / raw size: 103.1 GiB size: 100.93 GiB (97.89%) 
  used: 17.59 GiB (17.4%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 
  ID-2: /boot/efi raw size: 300 MiB size: 299.4 MiB (99.80%) 
  used: 5.8 MiB (1.9%) fs: vfat dev: /dev/sda1 maj-min: 8:1 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8.39 GiB used: 0 KiB (0.0%) 
  priority: -2 dev: /dev/sda3 maj-min: 8:3 
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A gpu: radeon temp: 50.0 C 
  Fan Speeds (RPM): cpu: 2100 
Repos:
  Packages: apt: 2600 lib: 1280 
  Active apt repos in: /etc/apt/sources.list 
  1: deb http://deb.debian.org/debian bullseye main
  2: deb http://deb.debian.org/debian bullseye-updates main
  3: deb http://security.debian.org/debian-security/ bullseye-security main
  Active apt repos in: /etc/apt/sources.list.d/eid.list 
  1: deb https://files.eid.belgium.be/debian bullseye main
Info:
  Processes: 214 Uptime: 20m wakeups: 1 Memory: 3.81 GiB 
  used: 1.58 GiB (41.4%) Init: systemd v: 247 runlevel: 5 Compilers: 
  gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4 running in: gnome-terminal 
  inxi: 3.3.01
I've been reading through a lot of internet info in preparation, but unfortunately I don't understand a damn thing
Does anyone see fit to help me out with this ?
Thank You
Last edited by Fossy on 2023-04-05 12:51, edited 1 time in total.
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#2 Post by Aki »

Hello,
Have you partitioned it before formatting ?
You can use the gparted program to partition and format it.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#3 Post by Fossy »

Aki wrote: 2023-03-30 16:59 Hello,
Have you partitioned it before formatting ?
You can use the gparted program to partition and format it.
Hello Aki
no , I did not perform any editing on the MicroSD card ... do not have access to it
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#4 Post by Aki »

Hello,
Have you tried gparted on it ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#5 Post by Fossy »

Aki wrote: 2023-03-30 17:12 Hello,
Have you tried gparted on it ?
I tried this , but GParted apparently does not detect the card :
Image
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#6 Post by Aki »

Hello,
What if do you click on the button in the upper right part of the gparted window named “/dev/sda” ? Does the /dev/sdb device appear ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#7 Post by Fossy »

Aki wrote: 2023-03-30 17:45 Hello,
What if do you click on the button in the upper right part of the gparted window named “/dev/sda” ? Does the /dev/sdb device appear ?
I think I understand what you mean , no I don't get to see /dev/sdb in any way , only /dev/sda2 & 3

as an aside , albeit out-dated … Debian Buster , relevant in this story ?
Debian Bug report logs - #983672
linux-image: fails to recognize certain microSD cards
https://bugs.debian.org/cgi-bin/bugrepo ... bug=983672
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#8 Post by Aki »

That’s quite strange because inxi recognized it with its size:

Code: Select all

  ID-2: /dev/sdb maj-min: 8:16 type: USB model: Multiple Card Reader 
  size: 116.48 GiB block size: physical: 512 B logical: 512 B 
  serial: <filter> rev: 1.00 
The bug cited in your previous post is reported as fixed in Debian Bullseye.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#9 Post by Fossy »

Aki wrote: 2023-03-30 18:18 That’s quite strange because inxi recognized it with its size:

Code: Select all

  ID-2: /dev/sdb maj-min: 8:16 type: USB model: Multiple Card Reader 
  size: 116.48 GiB block size: physical: 512 B logical: 512 B 
  serial: <filter> rev: 1.00 
The bug cited in your previous post is reported as fixed in Debian Bullseye.
Yep, only gnome-disk apparently recognizes the MicroSD card, but refuses to perform operations on it.

Moreover, what I find strange is the fact that I have no problem at all with USBs , including using external card readers ( bank card / eID card reader )...
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#10 Post by Aki »

Hello,
Have you verified device permissions ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#11 Post by Fossy »

Aki wrote: 2023-03-30 19:17 Hello,
Have you verified device permissions ?
does the following answer your question ? :

Code: Select all

~$ stat /etc/hostname
  Bestand: /etc/hostname
  Grootte: 14           Blokken: 8            IO-blok: 4096   normaal bestand
Apparaat: 802h/2050d   Inode: 6291973      Koppelingen: 1
Toegang: (0644/-rw-r--r--)   UID: (    0/    root)   GID: (    0/    root)
Toegang:   2023-03-01 00:35:05.388601028 +0100
Gewijzigd: 2023-03-01 00:42:41.460619936 +0100
Veranderd: 2023-03-01 00:42:41.460619936 +0100
Ontstaan:  2023-03-01 00:35:05.388601028 +0100
as far as I know I’m full administrator of the system ? : both as Root ( su … although never used ) and user

edit :

Code: Select all

ls -l ...  ?
totaal 48
drwxr-xr-x 2 ******* *******  4096 30 mrt 20:53  Afbeeldingen
drwxr-xr-x 2 ******* *******  4096 30 mrt 21:26  Bureaublad
drwxr-xr-x 2 ******* *******  4096  1 mrt 00:47  Documenten
drwxr-xr-x 2 ******* *******   4096 15 mrt 00:04  Downloads
drwxr-xr-x 2 ******* *******  20480 27 mrt 00:54  Muziek
drwxr-xr-x 2 ******* *******   4096  1 mrt 00:47  Openbaar
drwxr-xr-x 2 ******* *******   4096  1 mrt 00:47  Sjablonen
drwxr-xr-x 2 ******* *******  4096  1 mrt 00:47 "Video's"
Moderator edit (aki): added code tags for a better readability. You can embrace code or output in code tags this way:
[code]
this is code
[/code]
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#12 Post by Aki »

Hello,

I was referring to permission of the device file of the card reader, if any (for example /dev/sdb ). This is an example for device file /dev/sda :

Code: Select all

ls -la /dev/sda
brw-rw---- 1 root disk 8, 0 26 mar 19.22 /dev/sda
You can list devices recognized by the operating system and their partitioning with the following command (after inserting the MicroSD in the reader; note: root password will be asked if you are not using root user):

Code: Select all

su -l -c "fdisk -l"
Please report as text (embraced in code tags) the output of the previous command.

Then please report as text (embraced in code tags) the output of the two following commands to identify the usb or pci devices of your computer (after inserting the MicroSD in the reader):

Code: Select all

lspci
lsusb
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#13 Post by Fossy »

@Aki
Hello Aki ,
hopefully I understood your instructions correctly , they were all executed , with plugged in MicroSD card , in the gnome-terminal after switching to root : sudo -s

1/ ls -la /dev/sda and ls -la /dev/sdb

Code: Select all

~$ sudo -s
[sudo] wachtwoord voor *******: 
root@*******-k54hr:/home/*******# ls -la /dev/sda
brw-rw---- 1 root disk 8, 0 31 mrt 14:29 /dev/sda
root@*******-k54hr:/home/djuwita# ls -la /dev/sdb
brw-rw---- 1 root disk 8, 16 31 mrt 14:29 /dev/sdb
root@*******-k54hr:/home/*******# exit
exit
2/ su -l -c "fdisk -l"

Code: Select all

:~$ sudo -s
[sudo] wachtwoord voor *******: 
root@*******-k54hr:/home/*******# su -l -c "fdisk -l"
Schijf /dev/sda: 111,79 GiB, 120034123776 bytes, 234441648 sectoren
Disk model: KINGSTON SA400S3
Eenheid: sectoren van 1 * 512 = 512 bytes
Sectorgrootte (logisch/fysiek): 512 bytes / 512 bytes
In-/uitvoergrootte (minimaal/optimaal): 512 bytes / 512 bytes
Schijflabeltype: gpt
Schijf-ID: 3BB642FA-0EC0-9F48-A138-5915EEA7D1F2

Apparaat       Begin     Einde  Sectoren Grootte Type
/dev/sda1       4096    618495    614400    300M EFI-systeem
/dev/sda2     618496 216843812 216225317  103,1G Linux bestandssysteem
/dev/sda3  216843813 234436544  17592732    8,4G Linux wisselgeheugen
root@*******-k54hr:/home/*******# exit
exit
3/ lspci

Code: Select all

~$ sudo -s
[sudo] wachtwoord voor *******: 
root@*******-k54hr:/home/*******# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6450 / 7450/8450/8490 OEM / R5 230/235/235X OEM]
03:00.0 Network controller: Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe
04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
05:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)
root@*******-k54hr:/home/*******# exit
exit
4/ lsusb

Code: Select all

~$ sudo -s
[sudo] wachtwoord voor *******: 
root@*******-k54hr:/home/*******# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 003: ID 13d3:5710 IMC Networks UVC VGA Webcam
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@*******-k54hr:/home/*******# exit
exit
correct ?
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#14 Post by Aki »

Hello,

Yes, you run the previous commands correctly (note: if you use the sudo command, the su command is not required). Your SD internal reader is:

Code: Select all

Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
You could verify as the operative system recognizes the internal reader. You can type the following command and then insert the MicroSD card:

Code: Select all

sudo journalctl -f
A list of messages should appear about SD card recognition after it is inserted. Then, you can stop the previous command with CTRL-C and then you can copy the aforementioned output from the terminal and send it in a next message.

What is you computer model and manufacturer ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#15 Post by Fossy »

@Aki
Hello ,
The laptop is an Asus model X54H
The output of sudo journalctl -f + after inserting the MicroSD card + CTRL-C :

Code: Select all

~$ sudo journalctl -f
[sudo] wachtwoord voor *******: 
-- Journal begins at Wed 2023-03-01 00:47:38 CET. --
mrt 31 17:29:33 ******-k54hr systemd[620]: gnome-terminal-server.service: Succeeded.
mrt 31 17:29:33 ******-k54hr systemd[620]: gnome-terminal-server.service: Consumed 1.463s CPU time.
mrt 31 17:29:35 ******-k54hr dbus-daemon[649]: [session uid=1000 pid=649] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.98' (uid=1000 pid=4180 comm="gnome-terminal ")
mrt 31 17:29:35 ******-k54hr systemd[620]: Starting GNOME Terminal Server...
mrt 31 17:29:35 ******-k54hr dbus-daemon[649]: [session uid=1000 pid=649] Successfully activated service 'org.gnome.Terminal'
mrt 31 17:29:35 ******-k54hr systemd[620]: Started GNOME Terminal Server.
mrt 31 17:29:35 ******-k54hr systemd[620]: Started VTE child process 4195 launched by gnome-terminal-server process 4185.
mrt 31 17:29:41 ******-k54hr systemd[1]: NetworkManager-dispatcher.service: Succeeded.
mrt 31 17:29:51 ******-k54hr sudo[4198]:  djuwita : TTY=pts/0 ; PWD=/home/****** ; USER=root ; COMMAND=/usr/bin/journalctl -f
mrt 31 17:29:51 ******-k54hr sudo[4198]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
mrt 31 17:30:01 ******-k54hr CRON[4201]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
mrt 31 17:30:01 ******-k54hr CRON[4202]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
mrt 31 17:30:01 ******-k54hr CRON[4201]: pam_unix(cron:session): session closed for user root
mrt 31 17:30:24 ******-k54hr kernel: usb 1-1.4: new high-speed USB device number 5 using ehci-pci
mrt 31 17:30:24 ******-k54hr kernel: usb 1-1.4: New USB device found, idVendor=058f, idProduct=6366, bcdDevice= 1.00
mrt 31 17:30:24 ******-k54hr kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
mrt 31 17:30:24 ******-k54hr kernel: usb 1-1.4: Product: Mass Storage Device
mrt 31 17:30:24 ******-k54hr kernel: usb 1-1.4: Manufacturer: Generic
mrt 31 17:30:24 ******-k54hr kernel: usb 1-1.4: SerialNumber: 058F63666433
mrt 31 17:30:24 ******-k54hr kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
mrt 31 17:30:24 ******-k54hr kernel: scsi host6: usb-storage 1-1.4:1.0
mrt 31 17:30:24 ******-k54hr mtp-probe[4209]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
mrt 31 17:30:24 ******-k54hr mtp-probe[4209]: bus: 1, device: 5 was not an MTP device
mrt 31 17:30:24 ******-k54hr mtp-probe[4216]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
mrt 31 17:30:24 ******-k54hr mtp-probe[4216]: bus: 1, device: 5 was not an MTP device
mrt 31 17:30:26 ******-k54hr kernel: scsi 6:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 0
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] 244285440 512-byte logical blocks: (125 GB/116 GiB)
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] Write Protect is off
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] No Caching mode page found
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 djuwita-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel: ldm_validate_partition_table(): Disk read failed.
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 djuwita-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel: Dev sdb: unable to read RDB block 0
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
mrt 31 17:30:26 ******-k54hr kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
mrt 31 17:30:26 ******-k54hr kernel: Buffer I/O error on dev sdb, logical block 0, async page read
mrt 31 17:30:26 ******-k54hr kernel:  sdb: unable to read partition table
mrt 31 17:30:26 ******-k54hr kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
^C
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Hardware] MicroSD issue

#16 Post by Aki »

Hello,
As you can see from the previous log, the operating system cannot read from the SD reader.
Could be the reader incompatible with the specific Micro SD card ?
Have you any other Micro SD card (possibly of smaller memory size) to test with ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

User avatar
kent_dorfman766
Posts: 535
Joined: 2022-12-16 06:34
Location: socialist states of america
Has thanked: 57 times
Been thanked: 70 times

Re: [Hardware] MicroSD issue

#17 Post by kent_dorfman766 »

FWIW, uSD cards don't well handle power drops during write operations. A power drop at the wrong time during a write and the chip can become bricked. I'd ask that you tell us your use case and I can then tell you if the uSD or USB FLASH is appropriate for that use-case.

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#18 Post by Fossy »

@kent_dorfman766
specifically find it more convenient for this laptop than a usb stick backup tool .
@Aki
What we are working on now ( was originally intended for use in an endoscope )
https://www.bol.com/be/nl/p/kingston-ca ... 9083/?s2a=
After all the effort You made (much appreciated) I ordered a 32GB SD ( NO Micro ) ( +/- 1 week delivery time ) to explore this problem further .
https://www.bol.com/be/nl/p/kingston-ca ... oductTitle
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: [Hardware] MicroSD issue

#19 Post by sunrat »

I vaguely recall one USB SD card reader I had would only work if the SD card was inserted before the reader was connected to computer.
My current notebook has an internal SD card reader that doesn't work at all. Never tried to sort it as it has USB ports and I have a USB SD reader.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

Fossy
df -h | participant
df -h | participant
Posts: 338
Joined: 2021-08-06 12:45
Has thanked: 34 times
Been thanked: 31 times

Re: [Hardware] MicroSD issue

#20 Post by Fossy »

@sunrat and @Aki
Interim update
Still had a photographic device here that has a Sandisk of only 1GB in it , and have plugged this one in for now as a test .
And Yep the system did accept this card .
Image
sudo journalctl -f :
………….
apr 01 01:44:54 *******-k54hr kernel: scsi 6:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0
apr 01 01:44:54 *******-k54hr kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
apr 01 01:44:55 *******-k54hr kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
^C
also “ accepted “ by GParted :
Image

It is now waiting for the SD 32GB card I ordered ... realize that with this I deviate from the original problem ( MicroSD )
ASUS GL753VD / X550LD / K54HR / X751LAB ( x2 )
Bookworm12.5_Cinnamon / Calamares Single Boot installations
Firefox ESR / DuckDuckGo / Thunderbird / LibreOffice / GIMP / eID Software

https://cdimage.debian.org/debian-cd/cu ... so-hybrid/

Post Reply