SirCadian

I'm feeling foolish now. Just realised I have configured static DNS on Unraid itself to point to 1.1.1.1 and 1.0.0.1. Issue must have been related to something else.

Is there a requirement for functioning network when upgrading to 7.3? I run a Pihole docker and this usually means the network (more specifically, DNS) is unavailable when Unraid is rebooting. I backed up the flash and then upgraded from 7.2.6 to 7.3. Unraid booted to the OS selection screen but failed shortly after that. I left it for a 1600s or so while I went to get lunch but it was still unresponsive when I got back so I powered it down manually. I repointed the network to use 1.1.1.1 for DNS and tried to boot Unraid again and it booted without issue. Just posting here in case anyone else has seen similar behaviour?

Pretty excited about this, solid notifications support is something that has been missing from Unraid for a while, imo. Is the plan to include this as part of a future core Unraid release or will it become a plugin? Do you have an ETA for a stable/tested release? Thanks!

Just to follow up on this. The drive was confirmed as DOA and I returned it. Currently pre-cleared a new replacement drive and am in the process of rebuilding parity using the new drive. I'm doing this in maintenance mode so that the old parity drive remains valid in case there are any issues. Quick supplementary question. Once the parity sync completes, I will want to add the old parity drive back into the array as a data drive. Do I need to format it first, or do I just stop the array, add the old parity drive back in as a data drive and allow Unraid to do its thing (I'm assuming here that it will format the drive and that clear/pre-clear will be un-necessary)? Thanks!

I'm having some issues with a new drive that arrived today, a Western Digital 12Tb Red Plus. My array (3x8Tb Data + 1 8Tb Parity) is running short of space and I decided to upgrade the parity drive with a larger model and re-use the old parity drive as a data drive. I shut down my server, installed the drive and then rebooted. The drive appears in the BIOS but, unusually, the capacity shows as 0Gb. When I boot to Unraid, the new drive doesn't appear in Unassigned devices at all. I've tried the following: Updated to latest BIOS (Asus WS C246 Pro). Same problem. I've swapped the 12Tb drive out for an old 6Tb I had lying around. This was instantly picked up by unassigned devices and I was given the option to format it. I've installed the drive in my desktop PC. It appears in Windows 11 Disk Manager and I'm prompted to initialise it but when I try that I get "request could not be performed because of an I/O device error". I'm pretty sure the disk is DOA and I need to return it. Is there anything I'm missing here? It's a larger drive than I've used before but I can't find any reports of compatibility issues with larger SATA drives for my motherboard or Unraid. Thanks for any help or info.

Still no issues here. It's looking like the issue was either something to do with the Unbalanced plugin being installed (I didn't use it at any point) or possibly the Unassigned Devices plugin which I re-installed. Either way, I'm happily sitting at 41 days uptime and counting.

@Harb Sorry for the tardy response, I've had a busy couple of weeks. I removed Unbalanced and did a re-install of Unassigned Devices. Happily I'm in the same boat as you and have had no issues since then. I didn't really use Unbalanced anyway, it was more of a just-in-case plugin, so I've not re-installed that. I believe there's functionality in the mover now that can move the contents of a disk to other disks in the array, so I'll stick with the official tool in the event I need that capability. I think it seems to be fixed but I'll need a longer test period before I'm fully confident. Prior to this issue I was seeing uptimes measured in months, not weeks. I only really had to bounce the server for upgrades. I'll keep reporting back. As an aside, I also started tracking RAM consumption over time in the event that the issue was some kind of memory leak. I grab the stats from the homepage at the same time every day. Nothing much to see, big jump in docker usage is a new Ark Server I deployed for my kid (which Studio Wildcard borked with an update a couple of days later and I had to manually rollback) otherwise the dockers/vms are stable with no other changes. There's slight creep in system memory usage but nothing concerning. I'll keep logging the stats just for interest's sake.

OK, cool. I'll also re-install the unassigned devices plugins. See how it goes. I'll keep you posted.

I'm having exactly this issue. It has been driving me mad since I first installed 7.x. Based on the above, I've uninstalled Unbalance as I don't ever use it. I have occasional use for the Unassigned Devices plugins though so will leave them enabled for now. If I encounter the issue again, I'll post about it here. @Harb I'd appreciate it if you could post again if you encounter any further issues. I'm really not a fan of having to physically power off my server, so am keen to get to the bottom of this issue.

Sorry to necro this, but did you find a solution to this? I mapped the path to my unraid disks and set up the disks in the widgets yaml as mentioned. Ended up getting the same thing as you, a blank set of disks widgets. Not sure why. **EDIT** **Note: Discovered that the solution below causes Unraid to map user shares directly to disk1, etc. Whilst the solution works, it also generates warnings from the 'Fix Common Problems' plugin. Still looking for a solution that works around that issue** Found the solution on reddit. I mapped container paths to each disk individually: /disk1 = /mnt/disk1/ /disk2 =/mnt/disk2/ etc. You can map the whole array at '/mnt/user/' and the system/boot drive at '/boot/'. I mapped them all as read-only...seemed sensible.

I am. I'd completely forgotten I could use localhost. I feel quite foolish, thanks for the help!

I have a (hopefully) quick question. I have binhex PrivoxyVPN set up as network type "bridge". I have a number of other containers that route traffic through it using the "--net=container:binhex-privoxyvpn" extra parameter and have port mappings set up appropriately. This all works fine. I have one docker that both routes its traffic through the binhex-privoxyvpn container and needs to talk to other dockers using that container's network. I achieve this by using the binhex-privoxyvpn assigned ip and the relevant port. The issue is that, on reboot of Unraid or (sometimes) update of the binhex privoxyvpn container, that IP address changes and I have to change the dependant docker config. Is there any way I can fix the IP address or refer to the binhex-privoxyvpn container by name?

Afraid I don't. I think I may have identified the issue though. Docker wouldn't start after I posted my last update. It looks like the docker img was corrupt. I deleted it and re-added all my containers. I still saw some CPU spikes that seem to be related to the Dynamic Cache Directories plugin (high 'find' and 'shfs' CPU usage) so I've disabled. Things seem stable now. I'll live with it for a while and see if the issue is resolved. If not, i'll grab a diagnostics and issue timestamp and post here. Thanks for your help so far.

Yes. Although I had stopped Docker and VMs at that point as it was the only way I could get the diags. I can try to get everything up and running again and grab some diags then if it will help?

I use a user script to create persistent syslog. It's still an issue, I can't seem to run anything on it without the system becoming unstable. I've attached the diags. If you need earlier syslogs than the one in the diag zipfile, I can attach those. Thanks for looking at this. falcon-diagnostics-20240626-1557.zip