unRAID Server Release 6.1-rc5-x86_64 Available

[Bungy]

It happened with all 4 containers I tried to update. I also can't run a docker images rm - rf to remove the image. It returns the same error

 

What about stopping the docker service, manually deleting the docker.img and recreating and redownloading your containers..

 

Might be worth a shot.

 

That's exactly what I was about to do! I've been having issues and having to re-download my dockers regularly (every few days), so I was trying to avoid that and see if anybody else had that issue. I'm going to assume this is specific to my setup and I'll dig into why it's happening some more.

[BRiT]

Are you sure you're not running out of space in your docker.img? Or its not having corruptions?

 

[bungee91]

(I skipped from RC2 to 5, so maybe I missed something).

 

So what's the deal with disks spun up, or not, or temps not reporting currently?

 

I rebooted after upgrade, all disks showed still spinning (with temps) at 1.5 hours of uptime.

So I told it to spin down all disks, it came back with a single disk spinning, and just it's temp showing.

Now I see no temps, and all disks showing spun up.

I cleared browser cache, have cache directories and system temp running as plugins (plus a couple of others).

Pic attached (resize made it look awful).

[Bungy]

Are you sure you're not running out of space in your docker.img? Or its not having corruptions?

 

I'm pretty sure I'm not running out of free space - that was the first thing I checked

Label: none  uuid: 9296cea9-4513-4f4e-89c1-01f9abcc6c6d
Total devices 1 FS bytes used 10.21GiB
devid    1 size 30.00GiB used 16.29GiB path /dev/loop0

btrfs-progs v4.1.2

 

However I'm not sure that I'm not getting corruptions. Is there any easy way to check for those? This is the output from my btrfs fi df command but I don't believe it's showing anything interesting:

Data, single: total=13.01GiB, used=8.97GiB
System, DUP: total=8.00MiB, used=16.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=1.62GiB, used=1.23GiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=240.00MiB, used=0.00B

 

I'm going to run a btrfs check /mnt/cache/docker.img to see if it comes up with anything.

[Bungy]

Here are the results. The "cache and super generation don't match, space cache will be invalidated" is concerning, so I'm rebuilding the docker.img.

 

btrfs check --repair /mnt/cache/docker.img

enabling repair mode
Checking filesystem on /mnt/cache/docker.img
UUID: 9296cea9-4513-4f4e-89c1-01f9abcc6c6d
checking extents
Fixed 0 roots.
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
checking root refs
found 10957955101 bytes used err is 0
total csum bytes: 9407016
total tree bytes: 1325334528
total fs tree bytes: 1280851968
total extent tree bytes: 31342592
btree space waste bytes: 211518069
file data blocks allocated: 25897709568
referenced 25783037952
btrfs-progs v4.1.2

 

[billington.mark]

Ever since I upgraded to RC3, Chrome has been unable to retrieve any of the webfonts. It keeps getting 401 Not authorized responses. Navigating directly to the URL works. I experience no problems in Safari or Firefox.

 

I have the EXACT same issue. Fine in anything but chrome. Im on Chrome 46.0.2478.0 dev-m (64-bit).

Cleared Cache etc to no effect. Same 401 error given in the chrome dev tools. Image attached.

 

EDIT: Spelling, more info

 

Are you using authentication, that is, do you have a root user password set?

 

I do, yes.

If you remove the password does the issue still happen?

 

I think you are on to something...

 

If i clear the password so im not prompted for a login, the page loads correctly.

Reapplying the password, meaning i need to log into the GUI, issue returns.

 

Mark

[craigr]

Sorry if this is a stupid question, but this is my first time moving up to an rc for 6.1... I thought in rc2 there was a change to non-rotational drives in the webgui.  Well, my cache SSD has a "click to spindown" arrow on the Main tab in the webgui.  Am I misunderstanding the change to think that this shouldn't be an option?

 

Thanks!

