Anyone having issues with drives not showing up on this release?

 

Here's the log: https://pastebin.com/J4TNx6UN

 

EDIT:

I wish I had a better resolution than this.  I tried everything under the sun.  Even downgraded my M1015 SAS Card firmware, nothing worked.  Safe mode, nothing.  I ended up flashing back to stable, and everything came up right away.  Out of kicks, I flashed the beta back and rebooted.  Everything was working as intended then as well.  I will see if I see this issue in the future.  Not really sure what was going on to be honest.

Edited December 21, 20178 yr by dsmitty166

My steamcache container on it's own IP was also not launching with the "No such container" error. There is definitely a bug here..

3 minutes ago, rix said:

My steamcache container on it's own IP was also not launching with the "No such container" error. There is definitely a bug here..

Rebooting does not change this. The latest built killed my vlans.

38 minutes ago, rix said:

My steamcache container on it's own IP was also not launching with the "No such container" error. There is definitely a bug here..

 

Please post your diagnostics

Yeah, there is a regession bug. Corrected. Thanks

Edited December 21, 20178 yr by bonienl

anyone else finding the log tab sometimes work and sometimes lag? the system log under tools is working fine but the log tab keep loading and sometimes will load fast and sometimes hang.

I have not had any VM issues on rc16, or rc17 like I saw on rc15.

1 hour ago, dlandon said:

I have not had any VM issues on rc16, or rc17 like I saw on rc15.

Thanks - I'm going to upgrade my rc14 then to rc17

1 hour ago, PSYCHOPATHiO said:

anyone else finding the log tab sometimes work and sometimes lag? the system log under tools is working fine but the log tab keep loading and sometimes will load fast and sometimes hang.

 

Check how full your log is on the Dashboard's system status table. After a couple days of running rc16 I noticed that my system log popup window would remain blank when I opened it. Turned out that my syslog had filled to 100% with kernel panics and stack traces which I believe were caused by that experimental kernel patch included in rc16 since it specifically mentioned something along the lines of "bad udp_fragmentation_offload". I upgraded to rc17 and deleted /var/log/syslog* and everything seems back to normal.

So far so good after 24 hours VMs are still running well.

2 hours ago, Ambrotos said:

deleted /var/log/syslog* 

Thanks for the tip, I deleted the syslog and that simply just fixed it.

but I'm still having issues when I set a docker to a br0 they disappear and I see this 

 

I reinstalled the two dockers, removed them manually then reinstalled them on br0 subnet, it worked. so both of my issues are solved.

 will do a quick reboot and check again to see if br0 is still available.

 

EDIT: Rebooted & all dockers are up but the log is back to hanging.

Edited December 21, 20178 yr by PSYCHOPATHiO

After upgrading i keep getting the following errors in the log

 

Dec 21 15:03:04 Servername nginx: 2017/12/21 15:03:04 [error] 13716#13716: *30711 limiting requests, excess: 5.666 by zone "authlimit", client: 10.165.1.5, server: , request: "GET /sub/var HTTP/1.1", host: "removed.unraid.net"

 

Edited December 21, 20178 yr by mxmod

Still the same trouble, Ubuntu VM runs fine for hours and shuts down normally. But libvirtd never cleans it out, and it is not possible to start a new instance, only Unraid reboot works.

 I was updating the drivers on a Gaming VM I use for Nvidia GameStream and the VM locked up on me.

7 of its 8 threads are showing maxed out, have to reboot to get it to come back.

While typing this the threads went to their idle percentages but when I go to the VM tab it wont show my VMs only like the first one in the alphabetical list.

 

Here are two diagnostics, one before rebooting and another after.

server-diagnostics-20171221-1338.zip

server-diagnostics-20171221-1326.zip

Yeah, just had it happen again, Is there anywhere I can download RC14?

Here is the Libvirt Logs as of right now.

