I just updated to version 7, now my server does not boot. It just sits at a black screen doing nothing. Anybody have any suggestions on what I can try?

5 minutes ago, hitch said:

I just updated to version 7, now my server does not boot. It just sits at a black screen doing nothing. Anybody have any suggestions on what I can try?

Ok so turning the power on the PSU on and off appears to have worked... Strange though

11 hours ago, SimonF said:

Is logging enabled in the mover schedule.

Yes it is. With OS 7 the log only shows the file name after it has been moved. Previously, the log showed the file name when the file moving began. I don't see any option to change this behavior.

 

Ideally, I would like to know when the file begins moving. And also when it is finished. But, right now, I need to check the directory of the disk that is showing write activity. To see the name of the file being moved from the cache drive. Since the log doesn't show that info anymore.

1 minute ago, aaronwt said:

Yes it is. With OS 7 the log only shows the file name after it has been moved. Previously, the log showed the file name when the file moving began. I don't see any option to change this behavior.

 

Ideally, I would like to know when the file begins moving. And also when it is finished. But, right now, I need to check the directory of the disk that is showing write activity. To see the name of the file being moved from the cache drive. Since the log doesn't show that info anymore.

Are you just using native mover or mover tuner plugin?

Just now, SimonF said:

Are you just using native mover or mover tuner plugin?

I've always used the native unRAID mover.

9 minutes ago, aaronwt said:

I've always used the native unRAID mover.

Works ok form me. Create a separate post with diagnostics 

 

Jan 11 19:51:58 computenode emhttpd: shcmd (47074): /usr/local/sbin/mover start |& logger -t move &
Jan 11 19:51:58 computenode move: mover: started
Jan 11 19:55:26 computenode move: move: /mnt/disk1/isos/ubuntu-24.10-desktop-amd64.iso Success
Jan 11 19:55:48 computenode move: move: /mnt/disk1/isos/gparted-live-1.6.0-10-amd64.iso Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/virtio-win-0.1.266-1.iso Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/glmark2/Ubuntu Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/glmark2/UbuntuAMDVirgl Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/glmark2/UbuntuAMDPassThru Success
Jan 11 19:57:31 computenode move: move: /mnt/disk1/isos/ubuntu-24.10-live-server-amd64.iso Success
Jan 11 19:57:32 computenode move: mover: finished

10 minutes ago, SimonF said:

Works ok form me. Create a separate post with diagnostics 

 

Jan 11 19:51:58 computenode emhttpd: shcmd (47074): /usr/local/sbin/mover start |& logger -t move &
Jan 11 19:51:58 computenode move: mover: started
Jan 11 19:55:26 computenode move: move: /mnt/disk1/isos/ubuntu-24.10-desktop-amd64.iso Success
Jan 11 19:55:48 computenode move: move: /mnt/disk1/isos/gparted-live-1.6.0-10-amd64.iso Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/virtio-win-0.1.266-1.iso Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/glmark2/Ubuntu Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/glmark2/UbuntuAMDVirgl Success
Jan 11 19:56:15 computenode move: move: /mnt/disk1/isos/glmark2/UbuntuAMDPassThru Success
Jan 11 19:57:31 computenode move: move: /mnt/disk1/isos/ubuntu-24.10-live-server-amd64.iso Success
Jan 11 19:57:32 computenode move: mover: finished

This is what it looks like on mine. But, OS7 only shows the file name in the log AFTER the file is transferred. Previously, before unRAID Version 7.0.0, it showed the name of the file when the transfer started. Which, for me, was more helpful.

 

Since most of the files I use in my nine unRAIDs are 50GB to 100GB in size. So the files take ten to twenty minutes to transfer. They are not small files that basically transfer instantly.

Edited January 11, 20251 yr by aaronwt

Hi,

Thank you for the update. I worked like a charm for me (from 6.2.14).

Got "Stale file handle" samba error mounting private share from ubuntu linux after upgrade to 7.0.0

Fixed by adding noserverino parameter to /etc/fstab or in mount command in linux client