Your SSD is able to go into 'standby' mode, presumably lower power, that's what spindown means for such devices.

EXCELLENT.  I am glad to see this back.

 

Thank you,

craigr

[johnodon]

Two days in a row now, I have experienced USB disconnects and see this message in my syslog.  I have not experienced this with previous versions (seems to have started with rc5).  Unfortunately, when this happens it is causing my Flirc to get a new device # and the only way to fix is to restart the server.

 

Aug 22 19:00:31 unRAID kernel: usb usb3-port1: disabled by hub (EMI?), re-enabling...
Aug 22 19:00:31 unRAID kernel: usb 3-1: USB disconnect, device number 2
Aug 22 19:00:31 unRAID kernel: usb 3-1: new low-speed USB device number 3 using uhci_hcd
Aug 22 19:00:31 unRAID kernel: input: flirc.tv flirc as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:20A0:0001.0006/input/input10
Aug 22 19:00:31 unRAID kernel: hid-generic 0003:20A0:0001.0006: input,hidraw0: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1a.0-1/input0

 

Is anyone else experiencing this?

 

John

[jonp]

Two days in a row now, I have experienced USB disconnects and see this message in my syslog.  I have not experienced this with previous versions (seems to have started with rc5).  Unfortunately, when this happens it is causing my Flirc to get a new device # and the only way to fix is to restart the server.

 

Aug 22 19:00:31 unRAID kernel: usb usb3-port1: disabled by hub (EMI?), re-enabling...
Aug 22 19:00:31 unRAID kernel: usb 3-1: USB disconnect, device number 2
Aug 22 19:00:31 unRAID kernel: usb 3-1: new low-speed USB device number 3 using uhci_hcd
Aug 22 19:00:31 unRAID kernel: input: flirc.tv flirc as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:20A0:0001.0006/input/input10
Aug 22 19:00:31 unRAID kernel: hid-generic 0003:20A0:0001.0006: input,hidraw0: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1a.0-1/input0

 

Is anyone else experiencing this?

 

John

 

Hmm, I have had some odd issues with USB assignment lately, but I thought they were related to the new emulated USB controller I'm testing (nec-xhci).  You're 100% positive this only started with RC5?

[johnodon]

Two days in a row now, I have experienced USB disconnects and see this message in my syslog.  I have not experienced this with previous versions (seems to have started with rc5).  Unfortunately, when this happens it is causing my Flirc to get a new device # and the only way to fix is to restart the server.

 

Aug 22 19:00:31 unRAID kernel: usb usb3-port1: disabled by hub (EMI?), re-enabling...
Aug 22 19:00:31 unRAID kernel: usb 3-1: USB disconnect, device number 2
Aug 22 19:00:31 unRAID kernel: usb 3-1: new low-speed USB device number 3 using uhci_hcd
Aug 22 19:00:31 unRAID kernel: input: flirc.tv flirc as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:20A0:0001.0006/input/input10
Aug 22 19:00:31 unRAID kernel: hid-generic 0003:20A0:0001.0006: input,hidraw0: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1a.0-1/input0

 

Is anyone else experiencing this?

 

John

 

Hmm, I have had some odd issues with USB assignment lately, but I thought they were related to the new emulated USB controller I'm testing (nec-xhci).  You're 100% positive this only started with RC5?

 

Yep.  I haven't seen any random USB disconnects in a long time (probably back to early v6 betas).  In newer versions I only ever saw these when I force stopped and started a VM.

 

John

[jonp]

Two days in a row now, I have experienced USB disconnects and see this message in my syslog.  I have not experienced this with previous versions (seems to have started with rc5).  Unfortunately, when this happens it is causing my Flirc to get a new device # and the only way to fix is to restart the server.

 

