ljm42

Please see if this applies: https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1281063

Unrelated to the release, you can turn help on/off by clicking the question mark icon in the upper right corner of the page.

So the system is on 6.11.5 now right? Is the delayed bootup a new problem on that version or has it always been that way?

udev is what detects your hardware. For whatever reason this system is slow to respond about what hardware is connected. It might(?) help to go in your bios and disable things you aren't using, like bluetooth, wifi, serial ports. You could try messing with USB settings, like enable/disable legacy mode. Just some ideas, no guarantees : )

So at this point is everything good?

Unraid Connect doesn't yet support reverse proxies. To use Unraid Connect you need to access the server through one of the URLs listed on Settings -> Management Access.

Think of Unraid as an appliance, you want to modify the OS as little as possible. You should run apps like this in a Docker container, PiHole is a pretty popular one. We generally recommend that Unraid use public DNS servers like 8.8.8.8 to reduce issues with accidental blocking and increase stability when the container isn't running.

Yes, but there is a quick fix. This is from the 6.12.0 release notes:

That is what makes it difficult to track this down : ) but we're working on a solution. Thanks for confirming this resolved the issue with the stopping the array, we're working on a solution

The API looks good. If you are still seeing a message that says "disconnected from Unraid API" then it is likely you have ad blockers or extreme privacy settings getting in the way. Try a different browser or a clean browser profile.

We are working on a fix for nginx with IPv6 but for now you should go to Settings -> Network Settings and change eth0 to "IPv4 only" if that works in your environment. Also, please see my comment here about browsers potentially causing issues with backgrounded tabs: https://forums.unraid.net/bug-reports/stable-releases/612-unraid-webui-stop-responding-then-nginx-crash-r2451/page/3/?tab=comments#comment-25245

wanip4.unraid.net doesn't respond to ping, so no errors there. Your screenshot is cutoff, is there a "restart API" option? If so, go ahead and click that. If you don't have that option, open a web terminal and type: unraid-api start wait two minutes, then: unraid-api report and paste the results back here

UPDATE! please see my comment further down in this thread https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1283203 ------------------------------- Original message: ------------------------------- I hit this today when stopping my array. Here is what worked for me, would appreciate if someone hitting this would confirm it works for them too. To get into this state, stop the array. If you are having this issue you will see "retry unmounting shares" in the lower left corner. Note: There are other reasons this message could happen (like if you left an SSH terminal open while cd'd into the array). This discussion assumes none of the usual suspects apply. In a web terminal or SSH type 'losetup'. In my case it showed: root@Tower:/etc/rc.d# losetup NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/cache/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512 The problem is that docker.img is still mounted. Note that in my case is it on /dev/loop2 Then run `/etc/rc.d/rc.docker status` to confirm that docker has stopped: # /etc/rc.d/rc.docker status status of dockerd: stopped (It should be stopped, since you were in the process of stopping the array. But if Docker is still running, you can type `/etc/rc.d/rc.docker stop` and wait a bit, then run status again until it has stopped.) Then to fix the problem, type: umount /dev/loop2 (use whatever /dev/loopX docker.img is on, as noted above) Once that is unmounted, the array will automatically finish stopping. We are looking into a fix for this, but it would help if we could reliably reproduce the problem (it has only happened to me once). If anyone is able to identify what it takes to make this happen I'd appreciate it.

Do you have any Docker containers running on port 80 or port 443? nginx is refusing to start because something is already on port 80: Jul 5 18:15:20 PLEXBOXX nginx: 2023/07/05 18:15:20 [emerg] 1797#1797: bind() to [::1]:80 failed (99: Cannot assign requested address) The usual cause is a port conflict with a Docker container. However, a conflict with port 80 should also affect 6.9.2 so I'm somewhat confused. I'd suggest carefully editing config/docker.cfg on the flash drive and change this: DOCKER_ENABLED="yes" to this: DOCKER_ENABLED="no" Then reboot. The webgui should load after this. Then you can try starting Docker and probably one of your containers won't be able to load. You can either change the port that container uses, or go to Settings -> Management Access and change the port that Unraid uses for HTTP and HTTPS. We recommend you pick high numbers between 1000 and 64000.

Are you intentionally using a non-standard netmask for your network? NETMASK[0]="255.255.254.0" If that isn't intentional, edit config/network.cfg on the flash drive and change that to: NETMASK[0]="255.255.255.0" then reboot. If there are still issues please provide updated diagnostics.

What version of Unraid are you currently running? We improved the killswitch in 6.11.2 (after your previous thread) but it does require you to make a dummy change to the tunnel and apply. Please follow the first post of this guide closely to setup the tunnel and container: https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access-to-a-commercial-vpn-provider/ If you are able to bypass the kill switch using a tunnel created/modified in 6.11.5 or 6.12.2 please provide details on how to reproduce the issue

There are two known issues mentioned in the release notes

Your system has call traces related to macvlan, see https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues Doing a lot of back and forth in a release post is tough, I'd recommend making your own thread for further discussion

Please don't take this the wrong way : ) but when it fails, are you sure you are editing the right file? For instance, if there happens to be a copy of the go script in the wrong place, maybe you are editing that one instead of the one in the config folder? If you are 100% sure you are editing the right file, then I would suspect the flash drive is starting to fail. You should grab a backup (Main -> Boot -> Flash -> Flash Backup) and then get a new flash drive on order just in case. You don't need to actually swap it out yet, just have it ready in case there are other symptoms of failure.

These diags are from 2019 Also, in case I wasn't clear, while tracking down this problem you should not have anything in the extra folder either. We need the system to boot without old packages potentially causing issues.

What is the part you blanked out? The correct CN should be: CN=*.sfo2.digitaloceanspaces.com,O=DigitalOcean\\, LLC,L=New York,ST=New York,C=US If a different CN is listed then someone is trying to do a man-in-the-middle attack on you. I would talk to your IT department as something doesn't seem to be setup correctly on the network.

I moved @cyberdust's comment to its own thread:

Go ahead and let Windows repair the drive. On the flash drive, do you have a file named vfio-pci.cfg in the config folder? Try renaming that file to something else and see if it will let you boot. If so, once you get back in to the webgui go to Tools -> System Devices and reconfigure your vfio bindings.

@comet424 It looks like all three of these systems have Realtek network cards. Unraid ships with the official drivers that Linux provides, but the community has created a plugin with out-of-tree drivers from Realtek: https://forums.unraid.net/topic/141349-plugin-realtek-r8125-and-r8152-drivers/ This is a brand new plugin that isn't yet available in Community Apps, but you can install it manually if you'd like. You want the R8125 version. Can you clarify, are you still seeing the infinity cpu usage in 6.12.2?

General instructions for manually upgrading or downgrading are here: https://docs.unraid.net/unraid-os/manual/upgrade-instructions#manual-upgrade-or-downgrade But be sure to read the release notes for 6.12 to see additional steps to take after downgrading.