This problem sounds more like a drive lockup/failure than some sort of issue of running DW and then SD - it's more coincidence than anything else.

I would normally agree with that but my system is rock solid and so is SuperDuper cloning. This was only the second time in almost a year that I've been forced to shut down my laptop (the other incident was unrelated).

This has never happened before performing a smart update and I've been using SuperDuper for many, many years.

This was the first time I've ever run Diskwarrior before performing a smart update. It was the only factor that was different before this highly unusual event.

I rebuilt the clone from scratch and no issues. Could it be it was just stuck temporarily and I just should have waited it out?

Also, I'm seeing others mention issues where files are changed with Diskwarrior so it takes longer for them as well afterwards. So it seems running Diskwarrior does seem to affect clones.

I'm using Diskwarrior version 4.4 by the way. Perhaps something has changed with this version of DW.

Disk Warrior may change files, which would - of course - cause those files to be copied. But there's a big difference between having your system lock up as described and copying files.

If your system is locking up there's a low level problem. Patience won't 'fix' it (unless you're waiting for an I/O timeout, again, due to hardware problems).

But, again, this is more correlation than anything else. SuperDuper! is simply copying files...if the hardware or software environment those files are being copied in is unstable, or 'locks up', it will look like SuperDuper! "caused" it (because, after all, we're running), but these high level operations (eg "Copy file a from drive I to drive II") are really performed by the OS, and the lockups are happening at a very low level...

That's the thing. The hardware/software environment is stable. Zero crashes copying files or doing anything else for that matter. Zero crashes doing many multiple smart updates going on almost a year straight. The ONE time I run DW 4.4 on the laptop right before smart updating the same dmg clone and this stall happens.

Then why didn't it stall again while rebuilding the clone if there's an issue with the drive? I do understand that correlation doesn't equal causation. But, this will be the first and last time I ever run Diskwarrior on my computer right before smart updating a clone, that's for sure.

If my computer was already having issues beforehand or afterwards, I wouldn't be looking at this. But there's literally been no other issues with anything (including SuperDuper) until I ran Diskwarrior right before that attempt at a Smart Update.

That said, maybe it was some bizarre, temporary glitch in my high-end FireWire 800 G-Drive Mini that has never happened before (and is fine afterwards as well). I just find it strange that others have had issues with Smart Update and Diskwarrior as well.

Welp, thanks for the replies though. :)

I don't know of any issues that DW has with hardware, nor any issues or possible interference it might have with SD (that it wouldn't otherwise have with the system, since we're using the system to copy the files)... if I could point you at something known, I will. I just can't see how the two events could be related at all.