Unraid OS Version 7.0.0-beta.2 available

Upgraded to beta.2 without issues, hope to have some VM issues resolved with the extensive qemu and libvirt updates in this release. Had major USB problems in beta.1, no matter if using the passed through PCIe USB card or the ports on the mainboard passed through with the USB manager plugin. The USB keyboard and other devices would eventually start to constantly connecting/disconnecting from the Windows 11 VM even tho nothing shows up in the unraid logs or not even in windows logs... super weird and worked "fine" with 6.12.x. (fine as in... there are always some issues with USB soundcards unfortunately)

 

Edit:

Nah, still happening on the passed through PCIe USB card (ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host Controller) even after the updated. *sighs

Attached diagnostics if anyone is bored/want to have a look, I'm about to give up on this and just try to live with it.

tower-diagnostics-20240713-0035.zip

Edited July 12 by MellowB

Getting a: 

after reboot. 

Update: Seems to have cleared itself out after a few minutes. I see lots of errors in syslog though:

Also https doesn't seem to work, I don't use it normally so I don't remember when was the last time it worked if ever.  

 

Jul 12 16:59:13 NAS nginx: 2024/07/12 16:59:13 [error] 23529#23529: *3091 limiting requests, excess: 20.257 by zone "authlimit", client: 192.168.1.191, server: , request: "GET /login HTTP/1.1", host: "192.168.1.1

Jul 12 16:59:15 NAS nginx: 2024/07/12 16:59:15 [error] 23529#23529: *3108 limiting requests, excess: 20.057 by zone "authlimit", client: 192.168.1.191, server: , request: "GET /login HTTP/1.1", host: "192.168.1.1

Jul 12 16:59:19 NAS nginx: 2024/07/12 16:59:19 [error] 23529#23529: *3108 limiting requests, excess: 20.286 by zone "authlimit", client: 192.168.1.191, server: , request: "GET /login HTTP/1.1", host: "192.168.1.1

Jul 12 16:59:21 NAS nginx: 2024/07/12 16:59:21 [error] 23529#23529: *3108 limiting requests, excess: 20.065 by zone "authlimit", client: 192.168.1.191, server: , request: "GET /login HTTP/1.1", host: "192.168.1.1

Edited July 13 by foo_fighter

I am still having the same issue as Beta 1 and cannot boot into Unraid 7. I have now confirmed that a fresh USB drive without any pre-existing configuration will boot fine so I suspect a plugin maybe the issue here.

Note that I have also swapped my main USB to a new one too but this is not the issue.

Previous report from @jcarroll: 

Edited July 13 by ross232
Adding previous report link

1 hour ago, ross232 said:

I have now confirmed that a fresh USB drive without any pre-existing configuration will boot fine so I suspect a plugin maybe the issue her

You can boot in Safe Mode (which stops plugins loading) to see if that works?  That will identify if it is a plugin issue or something else.

Successfully upgraded to 7.0.0-beta.2.

 

I have noticed one issue - when setting "Settings -> Power Mode -> Set to 'Best power efficiency'" - the setting reverts back to 'Best performance' at each reboot.  This issue may have also been present in 7.0.0-beta.1 but I did not check this.

 

Have tested this a few times with multiple reboots and it defaults back to 'Best performance' (note, the option to select 'Balanced operation' is not available within my configuration - intel i3-10100T with ASRock motherboard).

Update works fine. Still have the issue Settings -> VPN Settings does not show data received and data sent correctly. Both stay at 0B.

Just now, itimpi said:

You can boot in Safe Mode (which stops plugins loading) to see if that works?  That will identify if it is a plugin issue or something else.

I'm back with an update. It wasn't the plugins though I really appreciate the help.

After trying unsuccessfully I decided I needed to remove my VFIO bindings as I wanted to be able to better see diagnostic messages. So I temporarily deleted the vfio-pci.cfg file and rebooted. Success!

I then manually re-enabled my VFIO bindings via the UI, rebooted and all was good. I did not set my USB controller to be bound at boot and I wonder if this was the issue - I saw USB errors which is why I left this out.

@jcarroll Can you try this and see if this resolves the problem for you as well?

Edited July 13 by ross232

Beta 1 seemed to go smoothly yesterday when I installed.  Today upgraded to beta 2 and my logs are being filled with line after line of errors with the following (with unique time stamps and share names):

emhttpd: error: get_fs_sizes, 7823: No such file or directory (2): statfs: /mnt/user/

 

