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.
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! 😮
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.
Also realized during benchmarks that the Orico enclosure I own has a strange limit of 100MB/s vs. my older Vantec NexStar 3 enclosure, which is higher than 100MB/s...
I would've used the NexStar in order to check the drive for errors faster, but then the drive would go past 50°C in this room...
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
Oof, bad sector count is now 21 from 9 as previously. SMART Device Error count remains at 22. I think this happened after the RAID check. So these consistency checks actually do their job, it seems.
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.
Should've mentioned beforehand: the main NAS is now using the previous Second Generation gaming system setup; the ASUS P5N-E SLI board was from the main NAS.