I have confirmed my two parity disks and one of my other disks will not spin down unless done manually.  It says it does it from the log but the disks are always spinning which won't let the machine shutoff during the schedule.

 

I just see this over and over

May 2 17:31:59 MJMS kernel: mdcmd (61): spindown 0
May 2 17:32:00 MJMS kernel: mdcmd (62): spindown 8
May 2 17:32:00 MJMS kernel: mdcmd (63): spindown 29

 

This was working fine on all versions before 6.5.1

mjms-diagnostics-20180502-1733.zip

 

I saw these errors in my log today, which I have never seen before.  Since upgrading to 6.5.1, these are the only errors so far.

 

Anything to worry about?  

 

May 2 05:28:30 Tower nginx: 2018/05/02 05:28:30 [error] 10265#10265: *761604 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost", referrer: "http://localhost/Main"
May 2 05:28:30 Tower php-fpm[10239]: [WARNING] [pool www] child 1600 exited on signal 7 (SIGBUS) after 328.611253 seconds from start

Edited May 2, 20188 yr by Switchblade

After updating to 6.5.1 from 6.5.0 all of my VM's started to experience stuttering and freezing especially under high load such as gaming. Rolled back to 6.5.0 and everything is fine again.

Today I have more errors.  Perhaps something to do with the sata drivers or some other change in 6.5.1.  I did not have any of these errors prior and I have not touched anything else.

 

May 3 06:13:32 Tower kernel: ata8.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen
May 3 06:13:32 Tower kernel: ata8.00: irq_stat 0x0c400040, interface fatal error, connection status changed
May 3 06:13:32 Tower kernel: ata8: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
May 3 06:13:32 Tower kernel: ata8.00: failed command: READ DMA EXT
May 3 06:13:32 Tower kernel: ata8.00: cmd 25/00:40:88:2e:73/00:05:a6:00:00/e0 tag 25 dma 688128 in
May 3 06:13:32 Tower kernel: res 50/00:00:87:2e:73/00:00:a6:00:00/e0 Emask 0x50 (ATA bus error)
May 3 06:13:32 Tower kernel: ata8.00: status: { DRDY }
May 3 06:13:32 Tower kernel: ata8: hard resetting link
May 3 06:13:38 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
May 3 06:13:42 Tower kernel: ata8: COMRESET failed (errno=-16)
May 3 06:13:42 Tower kernel: ata8: hard resetting link
May 3 06:13:48 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
May 3 06:13:49 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 3 06:13:49 Tower kernel: ata8.00: configured for UDMA/33
May 3 06:13:49 Tower kernel: ata8: EH complete
May 3 06:13:56 Tower kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen
May 3 06:13:56 Tower kernel: ata8.00: irq_stat 0x0c400040, interface fatal error, connection status changed
May 3 06:13:56 Tower kernel: ata8: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
May 3 06:13:56 Tower kernel: ata8.00: failed command: READ DMA EXT
May 3 06:13:56 Tower kernel: ata8.00: cmd 25/00:40:88:ce:94/00:05:a6:00:00/e0 tag 18 dma 688128 in
May 3 06:13:56 Tower kernel: res 50/00:00:87:ce:94/00:00:a6:00:00/e0 Emask 0x10 (ATA bus error)
May 3 06:13:56 Tower kernel: ata8.00: status: { DRDY }
May 3 06:13:56 Tower kernel: ata8: hard resetting link
May 3 06:14:02 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
May 3 06:14:06 Tower kernel: ata8: COMRESET failed (errno=-16)
May 3 06:14:06 Tower kernel: ata8: hard resetting link
May 3 06:14:12 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
May 3 06:14:13 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 3 06:14:13 Tower kernel: ata8.00: configured for UDMA/33
May 3 06:14:13 Tower kernel: ata8: EH complete

 

Any ideas?

11 minutes ago, Switchblade said:

Perhaps something to do with the sata drivers or some other change in 6.5.1.

Very unlikely, please post your diagnostics, might shed some light.

On 4/23/2018 at 7:54 PM, Dhovin said:

Updated from 6.5, getting error on Docker page but everything seems to be working.

 

Fixed in 6.5.2-rc1+

38 minutes ago, Squid said:

Fixed in 6.5.2-rc1+

Thanks. If you don't need me to test, i'll wait for official release.

8 hours ago, Switchblade said:

May 3 06:13:32 Tower kernel: ata8: hard resetting link

 

Looks like a bad cable to me. At least, that would be the first thing I'd replace to troubleshoot.

9 hours ago, johnnie.black said:

Very unlikely, please post your diagnostics, might shed some light.

 

