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.
Some notes: the last backup of the site before the recent upgrade was March 22, 2017, though the size of that archive has a discrepancy of full vs packed and will test it. The January 15, 2017 archive is more trustworthy and that size is ~95GB unpacked. The March 22, 2017 archive should be ~110GB unpacked.
The current September 6, 2023 archive is ~575GB unpacked due to the additional FTP archive data that was added since May 2018, though the FIC FTP archive may have been present in the 2017 archives, but that will be checked after retrieving the 1TB hard drive.
Retrieved the 1TB drive and looked at the March 22, 2017 file. The archive is fine, there's just no unpacked file size calculation data stored in the .tar.gz archive for some reason.
Also, the 2017 archives had the Abit and FIC FTP archives at the time. The Compaq FTP archive would then be added in May 2018.
I had to mirror the drive to another one. That was around September 1, 2023. Though interestingly, I had to position the IDE cable at the right position, otherwise the data transfer speed would literally be in the kilobyte range.
Old drive: Hitachi 180GXP IC35L060AVV207 - 61.4GB
Current drive: Western Digital Caviar WD800BB-22JHC0 - 80GB
That particular Western Digital was one of the many eBay purchases that sat mostly in storage until it was used in a Windows XP build, but even then, it wasn't used often. Found some unique data on that drive and sent that to the NAS before using it as a replacement system drive. It also had nearly 20K hours on it and no bad or pending sectors when initially examined.
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.
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.
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.
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.
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.
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 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).
Now the 1TB drive has pending sectors! This particular scratch disk has become a system backup image disk, however.
The 4TB scratch disk needs more write tests before I can use this one further. Add data to the drive before sending it to the main NAS.
The second 80GB system drive had to be directly imaged to another 80GB drive because that one developed bad sectors. The Seagate 80GB drive... the original NAS system drive, with over 112K Power-On-Hours, still reigns supreme. No known bad sectors so far.
That second 80GB system drive is dead. Seems I lucked out mirroring the original Windows XP data AND the NAS system data off that same drive before this! 😮
Previous version: ASUS P5N-E SLI with Intel Core 2 Quad Q9550 and 6GB of DDR2-800 RAM
Current version: ASUS P8H61-I R2.0 with Intel Core i5-3570 and 8GB of DDR3-1600 RAM
Instructions
1. Locate the drivers for the controller, which are 2.1.39.0, and install them.
2. After installation, run the USB 3.0 Host Controller utility.
3. Check Disable USB 3.0 power management functions and click OK.
I, however, restored it from a late June/early July session and test-restored the browser (closing and opening it again). It's fine now; just lost over 50 tabs instead. Meh.
Short of it, it works... the reading part, anyway. I have not tested the writing part yet. CDs and DVDs work, but I have no Blu-Ray data disc, but do have a few Playstation 3 discs. Unsurprisingly, those BDs aren't recognized by the player... a bit of a good sign.
It also tripped my USB 3.0 controller on my laptop, and seems borked since. I would have to reboot it after the data integrity check on the MediaDrive is finished.