unRAID Server Release 6.2.0-beta20 Available


Recommended Posts

Is anyone else noticing their drives getting hot and/or very busy with 6.2? On 6.19 my drives sat idle most of the time.. on 6.2 no matter how much I try to encourage them to spin down they keep coming back up..

 

Log excerpt:

Apr 3 23:41:01 VAULT kernel: usb 5-2.2: reset low-speed USB device number 4 using xhci_hcd

Apr 3 23:41:01 VAULT kernel: usb 5-2.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes

Apr 3 23:41:10 VAULT kernel: br0: topology change detected, propagating

Apr 3 23:41:10 VAULT kernel: br0: port 3(vnet0) entered forwarding state

Apr 3 23:41:12 VAULT sshd[13719]: Did not receive identification string from 222.255.174.138

Apr 3 23:41:15 VAULT sshd[13732]: fatal: mm_answer_moduli: bad parameters: 2048 2048 1024

Apr 3 23:41:50 VAULT emhttp: Spinning down all drives...

Apr 3 23:41:50 VAULT kernel: mdcmd (45): spindown 0

Apr 3 23:41:51 VAULT kernel: mdcmd (46): spindown 1

Apr 3 23:41:52 VAULT kernel: mdcmd (47): spindown 2

Apr 3 23:41:53 VAULT kernel: mdcmd (48): spindown 3

Apr 3 23:41:53 VAULT kernel: mdcmd (49): spindown 4

Apr 3 23:41:54 VAULT kernel: mdcmd (50): spindown 5

Apr 3 23:41:55 VAULT kernel: mdcmd (51): spindown 6

Apr 3 23:41:56 VAULT kernel: mdcmd (52): spindown 7

Apr 3 23:41:57 VAULT kernel: mdcmd (53): spindown 29

Apr 3 23:41:58 VAULT emhttp: shcmd (139): /usr/sbin/hdparm -y /dev/sdc &> /dev/null

Apr 3 23:41:58 VAULT emhttp: shcmd (140): /usr/sbin/hdparm -y /dev/sdf &> /dev/null

Apr 3 23:42:13 VAULT kernel: mdcmd (54): spindown 7

Apr 3 23:42:20 VAULT sshd[14418]: Did not receive identification string from 222.255.174.138

Apr 3 23:42:24 VAULT sshd[14442]: fatal: mm_answer_moduli: bad parameters: 2048 2048 1024

 

The spindown above was initiated by me and drives 3,6,7 spun back up.. my drive 7 seems to be on almost all the time and gets hot accordingly!!

Have you tried the Open Files plugin to see if you have files open on your drives?
Link to comment

- dynamix: Get rid of SMART db update in monitor

 

Can we fix it instead?  The underlying problem is pretty simple:

  https://lime-technology.com/forum/index.php?topic=47386.0

Debian got rid of it entirely due to "security concerns":

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804299

 

I think this is something that is more properly added as a plugin, but open to other opinions.  We'll see about refreshing that header file for each release.

 

For the time being, I have created a separate plugin, which allows to set up a update schedule for the SMART database (it will make the necessary correction in the SMART script to do a correct update).

 

The plugin can be installed by copying and pasting the URL below into the plugin manager.

 

https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.smart.drivedb.plg

 

Configuration of the plugin is under Settings -> Scheduler -> SMART DriveDB (by default no schedule is active)

 

 

Link to comment

- dynamix: Get rid of SMART db update in monitor

 

Can we fix it instead?  The underlying problem is pretty simple:

  https://lime-technology.com/forum/index.php?topic=47386.0

Debian got rid of it entirely due to "security concerns":

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804299

 

I think this is something that is more properly added as a plugin, but open to other opinions.  We'll see about refreshing that header file for each release.

 

For the time being, I have created a separate plugin, which allows to set up a update schedule for the SMART database (it will make the necessary correction in the SMART script to do a correct update).

 

The plugin can be installed by copying and pasting the URL below into the plugin manager.

 

https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.smart.drivedb.plg

 

Configuration of the plugin is under Settings -> Scheduler -> SMART DriveDB (by default no schedule is active)

 

 

 

This doesn't work for me:

 

Apr 4 12:10:01 Tower crond[1438]: exit status 1 from user root /usr/sbin/update-smart-drivedb 1>/dev/null 2>&1>

Apr 4 12:10:01 Tower sSMTP[9506]: Creating SSL connection to host

Apr 4 12:10:01 Tower sSMTP[9506]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256