Same thing happens once I start the array in safe mode and goes away when I stop it. If it is a recurring issue and I'm too stupid with search to find it then I apologize and a link to it would be much appreciated.

Edited July 13 by txwireless

Hello everyone,

I am currently using UNRAID version 7.0.0 beta 2, and I've noticed that my system log is filling up rapidly. The log entries show constant adding and deleting of the route for 2a03:XXXX:XXXX:402::/64, as seen below:

 

Jul 13 17:44:48 UNRAID dhcpcd[1540]: eth0: deleting route to 2a03:XXXX:XXXX:402::/64 via fe80::1472:1414:e94e:8303
Jul 13 17:44:48 UNRAID dhcpcd[1540]: eth0: adding route to fd2b:82ee:67b6:1::/64 via fe80::5802:d6da:8d:3db4
Jul 13 17:44:50 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:44:51 UNRAID dhcpcd[1540]: eth0: deleting route to fd2b:82ee:67b6:1::/64 via fe80::5802:d6da:8d:3db4
Jul 13 17:44:53 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:45:38 UNRAID dhcpcd[1540]: eth0: adding route to fd2b:82ee:67b6:1::/64 via fe80::5802:d6da:8d:3db4
Jul 13 17:45:40 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:46:34 UNRAID dhcpcd[1540]: eth0: adding route to 2a03:XXXX:XXXX:402::/64 via fe80::1472:1414:e94e:8303
Jul 13 17:46:34 UNRAID dhcpcd[1540]: eth0: deleting route to fd2b:82ee:67b6:1::/64 via fe80::5802:d6da:8d:3db4
Jul 13 17:46:36 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:49:09 UNRAID dhcpcd[1540]: eth0: adding route to fd2b:82ee:67b6:1::/64 via fe80::5802:d6da:8d:3db4
Jul 13 17:49:09 UNRAID dhcpcd[1540]: eth0: deleting route to 2a03:XXXX:XXXX:402::/64 via fe80::1472:1414:e94e:8303
Jul 13 17:49:11 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:49:35 UNRAID dhcpcd[1540]: eth0: adding route to 2a03:XXXX:XXXX:402::/64 via fe80::1472:1414:e94e:8303
Jul 13 17:49:35 UNRAID dhcpcd[1540]: eth0: deleting route to fd2b:82ee:67b6:1::/64 via fe80::5802:d6da:8d:3db4
Jul 13 17:49:37 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:49:50 UNRAID dhcpcd[1540]: eth0: deleting route to 2a03:XXXX:XXXX:402::/64 via fe80::1472:1414:e94e:8303
Jul 13 17:49:53 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:52:36 UNRAID dhcpcd[1540]: eth0: adding route to 2a03:XXXX:XXXX:402::/64 via fe80::1472:1414:e94e:8303
Jul 13 17:52:38 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:53:16 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*
Jul 13 17:56:10 UNRAID dhcpcd[1540]: eth0: deleting route to 2a03:XXXX:XXXX:402::/64 via fe80::1472:1414:e94e:8303
Jul 13 17:56:12 UNRAID ntpd[1708]: 192.168.88.150 on 1 eth0 -> *multiple*

 

I should note that IPv6 is running smoothly in my home network. My ISP has provided me with a prefix /56. I use the subnet 2a03:XXXX:XXXX:400::/64 for my main network (my UNRAID NAS included). This same subnet is also used for Docker macvlan (host access enabled). However, the log shows constant adding and deleting of the route for 2a03:XXXX:XXXX:402::/64. Does anyone know what might be causing this?

 

I also use the following subnets:

2a03:XXXX:XXXX:401::/64 for Wireguard (running on a MikroTik router)

2a03:XXXX:XXXX:405::/64 for the guest network.

 

Any advice on how to resolve or mitigate this issue would be greatly appreciated.

 

Thank you in advance for your help!

Well done. Update smooth. beta 2 run better as beta 1. nothing error in logs (i have some in beta 1) NICE WORK

  

22 hours ago, MellowB said:

still happening on the passed through PCIe USB card

3 hours ago, pkoci said:

Any advice on how to resolve or mitigate this issue would be greatly appreciated.

5 hours ago, txwireless said:

Today upgraded to beta 2 and my logs are being filled with line after line of errors with the following (with unique time stamps and share names):

 

