But I'd consider the controller went stupid for a reason, and the most likely reason is shitty NAND. Some try reviving flash drives using ChipGenius and so called MPtools that can often be found on Chinese and Russian websites dedicated to this topic. If this were a situation where you need to data from this device, the NAND can be 'dumped' without interference from the controller. Some data recovery engineers I know refer to this as 'controller just went stupid'. Your formatting may have just pushed it into such a state. It's not uncommon that at some 'threshold' the amount of errors becomes to overwhelming and the software (which firmware is) simply crashes and stops responding to host commands like 'ID yourself please!'. Limited in the sense that compared to their big brothers, the SSD, they're less complex and less money is invested in them to be fool-proof. If you do not find this a satisfactory answer I have a second hypothesis: Flash Drive controllers tend to be fairly limited. Given the fact that the device is close to a decade old it seems to me the most logical explanation. For most if not all flash drives it is fact that the firmware is stored on the NAND itself and thus is also subject to this data bleed.Īt some point, it's a matter of when not if, the firmware corrupts and the controller will be unable to load it during boot (yes, it boots). Number one reason for this is NAND degradation: NAND bleeds data, this is a fact of life. does not appear in Disk Management or it does appear but with a reduced capacity then it can not be salvaged. As a rule of thumb, if a USB flash drive, memory card, Media player that acts as flash drive, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |