New
#21
yea unfortunately all ive ever seen from them was referencing the documentation that says either memory or drive itself. Ive ran memory diagnostics a dozen times over and backed timings off. increased voltages through the roof just in case. did the same on the cpu in case it was a memory controller issue due to using 4 dimms etc.
ultimately all that was rendered moot once i found out it was backing up to externals absolutely fine. Its only the internals that fail and I have 6 internals 4 of which i tried before i gave up. last 2 are the same model as the first 4 anyhow, and theyre not ALL bad.
Plus i ran a full chkdsk /f /r /x on the usual drive that led to this saga - and it of course came back perfect.
im on 1903, but problem was present on 1809 so /shrug.
Dont want to get off topic with the whole windows rant, though I do agree its a hot mess more or less. The bi annual changes for the sake of doing so doesnt help.
I ordered an external drive to use in my dock which Ill have to either leave on, or remember to turn on before scheduled back ups. It'll get me by until I figure this out. 60 bucks I cant afford but the alternative should something happen and a backup actually NOT restore, id lose enough time and work that id probably walk away from my pc for life lol.
Almost considering trying a different backup software. Almost. I've just used macrium for quite some time - and the fact it will backup elsewhere leads me to believe its not the problem innately.
I have the problem whether I'm backing up to internal or external drive. Justt ran another backup whit verification on and it worked fine. But, I'm begenning not to trust any of it.
Almost wondering if it has to do with one of the settings like compression or something. They fail, yet ive restored a dozen times from subsequent incrementals at differerent points in the past year alone and never had an issue.
actually considering turning verification off.
I just want to understand why its happening and only on internal disks. I mean i "could" have an issue with external as well, and just havent in the past 3 i tried, lll do another momentarily to a different external to see what happens.
if your failing on internal and external, i presume you did check your memory?
I also have backups to the backups, but I take it 1 step further, the backup to the backup is Raid 1 !
But getting back to the issue, I assume everybody that has seen this issue has been verifying in-line ie: at the end of the backup ? Has anybody tried to re-verify using MR's manual verify ?
I have been using in-line. Not after the fact. Though i recall someone somewhere else during my absurd plethora of digigng to resolve the issue, mentioning they tried after the fact and failed.
Worth a try though.
is everyone using default compression of medium or? I'm using high, considering trying medium to see if it changes anything.