unRAID Server Release 6.2.0-beta19 Available

[archedraft]

 

I get this all the time in my VMs, i thought it was normal?

 

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

 

Same here.

It has happened with with all 6.1 and 6.2 versions I have used

 

All my VMs say the same thing in 6.1, my understanding is that it is because the VMs have root privileges . The interwebs left me believing that this message wasn't a big deal.

[sparklyballs]

 

I get this all the time in my VMs, i thought it was normal?

 

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

 

Same here.

It has happened with with all 6.1 and 6.2 versions I have used

 

All my VMs say the same thing in 6.1, my understanding is that it is because the VMs have root privileges . The interwebs left me believing that this message wasn't a big deal.

 

what isn't normal though is my VM totally freezing, that just happens to be the last entry in the log.

[archedraft]

 

 

I get this all the time in my VMs, i thought it was normal?

 

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

 

Same here.

It has happened with with all 6.1 and 6.2 versions I have used

 

All my VMs say the same thing in 6.1, my understanding is that it is because the VMs have root privileges . The interwebs left me believing that this message wasn't a big deal.

 

what isn't normal though is my VM totally freezing, that just happens to be the last entry in the log.

 

Agreed, freezing VMs is a pretty big deal.

[rix]

Hey, ssh is still not working for me. Telnet is available. Wasn't until the update till the connection issues started.

The connection is not coming through, so I have not found something useful in the logs.

 

Does this have anything to do with me default-booting into gui mode?

 

I am not using the custom media driver builds (which were working in 6.1.x) for now, and the only plugin I may deem responsible for these issues is openvpn server. That plugin is working for others, however...

 

Any idea why SSH is not (running) on my Server?

 

PS: I have also tried the ssh options plugin, which is unable to start the ssh service itself.

 

Thanks for your help

 

___

 

Unrelated: The gui defaults into the Key/registration tab and my array (only 1x parity) is still not auto-starting, as seen with others.

 

EDiT: Redacted sensible Mover log

syslog.txt

[trurl]

Hey, ssh is still not working for me. Telnet is available. Wasn't until the update till the connection issues started.

The connection is not coming through, so I have not found something useful in the logs.

 

Does this have anything to do with me default-booting into gui mode?

 

I am not using the custom media driver builds (which were working in 6.1.x) for now, and the only plugin I may deem responsible for these issues is openvpn server. That plugin is working for others, however...

 

Any idea why SSH is not (running) on my Server?

 

PS: I have also tried the ssh options plugin, which is unable to start the ssh service itself.

 

Thanks for your help

 

___

 

Unrelated: The gui defaults into the Key/registration tab and my array (only 1x parity) is still not auto-starting, as seen with others.

 

EDiT: Redacted sensible Mover log

Boot in SAFE mode. If the problem still happens in SAFE mode then post your diagnostics, not your syslog.

[mikeyosm]

Did the vfio fix as described here https://lime-technology.com/forum/index.php?topic=44010.0 make it in to the beta release?

I am having the same issue still but want to be sure the fix won't break anything else in the beta.

[dAigo]

NVMe support seems solid, temps are showing, but no SMART info.

 

It seems, that smartmontools added some form of NVMe support yesterday.

Any chance to add that while we are still in beta?

 

https://www.smartmontools.org/

2016-03-20: We added basic support for NVMe devices to smartctl on Linux. See ticket #657 for further info. Source tarball and binaries are available at builds.smartmontools.org. Please report any issues here in trac or on the smartmontools support mailinglist.

[jonp]

NVMe support seems solid, temps are showing, but no SMART info.

 

It seems, that smartmontools added some form of NVMe support yesterday.

Any chance to add that while we are still in beta?

 

https://www.smartmontools.org/

2016-03-20: We added basic support for NVMe devices to smartctl on Linux. See ticket #657 for further info. Source tarball and binaries are available at builds.smartmontools.org. Please report any issues here in trac or on the smartmontools support mailinglist.

 

That's actually what we've been waiting for those guys to do for us to get SMART data properly reported for NVMe devices.  Probably not going to happen for beta20, but thanks for reporting that to us!

