unRAID Server Release 6.1.6 Available

bonienl · December 3, 2015

Upon re-reading smartctl for different controllers, the numbers can range from 0-127 or 1-128. Will make something which can accommodate that and still user-friendly.

The self-test button is only enabled when the drive is active, this is tested by the code using hdparm. I can add that state "unknown" is seen as "active".

Addy90 · December 3, 2015

Wow okay up to 128 is kinda much, but who knows if and when unRAID will support more than 25 disks - so it should be good to go that high just for sure.

At least when using a RAID-controller, state "unknown" could be added. It did work when the disks were plugged in the mainboard, but does not work with the controller card - so when using a controller card, "unknown" could be ignored at least for the self-tests - guess that should not be a problem for being a little bit incorrect here

bonienl · December 3, 2015

I've made another update, which hopefully addresses all outstanding points.

Download the attached file, unzip it and install manually:

installpkg dynamix.smart.update-2015.12.04.txz

Thanks for your feedback!

dynamix.smart.update-2015.12.04.zip

htpcnewbie · December 4, 2015

After upgrading through the GUI, rebooted the server and started a parity check early this morning. I logged in to see the status this evening and was surprised to see this message:

"

unRAID Parity check: 03-12-2015 14:25

Notice [TOWER] - Parity check finished (0 errors)

Duration: unavailable (no parity-check entries logged)

"

Typically it takes about 13 hrs to complete the parity check and the last time it was couple of days ago on 12/1 with 0 sync errors. What does the above update mean?

Whaler_99 · December 4, 2015

Anyone seeing performance issues?

I updated to 6.1.5 and then a day or so later to 6.1.6 so I am not sure which version affected it, but in 6.1.4 there were no issues. I am noticing streaming shows from my server, via plex, video is skipping and jumping a bit. Audio seems fine, just the video. And no, it isn't a bad file, have tried with a few different ones, all seeing random skips and such since the upgrade to 6.1.5->6.1.6.

jonp · December 4, 2015

Anyone seeing performance issues?

I updated to 6.1.5 and then a day or so later to 6.1.6 so I am not sure which version affected it, but in 6.1.4 there were no issues. I am noticing streaming shows from my server, via plex, video is skipping and jumping a bit. Audio seems fine, just the video. And no, it isn't a bad file, have tried with a few different ones, all seeing random skips and such since the upgrade to 6.1.5->6.1.6.

Plex recently had some issues in a release the put out. Try just playing the media directly with another device or try another media streamer to rule that out before we troubleshoot further.

bonienl · December 4, 2015

After upgrading through the GUI, rebooted the server and started a parity check early this morning. I logged in to see the status this evening and was surprised to see this message:

"

unRAID Parity check: 03-12-2015 14:25

Notice [TOWER] - Parity check finished (0 errors)

Duration: unavailable (no parity-check entries logged)

"

Typically it takes about 13 hrs to complete the parity check and the last time it was couple of days ago on 12/1 with 0 sync errors. What does the above update mean?

You need to install the hot fix. See earlier message in this thread.

Whaler_99 · December 4, 2015

Anyone seeing performance issues?

I updated to 6.1.5 and then a day or so later to 6.1.6 so I am not sure which version affected it, but in 6.1.4 there were no issues. I am noticing streaming shows from my server, via plex, video is skipping and jumping a bit. Audio seems fine, just the video. And no, it isn't a bad file, have tried with a few different ones, all seeing random skips and such since the upgrade to 6.1.5->6.1.6.

Plex recently had some issues in a release the put out. Try just playing the media directly with another device or try another media streamer to rule that out before we troubleshoot further.

Looks like that is indeed the issue. I did check the Plexpass forum and didn't see anything off hand about the pausing issue. Playing same video just through Windows Explorer using VLC seems ok. Thanks!

TUMS · December 4, 2015

For me plex has been crashing ever since the 0.9.14.4 update. I'm using plex android app and my bluray rips refuse to play. I can play dvd rips but the plex server eventually crashes 5 minutes into a movie.

Addy90 · December 4, 2015

I've made another update, which hopefully addresses all outstanding points.

Download the attached file, unzip it and install manually:
installpkg dynamix.smart.update-2015.12.04.txz
Thanks for your feedback!

Hi boniel, thanks for your great work - we nearly have it!

What is working now are all ports, so this is the first time I could show the SMART values of all disks that are attached to my RAID controller - very great!

What also is working - beside the SMART details - are the self-tests! I can start them and see the result - worked on all disks (did a short test on all disks). Also great!

One very last thing: See attached screenshot - the place at "Last SMART test result" still shows "disk spun down" instead of the last smart test result which obviously can be seen correctly in the history. (The other details below are capped but all valid!) So perhaps "disk spun down" should only be shown when the disk really is spun down and not when the state is "unknown". So same case as with the self-test buttons that all work now

So except of this, everything else is working very perfect now - I have to say a big thanks!!! A really big one

jphipps · December 4, 2015

Anyone seeing performance issues?

