Just checked. Was sure I kept the old one around for reference as NcCheckboxRadioSwitch-hel9-sAH-DWj7ZO5U.mjs.old but alas not (well I think I did and probably removed it when happy with the fix, doh - als checked and tis is one of the servers I still have on ext4 not btrfs so lack a timely snapshot between the install and now).
I did look at it and it looked internally similar to the good one, like compressed JavaScript (unnecessary whitespace no more) and so it was tricky to diff, which I did with meld but of course the lines are very very long and so took a long time to diff with not very useful summary resulting.
PHP:
$ php --version
PHP Warning: JIT is incompatible with third party extensions that override zend_execute_ex(). JIT disabled. in Unknown on line 0
PHP 8.1.2-1ubuntu2.17 (cli) (built: May 1 2024 10:10:07) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.2, Copyright (c) Zend Technologies
with Zend OPcache v8.1.2-1ubuntu2.17, Copyright (c), by Zend Technologies
with Xdebug v3.1.2, Copyright (c) 2002-2021, by Derick Rethans
as to OS and distro:
$ inxi -Fz
System:
Kernel: 5.15.0-102-generic x86_64 bits: 64 Console: pty pts/0
Distro: Ubuntu 22.04.4 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: Intel model: D54250WYK v: H13922-305 serial: <superuser required>
UEFI: Intel v: WYLPT10H.86A.0051.2019.0322.1320 date: 03/22/2019
CPU:
Info: dual core model: Intel Core i5-4250U bits: 64 type: MT MCP cache: L2: 512 KiB
Speed (MHz): avg: 1297 min/max: 800/2600 cores: 1: 1297 2: 1297 3: 1297 4: 1297
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
Display: server: No display server data found. Headless machine? tty: 322x76
Message: GL data unavailable in console. Try -G --display
Audio:
Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel
Device-2: Intel 8 Series HD Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.15.0-102-generic running: yes
Network:
Device-1: Intel Ethernet I218-V driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 2.05 TiB used: 499.61 GiB (23.8%)
ID-1: /dev/sda vendor: Samsung model: SSD 840 EVO 250GB mSATA size: 232.89 GiB
ID-2: /dev/sdb type: USB vendor: LITE-ON model: 1 UITRA1 size: 1.82 TiB
Partition:
ID-1: / size: 113.32 GiB used: 25.37 GiB (22.4%) fs: ext4 dev: /dev/dm-0
ID-2: /boot size: 973.4 MiB used: 252.9 MiB (26.0%) fs: ext4 dev: /dev/sda2
ID-3: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
ID-1: swap-1 type: file size: 4 GiB used: 104.8 MiB (2.6%) file: /swap.img
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
Info:
Processes: 169 Uptime: 50d 13h 48m Memory: 15.51 GiB used: 1.61 GiB (10.4%) Init: systemd
runlevel: 5 Shell: Bash inxi: 3.3.13
It does indeed appear to be a mystery. Leaves me wondering if a bad disk sector perhaps caused a hiccup. fsck is useless on the running server, and haven’t time to bring it down and boot off a USB right now to use that on the root filesystem, but SMART is possible:
$ sudo smartctl /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-102-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
ATA device successfully opened
Use 'smartctl -a' (or '-x') to print SMART (and more) information
cirrus@nephele:/var/www/html/nextcloud/apps/activity/js$ sudo smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-102-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Samsung SSD 840 EVO 250GB mSATA
Serial Number: S1KPNEAF203696L
LU WWN Device Id: 5 002538 844584d30
Firmware Version: EXT41B6Q
User Capacity: 250,059,350,016 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
TRIM Command: Available
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Jun 6 09:07:20 2024 AEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 4800) seconds.
Offline data collection
capabilities: (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 80) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 076 076 000 Old_age Always - 119267
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 364
177 Wear_Leveling_Count 0x0013 093 093 000 Pre-fail Always - 78
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0
183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0032 077 049 000 Old_age Always - 23
195 Hardware_ECC_Recovered 0x001a 200 200 000 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0
235 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 273
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 41570598293
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
and I see Runtime_Bad_Block is at Pre-fail. Not sure that explains anything though as at the SMART level I’d expect any bad blocks not to present as a write issue in the user space (i.e. I’d expect it’s handled quietly by lower layers and just works in the user space).
