I was going to write more about Victoria and the trip – I talked about a open mic appearance on Friday already – but my Macbook drive is more fucked up than I feared.
Anybody know how to make Time Machine skip past files with read errors and not just bail out?
See, I currently have no backup because Time Machine last week decided the backup was damaged and that it needed to start over with a new one. It’s done this before over the years so I said sure, go ahead.
It deleted the old backup and refused to make a new one. It gets about 1.7 gig in, then fails due to what it calls probably-transient network errors.
What it’s actually failing on are read errors on the laptop drive. Read errors disk utility can’t find. Read errors fsck can’t find either. Read errors SMART says aren’t happening.
But there are a whole bunch of files that if you try to copy them generate read fails. dd sees them too, and fails, if I try to image the disk. I went through and generated a massive list of bad files – and there are many – by having the system cp -pr them all indiviually while I was in Victoria.
I’ve currently added all of them to the Time Machine exclusion list and am trying to get a backup that way. I rather suspect this, too, will fail, due to a previously-undetected bad file.
Does anyone out there know whether there’s a way to make Time Machine not bomb out on these read errors? Or failing that, have another, good solution? Because I really need a better backup than the results of a big tree of cp -pr.
But at least I now have that. Before I set up that job, I didn’t even have that. Not after Time Machine’s lies.
eta:: With a bunch of exclusions added, I have a time machine backup of most of the drive. But it could be better with fewer exclusions if you know how to make Time Machine skip files with read errors instead of failing out. Can this even be done?