I got two big hard drives that got corrupted, had all my music and tv shows etc on them.It seems like about half survived but I can't sit and play through every song and tv episode to be sure. There's gotta be a way to verify those thousands of files that look ok are actually ok?
Compare them to the backup
>>102444068the backup is corrupted, it's one of the two drives and anyways, names and file size are all there, you can't tell until you try to play them through whether they work or not
>>102444133He said you should compare it a bit by bit with the backup files.It's a one liner
>>102444257>It's a one lineryou mean like a joke..I don't have humor, sorry
>>102443837Use a filesystem repair tool? Something like CHKDSK if it's an NTFS drive?
>>102444347No, not a joke for fucks sake. It's a one-liner in your terminal...
>none of the replies actually understand op's question
>>102444423to what backup
>>102444479apparently..two extra internal drives I had for storage got corrupted, half the files on both are broken and won't play, some look like they'll play but won't, I want to somehow on a mass scale find out which files are broken so I can just save what's not broken
Unless you had or created a md5/hash of all your files, there is no way to know....Of probably do a ffmpeg pass and check for errors on the process
>>102443837ffmpeg -v error -i file.avi -f null - 2>error.logFirst answer on super user.
>>102444133You can probably use ffmpeg to detect errors
>>102444479The problem with the original poster is that he's retarded. You can't explain anything to people like this. Probably an iPhone user...
>>102444543>>102444545>>102444547ffmpeg mind
>>102444561I don't own any phonessee like you're the retard and these guys can understand english>>102444545>>102444547
>>102444609>see like you're the retard and these guys can understand englishI'm out
>>102443837unless you use a file system that uses CRCs, you are basically fucked. the hard drive only tells you which blocks are fucked and that's about it. unfortunately I had many drives that told me the blocks were okay, which was a lie. this is a silent error. you cannot recover from that unless you check with your backup. better use ZFS or BTRFS next time or create checksums for each file.
https://macperformanceguide.com/blog/2024/20240617_0930-IntegrityCheckerJava-3_0.html
>Page 5 after posting the solutionDid that link kill you, or what?
>>102443837You restart your torrent client and click force recheck. Hope that helps
>>102444792>create checksums for each filethat's a good idea..I will if I don't kms now those drives were 15 years of work
>>102445759many of these were downloaded over a decade ago
>>102445892Well just find the old torrents and load them up again. Unironically. If they weren’t torrents you could try something like ufs explorer but it’s only going to help if you know which ones are corrupted to begin with