Diag attached.  The Main screen shows no errors with the drives, so that is good.

 

Thanks!

tower-diagnostics-20180503-1614.zip

7 hours ago, Switchblade said:

 

Diag attached.  The Main screen shows no errors with the drives, so that is good.

 

Thanks!

tower-diagnostics-20180503-1614.zip

Looks like a connection problem check/replace cables.

hum..ok will do.  Weird how I can all the sudden have a cable issue, as I have not touched the cables in months.

 

Thanks much for your help!

 

On 5/3/2018 at 11:23 AM, PROJECTBLUE said:

After updating to 6.5.1 from 6.5.0 all of my VM's started to experience stuttering and freezing especially under high load such as gaming. Rolled back to 6.5.0 and everything is fine again.

 

facing a similar issue. my linux vm's with passthrough GPU fail to start, getting stuck at tianocore screen.

but windows VM's seemed ok, no issue encountered.

rolled-back and problem solved.

Updated from 6.3.5 to 6.5.1 without issues. I mainly use UnRaid for Plex streaming. Under the linux Plex docker setting it states that the server is accessible outside network, but when I tried to play a movie while outside my network, it wouldn't connect. I also tried to update the Plex docker, and it wouldn't update. I guess back to 6.3.5 since that's the last UnRaid version that works for me.tower-syslog-20180513-1120.zip

6 hours ago, GFOviedo said:

Updated from 6.3.5 to 6.5.1 without issues. I mainly use UnRaid for Plex streaming. Under the linux Plex docker setting it states that the server is accessible outside network, but when I tried to play a movie while outside my network, it wouldn't connect. I also tried to update the Plex docker, and it wouldn't update. I guess back to 6.3.5 since that's the last UnRaid version that works for me.tower-syslog-20180513-1120.zip

 

Did you take care of everything in the update notes linked near the top of the first post of this thread?

 

 

8 hours ago, trurl said:

 

Did you take care of everything in the update notes linked near the top of the first post of this thread?

 

 

 

Yes, I did. Everything seemed to be working, but I never tested accessing Plex outside my network until yesterday, and it wasn't working. I went under the Plex setting, and it stated it was accessible outside the network, but it wasn't.

 

I supposed I can give it another try and test it out, but I haven't been able to upgrade past 6.3.5 version due to this issue.

16 hours ago, GFOviedo said:

Updated from 6.3.5 to 6.5.1 without issues. I mainly use UnRaid for Plex streaming. Under the linux Plex docker setting it states that the server is accessible outside network, but when I tried to play a movie while outside my network, it wouldn't connect. I also tried to update the Plex docker, and it wouldn't update. I guess back to 6.3.5 since that's the last UnRaid version that works for me.tower-syslog-20180513-1120.zip

 

Followed the instructions again. Everything installs and works fine including Plex with in-network access. However, it doesn't work with out of network access. I noticed under Plex Settings that it shows accessible out side network, but there is no private / public IP and no internet access. I had to open the port under my router settings before in order to access Plex outside network with UnRaid version 6.3.5, but for some reason it isn't work for UnRaid 6.5.1.

 

It's 4 AM in CA, and I've been messing around with this for 3 hours already. So, I'll revert back and stay on 6.3.5 for now. May be one of new future version will eventually by plug and play and work. Thanks for your help.

Since the update, I have no GUI access or docker access via the browser, except plex. 

From local keyboard / monitor or via SSH, log in and

diagnostics

  then upload the resulting file

2 hours ago, GFOviedo said:

So, I'll revert back and stay on 6.3.5 for now. May be one of new future version will eventually by plug and play and work.

 

Unless you help find out what needs to be changed to make it work for you I wouldn't count on it. And some plugin authors aren't supporting 6.3.5 anymore.

 

*edit*

 

I say this having just now tested using plex from outside of my LAN and it is working fine for me. I haven't used 6.3.5 for a long time.

 

 

6 hours ago, Squid said:

From local keyboard / monitor or via SSH, log in and

 

diagnostics

  then upload the resulting file

 

The entire ZIP?

9 minutes ago, Rick Sanchez said:

 

The entire ZIP?

Yes. You can just attach it to your next post.

See Attached.

 

Thank you

daedalus-diagnostics-20180514-0332.zip

There are known issues with Docker in unRAID v6.5.0, It is highly recommended to upgrade to v6.5.1 (or v6.5.2 soon).

 

Can't access the GUI. 

1 minute ago, Rick Sanchez said:

Can't access the GUI. 

 

You can download the ZIP file of version 6.5.1 from the Limetech site and copy the bz* files to the flash device.