Amusingly, another drive in the array had gained one remapped sector over a decade ago and stayed like that since... Those old Western Digital drives are odd...
Tested the future eFiction 3.5.9 install script, but with PHP 7 rather than PHP 8. Since they are one and the same with 3.5.8.f1, it will work with PHP 8 as well.
However, I should add a note for efiction3-mod that PHP 8 is technically required despite this oversight.
Checked the modifications document against the files from eFiction 3.5.9 and only two files would be affected by the future changes: install/install.php and docs/settingstable.sql.
Won't be hard to alter the modification steps to accommodate for the future 3.5.9 changes.
This turned out fine (barring the buggy touchpad issues), so I do have a layout of the 3.5.9 additions/changes and my MD5 -> bcrypt password + MyISAM -> InnoDB engine + latin1 -> utf8mb4 collation modifications. (Though, looking back, it seems I may have to force all tables to utf8mb4 in the install script anyway...)
However, my mods are for the 3.5.8.f1 version, so this will have to be documented for the future 3.5.9 changes.
But... this is the sysadmin you're talking about, so I spent the last hour/hour and a half going through a just created image of the microSD card's exFAT filesystem to grab the contents of the current work.
Some context: on a non-journaled filesystem (which exFAT is), the following is more likely to be trashed: partition info, directory/filename info, its timestamps, and its attributes. (...the actual FAT, or File Allocation Table.) That is because all of that is stored near the beginning of the storage medium. The actual file contents could be further down and are less likely to be trashed... unless you're quite unlucky.
The NAS was originally a build that ran on an ASUS P5N-E SLI board with an Intel Core 2 Duo E8400 -> Intel Core 2 Quad Q9550 with 4GB of DDR2-800 RAM and originally ran NAS4Free/XigmaNAS -> OMV6... from 2018. In other words, MBR/BIOS only, no GPT/EFI. This was getting long in the tooth by ~2024 (or 2025...), so the entire system was migrated to an ASRock J4125B-ITX board... which is EFI only. This necessitated a conversion from MBR/BIOS to GPT/EFI, as BIOS emulators never really worked right with this board.
The GPT part was easy... EFI, not so much. Needed to be chrooted in order to install some necessary packages and a grub-install command to be run.
I actually mounted the EFI partition wrong in /etc/fstab in the initial conversion, so it came back to bite me when I performed the OMV upgrade. The mount is proper now; it was missing the umask (umask=0077) entry.
Today, in the basement running the old Redump.org CD-ripping machine, finally. Loads of updates for this build, months behind. It still runs Kubuntu 24.04; may have to update this one to 26.04, but I haven't ripped a CD in some years...
I did keep the old case for other purposes, and the old data integrity notice is still on the case.
--
During the migration to the new case, I managed to drop the last two RAID5 drives and the system drive from short distances. Almost surprisingly, they are still running perfectly so far. Not too worried about the system drive as there are backups of that, but not so much the data on the RAID5 setup...
Recompile
httpd: 2.4.68 (again) - due to structural changes with curl support
php: 7.4.33 (again) - due to structural changes with curl support
curl: 7.88.1 (after three years) - due to structural changes with... itself. Different builds with different OpenSSL support. Otherwise, different PHP versions will never truly be possible.
There will be some modifications to the eFiction code on this server. So far:
* Database tables will be using InnoDB instead of MyISAM. (Though, if needed, Aria could be used on some tables, but then you'll be stuck with MariaDB - no more MySQL. 😈)
* Managed to implement passwords to be hashed with bcrypt at a cost of 12 and a check for passwords that use the older MD5 hashing algorithm. (Though, you are not warned that your password is using the MD5 hash. However, changing/updating the password changes its hash to bcrypt.)
* Some visual modifications... I will also have to look through the 2000s/2010s-era 'patches' I have created but never actually shared; some I know are truly outdated.
Seems patched eFiction ('3.5.8' Testing Grounds) can run PHP 8.5 without freaking out. This also means my (overly ambitious) personal Sonic fanfiction project can run the latest PHP 8.5 builds.
Moved old Fanfiction Haven back to PHP 5.6, though it was likely fine with 7.4.
Moved old DRX Prototype Torrents back to PHP 5.6, which means the (truly) hacky MySQLi wrapper is used no more as a result. (It also wasn't a guarantee that the count issue would have been resolved by using the wrapper, either.)
Everything else runs PHP 7.4... even this GNU social install.