Sorry for the trouble. It is very difficult to do back and forth support in an announce post shared with everyone else, please start a new topic in the Prereleases board. Describe the problem from the beginning as best you can (i.e. don't assume people have read your comment in this thread).  Be sure to include your diagnostics.zip.

5 hours ago, txwireless said:

Beta 1 seemed to go smoothly yesterday when I installed.  Today upgraded to beta 2 and my logs are being filled with line after line of errors with the following (with unique time stamps and share names):

emhttpd: error: get_fs_sizes, 7823: No such file or directory (2): statfs: /mnt/user/

 

Same thing happens once I start the array in safe mode and goes away when I stop it. If it is a recurring issue and I'm too stupid with search to find it then I apologize and a link to it would be much appreciated.

Please disregard.  Unrelated issue where one of the xfs disks in the array wouldn't mount until a repair and zeroing of the log occurred.  It appeared the directories were there and I didn't notice at first that one of the 8 disks in the array wasn't happy.  After the array stop, maintenance mode, repair, end maintenance mode, and restart array and all is good.  Just unfortunate timing as that machine hadn't been rebooted in awhile as it serves as a backup for another unraid box (yes I'm paranoid) and when it came up the disk didn't mount.

 

So far 7.0 is looking nice.  Been running a zfs pool alongside the xfs array but nice that it is now optional for the xfs array.

Please Re/add, the Option to Deactivated the Autostart from Docker Containers after Creation or Recreation after Updated the Template. This was an Option in Unraid Pre 6.10 for example 6.9. In 6.10+ no Option for this and Autostart is the Default.

Saw that it's now possible to empty an array disk with mover in the 7.0 beta-2:

mover start -e diskN |& logger & # where N is [1..28]

However it does'nt seem to work(no files moved from disk1 to my other 2 disks in the same array) when i try to empty disk 1 in my array by running:

mover start -e disk1 |& logger & # where N is [1..28]

 

This is the output in the log after running the above command:

Jul 14 09:30:58 server root: ionice -c 2 -n 0 nice -n 0 /usr/local/sbin/mover.old start

Jul 14 09:30:58 server root: mover: started

Jul 14 09:30:58 server root: mover: finished

 

Anyone got this working or am i doing something wrong?

Edited July 14 by dannen

46 minutes ago, dannen said:

However it does'nt seem to work(no files moved from disk1 to my other 2 disks in the same array) when i try to empty disk 1 in my array by running:

Please create a new report and add the diagnostics.

On 7/13/2024 at 3:39 AM, mnglfr said:

Update works fine. Still have the issue Settings -> VPN Settings does not show data received and data sent correctly. Both stay at 0B.

This has been fixed.  The PR came in after this release.  The fix will be in the next release.

5 hours ago, JorgeB said:

Please create a new report and add the diagnostics.

Report created with diagnostics attached: https://forums.unraid.net/bug-reports/prereleases/version-700-beta2-cant-empty-array-disk-with-mover-r3103/

 

Going from beta1 to beta2, it stuck on copying of syslinux and I'm afriad to reboot. Is there a way to force stop and force start the update again?  Trying to trigger it again it doesn't seem to do anything.

 

Thanks

I have a small comment, not actually a bug but enforcing the removal of some non supported character by open ZFS  in the share name broke my *arr dockers & plex.

As I do not use open ZFS it is annoying.

Quick question. Was it on purpose or accident that the new default ip6tables rule for forwarding is drop?

update completed. I had to reboot twice though.

Is this a Part of the Mover Improvements?

 

I updated from latest 6.12 to Beta 2 and everything seems fine.

But, I was hoping that this would add support for my 'Intel Arc a310' for container video transcoding (official Plex container), It did not.

edit 2: Moved to another thread

Edited July 16 by motionthings
moved to another thread

On 7/13/2024 at 10:58 AM, PPH said:

Successfully upgraded to 7.0.0-beta.2.

 

I have noticed one issue - when setting "Settings -> Power Mode -> Set to 'Best power efficiency'" - the setting reverts back to 'Best performance' at each reboot.  This issue may have also been present in 7.0.0-beta.1 but I did not check this.

I have noticed under the new Power Mode in the Balanced Operations my CPU is pinned at max clocks when using this command

watch -n1 "cat /proc/cpuinfo | grep \"^[c]pu MHz\""

 

I went back to using "Tips & Tweaks" plugin and set my CPU back to Conservative.

The on demand option also keeps my CPU close to base clocks when the system isn't doing much compared to the new Balance Operations Mode.

2 hours ago, motionthings said:

Any tips?

 

From the OP: This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic in the Prereleases board. Be sure to include your diagnostics.zip.

Unfortunately, in this area of the forum I can't move your comment for you. Please go ahead and start a new topic