Public timeline, page 2

Notices

1. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 10-Oct-2023 00:36:06 EDT Clarissa Walker
   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.
2. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 30-Sep-2023 21:27:43 EDT Clarissa Walker
   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.
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 30-Sep-2023 21:39:13 EDT Clarissa Walker

     in reply to
     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 ~ $
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 30-Sep-2023 22:52:23 EDT Clarissa Walker

     in reply to
     Forgot about the Compile Box: the other Linux machine at hand... the 40GB drive can be accessed on that machine.
3. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 27-Sep-2023 22:55:38 EDT Clarissa Walker
   Server update!
   
   
   Upgrades:
   openssl: 1.1.1v -> 1.1.1w
   
   Recompiled:
   httpd-2.4.57
   php-7.4.33
4. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 23-Sep-2023 21:33:17 EDT Clarissa Walker
   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)
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 23-Sep-2023 21:40:29 EDT Clarissa Walker

     in reply to
     Forgot:
     
     Upgrades:
     pcre2: 10.39 -> master_20230920
5. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 23-Sep-2023 21:36:15 EDT Clarissa Walker
   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.
6. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Friday, 08-Sep-2023 12:57:58 EDT Clarissa Walker
   Server Update!
   
   mariadb: 10.11.4 -> 10.11.5
   
   
   OpenSSL needs to be updated; doing so another time, however.
7. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 07-Sep-2023 13:49:56 EDT Clarissa Walker
   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.
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 07-Sep-2023 14:00:36 EDT Clarissa Walker

     in reply to
     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.
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 07-Sep-2023 15:58:50 EDT Clarissa Walker

     in reply to
     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.
8. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 07-Sep-2023 14:21:21 EDT Clarissa Walker
   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.
9. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 07-Sep-2023 14:17:01 EDT Clarissa Walker
   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.
   • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 07-Sep-2023 14:19:10 EDT Clarissa Walker

     in reply to
     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.
10. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 14-Aug-2023 21:13:00 EDT Clarissa Walker
    There was unscheduled downtime due to me adding 2TB to the server. Finally, I am creating a backup of the current server data.
    
    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.
11. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 05-Aug-2023 19:51:27 EDT Clarissa Walker
    I was busy collating some Android stuff from the file server, probably to add to the main server at some point.
    
    
    The stuff as follows:
    
    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.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 05-Aug-2023 20:12:46 EDT Clarissa Walker

      in reply to
      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.
12. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 26-Jul-2023 07:07:59 EDT Clarissa Walker
    That said, Mastodon 4.x follows still do not work despite the 500 patch, so the site will probably have to be HTTPS. Amusingly, Soapbox follows still work regardless, as it seems to use a forked Mastodon 3.x format.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 26-Jul-2023 07:12:12 EDT Clarissa Walker

      in reply to
      Since these follows are merely tests on this setup, I unfollow them right after; this is why the Following section in my profile is 0.
13. Clarissa Walker started following Alex Gleason.
    In conversation Wednesday, 26-Jul-2023 07:02:28 EDT from activity permalink
14. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 26-Jul-2023 06:27:03 EDT Clarissa Walker
    Another test link: a Github one this time.
    
    https://github.com/madires/Transistortester-Warehouse
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 26-Jul-2023 06:31:28 EDT Clarissa Walker

      in reply to
      Okay, so it's just notabug links so far; seems there's no valid image linking to them in some way.
      
      Home page:
      https://notabug.org/
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 26-Jul-2023 06:32:44 EDT Clarissa Walker

      in reply to
      So that worked.
      
      Main repo for the GNU social fork:
      https://notabug.org/gnusocialjp/gnusocial
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 26-Jul-2023 06:34:54 EDT Clarissa Walker

      in reply to
      So linking repos from notabug have no valid image thumbnail filename here. Something to figure out someday.
15. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 25-Jul-2023 21:11:02 EDT Clarissa Walker
    Updated GNU social to the latest fork (GNUsocial.jp variant). A few more subtle changes there.
    
    This particular branch is here:
    https://notabug.org/gnusocialjp/gnusocial/src/develop
    
    Reference:
    http://cwcyrix.nsupdate.info/gnu-social/public/notice/34
16. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 25-Jul-2023 05:49:15 EDT Clarissa Walker
    Cosmetic change to the site data path: sitedata -> www-data
    
    Also, the mariadb systemd config is cleaned up... once again.
    
    I still have a copy of the pre-migration MariaDB config; this will be part of the server backup. I say this because I made changes to that as well.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 25-Jul-2023 05:54:30 EDT Clarissa Walker

      in reply to
      Okay, the database is more responsive after these changes... probably a coincidence.
17. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 06-Jul-2023 10:37:42 EDT Clarissa Walker
    Shut down the second NAS; will run a consistency check on the main NAS's MediaShare, now that I have the hashes for the MediaDrive.
    • Show all 4 replies
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Friday, 14-Jul-2023 23:05:39 EDT Clarissa Walker

      in reply to
      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.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 17-Jul-2023 17:00:37 EDT Clarissa Walker

      in reply to
      Copied the 500GB HDD image to the WD 1TB HDD again, and got an entirely different hash from the last attempt. The drive will have to be zero-filled.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 25-Jul-2023 05:53:45 EDT Clarissa Walker

      in reply to
      Yeah, the terabyte drive is to not be trusted... until I should try it out on a USB 3.x enclosure.
      
      The 500GB image had an entirely different hash, even after zero-filling the drive.
18. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 17-Jul-2023 08:43:45 EDT Clarissa Walker
    Most of that delayed time from the server upgrade has been spent reorganizing the main NAS data (and changing the system drive and backup drive). So I finally wrangled that issue.
    
    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.
19. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Friday, 14-Jul-2023 23:44:02 EDT Clarissa Walker
    Recently I have bought a Pioneer BDR-XD07B portable Blu-ray/DVD/CD burner for $40. The blue laser diode's preliminary testing was a a few PS3 discs; this worked in a way, as it "recognized" the PS3 discs - rather than the drive responding as 'No Disc', anyway.
    
    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.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 17-Jul-2023 08:17:59 EDT Clarissa Walker

      in reply to
      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).
20. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Sunday, 04-Jun-2023 20:42:17 EDT Clarissa Walker
    Bad sector count is now 9 from 8 as previously. SMART Device Error count remains at 22, which was there about a month before the first bad sector count (which was at 2).
    
    Reference:
    http://cwcyrix.nsupdate.info/gnu-social/public/notice/90
    • Show all 7 replies
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 11-Jul-2023 01:31:53 EDT Clarissa Walker

      in reply to
      Swapped the suspect drive with the replacement and the array is rebuilding as of this post. Should be done by morning.
      
      The old 4TB Toshiba Enterprise drive is now a scratch disk, as is the older 1TB Western Digital Blue drive.
      
      ...I think I have an idea of what to do with the 4TB drive, though.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 12-Jul-2023 20:20:36 EDT Clarissa Walker

      in reply to
      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.
    • Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 13-Jul-2023 11:37:12 EDT Clarissa Walker

      in reply to
      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! 😮