[[6.12.10] - Unraid Crashing After Update]

Do you have macvlan enabled for docker networking?   If so you need to make sure bridging is disabled on eth0 to avoid potential system instability.

[Windows 10 VM crashes server]

There is a good chance that the reason for the crash is the hardware ID of passed through hardware has changed so you are now passing through something critical to Unraid functioning.   Hardware IDs changing is not at all unusual when upgrading particularly if there is a significant upgrade to the underlying Linux kernel in the new release.

 

Have you tried removing any hardware current passthroughs and redoing them after the 6.12.10 upgrade, rebooting Unraid to make them take effect, and then seeing if the VM will start?

[Starting a drive preclear during a format function will pause the format]

I expect that is inherent in the fact that Unraid is based on Linux and the pre-clear stops a system ‘sync’ call from completing.

[server unresponsive]

looks like your server might be using macvlan networking?   If so to avoid stability problems you need to either switch to using ipvlan docker networking or disable bridging on eth0 

[[6.12.9] Disks missing after upgrading to 6.12.9]

1 hour ago, Haeldar said:

Is it best to rollback to 6.12.8 or will there be a hotfix for 6.12.9?

For the time being you need to revert.   Any ‘hot fix’ would get a higher patch number (e.g. 6.12.10).

[[6.12.8] Help text needs clarification]

It should be 'pool' rather than mentioning 'cache' as that is just a pool of that name.

[6.12.8 Unstable on Intel E5 V4 Intel platforms]

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.

