unRAID OS version 6.4.0-rc7a available


155 posts in this topic Last Reply

Recommended Posts

2 minutes ago, jjslegacy said:

 

Interesting - I am on 6.4.0-rc7a

 

Anything I can do to debug this?  Would a diagnostic file help although I don't see much in the log.

 

Can you open the LOG function in the GUI and perform the assignment again. The earlier mentioned race condtion would throw out a "missing_csrf" key message.

 

Try to do it several times and see if it sticks eventually.

 

Link to post
  • Replies 154
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Upgrading: We have changed the way one checks for new unRAID OS releases.  Please refer to Update OS below.   Bugs: If you want to report an issue, please start a new topic in this board.

The flash drive backup integrated into the OS instead of via a plugin is a good idea.  But I would like one change to take place:   On the backup disk.cfg, can you please set startArray to b

I can confirm there is a bug that makes it impossible to choose cores if you have 8 or less cores when creating a new VM. If there are more than 8 cores available the first 8 are grayed out until

Posted Images

1 minute ago, bonienl said:

 

Can you open the LOG function in the GUI and perform the assignment again. The earlier mentioned race condtion would throw out a "missing_csrf" key message.

 

Try to do it several times and see if it sticks eventually.

Tried a bunch of times -  log only says this line over and over:

 

Aug 11 13:15:18 MJMS emhttpd: req (40): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:19 MJMS emhttpd: req (41): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:21 MJMS emhttpd: req (42): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:22 MJMS emhttpd: req (43): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:24 MJMS emhttpd: req (44): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:25 MJMS emhttpd: req (45): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:26 MJMS emhttpd: req (46): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:27 MJMS emhttpd: req (47): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:29 MJMS emhttpd: req (48): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3

1 minute ago, bonienl said:

 

 

Link to post

Actually tried again and now I see that token error

 

Aug 11 13:15:15 MJMS emhttpd: error: changeDevice: missing csrf_token
Aug 11 13:15:18 MJMS emhttpd: req (40): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:19 MJMS emhttpd: req (41): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:21 MJMS emhttpd: req (42): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:22 MJMS emhttpd: req (43): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:24 MJMS emhttpd: req (44): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:25 MJMS emhttpd: req (45): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:26 MJMS emhttpd: req (46): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:27 MJMS emhttpd: req (47): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:15:29 MJMS emhttpd: req (48): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:17:53 MJMS emhttpd: req (49): changeDevice=Apply&slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP
Aug 11 13:17:53 MJMS emhttpd: error: changeDevice: missing csrf_token
Aug 11 13:17:55 MJMS emhttpd: req (50): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:17:57 MJMS emhttpd: req (51): slotId.9=Hitachi_HUS724030ALE641_P8J77NJP&csrf_token=EDDA1A93016334A3
Aug 11 13:17:58 MJMS emhttpd: req (52): slotId.10=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:17:59 MJMS emhttpd: req (53): slotId.11=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:18:02 MJMS emhttpd: req (54): slotId.13=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:18:04 MJMS emhttpd: req (55): slotId.16=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3
Aug 11 13:18:07 MJMS emhttpd: req (56): slotId.22=Hitachi_HUS724030ALE641_P8J77NJP&csrf_token=EDDA1A93016334A3

Link to post
7 hours ago, jjslegacy said:

Not sure if I am loosing it or haven't had enough caffeine this morning.

 

I added two new disks into my array the other day and have precleared and beat them up for a bit.  This morning I stopped the array to add one of them in.

 

When I pick the disk to add to the slot I want the page just refreshes and keeps the old unassigned status.  I can't seem to get it to stick to any of the choices I pick.

 

I have tried every browser I can find and no difference.

 

Any thoughts?

 

I see this in the syslog when I select the disk:

Aug 11 09:11:32 MJMS emhttpd: req (17): slotId.9=Hitachi_HUS724030ALE641_P8HP8WVP&csrf_token=EDDA1A93016334A3

 

I've had lots of similar issues lately, also on -rc7a.  The only solution I've found is to boot in safe mode.  I think a plugin is somehow breaking this functionality. 

 

I'm currently running in safe mode for this very reason, and a parity rebuild is in progress, so at the moment I can't tell you what plugins I normally run.  I'll check later.

 

 

Link to post
49 minutes ago, Pauven said:

 

I've had lots of similar issues lately, also on -rc7a.  The only solution I've found is to boot in safe mode.  I think a plugin is somehow breaking this functionality. 

 

I'm currently running in safe mode for this very reason, and a parity rebuild is in progress, so at the moment I can't tell you what plugins I normally run.  I'll check later.

 

 

 

Safe mode did indeed let me add the disk - thanks!

 

although now I can't format it.  Will gather some log info

 

Had to reboot into normal mode to get it to format - odd

Edited by jjslegacy
Link to post

