Corrupted SD card is readonly and not mounting
I'm having issues trying to recover a corrupted micro-SD card (not the data, just the card). I think it was formated to be part of the internal storage of an Android phone when that was an option.
# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 8F38-5495 /boot/efi
├─sda2 ext4 1d8431cf-f298-40af-be5d-413510537953 /boot
└─sda3 LVM2_mem mjbdHc-7AHE-LwUO-IlCo-chqH-EVhA-BVN0i4
├─fedora-root ext4 d38fec65-d7d1-40e2-9d16-dcbc0dcd6330 /
├─fedora-swap swap 6d365505-5e51-4bd5-8a93-bcd56ed1945d [SWAP]
└─fedora-home ext4 3f42f95e-85ce-44a6-9abf-474bf5ae3ab6 /home
sdb
├─sdb1
└─sdb2
-
# fdisk -l /dev/sdb
Disk /dev/sdb: 29.7 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 69704183-D789-43CC-A52A-6B69A888EA09
Device Start End Sectors Size Type
/dev/sdb1 2048 34815 32768 16M unknown
/dev/sdb2 34816 62333918 62299103 29.7G unknown
I tried fdisk /dev/sdb
, it yields:
fdisk: cannot open /dev/sdb: Read-only file system
I checked the adapter and is not locked. I tried mount --options remount,rw /dev/sdb
and it says:
mount: /dev/sdb: mount point not mounted or bad option.
without the remount option:
mount: /dev/sdb: can't find in /etc/fstab.
so apparently it's not mounted but still read only? anyway mount /dev/sdb1 /mnt/
does not yield an assertive error message:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
Another output I got from reading stuff on the internet:
# e2fsck -f -n /dev/sdb
e2fsck 1.44.3 (10-July-2018)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a gpt partition table in /dev/sdb
also tried both variants suggested and got the same output.
I'm not sure how to proceed as I can't get the card mounted (tried several filesystems) or even remove the read only condition. Any ideas?
linux android fdisk sd-card udisks
New contributor
add a comment |
I'm having issues trying to recover a corrupted micro-SD card (not the data, just the card). I think it was formated to be part of the internal storage of an Android phone when that was an option.
# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 8F38-5495 /boot/efi
├─sda2 ext4 1d8431cf-f298-40af-be5d-413510537953 /boot
└─sda3 LVM2_mem mjbdHc-7AHE-LwUO-IlCo-chqH-EVhA-BVN0i4
├─fedora-root ext4 d38fec65-d7d1-40e2-9d16-dcbc0dcd6330 /
├─fedora-swap swap 6d365505-5e51-4bd5-8a93-bcd56ed1945d [SWAP]
└─fedora-home ext4 3f42f95e-85ce-44a6-9abf-474bf5ae3ab6 /home
sdb
├─sdb1
└─sdb2
-
# fdisk -l /dev/sdb
Disk /dev/sdb: 29.7 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 69704183-D789-43CC-A52A-6B69A888EA09
Device Start End Sectors Size Type
/dev/sdb1 2048 34815 32768 16M unknown
/dev/sdb2 34816 62333918 62299103 29.7G unknown
I tried fdisk /dev/sdb
, it yields:
fdisk: cannot open /dev/sdb: Read-only file system
I checked the adapter and is not locked. I tried mount --options remount,rw /dev/sdb
and it says:
mount: /dev/sdb: mount point not mounted or bad option.
without the remount option:
mount: /dev/sdb: can't find in /etc/fstab.
so apparently it's not mounted but still read only? anyway mount /dev/sdb1 /mnt/
does not yield an assertive error message:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
Another output I got from reading stuff on the internet:
# e2fsck -f -n /dev/sdb
e2fsck 1.44.3 (10-July-2018)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a gpt partition table in /dev/sdb
also tried both variants suggested and got the same output.
I'm not sure how to proceed as I can't get the card mounted (tried several filesystems) or even remove the read only condition. Any ideas?
linux android fdisk sd-card udisks
New contributor
The following link should work with memory cards as well as with USB pendrives. It helps you analyze the problem, and if you are lucky solve it (revive your SD card). Can't format my usb drive. I have already tried with mkdosfs and gparted
– sudodus
2 mins ago
add a comment |
I'm having issues trying to recover a corrupted micro-SD card (not the data, just the card). I think it was formated to be part of the internal storage of an Android phone when that was an option.
# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 8F38-5495 /boot/efi
├─sda2 ext4 1d8431cf-f298-40af-be5d-413510537953 /boot
└─sda3 LVM2_mem mjbdHc-7AHE-LwUO-IlCo-chqH-EVhA-BVN0i4
├─fedora-root ext4 d38fec65-d7d1-40e2-9d16-dcbc0dcd6330 /
├─fedora-swap swap 6d365505-5e51-4bd5-8a93-bcd56ed1945d [SWAP]
└─fedora-home ext4 3f42f95e-85ce-44a6-9abf-474bf5ae3ab6 /home
sdb
├─sdb1
└─sdb2
-
# fdisk -l /dev/sdb
Disk /dev/sdb: 29.7 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 69704183-D789-43CC-A52A-6B69A888EA09
Device Start End Sectors Size Type
/dev/sdb1 2048 34815 32768 16M unknown
/dev/sdb2 34816 62333918 62299103 29.7G unknown
I tried fdisk /dev/sdb
, it yields:
fdisk: cannot open /dev/sdb: Read-only file system
I checked the adapter and is not locked. I tried mount --options remount,rw /dev/sdb
and it says:
mount: /dev/sdb: mount point not mounted or bad option.
without the remount option:
mount: /dev/sdb: can't find in /etc/fstab.
so apparently it's not mounted but still read only? anyway mount /dev/sdb1 /mnt/
does not yield an assertive error message:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
Another output I got from reading stuff on the internet:
# e2fsck -f -n /dev/sdb
e2fsck 1.44.3 (10-July-2018)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a gpt partition table in /dev/sdb
also tried both variants suggested and got the same output.
I'm not sure how to proceed as I can't get the card mounted (tried several filesystems) or even remove the read only condition. Any ideas?
linux android fdisk sd-card udisks
New contributor
I'm having issues trying to recover a corrupted micro-SD card (not the data, just the card). I think it was formated to be part of the internal storage of an Android phone when that was an option.
# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 8F38-5495 /boot/efi
├─sda2 ext4 1d8431cf-f298-40af-be5d-413510537953 /boot
└─sda3 LVM2_mem mjbdHc-7AHE-LwUO-IlCo-chqH-EVhA-BVN0i4
├─fedora-root ext4 d38fec65-d7d1-40e2-9d16-dcbc0dcd6330 /
├─fedora-swap swap 6d365505-5e51-4bd5-8a93-bcd56ed1945d [SWAP]
└─fedora-home ext4 3f42f95e-85ce-44a6-9abf-474bf5ae3ab6 /home
sdb
├─sdb1
└─sdb2
-
# fdisk -l /dev/sdb
Disk /dev/sdb: 29.7 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 69704183-D789-43CC-A52A-6B69A888EA09
Device Start End Sectors Size Type
/dev/sdb1 2048 34815 32768 16M unknown
/dev/sdb2 34816 62333918 62299103 29.7G unknown
I tried fdisk /dev/sdb
, it yields:
fdisk: cannot open /dev/sdb: Read-only file system
I checked the adapter and is not locked. I tried mount --options remount,rw /dev/sdb
and it says:
mount: /dev/sdb: mount point not mounted or bad option.
without the remount option:
mount: /dev/sdb: can't find in /etc/fstab.
so apparently it's not mounted but still read only? anyway mount /dev/sdb1 /mnt/
does not yield an assertive error message:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
Another output I got from reading stuff on the internet:
# e2fsck -f -n /dev/sdb
e2fsck 1.44.3 (10-July-2018)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a gpt partition table in /dev/sdb
also tried both variants suggested and got the same output.
I'm not sure how to proceed as I can't get the card mounted (tried several filesystems) or even remove the read only condition. Any ideas?
linux android fdisk sd-card udisks
linux android fdisk sd-card udisks
New contributor
New contributor
edited 6 mins ago
peterh
4,32592957
4,32592957
New contributor
asked 5 hours ago
vlizanavlizana
1123
1123
New contributor
New contributor
The following link should work with memory cards as well as with USB pendrives. It helps you analyze the problem, and if you are lucky solve it (revive your SD card). Can't format my usb drive. I have already tried with mkdosfs and gparted
– sudodus
2 mins ago
add a comment |
The following link should work with memory cards as well as with USB pendrives. It helps you analyze the problem, and if you are lucky solve it (revive your SD card). Can't format my usb drive. I have already tried with mkdosfs and gparted
– sudodus
2 mins ago
The following link should work with memory cards as well as with USB pendrives. It helps you analyze the problem, and if you are lucky solve it (revive your SD card). Can't format my usb drive. I have already tried with mkdosfs and gparted
– sudodus
2 mins ago
The following link should work with memory cards as well as with USB pendrives. It helps you analyze the problem, and if you are lucky solve it (revive your SD card). Can't format my usb drive. I have already tried with mkdosfs and gparted
– sudodus
2 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
vlizana is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494331%2fcorrupted-sd-card-is-readonly-and-not-mounting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
vlizana is a new contributor. Be nice, and check out our Code of Conduct.
vlizana is a new contributor. Be nice, and check out our Code of Conduct.
vlizana is a new contributor. Be nice, and check out our Code of Conduct.
vlizana is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494331%2fcorrupted-sd-card-is-readonly-and-not-mounting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The following link should work with memory cards as well as with USB pendrives. It helps you analyze the problem, and if you are lucky solve it (revive your SD card). Can't format my usb drive. I have already tried with mkdosfs and gparted
– sudodus
2 mins ago