|
i'm a member of the dorkroom freedom caucus, which thread are we handling the impeachment in?
|
#
¿
Oct 30, 2015 08:38
|
|
|
|
| # ¿ May 10, 2024 00:07 |
|
|
If that doesn't work, the TestDisk/PhotoRec bundle is also very good. It's explicitly designed for this contingency.
|
|
#
¿
Nov 2, 2015 08:04
|
|
|
dakana posted:Oh, a testing program sounds good. On Sunday I had two family sessions and out of curiosity I recorded to 2 cards -- the suspect CF card and an SD card I knew worked for safety. The CF card recorded the exact same photos as the SD card and worked perfectly. Some sort of analysis to "prove" that might be nice. TestDisk/PhotoRec are actually just undelete software. I don't know if they have a test function or not. You could run them on both the CF and SD card and then checksum the files that both recover? The CF should recover perfectly since it has an intact filesystem. They're pretty much the standard go-to when you gently caress up a filesystem. I broke the connector off an external drive and then realized that the controller wasn't running a passthrough to a standard GPT table. TestDisk managed to pin down the start of the partition and I got 100% recovery onto a separate disk, then copied it back. I'd try reformatting it and giving it another go, but after what you saw I would never rely solely on that card ever again. Best case you squeeze another couple of months out of it, but what you just saw is a gigantic lump on the MRI of your filesystem and sooner or later that card is gonna croak. Use it for Raspberry Pi or running stuff to the grocery store to print off on their kiosk or whatnot. Paul MaudDib fucked around with this message at 01:06 on Nov 3, 2015 |
|
#
¿
Nov 3, 2015 01:04
|
|
|
DJExile posted:All my photos are currently split between a desktop, 2 laptops, and a Surface. Check out git-annex sometime. Basically the idea is it's a distributed virtual filesystem where the file tables are stored in a git version-control repository. You take some files in a real filesystem, then mount them into the virtual filesystem at whatever location. So in other words all the stuff in D:\photoImports could be mounted at the virtual location /photos/import/ and so on. It can recognize identical files across multiple systems and allows you to check those in as duplicate sources for those files. It allows you to transfer the sources arbitrarily - for example you could do "git-annex checkout photos/mysexywife/" and it would pull it from your laptop or whatever. The sources don't have to be online - for example you can create repositories for a DVD, and then store a copy of the index as a remote. Then when you tell it to pull, it will tell you "source not available, bring source 'Backup DVD 12' online". It includes a tool called "git-annex assistant" which allows you to create rules about how data should be handled. For example you can say "everything in photos/mysexywife should exist on at least 2 independent repositories" and it can then automatically distribute your data to make that happen. Or auto-archive to Glacier after a certain period of inactivity. Or you can do things like "when repository USB comes online to host laptop, move any files from directory 'transfer' to repository 'USB'", followed by "when USB comes online to host desktop, move any files from 'USB' to 'Storage'". If you don't otherwise use git I think the learning curve is probably very steep but it's absolutely amazing for bringing a messy network full of files to heel.
|
|
#
¿
Nov 3, 2015 01:15
|
|