Edited January 11, 20251 yr by sharicov

Updated right now with no issues so far - thanks for this nice release 👍

updated all systems to stable release ov v7. no isseus with update. some minor previous rc2 bugs posted...

glad to see this finaly hit full release.

I updated my backup server to Unraid version 7 last night and its running stable. 

 

All docker containers where updated and the array stopped prior to upgrade. 

 

There is on thing that has not worked. The GPU nvidia drivers are not loading. 

 

Nvidia Info:

Nvidia Driver Version: 565.77

Open Source Kernel Module: No

Installed GPU(s):
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

 

Is there any trick to get the nvidia drivers to load in Unraid version 7? Hopefully it's just a user error on my en that can be easily fixed. 

 

I'll have to sort this out befour I can upgrade my main server. 

 

Any tips?

23 hours ago, JorgeB said:

There are two different errors mentioned in that post, you are likely seeing the second one, if yes, read the last line, I've edited the post to hopefully make it more clear.

 

 

Thanks JorgeB for your help. Your edited post helped.

I changed the pool slot value to 0 and everything is working well.

My feature request made it into release! Thank you!

 

You can now create VMs and remove GPUs after install to not expose VNC.
"nogpu option"

Edited January 12, 20251 yr by ezhik

Wow, that was uneventful.  Upgraded from 6.12.14 -> 7.0. Took longer to read the forum for issues than to upgrade.  I have a basic system but no issues yet.

 

Good job guys!

 

For those worried about the 2GB flash drive issue, I use a 2GB flash drive and 7.0 seems to use ~200MB more than 6.12.14, but I still have ~600MB free on mine.

This is not Part of the Release:

Maybe the next Update?

https://github.com/unraid/webgui/pull/1042

Edited January 12, 20251 yr by Revan335

Many Thanks for hard working to all!🥳

 

I tried the Upgrade soon.

10 hours ago, mikeofoslo said:

There is on thing that has not worked. The GPU nvidia drivers are not loading. 

Please create a post including your Diagnostics in the support thread form the plugin:

 

"bzfirmware checksum error -press Enter key to reboot..."

I get this error every reboot I make after updating to v7

 

11 minutes ago, Vitek said:

"bzfirmware checksum error -press Enter key to reboot..."

I get this error every reboot I make after updating to v7

 

I would suggest you download the zip file version of the release and extract all the bz* type files overwriting the versions on the flash drive.

Any chance of adding Screen?

9 minutes ago, gshlomi said:

Any chance of adding Screen?

Probably not since there's now a plugin for tmux that has visual management of sessions. 

Unraid upgrade from 6.12.14 to 7.0.0 seemed to be flawless in the first moment.

 

B U T  !

 

After 7.0.0 was installed, I wanted to make a new backup of the important parts of the server to my external USB 8TB backup HDD (rather new Seagate Exos type) as usual... (using famous rsync script of @mgutt)

 

However with the new system it doesn't work any more or is so slow, that the  it is useless...

 

Here is a typical message of syslog... it goes like this over thousands of lines in the syslog:

 

I have read in the release notes of Unraid 7.0.0, that there is a change with Linux Kernel about external Usb storage devices (like my external USB HDD is):

"...Other changes: ...

Linux kernel: force all buggy Seagate external USB enclosures to bind to usb-storage instead of UAS driver ..."

 

Question:

Could the fault with my external USB drive have to do with some Linux Kernel change causing incompatibilty problem between my USB hardware and new Linux Kernel ??

 

What should I do, in order to be able to take back-ups to that USB drive as with 6.12.14, which never had that problem ?

Perhaps there is some settings problem or anything else, I can do

 

Many thanks for support and greetings

 

 

 

10 minutes ago, ullibelgie said:

After 7.0.0 was installed, I wanted to make a new backup of the important parts of the server to my external USB 8TB backup HDD (rather new Seagate Exos type) as usual...

Please start a new thread in the general support forum and add the diagnostics.

from 6.12.13 to 7 stable. seems to have gone just fine  Thanks