Search the Community

I have a 400GB sdxc card from SanDisk that refuses to retain any data. (Including the partition table) Windows flat out hates the thing and hangs explorer (3 separate windows machines, one running AME) Linux sees the card, registers it, detects the correct size of the card, assigns it /dev/mmcblk0 and gives no errors when reading and writing to the disk (4 separate computers, using different card readers, running arch, debian, Ubuntu, Manjaro, Gentoo, etc. These distros I tried with unmodified kernels, Linux zen, Linux hardened -- only really messed with the kernels in Garuda arch --) What is weird in Linux though is if I write data from /dev/random to the card using dd (dd if=/dev/random of=/dev/mmcblk0 status=progress) Allowing dd to run for at least a minute before interrupting it. dd reports no errors, but when I go to read back the data (cat /dev/mmcblk0); all that is returned are zeros. I also had tried using dd to put the written data back into a file (dd if=/dev/mmcblk0 of=randomfile) and using a hex viewer shows only zeros were written to the file, again with no errors from dd Looking at dmesg also nets nothing, no errors thrown and everything looking normal. I know this card is almost certainly dead but I would like to find out how and why it is damaged and maybe learn a bit about how MicroSD cards work Something else that would be really helpful would be if someone could show me how to enable debugging on the mmc drivers

I have a SanDisk X400 M.2 2280 256GB chip with windows 10 installed as was booting SSD, my laptop suffered a motherboard failure and will be returning the laptop. However I need to get the data/files on the SSD off and onto another laptop or HDD before I return the laptop. I’m interested in getting the files that would be on it as got a few bits of work on it. How would I go about doing that?

Greetings, In my computer i've a 1TB WD Black HDD with Windows 10 Pro x64 and a 2TB WD Blue HDD with Windows XP Professional x64. I use the 2TB as backup, and since for various reasons my main Windows 10 installation got screwed up not long ago, i had moved all the data to the 2TB drive. Today i needed to access some of the things i had saved in the 2TB drive, but it didn't show up in my computer. I won't easily accept quickly reaching the "it's dead" answer because a similar issue happened 3 years ago, and after reformatting the drive scandisk reported no damaged sectors. The difference this time is i need to recover around 500gb of the data it has, which won't fit in the 1TB even if i recover it. Although the drive is 5 years old by now. Yesterday there was a power failure and my system got suddenly shut down because of it; and i guess since i was writing to it that it might have damaged the filesystem or something on these lines. Opening diskmgmt.exe on windows the drive is there, with it's usual size, but it results as entirely unallocated AND uninitialized. Through diskpart > list disk the drive is there Under linux i tried running testdisk, mount and gparted, none of them even detected the drive. The drive isn't available as a boot option on the bios. Even assuming a recovery tool could access to all the files without damage, i wouldn't have space to put them in unless i buy a new drive... Following this link, using R-Undelete i right-clicked on the drive and chose the S.M.A.R.T. option. All it has to say is "Status: UNKNOWN". R-Undelete also gives me an option "scan for partitions". After 4 hours it only scanned 1.4MB. Am i to assume it's that slow because it's a slow process, or it's really indicative of an hardware-level failure? In any case to prevent any risk i physically detached the drive for now and won't access it until i have something figured out.

Hello everyone, Recently, i accidentally formatted the drive and after that i tried to recover files with some data recovery programs. Even though one of the programs recovered all files, when i try to open any of them, they all seem to be corrupted. My question is, is there any way to recover files from this state or should i just accept it and move on?

Hi guys. My boss has an old Advent laptop (Win 7 32-bit, 2GB RAM, Dual-core) that recently died as the power supply given up on life. (Basically the laptop can charge for a small amount of time and then no matter what, it turns off - I was able to boot it up in safe mode, but even that sometimes crashed on me) I decided to take out the WD3200BEVT (WD 320GB) SATA HDD and try and recover data from it. I got the necessary cable and plugged it into my laptop, however I do not have access to it as I do not have enough "privileges". Do you guys know the proper way to check and recover data from this? I've tried to change the permissions, but it wouldn't allow me. I've also tried to run CHKDSK, but again, I do not have privileges (in both normal cmd and admin cmd). This is what I see in "This PC". image Needless to say, I've never done this kind of data recovery before, so I'm open to all suggestions - however please keep in mind that the HDD works, AFAIK it's not corrupted as I was able to browse when I could boot up my boss' computer for a couple minutes. I can't reformat by any chance as he needs his data. Here's what I tried, in order: I get this message G:\ is not accessible. The request failed due to a fatal device hardware error. I did a new CHKDSK test and got this error: image with this cmd message: image Tried yet another "supposedly" working method and checked that the drive is in "healthy condition", however I am getting the same error so far image Just tried Stellar Data Recovery and after scan completed I got a window popping up saying: No data found. Any help is much appreciated and thank you!

