rkulagow

OK - there was a go~ (backup file?) in the config directory, so I copied that to "go" and restarted. That seems to have fixed things, but not sure how we got into this state since I wasn't editing any files directly.

Attached. tower-diagnostics-20260104-0931.zip

Web page access when booted into GUI mode and from a different machine on the same LAN both state that the web page is unreachable, but SSH and local root login both work. In /etc/rc.d, I ran: ./rc.nginx start ./rc.php-fpm start That gets me to at least the login page being created, but providing my login credentials presents an HTTP 500 error /var/log/phplog has: [04-Jan-2026 09:39:29 America/Los_Angeles] PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/emhttp/plugins/dynamix/template.php:54 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(54): date('Ymd', '') #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 54 [04-Jan-2026 09:43:59 America/Los_Angeles] PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/emhttp/plugins/dynamix/template.php:54 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(54): date('Ymd', '') #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 54 [04-Jan-2026 09:44:07 America/Los_Angeles] PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/emhttp/plugins/dynamix/template.php:54 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/template.php(54): date('Ymd', '') #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/template.php on line 54

Since I have SSH, I've been just cat'ting the files to see what's in them. It's not looking good; even the filenames aren't valid in a lot of cases. So, just start taking screenshots of the running configurations, and rebuild what I can once I've rebooted onto a new Flash drive seems like my only course of action? There's no way to dump the config which is already in memory?

Thanks - I've been following that page and I've prepped a new flash drive. But will Unraid be able to re-establish my shares and docker configurations and VMs based on what's already on the hard disks, or will those be lost because the flash drive /boot/config directory is corrupted?

I've been checking in all the usual places where I might have a flash backup downloaded, (uncorrupted), but at this point I'm assuming that it's gone.

It appears the my flash drive is no longer functioning; I've ssh'd into the machine, and /boot is full of random looking garbage. For example, /boot/config/parity-checks.log has things like this: 2022<A0>May ^Q5 1;:1$:03|^T<B7>642|!26.0 MB's|0|0 202b I<E1>y 2" 13:20:35|4>034|124/9 MB/s|0|0 2<B0>22 Iay 2y 12:15:0^R\47701~165.8 MB/s|0|0 2022 Htn 5 13:"8:47|48526|123^N7 MB/s}0|2022 J<F5>n 12 93^Z47:53~49672|120.8 EJ/s|0| <B2>022"Jun 19 33:16:54|476;3|125.8 MBos|0| r022 Jun!26 13:14:14|4^W653|125.9 MB/s|0t4 2022 J<F5>l` 3 !3:14:42<47681~325.9 MB/s|0|8 r022 Jul 10 13:14:39|47278|125.9 MB/r| |1 002: Jul 15 13:24:11|48250|120.4 OB/s|0|0 My Plus.key file also appears to have high-ASCII characters. So, given that the machine is still running, is it possible to export the running config that's in memory, so that my shares, Docker configs, etc, are all retained? I did a flash backup, but I think it would be GIGO at this point. Or do I obtain a fresh flash drive and reboot with that? Knowing which drive is parity and which are data is easy, because my parity is larger than my data drives. But what about all the other settings? My Plus.key is from 2016, so I don't know that I have that email around any longer. tower-diagnostics-20230223-1805.zip