I updated to 6.1.5 and then a day or so later to 6.1.6 so I am not sure which version affected it, but in 6.1.4 there were no issues. I am noticing streaming shows from my server, via plex, video is skipping and jumping a bit. Audio seems fine, just the video. And no, it isn't a bad file, have tried with a few different ones, all seeing random skips and such since the upgrade to 6.1.5->6.1.6.

I have noticed issues with the drives not spinning up. Even doing a directory listing would just hang until I clicked spin up all drives and then everything worked as normal. When you see the slowness do you have drives powered down?

jphipps · December 4, 2015

Is it possible to get disk level configuration on smart notification on drives that are not part of the array? I have a disk that is failing, but has been removed from the array, but still in the machine and I keep getting alerts about it.

jumperalex · December 4, 2015

Is it possible to get disk level configuration on smart notification on drives that are not part of the array? I have a disk that is failing, but has been removed from the array, but still in the machine and I keep getting alerts about it.

If you have Unassigned drives plugin installed then you can go to MAIN and click on the disk to get that functionality. It doesn't seem to work from the Dashboard screen though. So that might be a feature request still.

jphipps · December 4, 2015

Is it possible to get disk level configuration on smart notification on drives that are not part of the array? I have a disk that is failing, but has been removed from the array, but still in the machine and I keep getting alerts about it.

If you have Unassigned drives plugin installed then you can go to MAIN and click on the disk to get that functionality. It doesn't seem to work from the Dashboard screen though. So that might be a feature request still.

Thanks for that info, I didn't realize you could do it from that plugin... I have that plugin and have disabled the notifications...

jbartlett · December 5, 2015

Who knows, maybe one day I update the Dynamix Stats plugin to graph parity check times

I have a script that does this if you want to utilize it.

bonienl · December 5, 2015

Who knows, maybe one day I update the Dynamix Stats plugin to graph parity check times

I have a script that does this if you want to utilize it.

Might be useful, definitely interesting

stealth82 · December 8, 2015

For those who want to retain their current parity-check information, please download the hot-fix file attached to this message. Unzip the file, copy the .txz file to your unRAID system and install manually:
installpkg dynamix.hot.fix-2015.12.02.txz
Delete the file /boot/config/parity-checks.log and wait a minute to have it automatically recreated.

Apologies for all inconvenience!

Ps. Hot fix works for both 6.1.5 and 6.1.6

I did as described here - actually installed the 2015.12.04 patch - but even after 20 mins the log didn't recreate by itself.

I decided to create manually but no history button is visible nor is the last parity sync duration time.

Should I reboot the server?

bonienl · December 8, 2015

For those who want to retain their current parity-check information, please download the hot-fix file attached to this message. Unzip the file, copy the .txz file to your unRAID system and install manually:
installpkg dynamix.hot.fix-2015.12.02.txz
Delete the file /boot/config/parity-checks.log and wait a minute to have it automatically recreated.

Apologies for all inconvenience!

Ps. Hot fix works for both 6.1.5 and 6.1.6
I did as described here - actually installed the 2015.12.04 patch - but even after 20 mins the log didn't recreate by itself.

I decided to create manually but no history button is visible nor is the last parity sync duration time.

Should I reboot the server?

No need to reboot, you need to have notifications enabled though to make the background updating work.

stealth82 · December 8, 2015

System notifications are indeed on. Just the "store to flash" was off. I enabled it but still no history button... what am I doing wrong?

bonienl · December 9, 2015

System notifications are indeed on. Just the "store to flash" was off. I enabled it but still no history button... what am I doing wrong?

Did you delete the file parity-checks.log ?

wirenut · December 9, 2015

System notifications are indeed on. Just the "store to flash" was off. I enabled it but still no history button... what am I doing wrong?

Did you delete the file parity-checks.log ?

For those who want to retain their current parity-check information, please download the hot-fix file attached to this message. Unzip the file, copy the .txz file to your unRAID system and install manually:
installpkg dynamix.hot.fix-2015.12.02.txz
Delete the file /boot/config/parity-checks.log and wait a minute to have it automatically recreated.

Apologies for all inconvenience!

Ps. Hot fix works for both 6.1.5 and 6.1.6
I did as described here - actually installed the 2015.12.04 patch - but even after 20 mins the log didn't recreate by itself.

I decided to create manually but no history button is visible nor is the last parity sync duration time.

Should I reboot the server?
No need to reboot, you need to have notifications enabled though to make the background updating work.

I don't know if it applies to your situation but I had a similar problem. After following the instructions and deleting the file it never re-created itself after waiting a good 10 minutes. I re-ran the installpkg cmd from a putty session and that did the trick. works now.

I also do not have save to flash enabled, just notifications. hope it works for you.

stealth82 · December 10, 2015

System notifications are indeed on. Just the "store to flash" was off. I enabled it but still no history button... what am I doing wrong?

Did you delete the file parity-checks.log ?

I did. I even restarted the server, renamed the parity-checks.log, installed the patch from command line but no parity-checks.log gets created.

rhinoman · December 13, 2015

