It does seem highly unusual. It would seem the common denominator is the SATA controller but I would also consider if the software you are using is reporting the issue accurately. Check out the optical disk in another PC. If it comes up clean then that narrows down the issue.
It is a storage device thing only. (an optical does not have storage of it's own, you insert disks)
sounds like it could be a controller issue. or could be 1 bad device on the sata controller causing the issues.
try removing 1 device at a time and see how it performs.
I was pretty confused on the CD bad block. However it is a DVD Re-writable which can behave like a storage device, so wasn't sure. Other forums with bad blocks on a CD had solutions all over the place.
When I did the exact sector by sector copy, there were no read errors. I'm used to have issues on actual bad blocks when I do those kind of copies.
It only happens about once a day, then 6 people are SOL for a bit. I'll see if I can recreate it and then start using one device at a time, and move hardware to other computers.
so what exactly is the error message, can you post a picture of the error?
Maybe solved. Tight SATA Cable.
I'm not at the location anymore, so can't post the error verbatim. It says Device/HardDisk3 has a bad block. Also had that for HardDisk4 and cdrom0.
I ended up getting an error that said the driver found an error with the controller for HardDisk3, which is one of the RAID disks. #4 is the disk I replaced.
I found that one of the DVD drive SATA cables was very tight, the builder did not leave enough slack. The angle it was pulling would have decreased the pressure and probably surface area of the SATA connections.
I gave it some more slack and have rebooted 4 times and ran Burnit Tests on the HDDs and Optical drives without error. All 6 drives are connected. I'll call it resolved after two days since this has been an intermittent problem.
Ended up having issues again. The mobo was sent overnight by the manufacturer, since the controller is integrated. Should receive it shortly. Their tech thought it could also be the optical drive causing it. But with it disconnected the issue returned.