[mikeyosm]

Upgraded to b19 and noticed the following in logs.... Is there anything there I should be concerned about? Since the upgrade my SSD which has the shares, docker img etc mysteriously disappears from UNRAID and I have to power cycle the computer to get it re-recognised in the BIOS again. It was not doing this in in 6.1.9.

 

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:19 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 22:48:21 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:48:21 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:48:22 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:48:22 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:49:16 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:49:16 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:49:17 MOUNRAID01 kernel: usb 3-7: device descriptor read/8, error -71

Mar 21 22:49:17 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:49:18 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 22:51:53 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 22:51:53 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

[interwebtech]

NVMe support seems solid, temps are showing, but no SMART info.

 

It seems, that smartmontools added some form of NVMe support yesterday.

Any chance to add that while we are still in beta?

 

https://www.smartmontools.org/

2016-03-20: We added basic support for NVMe devices to smartctl on Linux. See ticket #657 for further info. Source tarball and binaries are available at builds.smartmontools.org. Please report any issues here in trac or on the smartmontools support mailinglist.

 

That's actually what we've been waiting for those guys to do for us to get SMART data properly reported for NVMe devices.  Probably not going to happen for beta20, but thanks for reporting that to us!

 

Would adding their tools give me temps on JBOD hanging off my Areca ARC-1231ML? I wouldn't expect it for RAID volumes but perhaps the single disks?

[SuperW2]

I'm not sure exactly where to place this or if it's Beta related or not (only noticed with 6.2.0B18 and now 19)

 

I have User Shares ("TV" in this case) with Several "Included" Disks (and "None" in Excluded)... When I browse the user Share on Windows 10, not all of the files on all of the Disk shares appear... in fact nothing after Jan 15, 2016.  But if I browse the Disk Share directly ("\\Media\Disk15" for example) I see all of the files and folders that I expect to see in the User Share under a "TV" folder off the root of that disk share.  I don't use the Cache drive on my user shares, and have both SMB/NFS Export to Yes/Public.

 

I can browse to one of the "included" disk shares manually in Windows Explorer and I see all of the recent files/folders that don't appear in the User Share.  If I browse via the UnRaid console using the "view" explorer looking icon from the Share Tab the files are also not

 

I originally had "All" disks included and excluded just those not associated with that specific user share and saw the same issue.

 

No idea where to even start... this affect anything connecting to that user share (specifically Plex).  I've not made any changes to any of my user share settings since installing 6.2B18/19.

 

