<span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">This would explain the past corruption of my CF and SD cards on Windows. I just thought windows was crappy or I was messing something up. Good thing I have my Photo Album (digikam) on my Linux PC. </span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">
<br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;"><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">As per the SD card being over-written, there is a small slider on the SD card which locks the SD card from being written. I use it whenever I print out pictures at a Kiosk.</span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">
<br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;"><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">Note: This months' Linux Format LXF131 has done a "Roundup" on Photo Managers. Its a good read. If anyone needs that section, I can share the PDF.</span> <br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">
<br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;"><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">-GGR</span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;" clear="all">
<br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;"><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">--</span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;"><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">Rajiv G Gunja</span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">
<span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">Blog: <a href="http://ossrocks.blogspot.com">http://ossrocks.blogspot.com</a></span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">
<br><br><div class="gmail_quote">On 9 April 2010 20:30, Bryan J Smith <span dir="ltr"><<a href="mailto:b.j.smith@ieee.org">b.j.smith@ieee.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
FYI, my warning prior was to those who might try to dd if=/dev/zero<br>
of=device, not that you did such.<br>
<br>
The BB command you utilized likely didn't wipe anything but a<br>
key block (like the root of FAT filesystem). All of your data<br>
is likely intact, just removed from any indexing from that key block.<br>
In general many devices can be picky on the format, and are best<br>
formatted by the device before use. E.g., I only use my SDHC<br>
cards for my dSLR in my one dSLR brand/firmware and don't<br>
rotate them between other devices, other than for Linux<br>
to read. In fact, because Linux can do read-only mounts - while<br>
Windows can't - I always use such after seeing other people<br>
shoot and then Windows corrupt a FAT filesystem SD it didn't<br>
understand proper.<br>
<br>
It keeps me from getting burned at least. Although anytime<br>
you start filling up a NAND device, expect failures shortly afterwards.<br>
It's especially frustrating for users when their device has<br>
reached the point where there are fewer blocks left that<br>
have not reached the failure tolerance than the device reports<br>
for allocation. I've seen that many times myself, and it's funny<br>
to show the user with a vendor tool (rare these days, and most<br>
don't offer such tools now, every little off-shoot/whitebox<br>
SDHC, CF, USB, etc... NAND) that the device is only 70% usable<br>
from it's reported size.<br>
<div class="im"><br>
--<br>
Bryan J Smith - mailto:<a href="mailto:b.j.smith@ieee.org">b.j.smith@ieee.org</a><br>
<a href="http://www.linkedin.com/in/bjsmith" target="_blank">http://www.linkedin.com/in/bjsmith</a><br>
Sent via BlackBerry from T-Mobile<br>
<br>
<br>
-----Original Message-----<br>
</div><div><div></div><div class="h5">From: "Bryan J Smith" <<a href="mailto:b.j.smith@ieee.org">b.j.smith@ieee.org</a>><br>
Date: Fri, 9 Apr 2010 23:30:10<br>
To: James Ewing Cottrell 3rd<JECottrell3@Comcast.NET>; <<a href="mailto:calug-bounces@unknownlamer.org">calug-bounces@unknownlamer.org</a>>; Rajiv Gunja<<a href="mailto:opn.src.rocks@gmail.com">opn.src.rocks@gmail.com</a>><br>
Cc: CALUG<<a href="mailto:calug@unknownlamer.org">calug@unknownlamer.org</a>><br>
Subject: Re: [CALUG] Can Media cards have bad blocks?<br>
<br>
All commodity NAND blocks have bad cells from virtually day 1.<br>
Within 1,000 writes, they will be unreliable. These are the reality<br>
of the technology today. They are also normally very slow at<br>
writes, but techniques are used to sychronize commits in the<br>
circuits.<br>
Access times are much better than disk, but still poor next<br>
to actual DRAM (let alone SRAM). NAND != RAM, no matter how<br>
much people assume otherwise.<br>
<br>
--<br>
Bryan J Smith - mailto:<a href="mailto:b.j.smith@ieee.org">b.j.smith@ieee.org</a><br>
<a href="http://www.linkedin.com/in/bjsmith" target="_blank">http://www.linkedin.com/in/bjsmith</a><br>
Sent via BlackBerry from T-Mobile<br>
<br>
<br>
-----Original Message-----<br>
From: James Ewing Cottrell 3rd <JECottrell3@Comcast.NET><br>
Date: Fri, 09 Apr 2010 18:42:04<br>
To: Rajiv Gunja<<a href="mailto:opn.src.rocks@gmail.com">opn.src.rocks@gmail.com</a>><br>
Cc: CALUG<<a href="mailto:calug@unknownlamer.org">calug@unknownlamer.org</a>><br>
Subject: Re: [CALUG] Can Media cards have bad blocks?<br>
<br>
If you asked me 8 days ago I would have said...<br>
<br>
No. Flash drive always record all data accurately.<br>
<br>
But the other 364 days a years....<br>
<br>
If a device can have Good Blocks, it can have Bad Blocks.<br>
<br>
JIM<br>
<br>
Rajiv Gunja wrote:<br>
> Hello,<br>
> I have been using my Mobile to listen to Music and Audio books rather<br>
> than carry around both my Mobile and iPod. The other advantage being, I<br>
> have a stereo bluetooth headset for my Mobile.<br>
><br>
> On the media card 8GB MicroSD, There are folders created by my<br>
> BlackBerry. I have created couple of folders on them too, within the<br>
> directories it has created.<br>
><br>
> Under Documents, I have created Audiobooks and eBooks. For some reason,<br>
> if I copy my MP3s to "Music" folder created by the BB OS, BB hangs and<br>
> becomes very slow and I have remove the SD card to make it respond.<br>
> Whereas if I copy those same MP3 files to "Audiobook" directory, it<br>
> works fine and plays fine too.<br>
><br>
> Is this because there are bad block or whatever is holding the<br>
> information? Is it time to buy another card?<br>
><br>
> -GGR<br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> CALUG mailing list<br>
> <a href="mailto:CALUG@unknownlamer.org">CALUG@unknownlamer.org</a><br>
> <a href="http://lists.unknownlamer.org/listinfo/calug" target="_blank">http://lists.unknownlamer.org/listinfo/calug</a><br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
><br>
> No virus found in this incoming message.<br>
> Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>
> Version: 9.0.791 / Virus Database: 271.1.1/2775 - Release Date: 03/28/10 02:32:00<br>
><br>
<br>
_______________________________________________<br>
CALUG mailing list<br>
<a href="mailto:CALUG@unknownlamer.org">CALUG@unknownlamer.org</a><br>
<a href="http://lists.unknownlamer.org/listinfo/calug" target="_blank">http://lists.unknownlamer.org/listinfo/calug</a><br>
_______________________________________________<br>
CALUG mailing list<br>
<a href="mailto:CALUG@unknownlamer.org">CALUG@unknownlamer.org</a><br>
<a href="http://lists.unknownlamer.org/listinfo/calug" target="_blank">http://lists.unknownlamer.org/listinfo/calug</a><br>
</div></div></blockquote></div><br>