.... Soo CHDSK just viped my 3tb mass storage drive ... I was backing up some data, moved a HDD from my NAS to my PC, disconnected one drive to be able to connect another drive. Restarting my PC to get the drive I just connected to show up, and when the PC booted up CHKDSK wanted to check the drive (I didn't watch it closely enough to cancel in time). When PC booted up after running CHKDSK, the WD 3Tb I just connected, had been assigned the drive name of the drive previously connected to that SATA port. In short -> I disconnected ":1TB#1" -> connected ":WD3Tb" -> restarted the PC -> the 3TB drive previously named ":WD3Tb" had now been renamed to ":1TB#1" and the drive was empty. Already tried some free data recovery tools, but to no avail. I have kept the drive disconnected since the incident. Log file found on the drive: _______________________________________________________________________________________ Checking file system on Q: The type of the file system is NTFS. Volume label is 1 TB # 1. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... Attribute record of type 0x80 and instance tag 0x8 is cross linked starting at 0xb68a9 for possibly 0x41 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x8 in file 0x9 is already in use. Deleting corrupt attribute record (128, $SDS) from file record segment 9. 256 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 276 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... The security data stream is missing from file 0x9. The security data stream size 0x0 should not be less than 0x40000. Deleting an index entry with Id 256 from index $SII of file 9. Deleting an index entry with Id 257 from index $SII of file 9. Deleting an index entry with Id 258 from index $SII of file 9. Deleting an index entry with Id 259 from index $SII of file 9. Deleting an index entry with Id 260 from index $SII of file 9. Deleting an index entry with Id 261 from index $SII of file 9. Deleting an index entry with Id 262 from index $SII of file 9. Deleting an index entry with Id 263 from index $SII of file 9. Deleting an index entry with Id 264 from index $SII of file 9. Deleting an index entry with Id 265 from index $SII of file 9. Deleting an index entry with Id 266 from index $SII of file 9. Deleting an index entry with Id 267 from index $SII of file 9. Deleting an index entry with Id 268 from index $SII of file 9. Deleting an index entry with Id 260 from index $SDH of file 9. Deleting an index entry with Id 267 from index $SDH of file 9. Deleting an index entry with Id 262 from index $SDH of file 9. Deleting an index entry with Id 258 from index $SDH of file 9. Deleting an index entry with Id 266 from index $SDH of file 9. Deleting an index entry with Id 256 from index $SDH of file 9. Deleting an index entry with Id 257 from index $SDH of file 9. Deleting an index entry with Id 261 from index $SDH of file 9. Deleting an index entry with Id 263 from index $SDH of file 9. Deleting an index entry with Id 264 from index $SDH of file 9. Deleting an index entry with Id 265 from index $SDH of file 9. Deleting an index entry with Id 259 from index $SDH of file 9. Deleting an index entry with Id 268 from index $SDH of file 9. Replacing invalid security id with default security id for file 0. Replacing invalid security id with default security id for file 1. Replacing invalid security id with default security id for file 2. Replacing invalid security id with default security id for file 6. Replacing invalid security id with default security id for file 8. Replacing invalid security id with default security id for file 9. Replacing invalid security id with default security id for file 11. Replacing invalid security id with default security id for file 24. Replacing invalid security id with default security id for file 25. Replacing invalid security id with default security id for file 26. Replacing invalid security id with default security id for file 27. Replacing invalid security id with default security id for file 29. Replacing invalid security id with default security id for file 30. Replacing invalid security id with default security id for file 31. Replacing invalid security id with default security id for file 32. Replacing invalid security id with default security id for file 33. Replacing invalid security id with default security id for file 34. Replacing invalid security id with default security id for file 35. Replacing invalid security id with default security id for file 36. 256 file SDs/SIDs processed. Security descriptor verification completed. 10 data files processed. The MFT mirror is different from the MFT. Correcting errors in the Master File Table (MFT) mirror. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 2861586 MB total disk space. 21588 KB in 6 files. 16 KB in 12 indexes. 0 KB in bad sectors. 155371 KB in use by the system. 65536 KB occupied by the log file. 2861414 MB available on disk. 4096 bytes in each allocation unit. 732566271 total allocation units on disk. 732522028 allocation units available on disk. Internal Info: 00 01 00 00 1d 00 00 00 1c 00 00 00 00 00 00 00 ................ 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ _______________________________________________________________________________________ It is not a life or death situation, I have my personal stuff backed up, but a loss of 2.5Tb still stings somewhat :wacko: Any suggestions for software that (doesn't cost a fortune) that could solve this problem? Or any other possible solution? Or should I just suck it up and reformat the drive Appreciate any input from you guys and girls! Hope you all are having a nice weekend!