Updates from amisapphire on Ami Sapphire's Notices!
amisapphire: It was to the point that I isolated NetworkManager due to early assumptions that it was to blame. In the end, it is a years-old kernel bug. Yes, my main laptop's wireless setup is entirely manual now, and I can easily revert this.
amisapphire's status on Monday, 23-Mar-2026 13:03:49 EDT
It was to the point that I isolated NetworkManager due to early assumptions that it was to blame. In the end, it is a years-old kernel bug. Yes, my main laptop's wireless setup is entirely manual now, and I can easily revert this.
amisapphire: It seems that since around Linux kernel 6.6, newer Intel wireless cards will crash at suspend/wake... that is, unless you turned off the radio of the card entirely before suspending the system. My main laptop is still using Linux 6.2 (from 2023) due to this. I previously had 6.5, but some browser couldn't open with this kernel... No, this is still not fixed.
amisapphire's status on Monday, 23-Mar-2026 13:01:32 EDT
It seems that since around Linux kernel 6.6, newer Intel wireless cards will crash at suspend/wake... that is, unless you turned off the radio of the card entirely before suspending the system. My main laptop is still using Linux 6.2 (from 2023) due to this. I previously had 6.5, but some browser couldn't open with this kernel... No, this is still not fixed.
amisapphire: I honestly forgot about the rate limit settings! It was stuck on ~375KB average. This has been fixed.
amisapphire's status on Tuesday, 11-Nov-2025 21:57:37 EST
I honestly forgot about the rate limit settings! It was stuck on ~375KB average. This has been fixed.
amisapphire: We now have symmetrical upload since October 20 (known), but it may have been October 15. As a result, I have finally upped the bandwidth limit from 786KB/1MB (rest of main site) and 393KB/512KB (certain download sections) to ~5MB and ~2.5MB respectively. From there, stuff will be monitored occasionally.
amisapphire's status on Tuesday, 11-Nov-2025 20:43:05 EST
We now have symmetrical upload since October 20 (known), but it may have been October 15. As a result, I have finally upped the bandwidth limit from 786KB/1MB (rest of main site) and 393KB/512KB (certain download sections) to ~5MB and ~2.5MB respectively. From there, stuff will be monitored occasionally.
amisapphire: Finally have practically stable Live TV on Jellyfin 10.10.7! Quite recent Intel media drivers for Linux got it to that point. Other thing was Intel Core i3: 12100 -> 13100... but two pins located at the bottom-center of its socket on the board in question were quite bent. I managed to fix them perfectly, though.
amisapphire's status on Tuesday, 11-Nov-2025 15:04:14 EST
Finally have practically stable Live TV on Jellyfin 10.10.7! Quite recent Intel media drivers for Linux got it to that point. Other thing was Intel Core i3: 12100 -> 13100... but two pins located at the bottom-center of its socket on the board in question were quite bent. I managed to fix them perfectly, though.
amisapphire: Updates! mariadb: 11.4.5 -> 11.4.7 Cannot run 11.8.x on this server now due to SIGSEGV. A future version may run it. (26.04?)
amisapphire's status on Tuesday, 11-Nov-2025 14:50:54 EST
Updates! mariadb: 11.4.5 -> 11.4.7 Cannot run 11.8.x on this server now due to SIGSEGV. A future version may run it. (26.04?)
amisapphire: Updates! mariadb: 11.4.4 -> 11.4.5
amisapphire's status on Wednesday, 14-May-2025 04:12:00 EDT
amisapphire: Going to have to recompile PHP again as to have it no longer be thread safe. Also, pcre2 should be updated.
amisapphire's status on Friday, 22-Nov-2024 17:38:08 EST
Going to have to recompile PHP again as to have it no longer be thread safe. Also, pcre2 should be updated.
amisapphire: Updates! mariadb: 11.4.3 -> 11.4.4 Fixes... mariadb: tcp -> sockets Changes... php: fastcgi -> fpm (tcp) -> fpm (sockets)
amisapphire's status on Thursday, 21-Nov-2024 16:32:45 EST
Updates! mariadb: 11.4.3 -> 11.4.4 Fixes... mariadb: tcp -> sockets Changes... php: fastcgi -> fpm (tcp) -> fpm (sockets)
amisapphire: Updates! mariadb: 11.4.2 ->11.4.3
amisapphire's status on Thursday, 31-Oct-2024 22:47:01 EDT
amisapphire: Updates! Major Release mariadb: 10.11.7 -> 11.4.2
amisapphire's status on Wednesday, 14-Aug-2024 12:02:39 EDT
Updates! Major Release mariadb: 10.11.7 -> 11.4.2
amisapphire: Updates! Security httpd: 2.4.59 -> 2.4.62
amisapphire's status on Thursday, 18-Jul-2024 21:39:26 EDT
Updates! Security httpd: 2.4.59 -> 2.4.62
amisapphire: Updates! System Ubuntu Server: 23.10 -> 24.04 LTS Recompile php-7.4.33 - due to libicu change from 72 to 74 during system upgrade
amisapphire's status on Tuesday, 28-May-2024 18:41:27 EDT
Updates! System Ubuntu Server: 23.10 -> 24.04 LTS Recompile php-7.4.33 - due to libicu change from 72 to 74 during system upgrade
amisapphire: Updates! Security httpd: 2.4.58 -> 2.4.59 Other pcre2: master-20231204 -> 10.43 Recompile php-7.4.33 - due to external pcre2 update
amisapphire's status on Sunday, 14-Apr-2024 15:43:01 EDT
Updates! Security httpd: 2.4.58 -> 2.4.59 Other pcre2: master-20231204 -> 10.43 Recompile php-7.4.33 - due to external pcre2 update
amisapphire: This server is going to get some needed security patches... probably in ~30 minutes.
amisapphire's status on Sunday, 14-Apr-2024 15:01:58 EDT
This server is going to get some needed security patches... probably in ~30 minutes.
amisapphire: Updates! mariadb: 10.11.6 -> 10.11.7
amisapphire's status on Saturday, 10-Feb-2024 16:18:52 EST
amisapphire: Clearing some VERY redundant data on the main NAS today. About 300GB so far. Ironically, it started with trying to find a historical crack of Sonic Heroes (entire game included) on the server, lol. I never run it, but the .nfo mentioning its backstory is chuckleworthy; it's why I kept it.
amisapphire's status on Thursday, 04-Jan-2024 09:22:31 EST
Clearing some VERY redundant data on the main NAS today. About 300GB so far. Ironically, it started with trying to find a historical crack of Sonic Heroes (entire game included) on the server, lol. I never run it, but the .nfo mentioning its backstory is chuckleworthy; it's why I kept it.
amisapphire: So, one of the drives dropped off the RAID5 array some time ago. Got the drive back online after a reboot after I noticed it. However, the drive is perfectly fine. 🤨 So after figuring how to add the drive again, it was added back in the array. dmesg: md kicking non-fresh /dev/xyz from array run - mdadm /dev/md0 -a /dev/xyz Took a bit to resync, but the array is fine again.
amisapphire's status on Thursday, 28-Dec-2023 15:49:27 EST
So, one of the drives dropped off the RAID5 array some time ago. Got the drive back online after a reboot after I noticed it. However, the drive is perfectly fine. 🤨 So after figuring how to add the drive again, it was added back in the array. dmesg: md kicking non-fresh /dev/xyz from array run - mdadm /dev/md0 -a /dev/xyz Took a bit to resync, but the array is fine again.
amisapphire: Updates! httpd: 2.4.57 -> 2.4.58 pcre2: master_20230920 -> master_20231202 Recompiled: php 7.4.33 Somehow had issues with directory symlinking; httpd-2.4.57 really wanted to stick around!
amisapphire's status on Monday, 04-Dec-2023 01:57:15 EST
Updates! httpd: 2.4.57 -> 2.4.58 pcre2: master_20230920 -> master_20231202 Recompiled: php 7.4.33 Somehow had issues with directory symlinking; httpd-2.4.57 really wanted to stick around!
amisapphire: Updates! mariadb: 10.11.5 -> 10.11.6 Still haven't updated apache httpd yet...!
amisapphire's status on Friday, 01-Dec-2023 18:48:04 EST
Updates! mariadb: 10.11.5 -> 10.11.6 Still haven't updated apache httpd yet...!
amisapphire: Finally, an update: a few days ago, the install had to be cloned to another SSD because the system would lock up after login. Surprisingly, the system after cloning was fine. This, however, broke the AnyDVD HD trial eight days in. (I was imaging the somewhat large DVD collection during this incident.) Requesting a new trial also worked...!
amisapphire's status on Friday, 01-Dec-2023 18:46:42 EST
Finally, an update: a few days ago, the install had to be cloned to another SSD because the system would lock up after login. Surprisingly, the system after cloning was fine. This, however, broke the AnyDVD HD trial eight days in. (I was imaging the somewhat large DVD collection during this incident.) Requesting a new trial also worked...!
amisapphire: Oh, forgot it locked up once trying to remove some old files to free up space. It was also after one other file brought up an I/O error. That is what prompted me to run chkdsk in the first place. Will have to assess the drive and then possibly clone the install to another one to save it.
amisapphire's status on Monday, 20-Nov-2023 13:10:27 EST
Oh, forgot it locked up once trying to remove some old files to free up space. It was also after one other file brought up an I/O error. That is what prompted me to run chkdsk in the first place. Will have to assess the drive and then possibly clone the install to another one to save it.
amisapphire: ...Finally ran chkdsk after noticing some terrible hanging on the Dell Latitude E6220's Windows 7 install on an old Samsung SSD. The system is trashed; surprising it even boots at all. This was used to continue archiving the DVD video library. Those files are fine. Probably going to need my original Windows 7 DVDs if sfc /scannow fails to fix this after the chkdsk ends.
amisapphire's status on Monday, 20-Nov-2023 13:07:07 EST
...Finally ran chkdsk after noticing some terrible hanging on the Dell Latitude E6220's Windows 7 install on an old Samsung SSD. The system is trashed; surprising it even boots at all. This was used to continue archiving the DVD video library. Those files are fine. Probably going to need my original Windows 7 DVDs if sfc /scannow fails to fix this after the chkdsk ends.
amisapphire: Went through the main web server, and the entire willem-eprom-stuff section was actually duplicated. This was from an attempt to salvage what a Windows 10 install did to that directory. This is now fixed, and the pre-dupe-fix backup will be stored with the rest of the ServerBackup files.
amisapphire's status on Saturday, 18-Nov-2023 16:23:56 EST
Went through the main web server, and the entire willem-eprom-stuff section was actually duplicated. This was from an attempt to salvage what a Windows 10 install did to that directory. This is now fixed, and the pre-dupe-fix backup will be stored with the rest of the ServerBackup files.
amisapphire: Didn't update this: eventually got a cooler for the CPU, and the power supply is in the right location. There is also media on the media server. 😉
amisapphire's status on Saturday, 18-Nov-2023 16:21:20 EST
Didn't update this: eventually got a cooler for the CPU, and the power supply is in the right location. There is also media on the media server. 😉
amisapphire: The temporary cooler obstructing the location of the power supply on this early 2000s case. The power supply is not in obvious view here, but it is at the 5.25" drive/accessories section (originally meant for optical drives). I plan on using a low profile cooler after this. http://cwcyrix.nsupdate.info/gnu-social/public/url/50
amisapphire's status on Saturday, 04-Nov-2023 12:36:50 EDT
The temporary cooler obstructing the location of the power supply on this early 2000s case. The power supply is not in obvious view here, but it is at the 5.25" drive/accessories section (originally meant for optical drives). I plan on using a low profile cooler after this. http://cwcyrix.nsupdate.info/gnu-social/public/url/50
amisapphire: Motherboard test. Also tested the RAM to see if it was good as well. http://cwcyrix.nsupdate.info/gnu-social/public/url/47
amisapphire's status on Saturday, 04-Nov-2023 12:30:55 EDT
Motherboard test. Also tested the RAM to see if it was good as well. http://cwcyrix.nsupdate.info/gnu-social/public/url/47
amisapphire: The webserver, compile box, and the CD ripping machine are now running on Ubuntu 23.10. That was the main reason I never compiled Apache httpd 2.4.58 yet for the server. Also, the CPU came in for the media server yesterday, and I built it that same day. However, since I'm using a quite old case (looks to be from around 2000), the temporary large cooler blocks the way of where the power supply should be. Right now, the power supply is where the optical drives would normally be. Now, the media server is running, but there is no media on it yet...
amisapphire's status on Saturday, 04-Nov-2023 12:25:48 EDT
The webserver, compile box, and the CD ripping machine are now running on Ubuntu 23.10. That was the main reason I never compiled Apache httpd 2.4.58 yet for the server. Also, the CPU came in for the media server yesterday, and I built it that same day. However, since I'm using a quite old case (looks to be from around 2000), the temporary large cooler blocks the way of where the power supply should be. Right now, the power supply is where the optical drives would normally be. Now, the media server is running, but there is no media on it yet...
amisapphire: And the update: Sis's laptop seems to be fine now. Some settings seem to be working properly now (though that was done after DISM and SFC twice). Originally, the unit BSODed, then it was brought to me. Unit also had a delay powering on, then it started checking the disk for errors. Then it booted to the Windows desktop. Then part of the AMD GPU drivers were corrupt. This prompted me to scan the disk twice: /f, then /r. Noticed the Date/Time Settings would crash, but pretty much everything else was fine. Sadly, DISM was pretty much useless, but sfc /scannow was not so. This was run twice. Eventually, the Date/Time Settings worked. Also noticed after DISM, the build number discrepancy showed. Reference: http://cwcyrix.nsupdate.info/gnu-social/public/notice/179
amisapphire's status on Monday, 30-Oct-2023 17:41:11 EDT
And the update: Sis's laptop seems to be fine now. Some settings seem to be working properly now (though that was done after DISM and SFC twice). Originally, the unit BSODed, then it was brought to me. Unit also had a delay powering on, then it started checking the disk for errors. Then it booted to the Windows desktop. Then part of the AMD GPU drivers were corrupt. This prompted me to scan the disk twice: /f, then /r. Noticed the Date/Time Settings would crash, but pretty much everything else was fine. Sadly, DISM was pretty much useless, but sfc /scannow was not so. This was run twice. Eventually, the Date/Time Settings worked. Also noticed after DISM, the build number discrepancy showed. Reference: http://cwcyrix.nsupdate.info/gnu-social/public/notice/179
Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Sunday, 29-Oct-2023 08:20:20 EDT - Ami Sapphire's Notices
amisapphire: Dad's aging Core 2 Quad machine apparently does not like ancient nVidia graphics cards. Now uses an AMD Radeon HD 7770 GHz Edition just to render the desktop and other certain effects better than the onboard graphics does. Surprisingly, Windows 10 runs pretty well on that machine. Even if Windows 11 didn't restrict hardware requirements, I most definitely wouldn't install it on that system. I already almost didn't install Windows 10 on it; the machine had a Core 2 Quad Q6600. Since the changes - upgrade to fixed Q9550 and 128GB SSD -> 250GB HDD -> 256GB SSD, I finally upgraded it to Windows 10. But... This required a long EOL version of Windows 10. Basically: Windows 7 -> Windows 10 1607, Windows 10 22H2. I backed up the Windows 7 install before doing this so I had an ass-covering. It worked, though.
amisapphire's status on Sunday, 29-Oct-2023 08:38:41 EDT
Dad's aging Core 2 Quad machine apparently does not like ancient nVidia graphics cards. Now uses an AMD Radeon HD 7770 GHz Edition just to render the desktop and other certain effects better than the onboard graphics does. Surprisingly, Windows 10 runs pretty well on that machine. Even if Windows 11 didn't restrict hardware requirements, I most definitely wouldn't install it on that system. I already almost didn't install Windows 10 on it; the machine had a Core 2 Quad Q6600. Since the changes - upgrade to fixed Q9550 and 128GB SSD -> 250GB HDD -> 256GB SSD, I finally upgraded it to Windows 10. But... This required a long EOL version of Windows 10. Basically: Windows 7 -> Windows 10 1607, Windows 10 22H2. I backed up the Windows 7 install before doing this so I had an ass-covering. It worked, though.
amisapphire: The power supply arrived today, but it got misdelivered due to the address being one digit off. However, I got the package. 😏 The mainboard and RAM were delivered a few days prior, so the only thing needed is a CPU. Power supply test: * basic power on with no load. Short green power-on wire to ground, and that is it. All voltages are on point. * basic power good test. Connect power supply to motherboard and power it on through the board. Success. No actual load test has been done, e.g. power good test but with a complete system instead of just a motherboard.
amisapphire's status on Sunday, 29-Oct-2023 08:27:07 EDT
The power supply arrived today, but it got misdelivered due to the address being one digit off. However, I got the package. 😏 The mainboard and RAM were delivered a few days prior, so the only thing needed is a CPU. Power supply test: * basic power on with no load. Short green power-on wire to ground, and that is it. All voltages are on point. * basic power good test. Connect power supply to motherboard and power it on through the board. Success. No actual load test has been done, e.g. power good test but with a complete system instead of just a motherboard.
amisapphire: Sis's HP laptop has file integrity issues, but system is fine so far. Still monitoring the situation; the drive exhibited no actual issues. Apparently AMDGPU drivers are somewhat problematic. - Main server, compile box, and CD-ripping machine are still on Ubuntu 23.04 (Server, Xubuntu, and Kubuntu respectively), main laptop and test media server are on Kubuntu 23.10. - Speaking of test media server, it is on Mom's 2018 HP laptop, runs Jellyfin, and has a few test videos scrounged up from the main NAS and my old Windows 10 install. I'm still working out the quirks on the setup before the final install, which will not run on Ubuntu or any such spin; it will be running Debian 12, which is actually unusual to me, since I specifically prefer Ubuntu/spins.
amisapphire's status on Sunday, 29-Oct-2023 08:20:20 EDT
Sis's HP laptop has file integrity issues, but system is fine so far. Still monitoring the situation; the drive exhibited no actual issues. Apparently AMDGPU drivers are somewhat problematic. - Main server, compile box, and CD-ripping machine are still on Ubuntu 23.04 (Server, Xubuntu, and Kubuntu respectively), main laptop and test media server are on Kubuntu 23.10. - Speaking of test media server, it is on Mom's 2018 HP laptop, runs Jellyfin, and has a few test videos scrounged up from the main NAS and my old Windows 10 install. I'm still working out the quirks on the setup before the final install, which will not run on Ubuntu or any such spin; it will be running Debian 12, which is actually unusual to me, since I specifically prefer Ubuntu/spins.
amisapphire: Real life... Lot of maintenance to network and Internet equipment, then a certain HP laptop. I also started using Linux on my main laptop, and it's much more responsive than when it was on Windows 10. I still keep the install, because ~7 years' worth of cruft is on that install, which has gone through three laptops so far! - Routers have been upgraded from OpenWrt: 22.03.5 -> 23.05.0 and wireless signals have improved slightly, so has stability; no random disconnects on certain clients so far. Also, switched CPU governor from: schedutil -> ondemand and made a few tweaks to the ondemand settings... more responsive now. And... the minimum CPU frequency has been changed from 437500 to 600000 due to possible stability issues with the 2.4GHz radio and startup issues. Haven't had those myself, but it is preemptive.
amisapphire's status on Sunday, 29-Oct-2023 01:55:59 EDT
Real life... Lot of maintenance to network and Internet equipment, then a certain HP laptop. I also started using Linux on my main laptop, and it's much more responsive than when it was on Windows 10. I still keep the install, because ~7 years' worth of cruft is on that install, which has gone through three laptops so far! - Routers have been upgraded from OpenWrt: 22.03.5 -> 23.05.0 and wireless signals have improved slightly, so has stability; no random disconnects on certain clients so far. Also, switched CPU governor from: schedutil -> ondemand and made a few tweaks to the ondemand settings... more responsive now. And... the minimum CPU frequency has been changed from 437500 to 600000 due to possible stability issues with the 2.4GHz radio and startup issues. Haven't had those myself, but it is preemptive.
amisapphire: Blew up the server by adding the orphan_file feature to the system drive. 🙃 The filesystem was created before the feature even existed; better opportunity was to add it after moving off the old system drive.
amisapphire's status on Tuesday, 10-Oct-2023 00:36:06 EDT
Blew up the server by adding the orphan_file feature to the system drive. 🙃 The filesystem was created before the feature even existed; better opportunity was to add it after moving off the old system drive.
amisapphire: Forgot about the Compile Box: the other Linux machine at hand... the 40GB drive can be accessed on that machine.
amisapphire's status on Saturday, 30-Sep-2023 22:52:23 EDT
Forgot about the Compile Box: the other Linux machine at hand... the 40GB drive can be accessed on that machine.
amisapphire: The last install was a Raspbian (Raspberry Pi OS) Buster lite variant upgraded from Stretch on an 8GB SD card. Before that, it was a custom cut-down version of Jessie on a 4GB SD card (before a lite install was a thing). No known RPi2 server version here ran Wheezy as I recall. Last run: Using username "pi". pi@amisaph-raspi's password: Linux amisaph-raspi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Sep 24 19:35:07 2023 from 2601:406:4c00:55c7:e9ef:4335:e256:5dea pi@amisaph-raspi ~ $ uname -a Linux amisaph-raspi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux pi@amisaph-raspi ~ $
amisapphire's status on Saturday, 30-Sep-2023 21:39:13 EDT
The last install was a Raspbian (Raspberry Pi OS) Buster lite variant upgraded from Stretch on an 8GB SD card. Before that, it was a custom cut-down version of Jessie on a 4GB SD card (before a lite install was a thing). No known RPi2 server version here ran Wheezy as I recall. Last run: Using username "pi". pi@amisaph-raspi's password: Linux amisaph-raspi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Sep 24 19:35:07 2023 from 2601:406:4c00:55c7:e9ef:4335:e256:5dea pi@amisaph-raspi ~ $ uname -a Linux amisaph-raspi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux pi@amisaph-raspi ~ $
amisapphire: As of September 30, 2023, the Raspberry Pi 2 Test Server is now retired. This originally ran back in 2016 and had a few things that weren't on the main server. PHP was actually installed on the server but somehow broke a few months later; couldn't fix it. I now have the 40GB hard drive that contains the entire site contents. Will go through the drive on the CD ripping box as that runs a Linux distro. Other notes: * This is the second Raspberry Pi 2 in the entire set. - The first one unfortunately had a 9V spike due to a power outage, which killed it. * The RTC unit's battery installed on the Pi 2 is almost dead. * This particular Pi 2 has a header soldered for easy reset/power on.
amisapphire's status on Saturday, 30-Sep-2023 21:27:43 EDT
As of September 30, 2023, the Raspberry Pi 2 Test Server is now retired. This originally ran back in 2016 and had a few things that weren't on the main server. PHP was actually installed on the server but somehow broke a few months later; couldn't fix it. I now have the 40GB hard drive that contains the entire site contents. Will go through the drive on the CD ripping box as that runs a Linux distro. Other notes: * This is the second Raspberry Pi 2 in the entire set. - The first one unfortunately had a 9V spike due to a power outage, which killed it. * The RTC unit's battery installed on the Pi 2 is almost dead. * This particular Pi 2 has a header soldered for easy reset/power on.
amisapphire: Server update! Upgrades: openssl: 1.1.1v -> 1.1.1w Recompiled: httpd-2.4.57 php-7.4.33
amisapphire's status on Wednesday, 27-Sep-2023 22:55:38 EDT
Server update! Upgrades: openssl: 1.1.1v -> 1.1.1w Recompiled: httpd-2.4.57 php-7.4.33
amisapphire: Forgot: Upgrades: pcre2: 10.39 -> master_20230920
amisapphire's status on Saturday, 23-Sep-2023 21:40:29 EDT
Forgot: Upgrades: pcre2: 10.39 -> master_20230920
amisapphire: The compile box needed a hard drive replacement; moved from Lubuntu to Xubuntu in the process... which required rebuilding the compile box setup. Saved and updated notes regarding such this time.
amisapphire's status on Saturday, 23-Sep-2023 21:36:15 EDT
The compile box needed a hard drive replacement; moved from Lubuntu to Xubuntu in the process... which required rebuilding the compile box setup. Saved and updated notes regarding such this time.
amisapphire: Server update! Upgrades: openssl: 1.1.1u -> 1.1.1v Recompiled: apr-1.7.4 apr-util-1.6.3 curl-7.88.1 httpd-2.4.57 php-7.4.33 mod_bw-0.9.2a mod_limitipconn-0.24 mod_fcgid-2.3.9 Config fixed: php.ini (due to an oversight when htdocs server path changed again; broke session cookies)
amisapphire's status on Saturday, 23-Sep-2023 21:33:17 EDT
Server update! Upgrades: openssl: 1.1.1u -> 1.1.1v Recompiled: apr-1.7.4 apr-util-1.6.3 curl-7.88.1 httpd-2.4.57 php-7.4.33 mod_bw-0.9.2a mod_limitipconn-0.24 mod_fcgid-2.3.9 Config fixed: php.ini (due to an oversight when htdocs server path changed again; broke session cookies)
amisapphire: Server Update! mariadb: 10.11.4 -> 10.11.5 OpenSSL needs to be updated; doing so another time, however.
amisapphire's status on Friday, 08-Sep-2023 12:57:58 EDT
Server Update! mariadb: 10.11.4 -> 10.11.5 OpenSSL needs to be updated; doing so another time, however.
amisapphire: 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.
amisapphire's status on Thursday, 07-Sep-2023 15:58:50 EDT
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.
amisapphire: The site will be down on or around September 12, 2023 due to Comcast finally upgrading the network in our area. I think mid-split is finally going to be here, though the actual configuration for our bought modem would be further away.
amisapphire's status on Thursday, 07-Sep-2023 14:21:21 EDT
The site will be down on or around September 12, 2023 due to Comcast finally upgrading the network in our area. I think mid-split is finally going to be here, though the actual configuration for our bought modem would be further away.
amisapphire: Additional notes: Some additional fans were added to the server, as the hard drives would end up being around 50°C otherwise. This was in addition to the CPU being around 60°C under load... though the fact that it had no thermal paste after ~5 years didn't help.
amisapphire's status on Thursday, 07-Sep-2023 14:19:10 EDT
Additional notes: Some additional fans were added to the server, as the hard drives would end up being around 50°C otherwise. This was in addition to the CPU being around 60°C under load... though the fact that it had no thermal paste after ~5 years didn't help.
amisapphire: Post-upgrade notes: the system drive had exhibited massive read errors, coincidentally after the storage upgrade... and no, it was not the IDE cable. 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.
amisapphire's status on Thursday, 07-Sep-2023 14:17:01 EDT
Post-upgrade notes: the system drive had exhibited massive read errors, coincidentally after the storage upgrade... and no, it was not the IDE cable. 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.
amisapphire: 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.
amisapphire's status on Thursday, 07-Sep-2023 14:00:36 EDT
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.
amisapphire: I have finally created a backup of the site data, htdocs. The 4TB scratch disk should be formatted once again, as the entire www-data directory set is no longer needed. I have already removed it from the NAS as it was supposed to be temporary. 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.
amisapphire's status on Thursday, 07-Sep-2023 13:49:56 EDT
I have finally created a backup of the site data, htdocs. The 4TB scratch disk should be formatted once again, as the entire www-data directory set is no longer needed. I have already removed it from the NAS as it was supposed to be temporary. 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.