I just came home after a parity check to find 436 sync errors and part of my web gui broken

 

The main dashboard page will not load

The plugins page is missing a plugin

 

The dockers page is throwing these errors

Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 48		
Fatal error: Uncaught exception 'UnexpectedValueException' with message 'RecursiveDirectoryIterator::__construct(/boot/config/plugins/dockerMan/templates-user): failed to open dir: No such file or directory' in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:78
Stack trace:
#0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(78): RecursiveDirectoryIterator->__construct('/boot/config/pl...', 4096)
#1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(107): DockerTemplates->listDir('/boot/config/pl...', 'xml')
#2 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(207): DockerTemplates->getTemplates('all')
#3 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(324): DockerTemplates->getTemplateValue('emby/embyserver...', 'Registry')
#4 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(292) : eval()'d code(69): DockerTemplates->getAllInfo()
#5 /usr/local/emhttp/plugins/dynamix/include/DefaultPag in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 78

 

The VM tab is showing this error

Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/classes/libvirt_helpers.php on line 375

 

My syslog is spewed full of errors. The flash share is empty if i access it, and every share is publicly visible and accessible on my network even if they are set to hidden

 

Bit of a worry considering i have private data on these drives. I've got to do a reboot as this is too much of a risk to leave as is

archangel-diagnostics-20160401-1813.zip

 

Bit of a worry considering i have private data on these drives. I've got to do a reboot as this is too much of a risk to leave as is

 

Sorry to be harsh, but:

 

1. beta software

2. backups

 

I just came home after a parity check to find 436 sync errors and part of my web gui broken

 

The main dashboard page will not load

The plugins page is missing a plugin

 

The dockers page is throwing these errors

Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 48		
Fatal error: Uncaught exception 'UnexpectedValueException' with message 'RecursiveDirectoryIterator::__construct(/boot/config/plugins/dockerMan/templates-user): failed to open dir: No such file or directory' in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:78
Stack trace:
#0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(78): RecursiveDirectoryIterator->__construct('/boot/config/pl...', 4096)
#1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(107): DockerTemplates->listDir('/boot/config/pl...', 'xml')
#2 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(207): DockerTemplates->getTemplates('all')
#3 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(324): DockerTemplates->getTemplateValue('emby/embyserver...', 'Registry')
#4 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(292) : eval()'d code(69): DockerTemplates->getAllInfo()
#5 /usr/local/emhttp/plugins/dynamix/include/DefaultPag in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 78

 

The VM tab is showing this error

Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/classes/libvirt_helpers.php on line 375

 

My syslog is spewed full of errors. The flash share is empty if i access it, and every share is publicly visible and accessible on my network even if they are set to hidden

 

Bit of a worry considering i have private data on these drives. I've got to do a reboot as this is too much of a risk to leave as is

 

This sounds like your flash drive became unreadable. I would take it out and perform a disk check on it from a Windows machine.

 

Sorry to be harsh, but:

 

1. beta software

2. backups

I'm aware of this, all data is backed up, i was just stating that it is a bit of a flaw that if the usb is no longer readable all data on the server can be accessed publicly by anyone on the network. This would most likely be an issue on every version of unraid

No idea if there is a way around this but it was worth pointing out. I was not worried about data loss, i was more worried about the security issue this opens

 

This sounds like your flash drive became unreadable. I would take it out and perform a disk check on it from a Windows machine.

I've done that and it passed everything. Very weird issue but its the first time ive ever seen it so i'm not too worried about this happening again.

Just posting as much information as i can to see if there are any premature warnings for stuff like this or a resolution of the security issue it causes

This sounds like your flash drive became unreadable. I would take it out and perform a disk check on it from a Windows machine.

I've done that and it passed everything. Very weird issue but its the first time ive ever seen it so i'm not too worried about this happening again.

Just posting as much information as i can to see if there are any premature warnings for stuff like this or a resolution of the security issue it causes

 

Have you tried to use another USB port for your flash device?

This sounds like your flash drive became unreadable. I would take it out and perform a disk check on it from a Windows machine.

I've done that and it passed everything. Very weird issue but its the first time ive ever seen it so i'm not too worried about this happening again.

Just posting as much information as i can to see if there are any premature warnings for stuff like this or a resolution of the security issue it causes

 

Have you tried to use another USB port for your flash device?

Yep. The usb booted up straight away after a reboot so the USB is fine. My system is a  bit of an odd one where if i do a bios update it wont see my usb or any other boot usbs for ages then will randomly pick it up and work fine so it may be down to that but i'm not sure.

I just wanted to check nobody could see any issues in the syslog that i couldn't

This sounds like your flash drive became unreadable. I would take it out and perform a disk check on it from a Windows machine.

I've done that and it passed everything. Very weird issue but its the first time ive ever seen it so i'm not too worried about this happening again.

Just posting as much information as i can to see if there are any premature warnings for stuff like this or a resolution of the security issue it causes

 

Have you tried to use another USB port for your flash device?

