- This topic has 26 replies, 6 voices, and was last updated Mar 25-7:28 am by ModdIt.
-
Posts
-
Anonymous
@JohanS,
That makes no sense why the 64gb isn’t being recognized. You could try
reformatting the SD card to fat32 on the windows 10 machine to make sure
it’s not ntfs and then see if antiX mounts it.
I also noticed from your inxi that this is base … you could also see if the
antiX full iso will work.Robin
Hello JohanS
But it worked fine to read that 64 Gb SD from Windows 10 on my friends computer.
This was what I had presumed, since your SD card was not automounted, which is the standard behaviour on antiX for SD cards, as moddId pointed out already. You have seen it and proven to be functional whith your 32GB card yourself.
I have noticed SD cards not mounting on linux before, concering recent 64GB SD Cards on Linux systems. Hence I gave you the commands above to show details about the problem.There are two possible reasons, we have to trace down by process of elimination of possible sources of failur:
1.) Execute the commands I gave you above. They are neither dangerous nor difficult to handle. From their output we can try to understand what exactly happens on _mounting_ of the card on your PC (which is a mandatory function in the process of accessing the card). There is a slight chance Linux (or antiX) can’t handle SD cards of a specific type.
2.) Possibly your SD card reader can’t handle this specific card type. So to make sure it is not a problem of antiX (or Linux in general) please ask your friend to check, whether it can be read one his computer (whose SD card reader was proven to be compatible with your SD card when running on windows) when he boots with an antiX live Stick temporarily. This way we can exclude it is a problem antiX (or linux in general) has with a specific type of SD card.
- This reply was modified 2 years, 1 month ago by Robin.
- This reply was modified 2 years, 1 month ago by Robin.
- This reply was modified 2 years, 1 month ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.
ModdIt
@linuxdaddy, Robin,
please take a look at the posts on https://bugzilla.kernel.org/show_bug.cgi?id=202473
including the posts from yoshi.mxlinux Comment 37 onward.There is a kernel bug affecting some card reader/card combinations.
That may or may not be patched in antiX.
Probably not patched in the kernel JohanS is using at present.Another card can work ok, reformatting the present one is unlikely to solve the issue. .
@JohanS, please give us output of lspci, I am guessing you have a sandisk type 2 or 3 card
as they are the most commonly affected. type 1 cards, old and slow will probably all work fine.- This reply was modified 2 years, 1 month ago by ModdIt.
thanks moddlt … I was trying to make sure the SD card was fat32 not ntfs
as windows defaults to after a certain size as well. not sure if base has
the ntfs tools included. The laptop can run the newer
64-bit kernel if that will fix it.Many thanks, @ModdIt, what they describe there is exactly what I had experienced with some other 64GB SD cards myself.
I am on the most recent antiX kernel
4.19.180-antix.1-686-smp-pae
so the described patch is probably not present in antiX kernels still.
Here is what lsblk and mount command shows with a 64GB SD card:$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 2,6G 1 loop /live/linux loop1 7:1 0 1,5G 0 loop /home sda 8:0 0 93,2G 0 disk ├─sda1 8:1 0 8G 0 part /media/_daten1 ├─sda5 8:5 0 20G 0 part /media/_home ├─sda6 8:6 0 10G 0 part /media/antiX ├─sda7 8:7 0 42,5G 0 part /media/_daten3 ├─sda8 8:8 0 3G 0 part /media/_daten4 ├─sda9 8:9 0 2,2G 0 part [SWAP] └─sda10 8:10 0 7,5G 0 part /media/sda10 sdb 8:16 1 29,5G 0 disk ├─sdb1 8:17 1 29,5G 0 part /live/boot-dev └─sdb2 8:18 1 50M 0 part /media/antiX-uefi sr0 11:0 1 1024M 0 rom mmcblk3 179:0 0 59,7G 0 disk <----- this is the drivename └─mmcblk3p1 179:1 0 59,7G 0 part <----- this is the partitionname, it is not mounted.and mount command fails
demo@Birke:~ $ mkdir -p '~/test/SD-Card' demo@Birke:~ $ sudo mount '/dev/mmcblk3p1' '~/test/SD-Card' [sudo] Passwort für demo: mount: /dev/mmcblk3p1: can't read superblock <------ this is the errormessage while trying to mount. demo@Birke:~But it is still true what I said in my answer before, concerning JohanSs case: It _could_ be an incompatibility between card and reader still, as long this card was not tested on antiX with a card reader proven to be able to handle this specific card on another OS. But there is a good chance now this problem will be fixed for him over time, if it is _not_ an incompatibility. So, @JohanS, you might try different kernels. I’m quite sure antiX was able some time ago to read these 64GB cards flawlessly, I have one of them here, and it produces the same error, and yes @ModdIt, it is a Sandisk type 3.
Lspci shows the type of card reader, a “Texas Instruments” in my case$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04) 00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) 00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) 00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04) 00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 04) 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation NV43M [GeForce Go 6600] (rev a2) 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E Fast Ethernet Controller (rev 10) 06:02.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 06:02.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 06:02.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 06:02.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller 06:03.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d0) 06:08.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)I post all these output samples to show you, @JohanS, how it all works and what you might post here in order to sort this problem out.
Edit: In addition you might want to read this article about how to retrieve manufacturer information from your SD card.
- This reply was modified 2 years, 1 month ago by Robin.
- This reply was modified 2 years, 1 month ago by Robin.
- This reply was modified 2 years, 1 month ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.
JohanS
Moddlt here is the answer when I run lspci in terminal. The first lines that was returned in Terminal was only about,
“Host bridge, Intel Corporation Atom/Celeron/Pentium processor”
The only line I found about some card reader was about something called PCI Express Card reader. Can an SD-card reader be called “Express Card reader” ???
I will upload my printscreen of that Terminal windowAttachments:
Moddlt you where right about that Gparted idea. Gparted did find a storage unit close to 64 Gigabyte. Well Gparted shows a unit of 59 Gigabyte but I know the computers internal SSD-drive is smaller than 35 Gigabyte. So that 59 Gigabyte thing that Gparted found, I guess it can be nothing else than my 64 Gb SD-card (i tried to take screenshot ). But still the file manager in Antix does not see any 64 Gb storage unit. And you who are suspicious about the Card reader, I can tell as i Said before. I did try Bodhi linux on exactly the same computer ( i believe it was called Bodhi version 5.1 if i remember right ). So when I was running a live-session with Bodhi I did open terminal and run ,sudo apt install exfat-utils, then I answered yes to one or 2 questions in terminal, and After that I could read and write to exactly the Same SD-card that Antix does not like. I gave up Bodhi only because the web-browser had a lot of problems with web-pages I usually want to visit (for example it couldnt play news from Swedish Broadcasting company SVT).
Attachments:
userzero
See dmesg output:
[10131.129749] FAT-fs (mmcblk1p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [10131.134602] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.@Robin. Thanks for checking, in the first post JohanS stated that he was able to read the card on same device with Bodhi Linux.
Unfortunately (maybe fortunately for me) I do not have a fitting card to do any tests with my hardware.
As you are seeing same kind of problem it looks like a kernel bug or regression is present in antiX.@ JohanS To be more certain now it would be good if you could rescue your data to another storage device for
safety.
To rule out linux seeing some kind of file corruption, if you can please check again if Bodhi can read the card,
if yes which kernel is in use there. uname -r will give you the answer.
please do checks robin suggested and post.
Then try other available kernels in antiX, you can do that running live, Remaster, restart and see if you can read
the card.Fixing frustrating issues like this one is important both for users and the distro, if this is widespread as it seems likely
linux as a whole.
@Robin be nice if you could check if this this issue is present on Bullseye.What we need to know is which kernel version works with affected cards and devices, if possible where they stopped working, the
more precise the info the better. Maybe yoshi@mx linux can give some further insights regarding patch he applied after kernel
org posts.Although there is a known kernel issue:
As plenty of faked SD cards are in circulation, often bought at reputable stores.
Perhaps checking cards with f3 – Fight Flash Fraud toolset might be a good idea. This toolkit can only be used on an empty card
as it reads writes and confirms data, now routine for me before using usb sticks or sd cards. f3 is available in repos.- This reply was modified 2 years, 1 month ago by ModdIt.
- This reply was modified 2 years, 1 month ago by ModdIt.
I have read again some of the Answers here , and someone quoted a line from my terminal, including the message
“Volume was not properly unmouted”.
Just to make sure i do not hide any facts for all of you trying to help me, I should confess on thing,I believe when this message about “not properly unmounted” was returned in the terminal I had already also tried the 32 GB SD-micro (in the SD-adapter), just to see if the SD-card reader had any contact at all with Antix. I could not find any icon about unmount in the file manager so I just pulled out the card ( I mean the 32 GB SD ), so it was probably not correctly unmounted. I am sorry, I was so scared because I have a lot of work saved to that 64 Gigabyte SD-card. And by that moment it looked to me that the result of all work saved on that card had disappeared. Since Antix gave the answer in Terminal, something like ,”exfat-fuse is already the newest”, I assumed it would have correct support for a card formatted in exfat, and that made me even more worried that my 64 Gb card was broken. I was even more scared when I saw that the 32 Gbyte card was opened with the file manager within 4 seconds. I was so worried about everything seemed to be lost on my 64 Gb SD-card so i forget to unmount the 32 Gbyte SD-micro that evening. When I saw the mount path for the small SD, something like media/demo , I was eager to try if I could find the big SD in the same place/path so I just pulled out the 32 GB micro. I wasnt thinking clear , I was very worried about a lot lost work. I am sorry. ( It was first the day after I could lend a friends computer and see that all my documents and photos was still on the card ).
Hi JohanS,
First and foremost, Please rescue your data from the card. Please never keep important data on an SD Card or USB stick as only storage.
When Flash devices fail they usualy go without warning and data is gone, forever.Not cleanly ubnmounting a flash device can cause issues although unless data is being written the card controller will probably clean up
succesfully.After rescuing your data you can just reformat, see if antiX can read the card.
Please post result. We still do not know if your problem is solved or if, same as forum member Robin you are bug affected.
- This reply was modified 2 years, 1 month ago by ModdIt.
- You must be logged in to reply to this topic.
