[GRLUG] Flash Disk Recovery

[Justin Popa]

Yeah, that would make sense. One of the things we can prove have caused this
is the opening and closing of the xD card bay while a dictation file is
currently being written. We've watched some docs rapid fire flip it open and
closed, which doesn't cleanly eject the disk.

On Nov 29, 2007 12:24 PM, Collin Kidder <adderd at kkmfg.com> wrote:

> Something Casey said made me think of another potential suggestion:
>
> Some versions of windows default to write caching even flash drives. If
> windows does that and somebody yanks the drive without properly stopping
> the device first then they run the risk of blowing the fat table. This
> could be prevented by forcing windows to not write cache the drive.
>
> Justin Popa wrote:
> > All great suggestions, but they are doctors, so they get their way.
> > Infrequent downloading because they're too busy most of the time. We
> also
> > had originally set up a 'never to leave the office with this device'
> policy,
> > but now we're replacing about 1 a month due to lost items(lost at home,
> in
> > another state, on a plane, in the lake). That's why I'm more in the mood
> of
> > finding some decent recovery software than changing how they handle
> them.
> > It's just impossible. Anyway, I found Runtime Software's "GetDataBack
> for
> > FAT" that runs on Windows. It's recovered them and seems to be working
> fine.
> >
> > On Nov 29, 2007 11:52 AM, Ben Rousch <brousch at gmail.com> wrote:
> >
> >
> >> I'd suggest increasing the frequency of cradle visits.  When the
> >>
> >>> machines corrupt the drives, is the most-recently-recorded data also
> >>> corrupt, or just the other data that hasn't seen a cradle yet?
> >>>
> >>> I seem to recall that the FAT filesystems have a backup table, too.
> >>> But it's been ages since I fiddled with fsck.vfat
> >>>
> >>
> >> I would suggest reformatting the cards more frequently. I have had
> similar
> >> problems with card corruption in a digital camera and frequent
> reformatting
> >> seems to have fixed that problem. Considering the medical nature of the
> data
> >> being stored, pull each card aside once a week and format it to be
> safe. You
> >> might also consider tracking corruption for each card so you can tell
> if
> >> it's one or two cards that are the problem, or the whole batch.
> >>
> >>
> >> _______________________________________________
> >> grlug mailing list
> >> grlug at grlug.org
> >> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> >>
> >>
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > grlug mailing list
> > grlug at grlug.org
> > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
>
> _______________________________________________
> grlug mailing list
> grlug at grlug.org
> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shinobu.grlug.org/pipermail/grlug/attachments/20071129/5fe20934/attachment.htm