Aug 22 19:00:31 unRAID kernel: usb usb3-port1: disabled by hub (EMI?), re-enabling...
Aug 22 19:00:31 unRAID kernel: usb 3-1: USB disconnect, device number 2
Aug 22 19:00:31 unRAID kernel: usb 3-1: new low-speed USB device number 3 using uhci_hcd
Aug 22 19:00:31 unRAID kernel: input: flirc.tv flirc as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:20A0:0001.0006/input/input10
Aug 22 19:00:31 unRAID kernel: hid-generic 0003:20A0:0001.0006: input,hidraw0: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1a.0-1/input0

 

Is anyone else experiencing this?

 

John

 

Hmm, I have had some odd issues with USB assignment lately, but I thought they were related to the new emulated USB controller I'm testing (nec-xhci).  You're 100% positive this only started with RC5?

 

Yep.  I haven't seen any random USB disconnects in a long time (probably back to early v6 betas).  In newer versions I only ever saw these when I force stopped and started a VM.

 

John

Ok, I'll investigate again on Monday.

[bungee91]

Didn't get a response from my previous comment, will ask again.

 

I'm noticing that my drives do NOT spin down.

I have been up for 3 days, and can go to sleep (me, not my server, it is on all the time), wake up in the morning (~8 hours of inactivity minus VM's/Docker) and all of my drives are spinning.

I can force a spin down of disks, typically 2-3 remain up (which is expected). However upon refresh I will show all the green orbs lit (spinning), however only temps displayed on the 2-3 that remain up.

I check back later on, all drives are spinning again....

 

I thought maybe it was cache directories, as I reinstalled it ~5 days ago, however have removed it and the problem remains.

Cleared cache/browsing history/cookies, etc...

 

If it matters (I'd doubt it) I am using the intel_pstate=disable flag, as it is needed for proper idle with my setup.

My Go files looks like this for disable of messages for currently unchanged SMART reports, and load my MB temp:

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
#Add cache backup script to cron
#cp /boot/custom/cache_backup.sh /etc/cron.weekly
#modprobe for each sensor
modprobe nct6775
#SMART Notification Repeats disable unless values change
if [[ -f /boot/config/plugins/dynamix/monitor.ini ]]; then
  cp /boot/config/plugins/dynamix/monitor.ini /var/local/emhttp
  chmod -x /var/local/emhttp/monitor.ini
fi

 

My syslinux.cfg looks like this for PCIe downstream, and a stub for a NIC I pass:

default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pcie_acs_override=downstream intel_pstate=disable pci-stub.ids=8086:107d initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest

 

Syslog attached (no diagnostics zip at the moment, currently working on upgrading cache drive, Docker and VMs are off, etc...).

 

I have the following plugins, all up to date:

Community Applications
Server Layout
Preclear Disks
Powerdown
Dynamix System Temperature/System Statistics
Nerd Tools

server-syslog-20150823-0925.zip

[bonienl]

Not a real answer to your question.

 

You can actually remove the copying of the monitor.ini file from your go file, in v6.1 it is taken care off by unRAID itself.

 

Regarding the spinning disks, do you have any dockers or plugins installed which may spin up the disks? E.g. Plex may do a daily database update which can spin up your disks.

 

[bungee91]

Not a real answer to your question.

 

You can actually remove the copying of the monitor.ini file from your go file, in v6.1 it is taken care off by unRAID itself.

 

Regarding the spinning disks, do you have any dockers or plugins installed which may spin up the disks? E.g. Plex may do a daily database update which can spin up your disks.

 

So make it look like this?

#SMART Notification Repeats disable unless values change
if [[ -f /boot/config/plugins/dynamix/monitor.ini ]]; then
chmod -x /var/local/emhttp/monitor.ini
fi

 

No Plex, just what's listed.

Going to replace my cache drive now (bigger), so I will have a shutdown, and see if it changes.

 

Edit:... Interesting!!

However I don't have a clue what would be holding my drives up!

 

I disabled Docker and turned off all of my VM's for rsync to backup my current cache drive to my array.

In that amount of time (and talking here) all my drives are spun down as they should be!..

I now see this in my syslog:

Aug 23 09:35:26 Server kernel: mdcmd (198): spindown 4
Aug 23 09:35:26 Server kernel: mdcmd (199): spindown 8
Aug 23 09:35:54 Server kernel: mdcmd (200): spindown 3
Aug 23 09:36:44 Server kernel: mdcmd (201): spindown 5
Aug 23 09:39:19 Server kernel: mdcmd (202): spindown 2
Aug 23 09:39:21 Server kernel: mdcmd (203): spindown 6
Aug 23 09:41:46 Server kernel: mdcmd (204): spindown 1
Aug 23 09:41:47 Server kernel: mdcmd (205): spindown 9

[bonienl]

So make it look like this?

#SMART Notification Repeats disable unless values change
if [[ -f /boot/config/plugins/dynamix/monitor.ini ]]; then
chmod -x /var/local/emhttp/monitor.ini
fi

 

No, you can remove the complete section, anything related to monitor.ini is done by unRAID in v6.1.

[bungee91]

So make it look like this?

#SMART Notification Repeats disable unless values change
if [[ -f /boot/config/plugins/dynamix/monitor.ini ]]; then
chmod -x /var/local/emhttp/monitor.ini
fi

 

No, you can remove the complete section, anything related to monitor.ini is done by unRAID in v6.1.

 

Oh!..

So what you're saying is this is now the default behavior in 6.1 (don't notify unless a change in parameters)?

Sorry if that sounds like a stupid question, just want to make sure.

[bonienl]

So make it look like this?

#SMART Notification Repeats disable unless values change
if [[ -f /boot/config/plugins/dynamix/monitor.ini ]]; then
chmod -x /var/local/emhttp/monitor.ini
fi

 

No, you can remove the complete section, anything related to monitor.ini is done by unRAID in v6.1.

 

Oh!..

So what you're saying is this is now the default behavior in 6.1 (don't notify unless a change in parameters)?