Yep. The usb booted up straight away after a reboot so the USB is fine. My system is a  bit of an odd one where if i do a bios update it wont see my usb or any other boot usbs for ages then will randomly pick it up and work fine so it may be down to that but i'm not sure.

I just wanted to check nobody could see any issues in the syslog that i couldn't

 

Could that not manifest itself whilst the system is running bigjme and explain (some of) your longstanding issues mate?!

This sounds like your flash drive became unreadable. I would take it out and perform a disk check on it from a Windows machine.

I've done that and it passed everything. Very weird issue but its the first time ive ever seen it so i'm not too worried about this happening again.

Just posting as much information as i can to see if there are any premature warnings for stuff like this or a resolution of the security issue it causes

 

Have you tried to use another USB port for your flash device?

Yep. The usb booted up straight away after a reboot so the USB is fine. My system is a  bit of an odd one where if i do a bios update it wont see my usb or any other boot usbs for ages then will randomly pick it up and work fine so it may be down to that but i'm not sure.

I just wanted to check nobody could see any issues in the syslog that i couldn't

 

Your earlier error messages point to problems in reading the flash drive (/boot).

 

Could that not manifest itself whilst the system is running bigjme and explain (some of) your longstanding issues mate?!

 

Hey CHBMB

 

This was actually the main thing I thought was at fault with my system for a while.

 

I have mentioned this a number of times when talking to limetech that I think my usb was having issues but was always told it shouldn't cause it any issues as the system runs from memory once booted. Everything was still functioning like vms etc. I was just not able to use the Web gui properly and obviously the share privileges changed

 

My system crashing issue seems to have been resolved by killing all irqbalances before starting the array. Ive been running my system since jonp asked me to run the function without an actual system crash

 

I have been hitting it a lot harder then normal to be honest and it seems to be coping. I have even added my 750ti back into the system to see if i can force a system lockup with the seabios vm running (this vm always used to cause it without fault) but no luck yet

Thanks for the reply.  I am downgrading back to 6.1.9 until I have more time to play with the beta. The link you sent looked to be the issue I was bumping into.

Starting VMs independent of the array is a feature that has been requested allot and one I'd love to facilitate running pfsense. Did this "feature" make it into 6.2?

This is not going to happen anytime soon, if ever.  It interferes with features we have planned for the future.  "Array Start/Stop" is really a misnomer.  In this context "array" refers to the entire set of devices attached to the server, not just the ones that are assigned to the parity-protected devices.

So do you have a solution in mind for those who wish to host a pfsense or other end point firewall appliance as a VM on unraid?

 

What is the issue exactly?

Well for me if I want to upgrade disks in the array from reiserfs and still run the VM (Windows in this case) I have to continually start and stop the VM as I start and stop the array to change the file system type.  Since my Windows VM is recording from TV tuners I have to wait for windows in the recording schedule before I can do that so it took a month and a half to convert to xfs.  My Windows VM has its own passed through controller for recording drives but the boot drive has to be an image (as far as I know) so I have to start and stop the VM with the array.  I can see other things like this in the future where it would be nicer to have an external drive for the VM that doesn't cause problems like putting the array in to maintenance mode to trouble shoot drive problems - do disk checks without having to shut down the VM.

 

That's exactly why you would use something like ESXi/Proxmox/KVM/etc on a different machine or virtualize unRaid and keep unRaid's container use to Dockers and not VMs. IMO, unRaid should be limited to media (tv, movies, etc) and backups. Anything else like PVR, Security Cameras, Routers, that need to have solid uptime should be on a solid platform. unRaid is a NAS that has recently grown into a services device. Until they provide the means for better uptime (not of just the OS, but also the array), unRaid does not fit that bill.  This is no different than someone trying to install DD-WRT on their Linksys WRT54g and asking it to do packet analysis, ntop, QoS all while on a 100mbps+ download stream; that hardware just isn't meant for all that. Use unRaid for what it is meant for and stop jamming everything into an all-on-one machine. It's all-in-one for media and backups, not critical services.

 

edit: furthermore, unRaid does not support VLAN tagging OR officially support multiple nics outside of bonding. Until it does that, it is NOT a candidate for something like a router that requires at least 2 nics.

 

edit2: It's late and I didn't think of pci passthrough for a dual port nic, but even still, unRaid is not the type of hypervisor that other virtualization platforms are. I love unRaid, I have a ton of docker containers for a bunch of things, but a router VM would never be considered.

Since trying 6.2 beta18, on each beta I have noticed a few strange folders being at the / directory upon startup. 

 

Folders being created are:

/Media

/Server/Logs

/Shows

/Support/Plex

/mnt/user/TV

 

I have tracked down the creation of these folders to the rc.docker script in /etc/rc.d/.  It seems the for loop in the function do_container_paths() does not like the spaces I have setup in my various docker paths.  The function is thinking these folders are missing & is causing these extra folders to be created.

"/mnt/user/appdata/Plex/config/Library/Application Support/Plex Media Server/Logs/" & "/mnt/user/TV Shows/" are the paths causing issues.  I am able to recreate the issue by deleting these folders and issuing the commands "/etc/rc.d/rc.docker stop" followed by "/etc/rc.d/rc.docker start".  Once command has completed, the folders will reappear.  The dockers that contain these paths are set to autostart.

 