Ok, Glad I tried upgrading from RC6 when my family were away...

 

  1. booted fine initially, but my VMs didn't auto-start becuase my nvme didn't auto-mount.  Eventually managed to get NVME to mount and VMs to start
  2. tried rebooting to see if VMs would start 2nd time - no joy and couldn't get VMs to start.  Sometimes when I rebooted the NVME drive would show as mounted after a few mins, but I still couldn't get my VMs to start
  3. then noticed that my webui wasn't working - it would show 'info' but it wasn't updating e.g. CPU usage static, disk writes static etc so I think this is why I couldn't get VMs to start as when I was clicking 'enable' nothing was actually happening behind the scenes

I've now rolled back to 6.3.5 as I can't see how to rollback to RC6 without using the DVB plugin which lists all the previous versions.

highlander-diagnostics-20170812-1442.zip

Link to post

Had the server lockup this morning. I was prepping to move some files onto the cache pool (created folders, noticed it was a bit slower than usual doing that). Went back to working on the files prior to transfer, maybe a minute or two. Tried to open the server folder on movies share and got the Windows error that //tower was unavailable). Tried opening the webgui and that timed out. Decided to do a CLI power down. Watching that screen it indicated that it had to force the shutdown. Fix Common Problems reported unclean shutdown as well as call traces in the log (attached). 

This box has been rock solid for years. Diagnostics attached.

tower-diagnostics-20170812-0848.zip

Link to post
17 minutes ago, wayner said:

I apologize in advance if you are not allowed to ask this sort of question

You can ask all you want, but the only answer you will get is...

 

7 minutes ago, wgstarks said:

Soon™ :D

 

Limetech has been burned in the past by publishing firm dates, then not being able to meet them. So, now, the official answer is always...

 

Soon™

Link to post
Just now, Dark_Gypsy said:

I am having issues with Ryzen and Freezing / intermitent rebooting. I searched around and saw that some fixes for this are in 6.4.0-rc7a.

So that's good news, but... I can't seem to figure out where to download this at... :|

You should be able to update from the GUI. The exact method depends on which version you are currently using. What version?

Link to post

I like the new GUI. Since it has been years I added a share i just saw the new dialog for that today. Great is the possibility to copy the setting from another share. However it would by nice to collapse the info boxes.

Anime.PNG

Edited by shire
Link to post
9 minutes ago, shire said:

it would by nice to collapse the info boxes

By "info boxes" do you mean the Help text? Help is a toggle button in the GUI. If you turn it on it is on for every page, if you turn it off it is off for every page.

Link to post
1 hour ago, trurl said:

By "info boxes" do you mean the Help text? Help is a toggle button in the GUI. If you turn it on it is on for every page, if you turn it off it is off for every page.

@shire is talking about displaying them one at a time by clicking when the pointer turns into a pointer / question mark.  Currently the only way to collapse an individually opened help box AFAIK is to click help twice (to open all boxes and then collapse them all)

Link to post

I am also experiencing the CPU core issue. I assume that editing the XML manually will allow me to enable the other 3 cores that are greyed out to me, but I don't know exactly what that should look like. 

 

I have an i3-6500, so 2 cores, meaning 4 logical cpus. The XML file currently shows:

 

 <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
  </cputune>

 

Would I increment only the vcpu or both?

 

Thanks.

Link to post

I'm experiencing an odd issue. As of recent on rc7a whenever I halt or force stop my windows 10 VM I get this error when I try to start it back up.

 

internal error: qemu unexpectedly closed the monitor: 2017-08-26T14:45:49.801811Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2017-08-26T14:45:49.851579Z qemu-system-x86_64: -device vfio-pci,host=06:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio error: 0000:06:00.0: failed to open /dev/vfio/33: Device or resource busy

 

cold-rewind-diagnostics-20170826-0947.zip

 

 

It also seems odd when I properly tell unraid to reboot and it comes back up (required to fix VM issue) Fix Common Problems plugin claims "unclean shutdown" which I hope isn't true.

Edited by Darksurf
Link to post
I'm experiencing an odd issue. As of recent on rc7a whenever I halt or force stop my windows 10 VM I get this error when I try to start it back up.
 

internal error: qemu unexpectedly closed the monitor: 2017-08-26T14:45:49.801811Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2017-08-26T14:45:49.851579Z qemu-system-x86_64: -device vfio-pci,host=06:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio error: 0000:06:00.0: failed to open /dev/vfio/33: Device or resource busy

 
cold-rewind-diagnostics-20170826-0947.zip
 
 
It also seems odd when I properly tell unraid to reboot and it comes back up (required to fix VM issue) Fix Common Problems plugin claims "unclean shutdown" which I hope isn't true.
I also seem to get an unclean shutdown claim when my server shuts down. Triggered by apcupsd. When my server comes back up it does not do a parity check so i can assume the shutdown was done properly.

Sent from my LG-H870 using Tapatalk

Link to post

I just have one thing to say about 6.4 rc7......Wow my system is running a LOT faster love some of the esthetic changes too. keep up the great work guys....

 

Edited by Can0nfan
removed text
Link to post
1 hour ago, marshy919 said:

Same issue as darksurf. Rebooting while server seemed to eliminate the problem for me though.

Sent from my SM-G935F using Tapatalk
 

 

also same here, some win10 VM shutdowns with Nvidia GPU wont boot anymore until unraid server rebooted here.

Link to post
Guest
This topic is now closed to further replies.