Mat W

It's also reporting that dynamix.safe.mode.plg is not known as of today.

Last update: End result, my old USB decided to leave the chat AND the unRAID USB Creator decided it didn't want to fully create the new USB so I had to manually create it by extracting my backup to the new USB drive. Booted right up, imported key and I am back in business as if nothing went wrong. Side note: the nVidia driver was missing and had to be reinstalled but after a reboot all was happy. I'll update my original post for historical purposes.

Ok... So after much troubleshooting, I determined that the unRAID USB Creator was not working properly and did not install all of the folders and files from the USB backup I pulled down from Connect. Unsure why it is failing but unzipping the Flash backup shows all of the expected files/folders. I am in the process of manually extracting to the USB drive now. Will update again once it is complete and I have attempted to boot.

Ugh. System isn't booting as if the USB drive isn't bootable. Take it back over to Windows and run make_bootable.bat as admin and it complains that syslinux executable not found.

I've been in IT for 30 years and I can't count the number of times I've seen a reboot trigger a drive failure.

Yup. Thankfully it backed up successfully during the upgrade process! Might just stop fighting with the USB drive with an unknown age ;)

Problem I'm fighting now is getting windows to mount it, which I'm guessing might point at the USB being corrupted and not just some files. Will continue to fight with it, great way to start a Monday.

Looking at the screenshots, it looks like maybe the USB image got corrupted during the upgrade given the I/O errors for sda?

RESOLVED - My original USB died and I just needed to pull down the backup made right before the upgrade, manually extract it to a new USB (the unRAID USB Creator was not doing it properly for some reason), boot up and import the key. I'm back up and running. Just upgraded to 7.2.2 and it's not booting (see screenshots). It says the following and then say "hit enter to reboot". I'm going to continue troubleshooting and would prefer not have to reinstall the flash drive if avoidable. Please help. umount /dev: target is busy umount /: not mounted not found - press ENTER key to reboot...

Appreciate the heads up about 7.2+. Still really grateful that you republished this for 7.1.

@VladoPortos a 1000 thanks to you!!!

Yeah, no worries really. I monitor the Pi it's running on and there is the Pi-hole dashboard itself. Was mostly redundant for me if I'm being honest.

Looks like the new version of Pi-Hole (ver 6) breaks the exporter. The only way to have a token is to enable auth which then requires a password (sid=blah) which returns a csrf(?) token to also be included with requests. You can use an app token but I think it still hands out a csrf token that needs to be used. Honestly, APIs have always confused me. haha. If a password is not set, then there is no need for a token of any kind but the pi-hole exporter plugin requires a token. Just thought I'd pass all of this along...

Well, I think updating unraid-api has resolved my issue. After the update it wrote INFO level logs into stdout.log and hasn't written anything more to stdout.log.1. I'll continue to monitor but I believe that "fixed" it. root@Unplucky:/var/log/unraid-api# ls -alh total 37M drw-r--r-- 2 root root 100 Jan 11 04:40 ./ drwxr-xr-x 13 root root 780 Jan 12 08:11 ../ -rw------- 1 root root 146 Jan 3 12:40 stderr.log -rw------- 1 root root 2.8K Jan 12 08:11 stdout.log -rw------- 1 root root 37M Jan 12 08:11 stdout.log.1

I'm looking at a similar situation with stdout.log.1 not-so-slowly filling up /var/log. It seems to be set to DEBUG level logging and is not rotating despite being >10MB in size. root@Unplucky:/var/log# ls -alh unraid-api/ total 37M drw-r--r-- 2 root root 100 Jan 11 04:40 ./ drwxr-xr-x 13 root root 780 Jan 11 03:00 ../ -rw------- 1 root root 146 Jan 3 12:40 stderr.log -rw------- 1 root root 0 Jan 11 04:40 stdout.log -rw------- 1 root root 37M Jan 12 08:05 stdout.log.1 Also interesting that it's writing to ".1" and not the standard named file.

Unfortunately, my current parity check finished 10 minutes before the nightly appdata backup started. I don't know if it would have resumed properly.

Update successful. Hopefully I've got enough parity check remaining to naturally make it passed the backup tomorrow morning. I'll let you know how it does.

Awesome! Glad to help.

Here you go. unplucky-diagnostics-20230906-1005.zip

The backups finished around 4:14am and the plugin registered they finished and it was outside of increment window at 4:18am. Sep 5 04:14:05 Unplucky kernel: br-fa8d007e8d97: port 2(vethb97540b) entered blocking state Sep 5 04:14:05 Unplucky kernel: br-fa8d007e8d97: port 2(vethb97540b) entered forwarding state Sep 5 04:18:21 Unplucky Parity Check Tuning: Send notification: backup no longer running: Sep 5 04:18:21 Unplucky Parity Check Tuning: Send notification: Array operation not resumed - outside increment window: Scheduled Non-Correcting Parity-Check (68.2% completed) I have enabled testing mode logging and will provide the diags tomorrow morning.

It failed to restart after the 4am backups again this morning. I'm seeing the "Array operation not resumed - outside increment window" messaging in the logs. I'm currently using the 2023.09.03 version of the plugin.

Will do, appreciate the quick reply.

Well then, praise be onto you. 🙂

I, too, am running into the multi-notification issue but just updated to the latest so I'd expect that to resolve. I do however have another behavior that is plaguing me. I've got my parity check scheduled from 12:30am - 7:30am with it pausing for updates, backups and mover which occur at 3am, 4am and 6am respectively. What I can't figure out is the parity check pauses at 4am and does not resume until the next day at 12:30am. This feels like a config issue and maybe not a bug. Anyone have any ideas? I can provide the diagnostics if it would help.

@scolcipitato thank you, thank you and thank you. I didn't realize how much I relied on the old Docker Folder plugin until the support for it died off. Then you came along! Any way to "buy you a cup of coffee"?