Jump to content
limetech

Unraid OS version 6.8.1 available

145 posts in this topic Last Reply

Recommended Posts

First upgrade failure I think ever... my other server worked.

 

plugin: updating: unRAIDServer.plg
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip ... done
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 ... done

writing flash device - please wait...
Archive: /tmp/unRAIDServer.zip
plugin: run failed: /bin/bash retval: 1
 

Share this post


Link to post

My Dockers are also now down after the failed upgrade:

 

Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43

Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43

 

 

 

And my VM's:
 

Warning: parse_ini_file(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 460

 

 

 

root@nas:/boot# ls -alh
total 8.0K
drwx------ 10 root root 8.0K Jan 12 11:10 ./
drwxr-xr-x 20 root root  440 Jan 11 19:47 ../
 

Edited by RokleM

Share this post


Link to post
9 minutes ago, RokleM said:

My Dockers are also now down after the failed upgrade:

 

Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43

Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43

 

 

 

And my VM's:
 

Warning: parse_ini_file(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 460

 

 

 

root@nas:/boot# ls -alh
total 8.0K
drwx------ 10 root root 8.0K Jan 12 11:10 ./
drwxr-xr-x 20 root root  440 Jan 11 19:47 ../
 

Implies that your USB flash dropped offline.  Ideally, use a USB2.0 port as they are far more reliable than any given USB3 port

Share this post


Link to post
7 minutes ago, Squid said:

Implies that your USB flash dropped offline.  Ideally, use a USB2.0 port as they are far more reliable than any given USB3 port

Literally never had a problem with that disk for 5 years until I started this upgrade.  The sever will no longer see it but it works fine in windows.

 

Jan 12 11:10:40 nas emhttpd: req (8): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=update&arg2=unRAIDServer.plg&csrf_token=****************
Jan 12 11:10:40 nas emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg
Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
Jan 12 11:10:40 nas root: plugin: running: /tmp/unRAIDServer.sh
Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip
Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5
Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
Jan 12 11:10:49 nas root: plugin: running: /tmp/unRAIDServer.sh
Jan 12 11:11:00 nas kernel: usb 5-1: USB disconnect, device number 2

Share this post


Link to post
23 hours ago, Stripe said:

Unfortunately after upgrading from 6.8 my server won't boot. Any clues?

IMG_20200111_184646.jpg

Whoops... this is the message I am getting ! No boot...

 

I rebooted and tried again... Worked without an issue.. So file system corruption does not seem a likely cause ?

Edited by Helmonder

Share this post


Link to post
1 hour ago, RokleM said:

Literally never had a problem with that disk for 5 years until I started this upgrade.  The sever will no longer see it but it works fine in windows.

 

Jan 12 11:10:40 nas emhttpd: req (8): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=update&arg2=unRAIDServer.plg&csrf_token=****************
Jan 12 11:10:40 nas emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg
Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
Jan 12 11:10:40 nas root: plugin: running: /tmp/unRAIDServer.sh
Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip
Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5
Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
Jan 12 11:10:49 nas root: plugin: running: /tmp/unRAIDServer.sh
Jan 12 11:11:00 nas kernel: usb 5-1: USB disconnect, device number 2

Took a risk and rebooted and it's working... something in the upgrade process made the disk not accessible but somehow is restored during reboot.  Very odd.

Share this post


Link to post

Just upgraded to the latest...when it rebooted it hung after password, so I rebooted. So far it is good. I am testing to see if it solves my problem with pausing during movies.

Sent from my SM-T830 using Tapatalk

Share this post


Link to post
On 1/12/2020 at 2:14 AM, tjb_altf4 said:

Upgraded last night, smooth sailing so far.

 

I did noticed one issue, exiting from the web terminal session kicks you straight into a fresh terminal session.

Not great, not terrible 😛

 

+1 like some relases ago ... same behavior again

 

also exiting from docker terminal sessions is not properly closing anymore

Share this post


Link to post

After I upgraded from 6.8.0 to 6.8.1 through the update plugin, my server hung while booting. I was unable to access the webgui and couldn't connect via telnet. I had to hard power down the server. I then pulled the USB stick and reverted to 6.8.0 by copying the previous folder into the main. I don't have an easy way to connect to a monitor so I'm unsure what was going on. Seems like others are having similar issues though?

Share this post


Link to post
After I upgraded from 6.8.0 to 6.8.1 through the update plugin, my server hung while booting. I was unable to access the webgui and couldn't connect via telnet. I had to hard power down the server. I then pulled the USB stick and reverted to 6.8.0 by copying the previous folder into the main. I don't have an easy way to connect to a monitor so I'm unsure what was going on. Seems like others are having similar issues though?
I just did a control alt delete, and when it rebooted it worked fine...no need to revert to an older version on mine.

Sent from my SM-T830 using Tapatalk

Share this post


Link to post

I have some suspicions that from a while back something changed with the flash drive that makes it corrupt more often, I never used to have issues upgrading and last releases it happens some times (with multiple servers) that after an upgrade (either using the GUI or by manually copying the files) I need to run chkdsk, or it will panic on boot, other times get a lot of corrupted line scrolling on the server, but like mentioned it's only a suspicion.

Share this post


Link to post
3 minutes ago, johnnie.black said:

I have some suspicions that from a while back something changed with the flash drive that makes it corrupt more often, I never used to have issues upgrading and last releases it happens some times (with multiple servers) that after an upgrade (either using the GUI or by manually copying the files) I need to run chkdsk, or it will panic on boot, other times get a lot of corrupted line scrolling on the server, but like mentioned it's only a suspicion.

So if this is what is occurring here for me, what would the suggested fix be? I see some have had luck simply rebooting the server again which I actually didn't try (only because I had to physically hard power it down). For reference, this actually happened twice. I upgraded from 6.8 to 6.8.1, rebooted, it hung and was inaccessible. Then I reverted to 6.8. I then attempted this process again with the same result and had to pull the USB and revert a second time.

Share this post


Link to post
1 minute ago, highgear said:

So if this is what is occurring here for me, what would the suggested fix be?

I just run chkdsk on my desktop and it's fixed

 

Forgot to mention, now when doing an upgrade I look a the syslog, if I see lines similar to:

xz decompression failed, data probably corrupt

If this happens I know it won't reboot properly and chkdsk is needed.

Share this post


Link to post
6 minutes ago, johnnie.black said:

I have some suspicions that from a while back something changed with the flash drive that makes it corrupt more often, I never used to have issues upgrading and last releases it happens some times (with multiple servers) that after an upgrade (either using the GUI or by manually copying the files) I need to run chkdsk, or it will panic on boot, other times get a lot of corrupted line scrolling on the server, but like mentioned it's only a suspicion.

Starting with 6.8 writing the flash device changed in 2 ways:

 

First, via /etc/fstab the flash device is mounted with the 'flush' mount option.  The man page for that option says:

    "If set, the filesystem will try to flush to disk more early than normal.  Not set by default."

This was done to ensure data completely is written to the flash device sooner than normal Linux cache flush.

 

Second, after a release zip file has been downloaded, instead of unpacking to RAM and then copying files to the usb flash device, it extracts from the zip file directly to the usb flash device.  This was done to ensure those with low memory servers could still upgrade.

 

FWIW - we routinely update several servers several times almost daily with various models of usb flash and honestly in all the years I think I've seen one legit flash failure.

Share this post


Link to post
2 minutes ago, limetech said:

FWIW - we routinely update several servers several times almost daily with various models of usb flash and honestly in all the years I think I've seen one legit flash failure.

Most of my updates also result fine, but I do see some go wrong, I would guess 1 in 10 or less, but still more than I used to see, and don't remember seeing those "xz decompression failed, data probably corrupt" errors on the syslog before, but might have missed them.

 

 

 

 

Share this post


Link to post
33 minutes ago, johnnie.black said:

I just run chkdsk on my desktop and it's fixed

 

Forgot to mention, now when doing an upgrade I look a the syslog, if I see lines similar to:


xz decompression failed, data probably corrupt

If this happens I know it won't reboot properly and chkdsk is needed.

Ok thanks for the info. I may just wait until the next update to try upgrading again.

Share this post


Link to post
On 1/12/2020 at 11:28 AM, Helmonder said:

Whoops... this is the message I am getting ! No boot...

 

I rebooted and tried again... Worked without an issue.. So file system corruption does not seem a likely cause ?

I'm getting this same error and unable to boot after upgrading. I went from 6.8.0 to 6.8.1. I've tried both the normal boot and safe mode. 

 

 

error1.jpg

Share this post


Link to post

Just upgraded from 6.7.2 to 6.8.1:

 

All seems to work fine for now. Docker and VM's up and running.

 

I had to recreate two Windows VM's (using form view to create a new XML and point to existing .qcow2 and .img vdisk) because both of them didn't boot: Blackscreen with error: no bootable device.

These two Windows VM's boot off of an Unassignd SSD, i had to update the plugin (Unassignd Devices) before upgrade. So either this plugin update or the Unraid upgrade itself messed something up.

 

Passthrough of Intel IGD (4th Gen) still working 👍

Share this post


Link to post
2 hours ago, fatalfurry said:

I'm getting this same error and unable to boot after upgrading. I went from 6.8.0 to 6.8.1. I've tried both the normal boot and safe mode. 

 

 

error1.jpg

I was able to boot after going into my bios and disabling C-States. I've been stable for almost a year with C-States set to Auto and I don't  understand how these items could be related. 

Edited by fatalfurry

Share this post


Link to post
On 1/11/2020 at 12:54 PM, bonienl said:

Check and fix your USB stick for file system corruptions

How does one do this ?

Share this post


Link to post
4 minutes ago, Ginfrecss said:

How does one do this ?

Put it in a Windows machine and let it run chkdsk on it.  You can also run this manually, but, Windows usually does it automatically if it detects even the slightest anomaly.

Share this post


Link to post
14 minutes ago, Hoopster said:

Put it in a Windows machine and let it run chkdsk on it.  You can also run this manually, but, Windows usually does it automatically if it detects even the slightest anomaly.

Ok thx !

Share this post


Link to post

Would anyone know why I get the following errors during boot: 

 

error: failed to connect to the hypervisor

error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

 

IMG_0236.thumb.png.png.9e1a21c607a1d9f352804dc3be339f31.png

Share this post


Link to post
14 minutes ago, Ginfrecss said:

Would anyone know why I get the following errors during boot: 

 

error: failed to connect to the hypervisor

error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

Post diagnostics

Share this post


Link to post

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.