I rebooted (after running NFS repair and the log file seems small now, and attached

 

Here is the original....

https://www.dropbox.com/s/dl7qm547hqimb5j/media-diagnostics-20160321-1848.zip?dl=0

 

-SW2

media-diagnostics-20160321-1912.zip

[trurl]

...I have my Diag. zip file that I can attached but wasn't sure if that would be helpful or not.

See here

[RobJ]

Hi

After login over FTP im always getting

[  369.831674] vsftpd[18787]: segfault at 0 ip 00002aeeb9980e2a sp 00007ffd221ff098 error 4 in libc-2.23.so[2aeeb98e2000+1c0000]

[  374.350005] vsftpd[18833]: segfault at 0 ip 00002ad7ea42ee2a sp 00007ffeafd81418 error 4 in libc-2.23.so[2ad7ea390000+1c0000]

[  380.910259] vsftpd[18904]: segfault at 0 ip 00002b7b6d8eee2a sp 00007ffd4bdaaa98 error 4 in libc-2.23.so[2b7b6d850000+1c0000]

[  396.746897] vsftpd[19151]: segfault at 0 ip 00002b7e89b2ee2a sp 00007fffb6490ca8 error 4 in libc-2.23.so[2b7e89a90000+1c0000]

[  399.897735] vsftpd[19181]: segfault at 0 ip 00002b58c40e4e2a sp 00007ffe83003b78 error 4 in libc-2.23.so[2b58c4046000+1c0000]

 

This same was in b18 @limetech @jnop please try yourself connect and download/upload some bigger file. (thx)

The 2 reasons that I have seen most likely to cause segfaults are bad RAM or dependency version conflicts.  There might be other reasons, I haven't seen them.  You can try a Memtest (multiple passes) to eliminate RAM issues.  Then as he said, check for older plugins and their dependencies.

[piotrasd]

i have ECC ram for sure is OK

[RobJ]

NVMe support seems solid, temps are showing, but no SMART info.

 

It seems, that smartmontools added some form of NVMe support yesterday.

Any chance to add that while we are still in beta?

 

https://www.smartmontools.org/

2016-03-20: We added basic support for NVMe devices to smartctl on Linux. See ticket #657 for further info. Source tarball and binaries are available at builds.smartmontools.org. Please report any issues here in trac or on the smartmontools support mailinglist.

 

That's actually what we've been waiting for those guys to do for us to get SMART data properly reported for NVMe devices.  Probably not going to happen for beta20, but thanks for reporting that to us!

I don't think it's quite ready, at least I don't *think* I saw any NVME drives in the latest drivedb.  It's updated often, so dAigo, why not monitor it and let us know when your drives are entered there.  (Access it from the SmartMonTools page.)

[RobJ]

Upgraded to b19 and noticed the following in logs.... Is there anything there I should be concerned about? Since the upgrade my SSD which has the shares, docker img etc mysteriously disappears from UNRAID and I have to power cycle the computer to get it re-recognised in the BIOS again. It was not doing this in in 6.1.9.

 

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:19 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 22:48:21 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Please add your diagnostics zip, and if possible a recent diagnostics zip from v6.1.9 for comparison.

[RobJ]

Would adding their tools give me temps on JBOD hanging off my Areca ARC-1231ML? I wouldn't expect it for RAID volumes but perhaps the single disks?

There's already some support for Areca connected drives, takes some special handling and parameters.  Search for Areca.  I don't recall if it's complete though.

[RobJ]

...I have my Diag. zip file that I can attached but wasn't sure if that would be helpful or not.

See here

 

OK, I tried, but it's almost 10X bigger than the maximum attachment size the forum allows me to post... (almost 1.8MB)

Other options are put it on a download site like pastebin, mediafire, etc; or your own ftp site; or a 'cloud' site like your own dropbox; and provide us an accessible URL.

 

Or you can examine it for the one file that's blowing it up, and remove that, and post the rest.  Tell us what you had to remove, and we can examine the rest and determine how badly we need what's removed.

[SuperW2]

...I have my Diag. zip file that I can attached but wasn't sure if that would be helpful or not.

See here

 

OK, I tried, but it's almost 10X bigger than the maximum attachment size the forum allows me to post... (almost 1.8MB)

Other options are put it on a download site like pastebin, mediafire, etc; or your own ftp site; or a 'cloud' site like your own dropbox; and provide us an accessible URL.

 

Or you can examine it for the one file that's blowing it up, and remove that, and post the rest.  Tell us what you had to remove, and we can examine the rest and determine how badly we need what's removed.

 

I rebooted (after running NFS repair) and the log file seems small now, and attached to my Original Post #110... I also left the Dropbox link to the "before".

 

Interestingly enough after rebooting my user / disk share issue reported seem to at least for now to have gone away....Will continue to monitor

 

-Sw2

[luca]

With the new beta, I have one Win7 vm that keeps crashing consistently 15-20 minutes after booting.  Out of memory issue?  Server has 16GB, and I have only 1 vm running.  Also installed the plex plugin at the same time, so that may have caused (or exacerbated) the memory issue.

 

Mar 21 07:41:45 FS1 kernel: qemu-system-x86 invoked oom-killer: gfp_mask=0x26000c0, order=0, oom_score_adj=0

[...]

Mar 21 07:41:45 FS1 kernel: Out of memory: Kill process 28797 (qemu-system-x86) score 493 or sacrifice child

Mar 21 07:41:45 FS1 kernel: Killed process 28797 (qemu-system-x86) total-vm:9281680kB, anon-rss:8340604kB, file-rss:15060kB

fs1-syslog-20160321-2126.zip

[tr0910]

Would adding their tools give me temps on JBOD hanging off my Areca ARC-1231ML? I wouldn't expect it for RAID volumes but perhaps the single disks?

There's already some support for Areca connected drives, takes some special handling and parameters.  Search for Areca.  I don't recall if it's complete though.

Complete except for smart monitoring, and drive temps on the main screen.

 

Makes it difficult to pre clear on areca.  For that reason I keep a motherboard sata port free.

[bigjme]

So i just suffered my first major system lockup with this version. Yet again it seems to be the same as before where a vm shuts down.

 

Luckily i had the unraid gui with the log open and managed to capture the following:

 

So weirdly i have nothing added to the log in 2 days after that last load of errors it shows so i can not see why it locked up. Any ideas?

 

Regards,

Jamie

archangel-diagnostics-20160322-0829.zip

[mikeyosm]

Upgraded to b19 and noticed the following in logs.... Is there anything there I should be concerned about? Since the upgrade my SSD which has the shares, docker img etc mysteriously disappears from UNRAID and I have to power cycle the computer to get it re-recognised in the BIOS again. It was not doing this in in 6.1.9.

 

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:19 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 22:48:21 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Please add your diagnostics zip, and if possible a recent diagnostics zip from v6.1.9 for comparison.

 

Please see attached. I noticed some more sata related errors this morning.

 

thank you.

mounraid01-syslog-20160322-0934.zip

mounraid01-diagnostics-20160322-0941.zip

[mikeyosm]

Upgraded to b19 and noticed the following in logs.... Is there anything there I should be concerned about? Since the upgrade my SSD which has the shares, docker img etc mysteriously disappears from UNRAID and I have to power cycle the computer to get it re-recognised in the BIOS again. It was not doing this in in 6.1.9.

 

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:36:19 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen

Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Mar 21 22:48:21 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71

Please add your diagnostics zip, and if possible a recent diagnostics zip from v6.1.9 for comparison.

 

Please see attached. I noticed some more sata related errors this morning.

 

thank you.

 

I replaced my SATA cables and the SATA errors seems to have gone (for now). Still getting the  kernel: usb 3-7: device descriptor read/all, error -71 error though.

[snazz]

Wasn't called out as a fix or improvement in beta 19, but UnRaid still hangs on boot on one of my systems unless VT-d is explicitly disabled in bios as was my experience with beta 18.  It wasn't an issue on the affected hardware platform with 6.1.9. 

 

Try updating the BIOS in the machine.  VT-d works fine on the three systems I've tried b18 on.

 

That or try setting iommu=nopt in your syslinux.cfg file.

Thanks for the suggestions.  BIOS is already at the latest revision, and iommu=nopt didn't make a difference.

 

I'm still trying to track down what is causing this issue as 6.2 won't even boot on my older system (Intel DX58SO with i7 980x) with VT-d enabled.  As I noted I found a workaround, but it comes at a price...not being able to pass through hardware to a VM.  6.1.9 boots fine on the system in question and allows the GPU to be passed through.  I realize there were a lot of changes in 6.2 especially with regard to virtualization, so figuring out what change specifically caused this likely isn't simple.  I'm willing to test just about any idea...hopefully it will result in finding a solution before others who have yet to experience this are affected.

 

I've attached diagnostics from booting a fresh 6.1.9 install.  VT-d was enabled in the bios and IOMMU shows "enabled" in the web gui.

With the same bios configuration, 6.2 beta19 (or 18) boots this far and gets stuck: 

 

I've tried appending each (one line at a time) of the following to syslinux.cfg / pressing tab at the boot menu and manually adding the following, but all yield the same behavior as in the screenshot:

 

intel_iommu=pt

iommu=on

iommu=on intel_iommu=on

iommu=nopt

iommu=nopt intel_iommu=nopt

 

Any ideas?

 

Update:  I managed to get it to boot with VT-d enabled.  I had to disable the onboard sound in the bios.  Sorta strange, but getting closer to a fully working system on 6.2 and a 6-year old motherboard. 

 

 

 

tower-diagnostics-20160322-0428.zip