Had an issue only since this release, my cache drive is not staying mounted during reboot. Can stop the array, remount it and start it and its all good. Stop array, reboot and it drops out again.

Log

Dec 13 03:18:41 SUN logger: realtime =none extsz=4096 blocks=0, rtextents=0
Dec 13 03:18:41 SUN emhttp: shcmd (178): mkdir -p /mnt/cache
Dec 13 03:18:41 SUN emhttp: shcmd (179): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdq1 /mnt/cache |& logger
Dec 13 03:18:41 SUN kernel: BTRFS info (device sdq1): disk space caching is enabled
Dec 13 03:18:41 SUN kernel: BTRFS: has skinny extents
Dec 13 03:18:41 SUN kernel: BTRFS: detected SSD devices, enabling SSD mode
Dec 13 03:18:41 SUN emhttp: shcmd (180): sync
Dec 13 03:18:41 SUN emhttp: shcmd (181): mkdir /mnt/user0
Dec 13 03:18:41 SUN emhttp: shcmd (182): /usr/local/sbin/shfs /mnt/user0 -disks 12286 -o noatime,big_writes,allow_other |& logger
Dec 13 03:18:41 SUN emhttp: shcmd (183): mkdir /mnt/user
Dec 13 03:18:41 SUN emhttp: shcmd (184): /usr/local/sbin/shfs /mnt/user -disks 12287 2048000000 -o noatime,big_writes,allow_other -o remember=0 |& logger
Dec 13 03:18:41 SUN emhttp: shcmd (185): cat - > /boot/config/plugins/dynamix/mover.cron <<< "# Generated mover schedule:#01240 3 * * * /usr/local/sbin/mover |& logger#012"
Dec 13 03:18:41 SUN emhttp: shcmd (186): /usr/local/sbin/update_cron &> /dev/null
Dec 13 03:18:41 SUN emhttp: shcmd (187): :>/etc/samba/smb-shares.conf
Dec 13 03:18:41 SUN avahi-daemon[14811]: Files changed, reloading.
Dec 13 03:18:42 SUN emhttp: Restart SMB...
Dec 13 03:18:42 SUN emhttp: shcmd (188): killall -HUP smbd
Dec 13 03:18:42 SUN emhttp: shcmd (189): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service
Dec 13 03:18:42 SUN avahi-daemon[14811]: Files changed, reloading.
Dec 13 03:18:42 SUN avahi-daemon[14811]: Service group file /services/smb.service changed, reloading.
Dec 13 03:18:42 SUN emhttp: shcmd (190): pidof rpc.mountd &> /dev/null
Dec 13 03:18:42 SUN emhttp: shcmd (191): /etc/rc.d/rc.atalk status
Dec 13 03:18:42 SUN emhttp: Starting Docker...
Dec 13 03:18:42 SUN kernel: BTRFS: device fsid ff117a10-bc08-4b71-a5e2-e5835f33b4f4 devid 1 transid 931 /dev/loop0
Dec 13 03:18:42 SUN kernel: BTRFS info (device loop0): disk space caching is enabled
Dec 13 03:18:42 SUN kernel: BTRFS: has skinny extents
Dec 13 03:18:42 SUN logger: Resize '/var/lib/docker' of 'max'
Dec 13 03:18:42 SUN kernel: BTRFS: new size for /dev/loop0 is 21474836480
Dec 13 03:18:42 SUN logger: starting docker ...
Dec 13 03:18:42 SUN avahi-daemon[14811]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.42.1.
Dec 13 03:18:42 SUN avahi-daemon[14811]: New relevant interface docker0.IPv4 for mDNS.
Dec 13 03:18:42 SUN avahi-daemon[14811]: Registering new address record for 172.17.42.1 on docker0.IPv4.
Dec 13 03:18:43 SUN avahi-daemon[14811]: Service "SUN" (/services/smb.service) successfully established.
Dec 13 03:18:54 SUN logger: Updating templates... Updating info... Done.
Dec 13 03:18:54 SUN kernel: EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null)
Dec 13 03:18:54 SUN emhttp: Starting libvirt...
Dec 13 03:18:54 SUN logger: Starting libvirtd...
Dec 13 03:18:55 SUN dnsmasq[13171]: read /etc/hosts - 1 addresses
Dec 13 03:18:55 SUN dnsmasq[13171]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Dec 13 03:18:55 SUN dnsmasq-dhcp[13171]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Dec 13 03:19:01 SUN crond[1786]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null
Dec 13 03:19:16 SUN emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

trurl · December 13, 2015

Had an issue only since this release, my cache drive is not staying mounted during reboot. Can stop the array, remount it and start it and its all good. Stop array, reboot and it drops out again.

What filesystem is your cache drive?

rhinoman · December 13, 2015

Had an issue only since this release, my cache drive is not staying mounted during reboot. Can stop the array, remount it and start it and its all good. Stop array, reboot and it drops out again.

What filesystem is your cache drive?

BTRFS but it has been for a while now, was intending to move to a pool shortly.

unRAID Server Release 6.1.6 Available

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation