Starfiresg1

Hello, thanks for clarifying. From the wording of the message I thought the updater would make a "safety" backup if automatic backups are enabled. I have set it to 30 days but none of the current backups seem to be in an automatic interval, the last two I created manually for sure. I will see what happens next month, if it doesn't work I will run it via cron as suggested. The 0 days are confusing me - At the time of the message the last manual backup was approx. 10 days old and I configured it for 30 days - should the message not say "in the recent 30 days" then?

I have noticed an issue with automatic backups. I have configured it to take backups every 30 days but nothing seems to happen. During updates I get the following output Even through the last manual backup is several days old. Manual backups work fine however.

I have noticed the following: When I use the search and click on a result it always takes me to the last page in the topic instead of the specific post/comment. Searching within a topic is pretty pointless, because all results will just open the last page of the thread. In tried both on Firefox and Edge. Example: A search result links to this will open the end of the thread the post resides in and not the post itself If I manually change the link to the following it would take me to the correct post

You can try the following: First add a virtual SCSI contoller to your config: <controller type='scsi' index='0' model='virtio-scsi'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller> If slot 0x09 is already used in your config for another device change it to something else Then add the passthrough for the drive <hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host2'/> <address bus='0' target='0' unit='0'/> </source> <alias name='hostdev0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev> scsi_host2 -> the number of the drive in your system -> in your case scsi_host2 since you have [2:0:0:0] Both of these need to be in the devices-section.

Hello, I've been using the S3 Sleep plugin for ages without issues. But for a while now I've run into problems: Sometimes when I put the system to sleep using the button on the main page instead of going to sleep the server does a clean shutdown. More often the system does a clean shutdown immediately after waking up from sleep. This happens regardless of it waking up by manual button press or by using WOL. I've attached the diagnostics after this just happened. I couldn't find a reason for the shutdown in the previous syslog. It just states "shutdown[19899]: shutting down for system halt". Feb 9 11:08:43 Starhost kernel: sd 6:0:0:0: [sdd] Starting disk Feb 9 11:08:43 Starhost kernel: OOM killer enabled. Feb 9 11:08:43 Starhost kernel: Restarting tasks ... Feb 9 11:08:43 Starhost kernel: sd 7:0:0:0: [sdg] Starting disk Feb 9 11:08:43 Starhost kernel: done. Feb 9 11:08:43 Starhost kernel: random: crng reseeded on system resumption Feb 9 11:08:43 Starhost kernel: PM: suspend exit Feb 9 11:08:43 Starhost emhttpd: spinning down /dev/sdl Feb 9 11:08:43 Starhost shutdown[19899]: shutting down for system halt Feb 9 11:08:43 Starhost dhcpcd[2207]: br0: deleting route to 192.168.10.0/24 Feb 9 11:08:43 Starhost dhcpcd[2207]: br0: deleting default route via 192.168.10.1 Feb 9 11:08:43 Starhost dnsmasq[18427]: no servers found in /etc/resolv.conf, will retry Feb 9 11:08:43 Starhost dhcpcd[2207]: br0: carrier acquired Feb 9 11:08:43 Starhost kernel: sd 8:0:2:0: Power-on or device reset occurred Feb 9 11:08:43 Starhost kernel: sd 8:0:0:0: Power-on or device reset occurred Feb 9 11:08:43 Starhost kernel: sd 8:0:1:0: Power-on or device reset occurred Feb 9 11:08:43 Starhost kernel: sd 8:0:5:0: Power-on or device reset occurred Feb 9 11:08:43 Starhost kernel: sd 8:0:3:0: Power-on or device reset occurred Feb 9 11:08:43 Starhost kernel: sd 8:0:4:0: Power-on or device reset occurred Feb 9 11:08:43 Starhost dhcpcd[2207]: br0: soliciting a DHCP lease Feb 9 11:08:43 Starhost dhcpcd[2207]: br0: offered 192.168.10.10 from 192.168.10.1 Feb 9 11:08:43 Starhost dhcpcd[2207]: br0: probing address 192.168.10.10/24 Feb 9 11:08:44 Starhost init: Switching to runlevel: 0 Feb 9 11:08:44 Starhost s3_sleep: Wake-up from sleep mode Feb 9 11:08:44 Starhost rc.0: Running shutdown script /etc/rc.d/rc.0: Feb 9 11:08:44 Starhost init: Trying to re-exec init Feb 9 11:08:44 Starhost rc.0: Saving system time to the hardware clock (UTC). Feb 9 11:08:44 Starhost rc.0: Creating system time correction file /etc/adjtime. Feb 9 11:08:44 Starhost rc.0: /sbin/hwclock --utc --systohc diagnostics-20250209-1118.zip

