The recent database and htdocs mirror are being sent to the NAS, and all very old server data will be burned on two Blu-ray 25GB discs. That same data will remain on the older 1TB drive, but removed from the NAS.
I have yet to mirror the site configuration; that was planned about two months prior to the upgrade.
However, the drive is being zeroed because it was used as an NTFS drive with a GPT flag, and as a result, will be until tomorrow when I will start doing so.
This is actually a part of the delayed server upgrade.
Another thing being done is finally upgrading an old machine to Windows 10. Also, finding some practically unobtanium (read: expensive) 8GB RAM (2x 4GB DDR2) that works on an Intel board; most are AMD-supported because of the large RAM chip count. Hasn't really been much of an issue since DDR3 era; only real issue now is server vs. desktop compatibility nowadays.
8 or 16 memory chips for a 4GB DDR2 stick work on Intel boards, usually. AMD boards usually use 16 to 32 memory chips for a 4GB stick.
Installing an AMD-supported RAM stick on an Intel board will either show up as half-read (4GB stick as 2GB) or beeps indicating unrecognized RAM.
Blackview BV8000 Pro
Hisense Sero 7 Pro
Motorola Atrix HD
The Blackview BV8000 Pro phone is better off at Android 7 if you want to use it as an actual phone, otherwise you can use Android 8. I handed the phone back to Mom as it will eventually be used as a glorified web camera monitor.
The Hisense Sero 7 Pro tablet stays with me; it is on its third mainboard. USB port finally fixed (someone epoxied it; hasn't broken since!). Slow unit... unless a 4.2.x - 4.4.x custom ROM is used.
The Motorola Atrix HD phone is only dual core; this was Mom's first Android phone. The later custom ROMs do not handle screen drawing too well; so only real use is as a phone (if possible). Cannot use this fully as stock because AT&T will likely have phased out this device a long time ago.
The WD WD10EALS 1TB scratch disk is officially retired, as attempting to write data normally past the 139GB barrier actually crashes the drive and it would return as unrecognized. This did not show up in either the HD Tune Pro verify scan or the MHDD scan. (This, however, did hang HD Tune Pro, but the drive would return a few minutes later and the scan would resume as if nothing had happened.) The unrecognized part only happens when writing data normally.
Amusingly, this also did not show up in the HD Tune Pro erase procedure, but a verify after that would mark that area as red, but not crash the drive.
The Blu-ray drive is fully functional. I can erase and burn data to Blu-ray discs.
I erased one BD-RE due to a burning mishap (one video file was corrupt on the 4TB scratch disk), and I burned one BD-RE with two seasons of MST3K (old videos in storage from 2009).
I then got two different brands of 10 - 25GB Blu-ray rewritable discs (BD-RE) and inserted one of each disc to test the blue laser diode. The drive does recognize the discs: one Ritek (Smartbuy) and one CMC Magnetics (Verbatim).
Need a candidate for testing BD-RE burning, and I think it will be the old-stash MST3K movie set I found on TPB /years/ ago. Of course, the 4TB scratch disk and the old homemade DVD/CD sets will be involved.
The consistency check has passed, so the MediaDrive is erased. For now, it has the latest data from my main laptop, soon to be sent to the main NAS.
Meanwhile, there are two copies of a 500GB laptop HDD image, and the hashes do not match.
Toshiba 1TB HDD - original image copy
WD 1TB HDD - second image copy
The second image copy is the bad one; that drive where the second image copy resides has pending sectors; the original is fine. I'll copy the original again to that drive after copying both of them to the 4TB scratch drive.