Sorry if that sounds like a stupid question, just want to make sure.

 

Yes that is correct. There may be initial notifications but subsequent reboots will only give notifications when conditions have changed.

 

[bungee91]

Yes that is correct. There may be initial notifications but subsequent reboots will only give notifications when conditions have changed.

 

Ok, thanks, removed.

[Darqfallen]

So I just noticed that I cannot shutdown any dockers nor update them.

 

Aug 23 09:26:44 Dirge php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/docker stop Syncthing
Aug 23 09:26:44 Dirge php: /plugins/dynamix.docker.manager/scripts/docker stop Syncthing

 

Aug 23 09:31:24 Dirge php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/dockerupdate.php
Aug 23 09:31:24 Dirge php: /plugins/dynamix.docker.manager/scripts/dockerupdate.php

[Squid]

So I just noticed that I cannot shutdown any dockers nor update them.

 

Aug 23 09:26:44 Dirge php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/docker stop Syncthing
Aug 23 09:26:44 Dirge php: /plugins/dynamix.docker.manager/scripts/docker stop Syncthing

 

Aug 23 09:31:24 Dirge php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/dockerupdate.php
Aug 23 09:31:24 Dirge php: /plugins/dynamix.docker.manager/scripts/dockerupdate.php

Are you running RC5?  That was an issue with RC4 that I believe got fixed in RC5

[Darqfallen]

Are you running RC5?  That was an issue with RC4 that I believe got fixed in RC5

 

Ahh yes, I did the update but didn't reboot.

 

Thanks!

[pickthenimp]

Apologies if this is not directly related to rc5 but I am trying to track down an issue I'm encountering after my upgrade to unraid 6.  Ive since installed RC5 to see if that would help.  After a few days my shares become unresponsive, I can't load the web interface and I have to hard reboot.  The newest entry in my syslog makes me think something happened during the mover script?  Or maybe the apcupsd plugin?

 