2017-12-21 18:38:24.402+0000: 22193: info : libvirt version: 3.8.0
2017-12-21 18:38:24.402+0000: 22193: info : hostname: Server
2017-12-21 18:38:24.402+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=1 name='Windows 10 Test VM' uuid=3b0e8e8c-0a1d-882d-dfa6-983bb288c07d is tainted: high-privileges
2017-12-21 18:38:24.403+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=1 name='Windows 10 Test VM' uuid=3b0e8e8c-0a1d-882d-dfa6-983bb288c07d is tainted: host-cpu
2017-12-21 18:38:27.713+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=2 name='Windows 10 Nvidia Gaming VM' uuid=10d6836f-792f-cbea-c446-7c5006378601 is tainted: high-privileges
2017-12-21 18:38:27.713+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=2 name='Windows 10 Nvidia Gaming VM' uuid=10d6836f-792f-cbea-c446-7c5006378601 is tainted: host-cpu
2017-12-21 18:38:31.309+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=3 name='pfSense' uuid=a88a096d-20e4-2cc4-0d4d-48787381d881 is tainted: high-privileges
2017-12-21 18:38:31.309+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=3 name='pfSense' uuid=a88a096d-20e4-2cc4-0d4d-48787381d881 is tainted: host-cpu
2017-12-21 18:38:34.541+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=4 name='Ubuntu Server' uuid=37d13441-f940-0f78-bf97-6f9a8e092716 is tainted: high-privileges
2017-12-21 18:38:34.541+0000: 22193: warning : qemuDomainObjTaint:4855 : Domain id=4 name='Ubuntu Server' uuid=37d13441-f940-0f78-bf97-6f9a8e092716 is tainted: host-cpu

 

ip address on the rc17b keeps changing to 169.254.149.48, the ip address starts at 192.168.0.144

37 minutes ago, ren88 said:

ip address on the rc17b keeps changing to 169.254.149.48, the ip address starts at 192.168.0.144

That looks like a vlan address from a switch.  Power cycle your switch and see if it clears up.

Not sure what has happened to my nextcloud docker since upgrading to rc17. All of a sudden nextcloud cannot reach out to the internet and my port forward to 443 from outside my network does not work.

2 hours ago, mikeyosm said:

Not sure what has happened to my nextcloud docker since upgrading to rc17. All of a sudden nextcloud cannot reach out to the internet and my port forward to 443 from outside my network does not work.

 

What was your Network Type set to for the nextcloud docker?  Is a VLAN involved?

4 hours ago, ren88 said:

ip address on the rc17b keeps changing to 169.254.149.48, the ip address starts at 192.168.0.144

 

169.254.X.X is an APIPA address. Thats really odd..Can you check to see if you static'd the IP on the server or if that static setting is sticking?

https://www.pcmag.com/encyclopedia/term/37858/apipa

 

never mind i got it fix, all i needed to do was reboot the server 

i have a 64gb usb, but it gives me a error = unable to write to the last block of the device wen formatting it, can i use it as a cache drive wit out parity in unraid 

7 hours ago, eschultz said:

 

What was your Network Type set to for the nextcloud docker?  Is a VLAN involved?

br0 and the docker has is running on its own IP 192.168.1.91 - UNRAID is on 192.168.1.90.

No VLAN involved. I also have a plex docker that shares the UNRAID IP and this works OK.

 

For information, I also posted the issue here...

 

 

Edited December 22, 20178 yr by mikeyosm

3 hours ago, mikeyosm said:

br0 and the docker has is running on its own IP 192.168.1.91 - UNRAID is on 192.168.1.90.

No VLAN involved. I also have a plex docker that shares the UNRAID IP and this works OK.

I had the same issue when I upgraded to RC17b, This is how I fixed it

I removed the app & cleaned the folder with "Clean Appdata" then rebooted, I installed the app fresh on br0  and everything worked fine since

 

On 2017-12-19 at 10:44 AM, limetech said:

ethtool -k eth0

So I get a lot of info back with this command including the following:

 

--> udp-fragmentation-offload: off

 

I upgraded to 6.4.0_rc17b.  So far no problems as far as I can tell.  I have no experienced Windows 10 VM hanging when shutting down before or after this upgrade.