[[6.12.8] Parity drive won't start, no error]

Once you get the red ‘x’ which means a write to it failed for some reason and the data disks and parity are no longer in sync then Unraid stops using the drive until the status is cleared by a rebuild as documented here in the online documentation.

 

could not spot any issues in the SMART report in the logs but you could run an extended SMART test if you want to be sure.  By far the commonest cause of this type of issue is the cabling (either power or sata) not being perfectly seated so you might want to check that out.

[[6.12.8] Docker Container won't create when emty hostpath is in template]

Just found you can get a similar error if the host path is set but there is nothing in the server path field.

[Strange docker (tab) behaviour on 6.12.7-rc2]

4 minutes ago, JorgeB said:

 

Feb 14 09:11:41 DJW-UNRAID emhttpd: shcmd (733): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20
Feb 14 09:11:41 DJW-UNRAID root: Specified filename /mnt//system/docker/docker.img does not exist.

 

I've seen this before but don't now where this /mnt// comes from, docker still started though.

Strange as obviously the docker.img file DOES exist (i.e. it is not a new one) as otherwise the containers would have needed their binaries reloading before they could be run.

[Strange docker (tab) behaviour on 6.12.7-rc2]

11 minutes ago, JorgeB said:

You mean the docker service was initially disabled right?

 

Feb 14 08:50:27 DJW-UNRAID emhttpd: unclean shutdown detected

IIRC this can make docker settings go back to defaults, including disabling the service

 

Fair enough.   However I have had plenty of Unclean shutdowns on 6.12.6 which did not change the Docker service status from enabled to disabled.   I will do some testing in my test environment to see if I can reproduce this happening as it looks like new (albeit probably a good idea) behaviour to me.

 

However that does not explain the fact that after enabling the docker service I got the warning banner being displayed at the top of the Docker tab despite the fact that at that point the array is started and all docker containers appear to be working as normal.

 

I am going to try to do some more structured testing on this but thought I should get a report in in case others also experience it so we can see a pattern.

[BTRFS error]

12 hours ago, henrik38 said:

Accessing the cache pool as a disk share eliminated 95% of the "corrupted" files

BTW:  With the Unraid 6.12.x releases you can achieve the same results on a User Share as using a disk share if the share in question is all on one device/pool and you have enabled the Exclusive share option under Settings->Global Share settings.

[6.12.6 potential file deletion bug by mover]

@denishay This is the first time I have heard of this behaviour so it is probably going to need more information to sort out why it is happening to you .

[[6.12.6] Parity Check (tuning) schedule won't do correction]

3 hours ago, sonic6 said:

Any news on this? Problem is still present.

I assume that we will need to wait for a new Unraid release before this problem can be fixed.   I have seen suggestions that 6.12.7 might be imminent.

 

14 minutes ago, sonic6 said:

okay, there any files:

root@Unraid-1:~# ls -la /boot/config/plugins/parity.check.tuning/
/bin/ls: cannot access '/boot/config/plugins/parity.check.tuning/': No such file or directory

That would be expected if you have uninstalled the plugin as you mentioned earlier?   That folder should always be there if the plugin is installed.

[[6.12.6] Parity Check (tuning) schedule won't do correction]

On 1/3/2024 at 9:36 AM, sonic6 said:

what is the recommendes way to do this?

If you have the Dynamix File Manager plugin installed then you can navigate to the plugins folder on the flash drive  /boot/config/plugins/parity.check.tuning/ to get a file listing.

[Upgrade to 6.12.x causes instability]

There appear to be macvlan related crashes.    As mentioned in the releases notes if you want to continue using macvlan for docker networking then you should disable bridging on eth0.    The alternative is to switch docker to using ipvlan networking instead.

[[6.12.6] User Shares suddenly gone]

31 minutes ago, Videodr0me said:

Reboot restored functionality. Still this is a very annoying bug.

I am sure that if only a way could be found that reliably reproduces it then it would quickly be fixed.

[6.12.6 (and probably .5 as well) break VM with PCI passthrough]

Did you check that the hardware ID's for the passed through hardware did not change after the upgrade and thus the pass throughs need re-doing?   This is not uncommon after and upgrade.

[System instability when using Active/Backup link bonding on 6.12.6]

1 hour ago, Kaldek said:

Yeah I did plan on that but given the fact that I wasn't even getting Kernel Panic messages on the console, and the fact that it's core network driver related, the chances of that syslog message even getting out were...low.

If you use the “Mirror to Flash” option then there is no direct dependency on the network working so more chance of catching something.

[[6.12.6] Parity Check (tuning) schedule won't do correction]

While I think of it we normally recommended that scheduled parity checks are set to be non-correcting.   The rationale being that if you have a drive playing up you do not want to run a correcting check that might corrupt parity and reduce the chances of a clean data recovery.

[[6.12.6] Parity Check (tuning) schedule won't do correction]

The Parity Check Tuning plugin would not have initiated the check.

 

The only reason I can think of for it trying to resume is that there was some unexpected state information found in the plugins folder on the flash drive.   It might be useful if a listing of the files that are there could be given as that could provide a clue as to what that might be.   In addition the contents of any "progress" type files that are there.

[server freezes 6.12.6]

10 hours ago, TRusselo said:

ok here. have fun!

syslogs.zip

The syslog-previous file shows Macvlan related crashes so it is possible that is actually the cause of your problems?    You should either switch docker to using ipvlan networking, or alternatively make sure bridging is disabled on eth0.

[[6.8.3] shfs error results in lost /mnt/user]

1 hour ago, jackjack said:

Array says cant mount it needs to be formatted, so do so, disk unformattable, unmount, format, mount, make a folder and all working fine, do a pre-clear on the disk and start again.

That is not the process you should follow according to the online documentation.

[After upgrade 6.12.6 from 6.11.5 some VM tab elements are not working; primary GPU passthrough not working anymore]

2 hours ago, BasWeg said:

And its working. 🤷‍♂️
The old VM with the same config is not.

All I can suggest is compare the xml for the old and new VMs to see what is different.

[After upgrade 6.12.6 from 6.11.5 some VM tab elements are not working; primary GPU passthrough not working anymore]

Have you tried removing the docker folder plugin that is not compatible with this release of Unraid?