Unraid OS version 6.10.0 available


Recommended Posts

36 minutes ago, Lelo said:

Is there somewhere a changelog from RC8 to final release?

 

Everything seems to work fine!

I have not seen one that explicitly gives any changes since rc8

 

You could possibly compare the rc8 log to the latest stable one to look for changes.

Link to comment

Just updated to 6.10 stable and I have multiple docker containers that will no longer start.

Anyone else had an issue with containers not starting?

 

Anecdotally, appears to be related to any container that has the docker socket specified i.e. "/var/run/docker.sock"

Link to comment

Crap.....

plugin: updating: unRAIDServer.plg
plugin: downloading: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.10.0-x86_64.zip ... done
plugin: downloading: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.10.0-x86_64.md5 ... done
boot device shows 224825344 free but upgrade needs 309918020
plugin: run failed: /bin/bash retval: 1

 

I guess my 1G flash need replacing....

Link to comment

I updated from 6.9.2, got this message when starting the array: "Your flash drive is corrupted or offline. Post your diagnostics in the forum for help. See also here". Everything seems to be working normal.

 

Edit: Plex (official docker container) is not working after the update.

Container log is showing this every few seconds:

Error: Unable to set up server: sqlite3_statement_backend::loadOne: attempt to write a readonly database (N4soci10soci_errorE)
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

 

Edit 2: scrutiny container is also having issues (not working at all, I won't post logs in this thread).

Edited by Ademar
Link to comment
12 minutes ago, JorgeB said:

 

Follow here for possible solutions or fix:

 

 

 

I have already reviewed that and I see nothing in there that offers any sort of clear things to try. The only thing I was able to glean from that is some people aid to try to SSH to the server and edit a file but did not explain exactly how to do that.

Edited by BrandonV
Link to comment
8 minutes ago, BrandonV said:

I have already reviewed that and I see nothing in there that offers any sort of clear things to try.

Yes, but when there's one it should be posted there, and I'm going to re-open the report since it's not really solved.

 

 

Link to comment
35 minutes ago, BrandonV said:

You would think that after ALL the RC versions they released, they would have the bugs worked out of this but I guess not.

 

Ha, as a software dev I can say with certainty that is not how it works.  QA (Quality Assurance) and UA (User Acceptance) Testing tend to happen with a very small subset of the actual people that will end up using the product/service.  You will almost ALWAYS find bugs once "stable" is released to the masses.

Link to comment
31 minutes ago, JorgeB said:

Only what's reported can be fixed, once a release goes stable it starts being used by many more users, so a few new issues are expected/inevitable.

I get that however total loss of access to the unRAID GUI is not a minor problem. So hopefully there is a fix soon but if people can not get to their servers then it is going to be very challenging to resolve.  

 

Link to comment
59 minutes ago, BrandonV said:

I have already reviewed that and I see nothing in there that offers any sort of clear things to try. The only thing I was able to glean from that is some people aid to try to SSH to the server and edit a file but did not explain exactly how to do that.

 

Open the file /boot/config/ident.cfg with command

nano /boot/config/ident.cfg

and change:

USE_SSL=“no”

Save with ctrl-X and answer Y.

 

Reload nginx with command:

/etc/rc.d/rc.nginx reload

 

then try to login to the Gui using http://tower (your server name)

Link to comment

Unfortunately, my server also stopped working since the upgrade.

 

It upgraded well. I then restarted it. I can no longer access the GUI. In fact, the server no longer register in the network (i.e., I cannot see the server IP in my router).

 

Unfortunately, I am running headless, so cannot see the error message.

 

Any idea how to troubleshoot?

Link to comment

Upgraded the main server from 6.9.2 without issues.  OPNsense VM and Win10 VM started fine as well as all my dockers.

 

Time to install Win11 VM :)

 

One note, I had SSL disabled before the upgrade.

 

Thanks guys!

craigr

Edited by craigr
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.