I can adjust the paths of my dockers to avoid using spaces in the host directory paths to avoid this issue, but this seems like it would be a fairly trivial fix provided you have a decent understanding of linux scripting. However, I do not. 

Since trying 6.2 beta18, on each beta I have noticed a few strange folders being at the / directory upon startup. 

 

Folders being created are:

/Media

/Server/Logs

/Shows

/Support/Plex

/mnt/user/TV

 

I have tracked down the creation of these folders to the rc.docker script in /etc/rc.d/.  It seems the for loop in the function do_container_paths() does not like the spaces I have setup in my various docker paths.  The function is thinking these folders are missing & is causing these extra folders to be created.

"/mnt/user/appdata/Plex/config/Library/Application Support/Plex Media Server/Logs/" & "/mnt/user/TV Shows/" are the paths causing issues.  I am able to recreate the issue by deleting these folders and issuing the commands "/etc/rc.d/rc.docker stop" followed by "/etc/rc.d/rc.docker start".  Once command has completed, the folders will reappear.  The dockers that contain these paths are set to autostart.

 

I can adjust the paths of my dockers to avoid using spaces in the host directory paths to avoid this issue, but this seems like it would be a fairly trivial fix provided you have a decent understanding of linux scripting. However, I do not. 

 

Also seeing this exact behaviour, the problem is the for loop in the do_container_paths function is seeing spaces as the next variable to loop, I dont understand the scripts well enough to try fix it (Ive tried messing with IFS but had no luck)

Also seeing this exact behaviour, the problem is the for loop in the do_container_paths function is seeing spaces as the next variable to loop, I dont understand the scripts well enough to try fix it (Ive tried messing with IFS but had no luck)

 

Sounds like they need to switch from a for loop to a while read loop. I'm only running 6.1.8 right now and don't have a function by that name in my /etc/rc.d/rc.docker to compare it to.

 

Best practice, in any case, would be to use underscores instead of spaces in your folder names. I am guilty of using spaces myself though, especially in file names, simply because I don't like how the underscores look.

Since trying 6.2 beta18, on each beta I have noticed a few strange folders being at the / directory upon startup. 

 

Folders being created are:

/Media

/Server/Logs

/Shows

/Support/Plex

/mnt/user/TV

 

I have tracked down the creation of these folders to the rc.docker script in /etc/rc.d/.  It seems the for loop in the function do_container_paths() does not like the spaces I have setup in my various docker paths.  The function is thinking these folders are missing & is causing these extra folders to be created.

"/mnt/user/appdata/Plex/config/Library/Application Support/Plex Media Server/Logs/" & "/mnt/user/TV Shows/" are the paths causing issues.  I am able to recreate the issue by deleting these folders and issuing the commands "/etc/rc.d/rc.docker stop" followed by "/etc/rc.d/rc.docker start".  Once command has completed, the folders will reappear.  The dockers that contain these paths are set to autostart.

 

I can adjust the paths of my dockers to avoid using spaces in the host directory paths to avoid this issue, but this seems like it would be a fairly trivial fix provided you have a decent understanding of linux scripting. However, I do not. 

 

Very nice report man, thank you.  We have fixed this and are running some final tests.

As one of the people waiting (with a spare parity 2 drive ready to go) for the stable release version, i just wanted to thank everyone for their hard work and time at finding and fixing the bugs in the beta version.

 

I appreciate it.

@limetech @jnop please in kernel config enable finly megaraid sas drivers

i must any release compile myself kernel ... im using mazzeine card from Intel which using megaraid sas chipset.

 

issue in 6.2 all beta:

- for me when im try edit some VM from web, for me never save disk settings, everytime when i enter to edit i must setup again

 

- nice will be add possibility edit from web network device type (virtio, e1000 etc.)  still we must this do it manual, and after any change over web -  we must change manual again in XML becuase settings are overwriten

 

- nice will be add possibility map ROM to GPU - still we must this do it manual, and after any edit over web - we must map again manual in XML becuase settings are overwriten

 

Can you test the attached diagnostics script? It includes now the SMART configuration parameters. Thanks.

 

Thank you boniel - tried your script!

 

But still no valid SMART reports. Only the flash usb-drive is called (so a txt file only exists for the flash drive), but it gives the following output:

 

I understand you went back to version 6.1.9. Can you run the revised diagnostics script under this version?

 

Just wondering but does anyone know why the attached section of my syslog would have been generated?

 

I have not seen the system past 87% memory usage, or past 70% cpu usage (i was on a game in a vm with only half my system cores allocated when this was added to the log)

log_entry.zip

Hello, on many VM *BSD, i have keyboard work but no mouse on PC-BSD or FreeBSD is it a problem with beta version or with older version ?

If you know a solution ? for now the only things who work is passthrough mouse on VM

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!!

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?

Thank you Trurl... Had some rogue file in Transmission...  Really useful plugin though so staying installed (adding to the "must have" list!)

- 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)

 

 

- 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)