1 |
On Wed, Dec 29, 2021 at 12:15 PM Dale <rdalek1967@×××××.com> wrote: |
2 |
> |
3 |
> Mark Knecht wrote: |
4 |
> > On Wed, Dec 29, 2021 at 10:14 AM Dale <rdalek1967@×××××.com> wrote: |
5 |
> >> Mark Knecht wrote: |
6 |
> >>> <SNIP> |
7 |
> >>>> So while rare, it's not just me. ;-) I've had cards fail by just plain |
8 |
> >>>> refusing not to mount at all, mounting read only and such. I've never |
9 |
> >>>> had one to fail like this tho. I guess if this was some sort of |
10 |
> >>>> sensitive files, I'd have to put it in a shredder or take a pair of |
11 |
> >>>> scissors to it. LOL |
12 |
> >>>> |
13 |
> >>>> I ordered 6 new cards as replacements. They came in yesterday. Like I |
14 |
> >>>> said, I wouldn't trust that card even if it started working again. So, |
15 |
> >>>> off to the trash the weird card goes. Now I just have to wonder why dd |
16 |
> >>>> and such didn't report problems. :/ |
17 |
> >>>> |
18 |
> >>>> Thanks to all for the info. Interesting. |
19 |
> >>>> |
20 |
> >>>> Dale |
21 |
> >>>> |
22 |
> >>>> :-) :-) |
23 |
> >>>> |
24 |
> >>> Actually, it's possible that it failed this way by design. What if the |
25 |
> >>> card recognized that it's in some sort of a wear out condition and |
26 |
> >>> just shut off new writes? One might see it as a failure but a |
27 |
> >>> different view is as a potential opportunity to retrieve data before |
28 |
> >>> it's gone. |
29 |
> >>> |
30 |
> >>> You might want to check out this tool: |
31 |
> >>> |
32 |
> >>> https://github.com/BertoldVdb/sdtool |
33 |
> >>> |
34 |
> >>> which advertises that it can view, set and reset the write protection |
35 |
> >>> status of an SD card. Can't hurt if you're committed to throwing the |
36 |
> >>> device in the trash can anyway. (Well, it could possibly hose your |
37 |
> >>> system if you use it incorrectly or if it has bugs, but that's true |
38 |
> >>> about all software, right?) ;-) |
39 |
> >>> |
40 |
> >>> But at least you could view the status of the card. |
41 |
> >>> |
42 |
> >>> Cheers, |
43 |
> >>> Mark |
44 |
> >>> |
45 |
> >>> |
46 |
> >> |
47 |
> >> I downloaded sdtool but I don't have the required devices in /dev to use |
48 |
> >> it. In the readme it says not to use /dev/sd* but to use /dev/mmcblk*. |
49 |
> >> It seems my card reader doesn't connect in a way for those to be |
50 |
> >> created. Would have been nice just to see what it does tho. I still |
51 |
> >> wouldn't trust it of course but being curious . . . . |
52 |
> >> |
53 |
> >> By the way, the card is a Sandisk which has a fairly good reputation. |
54 |
> >> It is possible that it failed in the best way it could. On the positive |
55 |
> >> side, it did fail in a way that the files could be recovered. That's |
56 |
> >> always a good thing. It's certainly better than failing with no way to |
57 |
> >> get the files. |
58 |
> >> |
59 |
> >> Dale |
60 |
> > OK, sorry it's not easy. I suppose now that you are using some sort of |
61 |
> > USB bridge for reading your SD cards? That probably makes it show up |
62 |
> > as a standard /dev/sd device like other USB drives. |
63 |
> > |
64 |
> > I may be wrong, and it might not help you, but I think /dev/mmc is |
65 |
> > enabled through the MMC_BLOCK option in the kernel, but even if you |
66 |
> > enable that it may not change things if you have a USB bridge in the |
67 |
> > way. |
68 |
> > |
69 |
> > On Windows there are some partition editors that show the state of |
70 |
> > these bits. I haven't looked for a standard Linux partition editor |
71 |
> > that does that but it's probably out there somewhere if you go |
72 |
> > hunting. |
73 |
> > |
74 |
> > If you own a DSLR that supports whatever size SD card you are using |
75 |
> > then it probably has a way to write protect cards while in the camera. |
76 |
> > However if it's just a web cam that you're using it probably doesn't |
77 |
> > but check the documentation. |
78 |
> > |
79 |
> > Good luck, |
80 |
> > Mark |
81 |
> > |
82 |
> > |
83 |
> |
84 |
> |
85 |
> Those deer trail cameras are somewhat cheap, ish. Some of them don't |
86 |
> even have a format option. I have a old camera that the IR sensor |
87 |
> doesn't work on, it never knows something is there to take pictures of |
88 |
> so it does nothing. Anyway, I use it to format cards with since most |
89 |
> all trail cameras use the same format type and directory tree. One |
90 |
> partition and vfat. Basically, it is really simple and not a lot of |
91 |
> options. |
92 |
> |
93 |
> I use a card reader that hooks up via USB. It's one of those multi |
94 |
> reader thingys. It's been a pretty good one but it isn't a real |
95 |
> expensive one either. Given I got the data off and plan to trash it |
96 |
> anyway, it's not worth recompiling a kernel, rebooting and then hoping |
97 |
> it will have the right device thingys. |
98 |
> |
99 |
> This thread has been interesting tho. At least I know that a Sandisk |
100 |
> card at least tries to fail in a way that I can get the data off that |
101 |
> did get written to the card. Hey, that's a lot better than some I |
102 |
> guess. :-D I've had some other brands that when they die, they dead. |
103 |
> You get nothing at all. |
104 |
> |
105 |
> Dale |
106 |
> |
107 |
> :-) :-) |
108 |
> |
109 |
|
110 |
It's too bad that the little app I pointed you at doesn't work on your |
111 |
setup. I'm going to look around for something more generic. |
112 |
|
113 |
Keep in mind that the 'failure', if that's what it is, could be in |
114 |
your trail camera if it glitched and set the read only protection in |
115 |
the card by accident, or possibly something happened in the USB |
116 |
bridge. I think you'd possibly be better served in the long run by |
117 |
sticking this SD in a plastic bag and saving it until we can find a |
118 |
way to check it out more. Won't cost you anything to throw it away |
119 |
next year. |
120 |
|
121 |
Happy New Year. Hope you get lots more fun trail camera pictures! |
122 |
|
123 |
Cheers, |
124 |
Mark |