I updated again - installer now mentioned "Database successfully updated" - Dashboard was directly working after the update. 👍

When updating to 2024.10.27 the updates completes as expected and the "Done" button appears - it no longer navigated to the settings page during upgrade like it did with 2024.10.26 for me. The update windows states now that the existing database (that I restored from a backup) didn't need an upgrade. After the update the settings page of the plugin worked out of the box. The dashboard however was broken (empty) again. Going to the "Configuration" page in the plugin settings and clicking "Save" without actually changing anything fixed the dashboard again. Maybe my old database was missing some settings-migrations from the broken update to 2024.10.26? So far everything is working now Found the following new warning in the PHP log - maybe related to the initial empty Dashboard? [27-Oct-2024 12:56:43 Europe/Berlin] PHP Fatal error: Uncaught Error: Failed opening required '/usr/local/emhttp/plugins/disklocation/pages/styles/signals.css' (include_path='.:/usr/local/emhttp') in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715) : eval()'d code:61 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715): eval() #1 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715) : eval()'d code on line 61

I just upgraded this plugin inside Unraid. During the update progress I noticed a big bold red text appearing in the progress window "database too old ..." - I can't remember the rest because it disappered too quickly. Right after that the Web GUI automatically changed to "http://xxxx/Tools/disklocation" which shows basically an empty page with the label "Devices" in the top left. I have never seen such behavior during a plugin upgrade before, normally the progress window informs me that the update is done and I click the "done" button - here automatically the WebGUI goes somewhere else, which is completely unexpected. After reading the previous reports, I can conform that the Dashboard is also fully broken, meaning completely empty. I'm using current Unraid 6.12.13 I found the following in the PHP log (log level default): [26-Oct-2024 22:35:06 Europe/Berlin] PHP Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php:9 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/load_settings.php(9): json_decode(Array, true) #1 /usr/local/emhttp/plugins/disklocation/pages/system.php(486): include('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715) : eval()'d code(21): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php on line 9 [26-Oct-2024 22:35:28 Europe/Berlin] PHP Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php:9 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/load_settings.php(9): json_decode(Array, true) #1 /usr/local/emhttp/plugins/disklocation/pages/system.php(486): include('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715) : eval()'d code(21): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php on line 9 [26-Oct-2024 22:35:41 Europe/Berlin] PHP Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php:9 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/load_settings.php(9): json_decode(Array, true) #1 /usr/local/emhttp/plugins/disklocation/pages/system.php(486): include('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715) : eval()'d code(24): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php on line 9 [26-Oct-2024 22:41:41 Europe/Berlin] PHP Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php:9 Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/load_settings.php(9): json_decode(Array, true) #1 /usr/local/emhttp/plugins/disklocation/pages/system.php(486): include('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715) : eval()'d code(21): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(715): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(82): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/load_settings.php on line 9 Edit: I looked at the PHP, and the error seems to occur while reading the settings from the database. So I took a look at mine and noticed, that the current database (/boot/config/plugins/disklocation/disklocations.sqlite) is completely empty - it contains the table structure but no actual data anymore. My guess is that the updater tried to migrate the database (hence the message "database too old" i saw) and failed - maybe by automatically loading another URL during the upgrade process which happened to me. I replaced the database with the most recent backup (from /boot/config/plugins/disklocation/backup - file needs to be unzipped first!) - this gets the dashboard working again. There will probably be issues with that path, because something that was supposed to be changed in the database during the upgrade is now not there! TLDR: Restoring from a recent disklocation-database backup will fix the dashboard - hopefully @FlamongOle will be able to fix this soon

You can use the Unraid USB Creator - choose "Local Zip" instead of "Stable" and point it to your backup.