SD card errors - what to do?
I've just had SD card errors for the first time and don't know what they mean exactly nor how to investigate further. The SD card was in a wildlife camera, which said there was an error. I thought it might have become full. I brought it back to my computer and put it in the card reader. Nothing shows up on screen (it normally opens a dialog box that offers to open my file manager when I insert an SD card). I see repeating blocks of messages in the journal: Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 Jun 25 12:57:54 acer-suse kernel: print_req_error: I/O error, dev sdc, sector 0 Jun 25 12:57:54 acer-suse kernel: Buffer I/O error on dev sdc, logical block 0, async page read I don't really know what these mean. I thought the normal failure mode for SD cards was to go read-only, so I'm a bit lost. Any suggestions to recover the images at least? Or is it totally dead?
Le 25/06/2021 à 14:10, Dave Howorth a écrit :
Any suggestions to recover the images at least? Or is it totally dead?
photorec jdd -- http://dodin.org
On 25.06.21 14:10, Dave Howorth wrote:
I've just had SD card errors for the first time and don't know what they mean exactly nor how to investigate further.
The SD card was in a wildlife camera, which said there was an error. I thought it might have become full. I brought it back to my computer and put it in the card reader. Nothing shows up on screen (it normally opens a dialog box that offers to open my file manager when I insert an SD card).
I see repeating blocks of messages in the journal:
Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 Jun 25 12:57:54 acer-suse kernel: print_req_error: I/O error, dev sdc, sector 0 Jun 25 12:57:54 acer-suse kernel: Buffer I/O error on dev sdc, logical block 0, async page read
I don't really know what these mean. I thought the normal failure mode for SD cards was to go read-only, so I'm a bit lost.
Any suggestions to recover the images at least? Or is it totally dead?
I'm afraid the device is dead. "Hardware Error" meaning "Indicates that the device server detected a non-recoverable hardware failure (e.g., controller failure, device failure, or parity error) while performing the command or during a self test." [https://www.stix.id.au/wiki/SCSI_Sense_Data] You may want to try a different adapter, though, maybe just the contacts are worn/dirty/... Josef -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
On 25/06/2021 14.10, Dave Howorth wrote:
I've just had SD card errors for the first time and don't know what they mean exactly nor how to investigate further.
The SD card was in a wildlife camera, which said there was an error. I thought it might have become full. I brought it back to my computer and put it in the card reader. Nothing shows up on screen (it normally opens a dialog box that offers to open my file manager when I insert an SD card).
I see repeating blocks of messages in the journal:
Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information Jun 25 12:57:54 acer-suse kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 Jun 25 12:57:54 acer-suse kernel: print_req_error: I/O error, dev sdc, sector 0 Jun 25 12:57:54 acer-suse kernel: Buffer I/O error on dev sdc, logical block 0, async page read
I don't really know what these mean. I thought the normal failure mode for SD cards was to go read-only, so I'm a bit lost.
Any suggestions to recover the images at least? Or is it totally dead?
I hope that /dev/sdc is not your hard disk, but the photo card. Whichever it is, is broken. So find out which one it is, and replace it. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Dave Howorth wrote:
I don't really know what these mean. I thought the normal failure mode for SD cards was to go read-only, so I'm a bit lost.
Any suggestions to recover the images at least? Or is it totally dead?
I would try another reader - I have had cards that refused to be read in one laptop, but worked fine in another - maybe even try a camera? I have also had varying experiences with formatting routines - a card could not be read in my laptop, nor formatted, but in my Nikon camera, it could be formatted (vfat), and then worked fine. -- Per Jessen, Zürich (23.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
On Fri, 25 Jun 2021 16:00:13 +0200 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
I don't really know what these mean. I thought the normal failure mode for SD cards was to go read-only, so I'm a bit lost.
Any suggestions to recover the images at least? Or is it totally dead?
I would try another reader - I have had cards that refused to be read in one laptop, but worked fine in another - maybe even try a camera? I have also had varying experiences with formatting routines - a card could not be read in my laptop, nor formatted, but in my Nikon camera, it could be formatted (vfat), and then worked fine.
Thanks everybody so far. Per, yes, I will try it in another camera. Carlos, yes sdc is the dodgy SD card. I'm not that gaga yet! :) Josef, hmm maybe. See below. jdd, Why does it want to be root, to read a device mounted under my ownership? Anyway, I tried to mount the card again and this time it succeeded. But there are some read errors. An ls starts $ ls /run/media/dhoworth/700A-8EF3/DCIM/100_BTCF/ ''$'\036\036\036\036\036\036\036\036''.'$'\036\017' IMG_0031.MP4 IMG_0032.MP4 IMG_0033.MP4 IMG_0034.MP4 IMG_0035.MP4 IMG_0036.MP4 IMG_0037.MP4 IMG_0038.MP4 IMG_0039.MP4 IMG_0040.MP4 IMG_0041.MP4 IMG_0042.MP4 IMG_0043.MP4 IMG_0044.MP4 IMG_0045.MP4 IMG_0046.MP4 IMG_0047.MP4 IMG_0048.MP4 IMG_0049.MP4 IMG_0050.MP4 IMG_0051.MP4 IMG_0052.MP4 IMG_0053.MP4 IMG_0054.MP4 IMG_0055.MP4 IMG_0056.MP4 IMG_0057.MP4 IMG_0058.MP4 IMG_0059.MP4 IMG_0060.MP4 IMG_0061.MP4 IMG_0062.MP4 IMG_0063.MP4 IMG_0064.MP4 IMG_0065.MP4 IMG_0066.MP4 IMG_0067.MP4 IMG_0068.MP4 IMG_0069.MP4 IMG_0070.MP4 IMG_0071.MP4 IMG_0072.MP4 IMG_0073.MP4 IMG_0074.MP4 IMG_0075.MP4 IMG_0076.MP4 IMG_0077.MP4 IMG_0078.MP4 IMG_0079.MP4 IMG_0080.MP4 IMG_0081.MP4 IMG_0082.MP4 IMG_0083.MP4 IMG_0084.MP4 IMG_0085.MP4 IMG_0086.MP4 IMG_0087.MP4 ' '$'\036\036\036\036\036\036\036''.'$'\036\017' çç≈ì ç.µ çç≈═ ç.µ çç ì ç.µ çç┐ ç.µ çç≈ ç.µ çç≈ ç.µ çç≈ ç.µ ╟ç┐ ç.τ etc etc Does photorec work better than e.g. dd? And again, why does it need to be root?
Hello, On Fri, 25 Jun 2021, Dave Howorth wrote:
Anyway, I tried to mount the card again and this time it succeeded. But there are some read errors. An ls starts [..]
First: grab an image of the card with ddrescue or dd_rescue. Then you can work on the image with photorec to recover what was still readable. HTH, -dnh -- Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas N. Adams, Last Chance To See
On 25/06/2021 16.32, Dave Howorth wrote:
On Fri, 25 Jun 2021 16:00:13 +0200 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
...
Thanks everybody so far.
Per, yes, I will try it in another camera.
Carlos, yes sdc is the dodgy SD card. I'm not that gaga yet! :)
Good :-)
Josef, hmm maybe. See below.
jdd, Why does it want to be root, to read a device mounted under my ownership?
Anyway, I tried to mount the card again and this time it succeeded. But there are some read errors. An ls starts
$ ls /run/media/dhoworth/700A-8EF3/DCIM/100_BTCF/ ''$'\036\036\036\036\036\036\036\036''.'$'\036\017' IMG_0031.MP4 IMG_0032.MP4 ... IMG_0087.MP4 ' '$'\036\036\036\036\036\036\036''.'$'\036\017' çç≈ì ç.µ çç≈═ ç.µ çç ì ç.µ çç┐ ç.µ çç≈ ç.µ çç≈ ç.µ çç≈ ç.µ ╟ç┐ ç.τ etc etc
Does photorec work better than e.g. dd? And again, why does it need to be root?
Because it accesses the raw /dev/sdc device, not the mount. As you were able to mount the device, make a copy of the files somewhere else now. Then you will possibly need to do an fsck, but if the card is finished, it may refuse the write operation. Then you would need to make an image of it with dd, and do the fsck on the image, not the original. Finally, photorec might be able to recover some lost photos. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Fri, 25 Jun 2021 15:32:10 +0100 Dave Howorth <dave@howorth.org.uk> wrote:
On Fri, 25 Jun 2021 16:00:13 +0200 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
I don't really know what these mean. I thought the normal failure mode for SD cards was to go read-only, so I'm a bit lost.
Any suggestions to recover the images at least? Or is it totally dead?
I would try another reader - I have had cards that refused to be read in one laptop, but worked fine in another - maybe even try a camera? I have also had varying experiences with formatting routines - a card could not be read in my laptop, nor formatted, but in my Nikon camera, it could be formatted (vfat), and then worked fine.
Thanks everybody so far.
Per, yes, I will try it in another camera.
Carlos, yes sdc is the dodgy SD card. I'm not that gaga yet! :)
Josef, hmm maybe. See below.
jdd, Why does it want to be root, to read a device mounted under my ownership?
Anyway, I tried to mount the card again and this time it succeeded. But there are some read errors. An ls starts
[snip] Just an update to let everybody know the state of play. Since the card is now mountable with errors, it seems one possibility is a dodgy reader in my PC, so I'll get a new USB reader and see whether that works any better to recover the files. I'll let you know what I manage to retrieve if anything once it arrives. In the meantime I contacted the supplier who said they've had other people reporting problems with this particular batch of Integral cards, so they're sending me a replacement SanDisk card.
On 27/06/2021 13.14, Dave Howorth wrote:
On Fri, 25 Jun 2021 15:32:10 +0100 Dave Howorth <> wrote:
Just an update to let everybody know the state of play.
Since the card is now mountable with errors, it seems one possibility is a dodgy reader in my PC, so I'll get a new USB reader and see whether that works any better to recover the files. I'll let you know what I manage to retrieve if anything once it arrives.
Your camera also complained.
In the meantime I contacted the supplier who said they've had other people reporting problems with this particular batch of Integral cards, so they're sending me a replacement SanDisk card.
I would skip on the purchase of a new USB reader, unless you buy a good (I mean better) and reliable one :-D -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (6)
-
Carlos E. R. -
Dave Howorth -
David Haller -
jdd＠dodin.org -
Josef Moellers -
Per Jessen