unRAID OS version 6.5.0 Stable Release Available


Recommended Posts

6 minutes ago, doppelt said:

But why to boot the other PC with the drive ?

 

To verify that there is nothing wrong with the flash drive.

 

6 minutes ago, doppelt said:

There can nothing happen ? I´ll do it better in a laptop.

 

 

That is correct.  Use any recent PC  (Laptop or Desktop).  It does not make any difference.  

 

8 minutes ago, doppelt said:

I´ll let you know what chkdsk found. ...without any options yes ?

 

It doesn't make any difference.  I have never heard of ChkDsk  'fixing'  an unRAID boot disk.  However, it has  found a lot of them that have errors on them.  

Link to comment

Just updated to 6.5.0 from 6.4.1 and my dockers appeared to be hosed. :(

Kept getting "No such container" errors.

As a test I uninstalled Netdata and Plex and then reinstalled using CA and I still got an execution error when trying to start the dockers.

No such container.

 

Then I noticed that the Dashboard said my Plex and Crashplan Pro were running.

At this point I was a bit confused.

Docker tab says they are stopped and I can't start them but Dashboard says they are running.

WTH...

 

So I went in and looked at the settings on my Plex docker and noticed the network had been set to "none".

Put Plex back to br0 and set the IP back to what it should be and now that's working.

Crashplan Pro was already set correctly and it is working as well.
 

What's really weird is I can start and stop dockers from the dashboard but the docker tab of the GUI is hosed.

All dockers show as stopped on that page and I keep getting that no such container error.

What's up with that?

Should I just blow away my docker.img file and let it build a new one?

Diags attached in case anyone wants a peek at 'em.

unraid-diagnostics-20180404-1821.zip

Link to comment
9 hours ago, Matt_G said:

Should I just blow away my docker.img file and let it build a new one?

 

I had similar when I first upgraded, and now I occasionally get my dockers disappear completely.  Restarting the dockers system by going to settings/docker, selecting "no" and saving, then changing it back to "yes" brings things back.  Might be worth a try until somebody with proper knowledge drops by - from what I can make out the docker version in this release seems a bit flaky.

Link to comment
18 hours ago, Matt_G said:

Just updated to 6.5.0 from 6.4.1 and my dockers appeared to be hosed. :(

Kept getting "No such container" errors.

As a test I uninstalled Netdata and Plex and then reinstalled using CA and I still got an execution error when trying to start the dockers.

No such container.

 

Then I noticed that the Dashboard said my Plex and Crashplan Pro were running.

At this point I was a bit confused.

Docker tab says they are stopped and I can't start them but Dashboard says they are running.

WTH...

 

So I went in and looked at the settings on my Plex docker and noticed the network had been set to "none".

Put Plex back to br0 and set the IP back to what it should be and now that's working.

Crashplan Pro was already set correctly and it is working as well.
 

What's really weird is I can start and stop dockers from the dashboard but the docker tab of the GUI is hosed.

All dockers show as stopped on that page and I keep getting that no such container error.

What's up with that?

Should I just blow away my docker.img file and let it build a new one?

Diags attached in case anyone wants a peek at 'em.

unraid-diagnostics-20180404-1821.zip

 

Does this sounds like your issue?:

 

Link to comment
On 4/5/2018 at 12:36 PM, bobbintb said:

 

Does this sounds like your issue?:

 

Yes, is sure does.

I noticed bonienl suggested going to 6.5.1-rc3.

I'll wait for it to go stable. :)

Like I said, everything appears to be working.

I just can't trust what the GUI says on the Docker tab...

Edited by Matt_G
Link to comment
On 3/15/2018 at 10:51 AM, Hoopster said:

There is a discussion about this now in the General Support forum.  There are several of us with the issue and the only solution is to boot the GUI, otherwise, the server will not start.  Neither "normal" mode nor safe mode will boot.

 

 

 

Thanks for the head up. I'll give it a try on my system to see if it fixes the issue.

Link to comment
1 minute ago, Hanzo404 said:

 

Thanks for the head up. I'll give it a try on my system to see if it fixes the issue.

If you happen to have an ASRock C236 WSI board, setting boot priority #1 to UEFI: (flash drive), eliminating all other boot priority options and renaming the EFI- folder on the flash drive to EFI has resolved the issue for all of us with this board.

Link to comment
5 minutes ago, Hoopster said:

If you happen to have an ASRock C236 WSI board, setting boot priority #1 to UEFI: (flash drive), eliminating all other boot priority options and renaming the EFI- folder on the flash drive to EFI has resolved the issue for all of us with this board.

I've got an ASRock - H170M-ITX/DL, but I'll try this first anyway. I wonder if its an ASRock BIOS issue? I first noticed the problem when I applied the patch to fix the Intel Management Engine vulnerability.

Link to comment
33 minutes ago, bombz said:

what is the safest method to get up to the latest version?

BEFORE you update,

 

Install Fix Common Problems (or make sure that it's up to date)

 

Go to Tools, Update Assistant, run the tests against either Stable or Next and do whatever it says

 

Then,

 

Download the zip file from limetech's website

Extract all of the bz* files in the zip onto the flash drive (but make a backup of the files on the flash first)

Reboot

  • Upvote 1
Link to comment
On 4/14/2018 at 6:06 PM, Squid said:

BEFORE you update,

 

Install Fix Common Problems (or make sure that it's up to date)

 

Go to Tools, Update Assistant, run the tests against either Stable or Next and do whatever it says

 

Then,

 

Download the zip file from limetech's website

Extract all of the bz* files in the zip onto the flash drive (but make a backup of the files on the flash first)

Reboot

Alrighty 

I didn't know that step one (common problems) I am glad I reached out!
So it is just the few root files I need to be concerned about? I will keep reading.
And yes I have a full flash image backed up, zipped and uploaded to the cloud, many copies :-) 
Let's see what I can make of this, I will report back most likely 

Thanks !

EDIT:

Thanks, that script is awesome! I have 1 fault

1 fault = 

Checking for extra parameters on emhttp

Issue Found: emhttp command in /boot/config/go has extra parameters passed to it. Currently emhttp does not accept any extra paramters. These should be removed

 

^^ I don't know how to go about adjusting this ^^

I have attached the full log.
 

 

 

UNRAID-upgrade-log3.docx

UNRAID-upgrade-log4.txt

Edited by bombz
new content
Link to comment
22 minutes ago, bombz said:

Issue Found: emhttp command in /boot/config/go has extra parameters passed to it. Currently emhttp does not accept any extra paramters. These should be removed

 

^^ I don't know how to go about adjusting this ^^

Just replace the config/go file on your flash with the config/go file from the download.

Link to comment
16 minutes ago, trurl said:

Just replace the config/go file on your flash with the config/go file from the download.

OK, makes sense
noob question confirmed :-) 

Appreciate the help.

I am going to do this OS upgrade tomorrow. Anything else I should be concerned about with the major upgrade (kernel SSL etc.) Any issues connecting to the GUI / Plex / Dockers?

To clarify
Replacing:

 

bzfirmware
bzimage
bzmodules
bzroot
bzroot-gui

memtest (cause why not)

 

What about this new EFI Folder I see? I haven't seen that before. Does that relate to the new UEFI features? 


I don't need to be concerned about the 'syslinux' folder?


Thanks,

Edited by bombz
content
Link to comment

s3 sleep seems to no longer work for me, just comes right back out of sleep:

 

Apr 14 19:46:45 Tower s3_sleep: Enter sleep mode
Apr 14 19:46:45 Tower s3_sleep: Execute custom commands before sleep
Apr 14 19:46:45 Tower s3_sleep: Enter sleep state now
Apr 14 19:46:45 Tower kernel: PM: suspend entry (deep)
Apr 14 19:46:46 Tower kernel: PM: Syncing filesystems ... done.
Apr 14 19:47:06 Tower kernel: Freezing user space processes ... 
Apr 14 19:47:06 Tower kernel: Freezing of tasks failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 14 19:47:06 Tower kernel: find D 0 29092 29091 0x00000004
Apr 14 19:47:06 Tower kernel: Call Trace:
Apr 14 19:47:06 Tower kernel: ? __schedule+0x4c6/0x503
Apr 14 19:47:06 Tower kernel: schedule+0x76/0x8e
Apr 14 19:47:06 Tower kernel: request_wait_answer+0xd2/0x19c
Apr 14 19:47:06 Tower kernel: ? wait_woken+0x68/0x68
Apr 14 19:47:06 Tower kernel: __fuse_request_send+0x70/0x75
Apr 14 19:47:06 Tower kernel: fuse_simple_request+0xfc/0x132
Apr 14 19:47:06 Tower kernel: fuse_send_open.isra.1+0x7f/0x84
Apr 14 19:47:06 Tower kernel: fuse_do_open+0x72/0xd0
Apr 14 19:47:06 Tower kernel: ? __schedule+0x4ce/0x503
Apr 14 19:47:06 Tower kernel: fuse_open_common+0x6f/0xa9
Apr 14 19:47:06 Tower kernel: ? fuse_dir_release+0x10/0x10
Apr 14 19:47:06 Tower kernel: do_dentry_open.isra.1+0x18e/0x27d
Apr 14 19:47:06 Tower kernel: path_openat+0xa64/0xbec
Apr 14 19:47:06 Tower kernel: do_filp_open+0x48/0x9e
Apr 14 19:47:06 Tower kernel: ? do_sys_open+0x129/0x1b0
Apr 14 19:47:06 Tower kernel: do_sys_open+0x129/0x1b0
Apr 14 19:47:06 Tower kernel: do_syscall_64+0xfe/0x107
Apr 14 19:47:06 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Apr 14 19:47:06 Tower kernel: RIP: 0033:0x14d4a14bfff0
Apr 14 19:47:06 Tower kernel: RSP: 002b:00007fff7f167190 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Apr 14 19:47:06 Tower kernel: RAX: ffffffffffffffda RBX: 00007fff7f1673b0 RCX: 000014d4a14bfff0
Apr 14 19:47:06 Tower kernel: RDX: 0000000000020000 RSI: 000000000042ae05 RDI: 00000000ffffff9c
Apr 14 19:47:06 Tower kernel: RBP: 0000000000020000 R08: 00007fff7f1674df R09: 0000000000000000
Apr 14 19:47:06 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
Apr 14 19:47:06 Tower kernel: R13: 000000000042ae05 R14: 000014d4a1f56b00 R15: 00000000006422c0
Apr 14 19:47:06 Tower kernel: OOM killer enabled.
Apr 14 19:47:06 Tower kernel: Restarting tasks ... done.
Apr 14 19:47:06 Tower kernel: PM: suspend exit
Apr 14 19:47:06 Tower s3_sleep: Wake-up now
Apr 14 19:47:06 Tower s3_sleep: Execute custom commands after wake-up
Apr 14 19:47:06 Tower s3_sleep: Wake-up from sleep mode
Apr 14 19:47:32 Tower s3_sleep: Disk activity on going: sdb
Apr 14 19:47:32 Tower s3_sleep: Disk activity detected. Reset timers.

Link to comment
11 hours ago, foo_fighter said:

s3 sleep seems to no longer work for me, just comes right back out of sleep:

 

Apr 14 19:46:45 Tower s3_sleep: Enter sleep mode
Apr 14 19:46:45 Tower s3_sleep: Execute custom commands before sleep
Apr 14 19:46:45 Tower s3_sleep: Enter sleep state now
Apr 14 19:46:45 Tower kernel: PM: suspend entry (deep)
Apr 14 19:46:46 Tower kernel: PM: Syncing filesystems ... done.
Apr 14 19:47:06 Tower kernel: Freezing user space processes ... 
Apr 14 19:47:06 Tower kernel: Freezing of tasks failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 14 19:47:06 Tower kernel: find D 0 29092 29091 0x00000004
Apr 14 19:47:06 Tower kernel: Call Trace:
Apr 14 19:47:06 Tower kernel: ? __schedule+0x4c6/0x503
Apr 14 19:47:06 Tower kernel: schedule+0x76/0x8e
Apr 14 19:47:06 Tower kernel: request_wait_answer+0xd2/0x19c
Apr 14 19:47:06 Tower kernel: ? wait_woken+0x68/0x68
Apr 14 19:47:06 Tower kernel: __fuse_request_send+0x70/0x75
Apr 14 19:47:06 Tower kernel: fuse_simple_request+0xfc/0x132
Apr 14 19:47:06 Tower kernel: fuse_send_open.isra.1+0x7f/0x84
Apr 14 19:47:06 Tower kernel: fuse_do_open+0x72/0xd0
Apr 14 19:47:06 Tower kernel: ? __schedule+0x4ce/0x503
Apr 14 19:47:06 Tower kernel: fuse_open_common+0x6f/0xa9
Apr 14 19:47:06 Tower kernel: ? fuse_dir_release+0x10/0x10
Apr 14 19:47:06 Tower kernel: do_dentry_open.isra.1+0x18e/0x27d
Apr 14 19:47:06 Tower kernel: path_openat+0xa64/0xbec
Apr 14 19:47:06 Tower kernel: do_filp_open+0x48/0x9e
Apr 14 19:47:06 Tower kernel: ? do_sys_open+0x129/0x1b0
Apr 14 19:47:06 Tower kernel: do_sys_open+0x129/0x1b0
Apr 14 19:47:06 Tower kernel: do_syscall_64+0xfe/0x107
Apr 14 19:47:06 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Apr 14 19:47:06 Tower kernel: RIP: 0033:0x14d4a14bfff0
Apr 14 19:47:06 Tower kernel: RSP: 002b:00007fff7f167190 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Apr 14 19:47:06 Tower kernel: RAX: ffffffffffffffda RBX: 00007fff7f1673b0 RCX: 000014d4a14bfff0
Apr 14 19:47:06 Tower kernel: RDX: 0000000000020000 RSI: 000000000042ae05 RDI: 00000000ffffff9c
Apr 14 19:47:06 Tower kernel: RBP: 0000000000020000 R08: 00007fff7f1674df R09: 0000000000000000
Apr 14 19:47:06 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
Apr 14 19:47:06 Tower kernel: R13: 000000000042ae05 R14: 000014d4a1f56b00 R15: 00000000006422c0
Apr 14 19:47:06 Tower kernel: OOM killer enabled.
Apr 14 19:47:06 Tower kernel: Restarting tasks ... done.
Apr 14 19:47:06 Tower kernel: PM: suspend exit
Apr 14 19:47:06 Tower s3_sleep: Wake-up now
Apr 14 19:47:06 Tower s3_sleep: Execute custom commands after wake-up
Apr 14 19:47:06 Tower s3_sleep: Wake-up from sleep mode
Apr 14 19:47:32 Tower s3_sleep: Disk activity on going: sdb
Apr 14 19:47:32 Tower s3_sleep: Disk activity detected. Reset timers.

Does that have to do with C-States (CPU BIOS Settings) 
I personally disable C-States. It's just a thought, maybe it's related
 

Link to comment
2 hours ago, bombz said:

Does that have to do with C-States (CPU BIOS Settings) 
I personally disable C-States. It's just a thought, maybe it's related
 

 

I haven't changed any BIOS settings...turns out if I wait long enough it eventually does go to sleep....Must be something preventing sleep that eventually finishes up.

Link to comment

Upgrading to 6.5.0 seems to have made my UNRAID server quite unstable. Call traces, missing apps, docker page hanging.

 

perhaps a downgrade is needed?

 

Errors in the logs:

Apr 16 23:17:59 FoxServer nginx: 2018/04/16 23:17:59 [error] 10515#10515: *390911 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.107, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.20", referrer: "http://192.168.1.20/Docker"

 

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.