On Thu, Jan 03, 2019 at 11:26:43AM +0200, Eric Pozharski wrote:
> On Tue, Jan 01, 2019 at 06:22:34PM -0500, Hendrik Boom wrote:
>
> *SKIP*
> > I tried magicrescue. But it kept finding many many starts for mp3
> > files, and running a script for each one to see if it was really and
> > mp3 file, in the course of which writing file hundreds of megbytes
> > long, deciding it wasn't mp3 after all and deleting it.
> >
> > Far too slow. Running for a full 18 hours found nothing, and it
> > looked as if it had searched ony a fraction of the 32G SDXC card.

Well, it *was* 32G. That takes a while just to read *once*.

>
> Sorry for wasting your time -- I didn't know this component is in such
> bad shape.

Not wasted. I learned, and was expecting some solutions to turn out
impractical. There will likely be other circumstances where it does
help, and now I know it exists.

>
> > I then used WxHexEdit, a hex editor, in immediate update mode. It found
> > the troublesome file names, and I replaced the slashes by zeros. After
> > that it was easy to read those files.
>
> Are we cool now?

Yes.

-- hendrik