Apr 4 12:10:01 Tower sSMTP[9506]: Authorization failed (535 5.7.8 https://support.google.com/mail/answer/14257 ll9sm28582379wjc.29 - gsmtp)

 

 

Link to comment

This doesn't work for me:

 

Apr 4 12:10:01 Tower crond[1438]: exit status 1 from user root /usr/sbin/update-smart-drivedb 1>/dev/null 2>&1>

Apr 4 12:10:01 Tower sSMTP[9506]: Creating SSL connection to host

Apr 4 12:10:01 Tower sSMTP[9506]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256

Apr 4 12:10:01 Tower sSMTP[9506]: Authorization failed (535 5.7.8 https://support.google.com/mail/answer/14257 ll9sm28582379wjc.29 - gsmtp)

 

I've made a typo in the cron generation text. It is corrected in version 2016.04.04a. You need to re-apply settings to reflect the changes.

Link to comment

This doesn't work for me:

 

Apr 4 12:10:01 Tower crond[1438]: exit status 1 from user root /usr/sbin/update-smart-drivedb 1>/dev/null 2>&1>

Apr 4 12:10:01 Tower sSMTP[9506]: Creating SSL connection to host

Apr 4 12:10:01 Tower sSMTP[9506]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256

Apr 4 12:10:01 Tower sSMTP[9506]: Authorization failed (535 5.7.8 https://support.google.com/mail/answer/14257 ll9sm28582379wjc.29 - gsmtp)

 

I've made a typo in the cron generation text. It is corrected in version 2016.04.04a. You need to re-apply settings to reflect the changes.

 

Had to remove and reinstall the plugin as the update removed the tab from the Scheduler page. It's now just hanging at:

 

Apr 4 13:35:16 Tower crond[1438]: exit status 1 from user root /usr/sbin/update-smart-drivedb 1>/dev/null 2>&1

 

SR

Link to comment

Not sure what happened. Made another update - version 2016.04.04b - with revised cron entry.

 

Perhaps safest to uninstall the existing version and re-install using the URL: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.smart.drivedb.plg

 

Still hanging with the same error.

 

SR

 

What happens when you execute the command directly from CLI: /usr/sbin/update-smart-drivedb

 

Link to comment

I get...

 

/usr/sbin/update-smart-drivedb: download from trunk failed (HTTP error)

 

 

SR

 

This error means that the script is using HTTP and not HTTPS, upon installation of the plugin, it should modify the script to use HTTPS...

 

Do you have anything running that might 'restore'  the script?

 

Link to comment

- dynamix: Get rid of SMART db update in monitor

 

Can we fix it instead?  The underlying problem is pretty simple:

  https://lime-technology.com/forum/index.php?topic=47386.0

Debian got rid of it entirely due to "security concerns":

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804299

 

I think this is something that is more properly added as a plugin, but open to other opinions.  We'll see about refreshing that header file for each release.

 

For the time being, I have created a separate plugin, which allows to set up a update schedule for the SMART database (it will make the necessary correction in the SMART script to do a correct update).

 

The plugin can be installed by copying and pasting the URL below into the plugin manager.

 

https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.smart.drivedb.plg

 

Configuration of the plugin is under Settings -> Scheduler -> SMART DriveDB (by default no schedule is active)

 

Thanks for this bonienl!  I haven't installed it yet, but I looked at the code and I have a request - after the install fixes the update-smart-drivedb script, can it go ahead and run the script one time rather than wait for the cron job?  That would let me remove it from my go script altogether.  Thanks!

Link to comment

I get...

 

/usr/sbin/update-smart-drivedb: download from trunk failed (HTTP error)

 

 

SR

 

This error means that the script is using HTTP and not HTTPS, upon installation of the plugin, it should modify the script to use HTTPS...

 

Do you have anything running that might 'restore'  the script?

 

Not that I know of. Running a few Dynamix plugins (System Stats, Local Master, Cache Dir, Active Streams), Powerdown, CA, UD. The only active dockers are Plex and Crashplan.

 

SR

Link to comment

Rolled back to 6.1.9 after hard lock of w10 gaming vm which in turn locked unraid necessitating in a unclean shutdown. Spent the rest of the night getting the server back up to scratch and creating a new w10 vm.

 

I think at this point I'm "out" with 6.2 after the initial hassle of getting it installed upgrade followed by this.

Link to comment

I have noticed a problem with smb shares that only happens on unraid.

 

I am using beta 6.2 beta 20 and this problem didnt happen on 6.1.9. When running windows 10(vm) i cant mount an iso file that is on a network smb share on my unraid server.  I get error "Sorry, there was a problem mounting the file"

 

I can copy the iso file to the local pc and it will mount fine. I wondered if the problem was the iso needed to be unsparsed. So i enabled that option in windows with a reg change. But the iso still would not mount from the unraid share.

 

I needed check the problem was not with my windows 10 so i ran all updates. Still would not open iso over unraid share.

I had a copy of my windows 10 vm image from december (everything worked fine back then). Using that backup windows 10 vm same problem existed. I even created a new windows 10 vm and got same problem.

 

So now i think i have ruled out that it was a windows 10 OS problem.

 

Next thing I did was to setup a network share separate from my unraid server. So I plugged a usb flash drive into my asus router and created a share on that. I mapped a drive to the share on the asus router and copied the iso image to that location.

The iso image mounted fine from the asus router share.

 

So my windows 10 machine will mount iso files from a network share on my router, but will not open the same iso file from the unraid share.

 

Has anyone else noticed this problem. Maybe you guys could try to recreate my problem.

 

Thanks

prime-diagnostics-20160405-1120.zip

Link to comment

I have noticed a problem with smb shares that only happens on unraid.

 

I am using beta 6.2 beta 20 and this problem didnt happen on 6.1.9. When running windows 10(vm) i cant mount an iso file that is on a network smb share on my unraid server.  I get error "Sorry, there was a problem mounting the file"

 

I can copy the iso file to the local pc and it will mount fine. I wondered if the problem was the iso needed to be unsparsed. So i enabled that option in windows with a reg change. But the iso still would not mount from the unraid share.

 

I needed check the problem was not with my windows 10 so i ran all updates. Still would not open iso over unraid share.

I had a copy of my windows 10 vm image from december (everything worked fine back then). Using that backup windows 10 vm same problem existed. I even created a new windows 10 vm and got same problem.

 

So now i think i have ruled out that it was a windows 10 OS problem.

 

Next thing I did was to setup a network share separate from my unraid server. So I plugged a usb flash drive into my asus router and created a share on that. I mapped a drive to the share on the asus router and copied the iso image to that location.

The iso image mounted fine from the asus router share.

 

So my windows 10 machine will mount iso files from a network share on my router, but will not open the same iso file from the unraid share.

 

Has anyone else noticed this problem. Maybe you guys could try to recreate my problem.

 

Thanks

 

I too had this problem which can be resolved as a workaround by adding max protocol = SMB2_02 to SMB settings in GUI. It's a known issue with SMB. i received a message from Jonp stating they are aware of it.

Link to comment

I have noticed a problem with smb shares that only happens on unraid.

 

I am using beta 6.2 beta 20 and this problem didnt happen on 6.1.9. When running windows 10(vm) i cant mount an iso file that is on a network smb share on my unraid server.  I get error "Sorry, there was a problem mounting the file"

 

I can copy the iso file to the local pc and it will mount fine. I wondered if the problem was the iso needed to be unsparsed. So i enabled that option in windows with a reg change. But the iso still would not mount from the unraid share.

 

I needed check the problem was not with my windows 10 so i ran all updates. Still would not open iso over unraid share.

I had a copy of my windows 10 vm image from december (everything worked fine back then). Using that backup windows 10 vm same problem existed. I even created a new windows 10 vm and got same problem.

 

So now i think i have ruled out that it was a windows 10 OS problem.

 

Next thing I did was to setup a network share separate from my unraid server. So I plugged a usb flash drive into my asus router and created a share on that. I mapped a drive to the share on the asus router and copied the iso image to that location.

The iso image mounted fine from the asus router share.

 

So my windows 10 machine will mount iso files from a network share on my router, but will not open the same iso file from the unraid share.

 

Has anyone else noticed this problem. Maybe you guys could try to recreate my problem.

 

Thanks

 

I too had this problem which can be resolved as a workaround by adding max protocol = SMB2_02 to SMB settings in GUI. It's a known issue with SMB. i received a message from Jonp stating they are aware of it.

 

Thankyou Mikeyosm  got it working now  :)

Link to comment

I had reverted back to 6.1.9 because of issues with my Realtek ethernet card.    I decided to install a different eth card to get around the issue, but when I re-updated to 6.2 B20, the Array Operations screen  no longer has the section for doing a parity check.  I am wondering if it was do to the dynamix update for 6.1.9 that I had applied before re-upgrading.  Any ideas?

 

Screen shot https://www.dropbox.com/s/wa2findx9v3om40/Screen%20Shot%202016-04-05%20at%208.08.51%20PM.png?dl=0

 

Link to comment

I had reverted back to 6.1.9 because of issues with my Realtek ethernet card.    I decided to install a different eth card to get around the issue, but when I re-updated to 6.2 B20, the Array Operations screen  no longer has the section for doing a parity check.  I am wondering if it was do to the dynamix update for 6.1.9 that I had applied before re-upgrading.  Any ideas?

 

Screen shot https://www.dropbox.com/s/wa2findx9v3om40/Screen%20Shot%202016-04-05%20at%208.08.51%20PM.png?dl=0

Possibly.  Delete /boot/config/dynamix.plg

Link to comment

I had reverted back to 6.1.9 because of issues with my Realtek ethernet card.    I decided to install a different eth card to get around the issue, but when I re-updated to 6.2 B20, the Array Operations screen  no longer has the section for doing a parity check.  I am wondering if it was do to the dynamix update for 6.1.9 that I had applied before re-upgrading.  Any ideas?

 

Screen shot https://www.dropbox.com/s/wa2findx9v3om40/Screen%20Shot%202016-04-05%20at%208.08.51%20PM.png?dl=0

Possibly.  Delete /boot/config/dynamix.plg

Good Call, that fixed it.. Thanks..

Link to comment
Guest
This topic is now closed to further replies.