Aug 23 01:00:01 nas logger: mover started

Aug 23 01:00:01 nas logger: moving "TV"

Aug 23 01:00:01 nas logger: ./TV/Why! With Hannibal Buress/Season 01/Why! With Hannibal Buress - S01E07 - Episode 7 - HDTV-720p.mkv

Aug 23 01:00:07 nas logger: .d..t...... ./

Aug 23 01:30:39 nas kernel: mdcmd (92): spindown 0

Aug 23 01:58:53 nas kernel: mdcmd (93): spindown 1

Aug 23 01:59:02 nas kernel: mdcmd (94): spindown 2

Aug 23 01:59:09 nas kernel: mdcmd (95): spindown 3

Aug 23 01:59:18 nas kernel: mdcmd (96): spindown 4

Aug 23 02:01:30 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 23 02:30:27 nas kernel: mdcmd (97): spindown 3

Aug 23 04:20:45 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 23 04:40:01 nas apcupsd[1882]: apcupsd exiting, signal 15

Aug 23 04:40:01 nas apcupsd[1882]: apcupsd shutdown succeeded

Aug 23 04:40:04 nas apcupsd[10225]: apcupsd 3.14.13 (02 February 2015) slackware startup succeeded

Aug 23 04:40:04 nas apcupsd[10225]: NIS server startup succeeded

Aug 23 05:48:15 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

 

 

I started a thread here but hoping to get some more traction: https://lime-technology.com/forum/index.php?topic=42319.msg403262#msg403262

[dlandon]

The new menu layout with the Feedback button crowds out the Help, Info, and Log buttons on an iPad and makes those buttons unusable.  Of course I didn't help the situation because I added the Dynamix System Buttons making the issue worse.

 

I know that it is not a high priority to be able to use the unraid webgui on an iPad, but more people are using tablets instead of computers, and it might be time to consider a responsive webgui design to fit different size devices.

 

You get the same effect by shrinking down a normal browser window.

[digitalfixer]

Since updating to 6.1rc5 I'm seeing lots of errors like this in the log file.

 

Aug 24 09:34:01 Tower kernel: xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 1
Aug 24 09:34:01 Tower kernel: xhci_hcd 0000:00:14.0: Looking for event-dma 00000000fffd4000 trb-start 00000000fffd5fe0 trb-end 00000000fffd6000 seg-start 00000000fffd5000 seg-end 00000000fffd5ff0
Aug 24 09:34:04 Tower kernel: usb 1-3.2: reset high-speed USB device number 5 using xhci_hcd

 

I've included the diagnostic file.

 

Kevin.

tower-diagnostics-20150824-0941.zip

[dlandon]

Since updating to 6.1rc5 I'm seeing lots of errors like this in the log file.

 

Aug 24 09:34:01 Tower kernel: xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 1
Aug 24 09:34:01 Tower kernel: xhci_hcd 0000:00:14.0: Looking for event-dma 00000000fffd4000 trb-start 00000000fffd5fe0 trb-end 00000000fffd6000 seg-start 00000000fffd5000 seg-end 00000000fffd5ff0
Aug 24 09:34:04 Tower kernel: usb 1-3.2: reset high-speed USB device number 5 using xhci_hcd

 

I've included the diagnostic file.

 

Kevin.

 

I too am seeing this once in a while:

Aug 24 05:39:57 MediaServer kernel: xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 0 comp_code 1
Aug 24 05:39:57 MediaServer kernel: xhci_hcd 0000:00:14.0: Looking for event-dma 00000000fffb0000 trb-start 00000000fffb1fd0 trb-end 00000000fffb2000 seg-start 00000000fffb1000 seg-end 00000000fffb1ff0

 

You have the unassigned devices plugin installed and so do I.  I wonder if this is a udev/unassigned devices issue.  You are getting this a lot more than I am.  Can you uninstall the unassigned devices plugin and see if the messages stop?