Question I need to recover data from a corrupted SD card ?

[captaincandellight]

I have quite a few photographs and short videos on a corrupted SD card which I have to recover. When I insert the SD card in the card reader I get the error message from Windows taskbar notifications that says - "There's a problem with this drive. Scan the drive now and fix it". I still can enter and see the SD card contents and folders, but when I double-click a photograph to view it, Windows photo viewer cannot open it. I am insted presented with a black blank screen.

Also I am unable to copy the photographs to my computer. While trying to copy them to my computer and after bypassing the error messages I can see the copied file on my computers folder before it disappears within a few minutes. When I try to copy them to my computer I get the following error messages -

a) "Can't read from the source file or disk".
b) "An error occured applying attributes to the file" - "The system cannot find the file specified".

I am also attaching images of the errors received while accessing, copying contents from SD card and showing that I can still open and see the contents inside -

 

[Ralston18]

Will the current card reader read other cards and files?

Do you have another known working card reader?

Also:

Open the Disk Management window and expand so all can be seen.

Take a screenshot and post accordingly.

I am wondering about the double "Drive E:" in the 3rd screen....

 

[captaincandellight]

Will the current card reader read other cards and files?

Yes I have another MMC card and it reads fine.

Do you have another known working card reader?

No.

Open the Disk Management window and expand so all can be seen.

 

[captaincandellight]

I am wondering about the double "Drive E:" in the 3rd screen....

Even I am finding it strange to see two E drives in my file explorer.

 

[Ralston18]

Take another look without using Explorer.

Powershell Get-Disk

https://shellgeek.com/powershell-get-disk-information/

Get cmdlets are safe. They only get information/data and present it.

The results may reveal something astray.

 

[captaincandellight]

Should I run PowerShell in administrator mode for this ?

 

[Ralston18]

Try local first.

Use administrator mode only if Powershell requires you to do so.

Gets are safe and within themselves make no changes. Local should work.

Caveat being that you do not have the necessary rights to even run Powershell. That is a different matter.

Problems can occur with longer cmdlets or scripts that start out with a Get- then "pipe" the results into additional cmdlets that, in turn, make a change.

For example, a Get that looks for a registry entry and if not found or is other than expected then uses another cmdlet to force a registry change.

= = = =

Under the hood many utilities and apps use Microsoft's own tools to dig out details and then simply repackage the results to be more end user friendly, look prettier, or more techy...

 

[JayGau]

Try Testdisk. If it can't read the partition or extract the data, try PhotoRec.

Testdisk extracts the files and keeps the filenames and folder structure. But the partition has to be readable.

PhotoRec is a last resort solution. It can extract files from even corrupted and unreadable devices, but it can't preserve the filenames and folders, but at least you get your files back.

 

[kerberos_20]

I am wondering about the double "Drive E:" in the 3rd screen....

that seems to be normal windows behaviour for external drives

https://imgur.com/naEugVy

View: https://imgur.com/naEugVy

 

[Ralston18]

An A: drive and two F: drives. Not two E: 's as before....

A: should not be being used at all.

I Ireally do not understand how the system would resolve a request to read and/or write to the F: drive.

It does appear that the "first" F: drive is indented. and thus a drive on This PC.

And the second F: being the external drive.

That image does not match the first presentation of Disk Management.

I did a google search using "RTL_UL". Resulted in a number of links about "phantom drives". Known issue - going quite a ways back but current.

@captaincandellight

My suggestion is to do the same search and read though the results. Revise the search criteria as necessary to match your build and drives.

The solution may vary with the details.

Overall, just ensure that each drive is uniquely named and lettered. Check drive pathnames as well.

 

[captaincandellight]

Take another look without using Explorer.

Powershell Get-Disk

https://shellgeek.com/powershell-get-disk-information/

Take another look without using Explorer.

Powershell Get-Disk

https://shellgeek.com/powershell-get-disk-information/

Get cmdlets are safe. They only get information/data and present it.

The results may reveal something astray.

What I am noticing since yesterday is that Windows is trying to repair the drive E on the booth screen but within seconds of starting the repair procidure it gets aborted at 0%. I did all the six Powershell cmdlets. I did not find anything wrong on the five cmdlets no warning or errors but I did get a health status of - warning and operational status as - full repair needed in the Get-Volume cmdlet. I am posting images of all my six cmdlets please have a look.

 

[Ralston18]

Thinking about the Get-Volume warning.....

Make and model card reader?

Make and model SD Card? 4GB/FAT32 being known and shown correctly?

Did that card come out of a camera? If so, make and model camera?

And the photos were indeed taken in May, 2008?

Which suggests that the SD Card around 17 years old - is that correct?

 

[captaincandellight]

Thinking about the Get-Volume warning.....

Make and model card reader?

Make and model SD Card? 4GB/FAT32 being known and shown correctly?

Did that card come out of a camera? If so, make and model camera?

And the photos were indeed taken in May, 2008?

Which suggests that the SD Card around 17 years old - is that correct?

Make and model card reader?

Card reader is unbranded multi card reader.

Make and model SD Card?

It is - Transcend SDHC TM4

Did that card come out of a camera? If so, make and model camera?

"Exactly"
Make is - Kodak
Model number is - KKL-M883(B)

Which suggests that the SD Card around 17 years old - is that correct?

"Exactly to the point"

 

[Ralston18]

Corruption is certainly a possibility.

However, I would wonder if there is some proprietary issue: meaning Kodak camera and needing a Kodak card reader.

There was a thread along those lines not too long ago.

My thought is to move this thread to Digital Cameras - may be a camera enthusiast in that Forum would could offer additional insight and suggestions.

 

[captaincandellight]

However, I would wonder if there is some proprietary issue: meaning Kodak camera and needing a Kodak card reader.

No there is no proprietary issue. This SD card was bought seperately from another retail store and it used to work fine with my PC card readers till 2014.

 

[Ralston18]

Not sure what to directly suggest.

I am going to move this thread to Digitial Camera's.

There is quite a bit of detail to be read in this thread and someone may recognize one or more issues that can be looked into.

 

[captaincandellight]

Not sure what to directly suggest.

I am going to move this thread to Digitial Camera's.

There is quite a bit of detail to be read in this thread and someone may recognize one or more issues that can be looked into.

This is not a digital camera issue it is an SD card corruption. It makes no sense moving this thread to digital camera's and my camera does not even work.

 

[Ralston18]

Your question clearly includes "corrupted SD card".

Something that many SD card users, including camera users, have had to deal with.

There is also this: "Windows photo viewer cannot open it. I am insted presented with a black blank screen."

Someone may be aware of another viewer or photo recovery app worth trying.

I suggest allowing a few days in Digital Cameras. The thread can always be moved back to Storage.