![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Nazo
2[H]4U
- Joined
- Apr 2, 2002
- Messages
- 3,672
So I was playing around with my old Dingoo A320 trying to get OpenDingux fully up and running since for some reason it has been giving me troubles and next thing I know the system won't start up. I put the 8GB MicroSDHC card in my computer to try to find out why, mostly assuming the kernel or something must be damaged somehow only to find out that the computer won't accept the card. The system more or less stops responding, only getting a bit through here and there. Nothing will touch the card. I can't get it to show up in things like the Panasonic SD formatter or even fdisk in linux. Ok, so I assume the card might theoretically have died just because it was a relatively cheap card and this sort of thing happens and I grab an older 1GB MicroSD and put the necessary stuff on it. It seems to be working fine, so I shut down the A320 and get ready to put stuff onto it to use and next thing I know, THIS card is messed up. Exact same issue. Nothing will see it now, not even linux's fdisk. I've tried using a MicroSDHC-to-SDHC adapter, a MicroSDHC card reader, and another card reader via that MicroSDHC-to-SDHC adapter and all had the same results.
Well, obviously it's basically impossible for two to just happen to fail in a row, one right after the other within such a short time period of each other (it's technically possible, but so statistically unlikely that we can safely call it impossible) so I have to blame the A320 -- or more likely, probably the MiniSD adapter since that's the only thing that has changed (I had that 8GB card in there for a very long time without a single problem ever but I wasn't sure which adapter was which and they probably got switched around while I was working on this problem.)
It's hard to really accept that it could be completely ruined just from whatever caused this, yet nothing seems to be responding at all and, in fact, attempts to access the cards seem to cause lockups. Are they just completely beyond hope? The fact is that I can't really afford to buy memory cards right now and even if I did, what guarantee would I have that it wouldn't just break another even with the right adapter? I'm still not even sure what exactly happened... If it weren't the adapter I'd be buying another just to ruin it too... I know they probably are ruined, but just in case there is anything at all -- perhaps some more advanced program that can get at it where the OS fails because of some error code (I saw something about a "drive_sense" error in the dmesg output once, but I couldn't repeat it since it was too busy trying to keep anything from really responding. Still, this implies to me that it was able to communicate at least somewhat even if the result was hardly positive.) If they can't be saved, I guess that's that, but I'd like to at least try.
Well, obviously it's basically impossible for two to just happen to fail in a row, one right after the other within such a short time period of each other (it's technically possible, but so statistically unlikely that we can safely call it impossible) so I have to blame the A320 -- or more likely, probably the MiniSD adapter since that's the only thing that has changed (I had that 8GB card in there for a very long time without a single problem ever but I wasn't sure which adapter was which and they probably got switched around while I was working on this problem.)
It's hard to really accept that it could be completely ruined just from whatever caused this, yet nothing seems to be responding at all and, in fact, attempts to access the cards seem to cause lockups. Are they just completely beyond hope? The fact is that I can't really afford to buy memory cards right now and even if I did, what guarantee would I have that it wouldn't just break another even with the right adapter? I'm still not even sure what exactly happened... If it weren't the adapter I'd be buying another just to ruin it too... I know they probably are ruined, but just in case there is anything at all -- perhaps some more advanced program that can get at it where the OS fails because of some error code (I saw something about a "drive_sense" error in the dmesg output once, but I couldn't repeat it since it was too busy trying to keep anything from really responding. Still, this implies to me that it was able to communicate at least somewhat even if the result was hardly positive.) If they can't be saved, I guess that's that, but I'd like to at least try.