Data recovery - micro SD “no medium found” after running in Pi 3
up vote
0
down vote
favorite
Earlier today I unplugged my Raspberry Pi 3 after running it for a few hours, then plugged it back in.
After this, the Pi would turn on (steady red light) but would not boot (no flashing green light).
I tried another micro SD in the Pi, and it booted just fine.
So I plugged the micro SD into a Ubuntu 16.04 machine...
~$ ls /dev/sd*
/dev/sda
When unplugged, /dev/sda
disappears, so it must be that. Tried to mount it...
~$ sudo mount /dev/sda /media/usb
After a long delay, mount: no medium found on /dev/sda
.
I then realized the micro SD is probably toast. So I went about installing and using gddrescue
:
~$ sudo apt update
~$ sudo apt install gddrescue
~$ sudo ddrescue -f -n /dev/sda rescue.dd logfile.dd
ddrescue: Can't open input file: No medium found
Output of sudo tail -f /var/log/syslog
when disconnecting then connecting the micro SD:
Dec 11 12:27:08 x kernel: [14878.890383] usb 1-14: USB disconnect, device number 23
Dec 11 12:27:11 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:28 x kernel: [14899.667251] usb 1-14: new high-speed USB device number 24 using xhci_hcd
Dec 11 12:27:29 x mtp-probe: checking bus 1, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14"
Dec 11 12:27:29 x mtp-probe: bus: 1, device: 24 was not an MTP device
Dec 11 12:27:29 x kernel: [14899.815464] usb 1-14: New USB device found, idVendor=1908, idProduct=0226
Dec 11 12:27:29 x kernel: [14899.815465] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec 11 12:27:29 x kernel: [14899.816000] usb-storage 1-14:1.0: USB Mass Storage device detected
Dec 11 12:27:29 x kernel: [14899.816211] scsi host6: usb-storage 1-14:1.0
Dec 11 12:27:30 x kernel: [14900.843636] scsi 6:0:0:0: Direct-Access Generic Mass-Storage 1.11 PQ: 0 ANSI: 2
Dec 11 12:27:30 x kernel: [14900.843924] sd 6:0:0:0: Attached scsi generic sg0 type 0
Dec 11 12:27:32 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:41 x kernel: [14912.437282] sd 6:0:0:0: [sda] Attached SCSI removable disk
Just looking for any insight on what can be done next here. I need to at least get some scripts/config files off the micro SD.
I should add that the SD card got very hot during this process, which tells me it's indeed fried.
boot partitioning usb mount sd-card
New contributor
add a comment |
up vote
0
down vote
favorite
Earlier today I unplugged my Raspberry Pi 3 after running it for a few hours, then plugged it back in.
After this, the Pi would turn on (steady red light) but would not boot (no flashing green light).
I tried another micro SD in the Pi, and it booted just fine.
So I plugged the micro SD into a Ubuntu 16.04 machine...
~$ ls /dev/sd*
/dev/sda
When unplugged, /dev/sda
disappears, so it must be that. Tried to mount it...
~$ sudo mount /dev/sda /media/usb
After a long delay, mount: no medium found on /dev/sda
.
I then realized the micro SD is probably toast. So I went about installing and using gddrescue
:
~$ sudo apt update
~$ sudo apt install gddrescue
~$ sudo ddrescue -f -n /dev/sda rescue.dd logfile.dd
ddrescue: Can't open input file: No medium found
Output of sudo tail -f /var/log/syslog
when disconnecting then connecting the micro SD:
Dec 11 12:27:08 x kernel: [14878.890383] usb 1-14: USB disconnect, device number 23
Dec 11 12:27:11 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:28 x kernel: [14899.667251] usb 1-14: new high-speed USB device number 24 using xhci_hcd
Dec 11 12:27:29 x mtp-probe: checking bus 1, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14"
Dec 11 12:27:29 x mtp-probe: bus: 1, device: 24 was not an MTP device
Dec 11 12:27:29 x kernel: [14899.815464] usb 1-14: New USB device found, idVendor=1908, idProduct=0226
Dec 11 12:27:29 x kernel: [14899.815465] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec 11 12:27:29 x kernel: [14899.816000] usb-storage 1-14:1.0: USB Mass Storage device detected
Dec 11 12:27:29 x kernel: [14899.816211] scsi host6: usb-storage 1-14:1.0
Dec 11 12:27:30 x kernel: [14900.843636] scsi 6:0:0:0: Direct-Access Generic Mass-Storage 1.11 PQ: 0 ANSI: 2
Dec 11 12:27:30 x kernel: [14900.843924] sd 6:0:0:0: Attached scsi generic sg0 type 0
Dec 11 12:27:32 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:41 x kernel: [14912.437282] sd 6:0:0:0: [sda] Attached SCSI removable disk
Just looking for any insight on what can be done next here. I need to at least get some scripts/config files off the micro SD.
I should add that the SD card got very hot during this process, which tells me it's indeed fried.
boot partitioning usb mount sd-card
New contributor
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Earlier today I unplugged my Raspberry Pi 3 after running it for a few hours, then plugged it back in.
After this, the Pi would turn on (steady red light) but would not boot (no flashing green light).
I tried another micro SD in the Pi, and it booted just fine.
So I plugged the micro SD into a Ubuntu 16.04 machine...
~$ ls /dev/sd*
/dev/sda
When unplugged, /dev/sda
disappears, so it must be that. Tried to mount it...
~$ sudo mount /dev/sda /media/usb
After a long delay, mount: no medium found on /dev/sda
.
I then realized the micro SD is probably toast. So I went about installing and using gddrescue
:
~$ sudo apt update
~$ sudo apt install gddrescue
~$ sudo ddrescue -f -n /dev/sda rescue.dd logfile.dd
ddrescue: Can't open input file: No medium found
Output of sudo tail -f /var/log/syslog
when disconnecting then connecting the micro SD:
Dec 11 12:27:08 x kernel: [14878.890383] usb 1-14: USB disconnect, device number 23
Dec 11 12:27:11 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:28 x kernel: [14899.667251] usb 1-14: new high-speed USB device number 24 using xhci_hcd
Dec 11 12:27:29 x mtp-probe: checking bus 1, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14"
Dec 11 12:27:29 x mtp-probe: bus: 1, device: 24 was not an MTP device
Dec 11 12:27:29 x kernel: [14899.815464] usb 1-14: New USB device found, idVendor=1908, idProduct=0226
Dec 11 12:27:29 x kernel: [14899.815465] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec 11 12:27:29 x kernel: [14899.816000] usb-storage 1-14:1.0: USB Mass Storage device detected
Dec 11 12:27:29 x kernel: [14899.816211] scsi host6: usb-storage 1-14:1.0
Dec 11 12:27:30 x kernel: [14900.843636] scsi 6:0:0:0: Direct-Access Generic Mass-Storage 1.11 PQ: 0 ANSI: 2
Dec 11 12:27:30 x kernel: [14900.843924] sd 6:0:0:0: Attached scsi generic sg0 type 0
Dec 11 12:27:32 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:41 x kernel: [14912.437282] sd 6:0:0:0: [sda] Attached SCSI removable disk
Just looking for any insight on what can be done next here. I need to at least get some scripts/config files off the micro SD.
I should add that the SD card got very hot during this process, which tells me it's indeed fried.
boot partitioning usb mount sd-card
New contributor
Earlier today I unplugged my Raspberry Pi 3 after running it for a few hours, then plugged it back in.
After this, the Pi would turn on (steady red light) but would not boot (no flashing green light).
I tried another micro SD in the Pi, and it booted just fine.
So I plugged the micro SD into a Ubuntu 16.04 machine...
~$ ls /dev/sd*
/dev/sda
When unplugged, /dev/sda
disappears, so it must be that. Tried to mount it...
~$ sudo mount /dev/sda /media/usb
After a long delay, mount: no medium found on /dev/sda
.
I then realized the micro SD is probably toast. So I went about installing and using gddrescue
:
~$ sudo apt update
~$ sudo apt install gddrescue
~$ sudo ddrescue -f -n /dev/sda rescue.dd logfile.dd
ddrescue: Can't open input file: No medium found
Output of sudo tail -f /var/log/syslog
when disconnecting then connecting the micro SD:
Dec 11 12:27:08 x kernel: [14878.890383] usb 1-14: USB disconnect, device number 23
Dec 11 12:27:11 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:28 x kernel: [14899.667251] usb 1-14: new high-speed USB device number 24 using xhci_hcd
Dec 11 12:27:29 x mtp-probe: checking bus 1, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14"
Dec 11 12:27:29 x mtp-probe: bus: 1, device: 24 was not an MTP device
Dec 11 12:27:29 x kernel: [14899.815464] usb 1-14: New USB device found, idVendor=1908, idProduct=0226
Dec 11 12:27:29 x kernel: [14899.815465] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec 11 12:27:29 x kernel: [14899.816000] usb-storage 1-14:1.0: USB Mass Storage device detected
Dec 11 12:27:29 x kernel: [14899.816211] scsi host6: usb-storage 1-14:1.0
Dec 11 12:27:30 x kernel: [14900.843636] scsi 6:0:0:0: Direct-Access Generic Mass-Storage 1.11 PQ: 0 ANSI: 2
Dec 11 12:27:30 x kernel: [14900.843924] sd 6:0:0:0: Attached scsi generic sg0 type 0
Dec 11 12:27:32 x colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 12:27:41 x kernel: [14912.437282] sd 6:0:0:0: [sda] Attached SCSI removable disk
Just looking for any insight on what can be done next here. I need to at least get some scripts/config files off the micro SD.
I should add that the SD card got very hot during this process, which tells me it's indeed fried.
boot partitioning usb mount sd-card
boot partitioning usb mount sd-card
New contributor
New contributor
New contributor
asked Dec 11 at 19:30
star_trac
11
11
New contributor
New contributor
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
star_trac 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%2faskubuntu.com%2fquestions%2f1100136%2fdata-recovery-micro-sd-no-medium-found-after-running-in-pi-3%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
star_trac is a new contributor. Be nice, and check out our Code of Conduct.
star_trac is a new contributor. Be nice, and check out our Code of Conduct.
star_trac is a new contributor. Be nice, and check out our Code of Conduct.
star_trac is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2faskubuntu.com%2fquestions%2f1100136%2fdata-recovery-micro-sd-no-medium-found-after-running-in-pi-3%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