You are not logged in.
Hello.
I'm trying to edit my FAT32-formatted 32Go SD card with Dolphin but this piece of cr*p won't let me touch to its data. I can just watch the contents, but not do any modification. The SD card, after multiple checks, isn't physically locked.
I tried mounting it individually with
sudo mount -o rw,uid=1000,gid=1000,dmask=000,fmask=111 /dev/sdf1 /media/iso/, but the problem remains unresolved.
I'm surprised there's not a more intuitive way to mount FAT filesystems, but also, I don't see what else I could do.
OS: Arch Linux x86_64 6.4.2-arch1-1.
Dolphin 23.43.04.3.
Last edited by byjove01 (2023-07-22 17:18:36)
Offline
... but not do any modification
why not? What modifications are you attempting? What do the following return:
stat /mnt/iso/
touch /mnt/iso/test"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Sorry, I'm not used to Linux commands, that's why I can't provide directly a log. I'm still a beginner in that domain.
Here's a gross translation of the output.
File : /media/iso/
Size : 16384 Blocks : 32 E/S Blocks : 16384 Repository
Device : 8/81 Inœud : 1 Links : 13
Access : (0777/drwxrwxrwx) UID : ( 1000/ byjove) GID : ( 1000/ byjove)
Access : 1970-01-01 01:00:00.000000000 +0100
Edit : 1970-01-01 01:00:00.000000000 +0100
Changed : 1970-01-01 01:00:00.000000000 +0100
Created : 1970-01-01 01:00:00.000000000 +0100
touch: impossible de faire un touch '/media/iso/test': Système de fichiers accessible en lecture seulement # "Can't run 'touch' : Read-only filesystem" Offline
"LC_ALL=C touch touch /media/iso/test", however:
The SD card, after multiple checks, isn't physically locked.
The latch on the card is merely a friendly suggestion for the card reader that implements the actual lock.
Remove the card, run "sudo dmesg -W", plug the card, post the resulting output.
Do you care about the data on the disk?
Do you have a second card reader?
Can you try the card against a different system (HW/OS)?
Offline
The latch on the card is merely a friendly suggestion for the card reader that implements the actual lock.
Remove the card, run "sudo dmesg -W", plug the card, post the resulting output.
Ok.
[33238.604056] sd 17:0:0:0: [sdg] 62521344 512-byte logical blocks: (32.0 GB/29.8 GiB)
[33238.605245] sdg: detected capacity change from 0 to 62521344
[33238.606710] sdg: sdg1
[33244.418566] FAT-fs (sdg1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[33245.318542] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 462c452c)
[33245.318551] FAT-fs (sdg1): Filesystem has been set read-only
[33245.318565] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 63752820)
[33245.318576] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2d207449)
[33245.318607] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2c722c73)
[33245.318620] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2c722c73)
[33245.318642] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 6e617420)
[33245.318666] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2820646e)
[33245.318680] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 61482066)
[33245.318695] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 28202029)
[33245.318727] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 616e746e)
[33251.660727] fat_get_cluster: 11 callbacks suppressed
[33251.660732] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 462c452c)
[33251.660755] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 63752820)
[33251.660765] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2d207449)
[33251.660782] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2c722c73)
[33251.660794] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2c722c73)
[33251.660808] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 6e617420)
[33251.660823] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 2820646e)
[33251.660836] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 61482066)
[33251.660849] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 28202029)
[33251.660869] FAT-fs (sdg1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 616e746e)Do you care about the data on the disk?
Kinda. But I can still recover it. The thing is that I'm not sure formatting my SD card will resolve anything, because I'll need to put it back to FAT32.
It's a SD card for my Nintendo DSi and it seems like Nintendo thought it was a great idea to force the use of FAT32 on SD cards.
Do you have a second card reader?
Nope.
Can you try the card against a different system (HW/OS)?
Yes. On a Linux Mint 20.3 distro. I could access the device with no issues and read/write its files.
Offline
You could access the files on Mint, but can you still. It seems the problem it was removed (perhaps from that Mint system) without being properly unmounted. Run fsck on it as advised.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I did it one hour ago, so I guess I still can access the device contents via Linux Mint. Could not run fsck, it interrupts before having started. Should I think about formatting it?
Last edited by byjove01 (2023-07-22 16:36:33)
Offline
What interrupts how?
Don't paraphrase, post the actual errors.
Offline
> sudo fsck
fsck de util-linux 2.39.1
e2fsck 1.47.0 (5-Feb-2023)
/dev/sdc2 est monté. # /dev/sdc2 mounted.
e2fsck: Ne peut continuer, arrêt immédiat. # Can't continue, immediate stop.Would be a pleasure to be more specific than fsck itself, but I sadly can't...
Last edited by byjove01 (2023-07-22 16:38:42)
Offline
You can't fsck a mounted device.
I'm not used to Linux commands
Aparently. But if you are not inclined to learn any, you should consider another distro. You've been a member on these forums for well over 2 years - you should know the basics of the system you are using (or at least be able to read error messages).
Last edited by Trilby (2023-07-22 16:43:48)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
You can't fsck a mounted device.
byjove01 wrote:I'm not used to Linux commands
Aparently. But if you are not inclined to learn any, you should consider another distro. You've been a member on these forums for well over 2 years - you should know the basics of the system you are using.
Didn't say I wasn't inclined to learn commands. I'm just learning as time goes on. The lake isn't on fire. ![]()
I'm using Arch since three years ago and I don't have a lot of problems with it, so I don't think I need to switch to another distro.
Yep you're right about fsck, my bad. I know how to read error messages, thank you, I'm just not used to use this kind of command since I rarely have to. Here's what I got.
fsck de util-linux 2.39.1
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
[123?q]? Last edited by byjove01 (2023-07-22 16:51:21)
Offline
Ok, I ran several times fsck and it seemed like the file system was very corrupted. I finally formatted the SD card again and now it perfectly works. Thanks for the provided help.
Offline