**Background: **I want to store important files from my desktop computer to a micro SD card that will be readable by my Galaxy Tablet for when I travel. I bought a 64gb MicroSD that is compatible with the Tablet and a USB card reader/writer that will connect to my computer.
Problem: After working for a short time, Dolphin now gives the following error message when I try to access the microSD on my desktop computer:
An error occurred while accessing ‘59.5 GiB Removable Media’, the system responded: The requested operation has failed: Error mounting system-managed device /dev/sdb1: Command-line `mount “/tmp”’ exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
Question: What do I need to do to correct this error?
I followed the instructions after 1-Click “filesystems” and installed the repository on my system. Do I need to remove this repository after this problem is solved. All the warnings make me wonder…
I plugged in the card reader and got the same error message. What next?
If it doesn’t work, then you can remove the tools… But you can also delay that until you find some kind of solution.
A general observation on my part…
I’ve generally always found that moving cards around from one machine unreliable and the card might become unreadable unexpectedly as you describe… And then the next thing I’m usually doing is reformatting the media which of course means that everything on the card is lost.
This seems to happen more often with “smart devices” like PCs, phones and tablets. Doesn’t seem to be problem with “dumb devices” like cameras.
In fact, if you want to translate your error into layman’s language, assuming the card has worked before in that machine it’s saying that the file system is unreadable because the starting point of the file system can’t be found… that information has likely been corrupted, so if the file system’s info can’t be found everything on the volume is unintelligible. I haven’t explored whether there is a way to restore that superblock which could theoretically make the volume readable again (would be similar to restoring the MBR on a HDD).
So,
Although I might initially load a card with files in a different machine, after that the card stays in its permanent home.
I use other means to update the files on the card, like file transfers over a USB cable or network file shares.
But, that’s my own personal experience,
Maybe you’ll find a solution and can keep switching cards between machines.
Thank you for the information. I am sure you are correct. My current experience confirms it.
I keep looking for a way to take the information on my computer on the road with me without sharing it with Google, Apple, Amazon or some other cloud storage provider. I simply don’t trust them to keep it private and safe. Plus it takes a connection of some sort to access it which is often unavailable in remote areas.
The tablet is an old one (Galaxy 3) that I don’t use anymore. By keeping the WiFi and cell connections turned off when the microSD is installed, it should be fairly secure from Google, the Android snoop. It isn’t a big deal to reformat and reload the books, music, videos, pictures and reference manuals from my computer when I travel. They are all in a single directory and are updated regularly.
Any ideas on how to accomplish this without shuttling media like we once did with floppy disks at the office?
You can Google “Galaxy 3 usb transfer linux” and get results. Some people have had to overcome issues but it can work.
Otherwise, you can set up an FTP server, web server, or your choice of network file sharing on your openSUSE and then install a client app on to your Galaxy, then transfer files like any other networking file transfer.
The alternative is as you describe because mobile devices are generally set up to use cloud services for storage.
If you prefer not to use a commercial cloud service, I guess you can set up your own Owncloud/Nextcloud or similar.
The error message shown in your first post tends to indicate a non-supported files system, hence Knurpht’s speculative suggestion to install exfat-utils.
What file system is the card using?
Insert the card into your reader and then show the output from:
So the card has a W95 FAT32 (LBA) file system, which should be able to be mounted OK…
I assume the card works perfectly OK in the Galaxy Tablet, which together with you earlier comment, (sorry I initially missed it), that it had worked for a short time, would lead me to agree with tsu2’s comments in post #6. (Perhaps the Galaxy uses some sort of proprietary “quirky” version of FAT32).
Maybe follow up on tsu2’s suggestion in post #8 of some type of usb transfer of data, or look at KDE Connect as suggested by knurpht in post #9
As an aside, you probably have no reason now to retain the exfat-utils, although there is no harm in leaving them installed.
An error occurred while accessing ‘59.5 GiB Removable Media’, the system responded: The requested operation has failed: Error mounting system-managed device /dev/sdb1: Command-line `mount “/tmp”’ exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
The Galaxy Tab 3 isn’t the problem. I’ll work out the file transfer later.
The problem is with my computer which takes nearly an hour to boot as it tries to resolve the “exited with non-zero exit status 32” issue. Apparently, it cannot mount the removable media until it is properly unmounted and exit status = 0. (Probably, I took it out of the USB before it was “safe to remove”. I don’t know)
How do I resolve this issue and get it mounted in /media instead of /tmp?
It says that the partition has a partition type of x’oc", which is explained as “W95 FAT32 (LBA)”.
That is a byte stored in the partition table ( by the partitioner that made the partition).
There is no guarantee whatsoever that the contents of the partition corresponds to that.
I admit that in most of the cases the contents is created so that fits with the partition type (the more when a managment tool like YaST is used, because the tool combines the partitioning and the contents creating and thus knows what partition type to store when it is asked to create a file system of some type or swap). But having a strange problem here, we must check for deviations.
If it helps, a microSD from a friend’s Galaxy Tablet mounts, reads and writes with no problem. It does require root permission to un-mount and remove it safely.
Well, as long as you have no details about the file system type on that other card, comparing with this card, where we also do not know what file system is on it, is a bit difficult.
All we know thus far is that it is MS-DOS partitioned with only one partition (no space left) and that the partition type is x’0C’.
We do not know for sure if there is a file system on that partition, and when yes, which file system type. You only say in your first post “… After working for a short time,…”, but it is not clear to me if that “working” means you had then access to the file system (in other words if it was mounted at that time).
The error message of that first post points to a failure at mounting because there was no file system recognized. Thus either a wrong type specified, or during the heuristic checking if there is a supported file system type, no such one was detected.
This is strange when it is true that you already “worked” on it.
When there is no important data on the device, you could of course create a new file system on it. And then of a type that best fits your requirements. So when all systems you will use with it are Unix/Linux, choose something like ext2. Else another one that is supported by all operating systems you use.
I believe the Galaxy Tablet used FAT or FAT32. I can mount and reformat the microSD on the Tablet. Would that solve the problem? If not, how do I remove everything on the microSD and re-format from my computer when it won’t mount?
How do I reset the Non-zero state on my computer to zero so the computer boots in a normal, reasonable amount of time?
Yes, should have said looks like it’s probably “W95 FAT32 (LBA)”. (New card which had been working, likely preformatted, claims to be FAT32, so probably is, rather than some esoteric type). File system could be corrupted of course.
Perhaps, or it may again “work for a short time”.
If not, how do I remove everything on the microSD and re-format from my computer when it won’t mount?
Formatting will (effectively) “remove” everything on the card. You could use a utility such as “gparted” to format on your computer. Take care, ensure you are working on the correct device.
How do I reset the Non-zero state on my computer to zero so the computer boots in a normal, reasonable amount of time?
There is no need to “reset” anything. A programme terminates normally with an exit code of zero, terminating on error will return a non zero value which in most cases also indicates the type of error that occurred.
If your machine is taking a long time to boot then I suspect the reason may possibly be elsewhere.
