Unraid 6.12

[Abbie Buesing]

Secondwe fixed a corner case bug that can lead to data loss if a newly added array drive has a non-standard partition layout. If you add one of these drives, the second time you start the array, the drive will show as unformatted. If this happens, please contact support, and we can help you with data recovery. Even if you have not encountered this issue, we recommend upgrading so that you will not be affected when adding drives in the future.

This release also includes some nice fixes in networking, Docker containers, Time Machine support, and VMs as well as fix for a slowdown some systems were having on the Dashboard. We have also improved the SMART attribute handling for NVME and SSD drives.

Some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. If this affects you, see the alternate solution available since Unraid 6.12.4.

If you are having network issues of any kind, confirm that you have not enabled jumbo frames. Navigate to Settings > Network Settings > eth0 and confirm the Desired MTU is 1500. For more information see the Fix Common Problems warning for jumbo frames.

If you continue to have network stability issues and Tools > System Devices shows that you have a Realtek ethernet controller, grab the part number shown and search Community Apps to see if there is a Realtek vendor-supplied driver plugin for that device. For more information, see the support page for Realtek driver plugins.

If you have other crashes or stability issues, navigate to Settings > Syslog Server and enable Mirror syslog to flash. This will cause additional wear and tear on you USB flash boot device but is useful in the short term for gathering logs after a crash.

If you are getting call traces related to macvlan (or any unexplained crashes, really), as a first stepwe recommend navigating to Settings > Docker, switching to advanced view, and changingthe Docker custom network type from macvlan to ipvlan. This is the default configurationthat Unraid has shipped with since version 6.11.5 and should work for most systems.

Note that some users have reported issues with port forwarding from certain routers (Fritzbox) and reducedfunctionality with advanced network management tools (Ubiquity) when in ipvlan mode. If this affects you,see the alternate solution available since Unraid 6.12.4.

If you are having network issues of any kind, confirm that you have not enabled jumbo frames.Navigate to Settings > Network Settings > eth0 and confirm the Desired MTU is 1500.For more information see the Fix Common Problems warning for jumbo frames.

If you continue to have network stability issues and Tools > System Devices shows that you have a Realtek ethernet controller,grab the part number shown and search Community Apps to see if there is a Realtek vendor-supplied driver plugin for that device.For more information, see the support page for Realtek driver plugins.

If you are having other crashes or stability issues, navigate to Settings > Syslog Server andenable Mirror syslog to flash. This will cause additional wear and tear on you USB flash boot device but isuseful in the short term for gathering logs after a crash.

After the next reboot, navigate to Tools > Diagnostics and download your anonymized diagnostics (as of 6.12.5,diagnostics automatically include logs that were mirrored to the flash drive).

I recently upgraded to 6.12.6 from 6.10.something, and since then, my server has been consistently becoming unresponsive. Remote access goes dead, the web UI times out, and I get connection refused when trying to SSH. I have a monitor connected to the server, and there's simply no display when this happens, and keyboard inputs do nothing. This has happened now 3 times in the last 5 days or so.

After the second crash, I have configured syslog to dump onto the array, but in looking at the log, there doesn't seem to be anything logged during the problem. I've attached both the diagnostics file and the syslog file that is on the array.

This is the only crash that has happened since I started the syslog. I've set up external monitoring now, so I should get a better idea of when exactly it crashes, but I don't know how much help that will be if nothing is logged during the crash...

Having nothing relevant logged usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Any diags I can run to test the hardware and see what might be failing? Not sure if unraid has anything like that built in... my motherboard is old enough that it doesn't have built-in diagnostics that I'm aware of...

@count-zero I have similiar issues, random crashes and nothing in the logs. For me all started with the 6.12.x builds. What I noticed during the last weeks as long as I'am not logged in Unraids webui it doesn't crash. I now close any VNC VM windows and logout from the webui if I don't need to use it. Firefox on a Windows machine I use tu administrate the server.

@JorgeB did you heared about that "phenomenon"? I have tested basically everything. Disks are ok, no errors. Memtest no errors. Switched to different power outlets, configured all sorts of stuff in the BIOS, with or without virtualisation, different power saving modes, disabled all sorts of devices like wifi or BT cards. Also disabling Docker or VMs or even running Unraid in Save Mode for a couple days didn't help. It always crashes between 4hours uptime up to 3-4 days with nothing logged.

Now the interesting part. During all that crashes I had a Firefox window on another Windows box with different Unraid pages opened. Sometimes the Docker page, next time the Dashboard or the Main tab. As soon as I log out and close the Firefox Tabs surprise surprise crashes are gone.

I saw a lot of threads opened with random freezes and crashes with the 6.12.x Unraid builds. Most people had issues with MacVLAN, switching to IPVLAN didn't help for me. Maybe this is something you can tell the people to test to pin down the problem.

Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

Just came across this thread. Good to know its not just me. My server seems to be locking up or something every few days or so. Then all of a sudden without doing anything its just fine. Rebooting doesnt seem to matter. Also "Fix Common Issues" plugin seems to be broken as well. Haven't even looked into that yet.

I think I may be in the same boat. Everything was working fine until today when I found I could no longer connect to the unraid. The box was running and I started the GUI on the server after a reboot and started the array to find that networking is failing going out and now it says that it can't mount the XFS drives which was odd as I thought they were using ZFS before I upgraded to 6.12.6

True... But the plugin does not allow you to setup the main array with ZFS so i would need to sacrafice one of my drives or setup something like a USB flash drive as the array just so i can use the server.

Which i may end up doing. But for now i think i am just going to continue using this as an excuse to procrastinate...

I really hope i have not misunderstood the planned ZFS implementation. When i hear "ZFS Support", Single device pools are not exactly the first thing that comes to mind. My plan this whole time has been to setup my main array as a RAID-Z2 with 8 disks. Please tell me thats actually going to be possible...

AFAIK, Unraid's parity protection can ONLY work with single device pools. That doesn't mean you can't use a multi device pool as YOUR main array in Unraid though, it just won't be part of the parity1, parity2, disk1, disk2 etc. array, but it can participate in the user share system. Whether or not you will still be required to have one volume of whatever format in the disk1 slot for 6.12, probably, but I don't know.

It would be a departure for unRAID technically and philosophically. The unRAID array has always been about single disks with independent file systems that function together and have some RAID-like parity protection. Traditional RAID implementations have not been supported in the main array. RAID-Z seems to fall in the traditionally-unsupported category.

The system tries to boot, I just see the bootloader screen, later on it starts to print the usual lines of text that show the boot process. Then nothing happens and the screen it's completely black. I've tried to boot using every other option of the bootloader, but it seems it is not able to boot at all and it's not visible on the network.

I'm very afraid because I have already changed my usb key in November 2022 and I'm not sure if I can get a new one if I have to replace the drive. The drive seems fine, I can access its content from windows. Windows ask me if I want to repair when I plug it in, but i always choose "no" and I can access the drive contents.

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.

Unraid 6.12 definitely seems to be much more picky about VFIO bindings left after hardware has been removed.... for me however, I was able to boot but was greeted with error notifications that were very confusing (not intuitive of how to resolve) because of course the VFIO page didn't show anything checked.

3a8082e126