JoreLack

Same problem. Works fine when i use Win7 template to install Win10, but when using Win10 template this happens. I want to use Win10 template cos it allows USB3 from the menu.

Okay maybe I am missing on something, but where do i get the actual plugin? I have lmsensors up and running.

Thanks, will try that!

Please include some kind of file browser to the GUI X11 enviroment, like Thunar (really lightweight). That would be really handy when sorting out files to different drives. MC does the trick, but it is not efficient in handling multiple drives at the same time, as for GUI file browser shines in that (for example having eight file browser opened simultaneously for different locations/disks). Hope this get included soon!

This might have been covered already... What is the best way to connect to UnRaid GUI (X11) remotely? Is VNC supported out-of-the-box? Any plans to add XRDP to UnRaid?

Thanks, that did the trick!

Thanks dmacias for the info! That sound pretty good, not perfect but good'ish enough i guess. Anyone have any experience using external (USB) fan controllers with Unraid? For example Aquacomputer Aquaero 5 LT USB could be pretty nice (http://www.frozencpu.com/products/13696/bus-271/Aquacomputer_Aquaero_5_LT_USB_Fan_Controller_Liquid_System_Controller_53095.html). Seems to have some kind of Linux support (https://github.com/lynix/aerotools-ng/tree/devel). Something like this could be used to make your fan control real smart, ie. only spin those hdd caddies fans that are in use etc.

What is the best way to display temperature data on the webgui. Or are there any plans to integrate this feature on to the Unraid6? This would be cool thing to have on the dashboard view. My server has sensor package configured and sensor command works properly: root@tank:~# sensors acpitz-virtual-0 Adapter: Virtual device temp1: +45.0 C (crit = +127.0 C) temp2: +27.8 C (crit = +106.0 C) temp3: +29.8 C (crit = +106.0 C)

How are the fan settings on the bios on this board? Can you set the fans to spin really slow when internal temp is low, and make them spin faster as the temps rises? I know this is not the same as controlling the fans based on actual hdd temps, but could be close enough. Someone was talking about external fan controller, could that be used to manage the fans with software, as in stop the fans when hdd's are not spinning. My ideal setup would be that when only one or more of the lower four hdd's are spinning, only the lower front fan would spin up. And the same thing on the upper four hdd's. And it would be really great to get the fans spin according to actual hdd temps.

Thank you for the tips. Was able to cleanly reboot the server from command line using jonathanm's link. Cache was a PIA to unmount, had to stop docker containers and force umount with -l. After reboot checked the cache driver manually with btrfschk just to be sure. Now running normally again and parity check was not needed.

Hi, Running 6B14. Tried to generate a windows KVM machine and the webgui stopped responding and emhttp process has died. If i try to restart it, this happens: root@tank:/etc/rc.d# /usr/local/sbin/emhttp Segmentation fault And syslog shows this: Apr 9 21:03:28 tank kernel: emhttp[27632]: segfault at 0 ip 00002b8ebad72d16 sp 00007fffe3d89408 error 4 in libc-2.17.so[2b8ebac3c000+1bf000] Any idea can this be fixed without reboot? If reboot is necessary, i would really like to know how to restart cleanly from the console? Dirty restart is not an option because parity check for 22TB takes forever Hopefully someone has some ideas how to solve this!

Not sure if this is related, but i have my docker image on ssd cache, but the content still gets copied to main array (disk1). How do i make certain folders only stay in cache drive?

There were some issues with the Marvel sata-controller. Would be interesting to hear from some of the users about the current state of this issue. Also read that SST-CP11B are the sata-cables to go with... Thinking about getting this board to go with latest Unraid 6 beta.

Stock fans have 3-pin connectors. Hdd cage has two connectors for the front case fans, but those seems to provide constant 12v to the fans, so they run at full full speed. With all three fans running full speed you can definitely hear them, but but they are not especially loud. I am using pci bracket fan controller to control all three fans and with around 75% speed they are almost silent and still provide more than enough airflow to keep hdd's cool (six in my case). E: I have covered the inner side of the case completely with Akasa sound absorbing mat, including the inside of the front door, so that will most likely lower the noise coming from the case.

Thank you for the update! Is there a list of plugins that can be used with unraid 6 beta? I tried the install extension gui to install unmenu but that just returned a bunch of errors. Are you supposed to put a url of the plugin zip-file to the install field (i.e. https://unraid-unmenu.googlecode.com/files/unmenu_install1371.zip)?

Slightly off topic but i have one of those "fake" $100 LSI SAS 9211-8i, does not seem fake to me as it's working great and i have 150mbytes parity check speeds with the controller flashed to latest IT firmware (initiator target, all the raid functions disabled)

I have the case up and running. Amazing case, running 4x4tb and 2x2tb and the temperatures stay low and the case is really silent (i am controlling the case fan speeds manually). I also applied akasa sound absorbing mat inside the case. Hdd cages also works like they should, easy to use and solid construction. What i really like is the positive air pressure inside the case. With all the incoming air coming throught dust filter, there is no dust buildup inside the case...

Thank you very much Trurl and Garycase! I deleted the old config, rebuild it and now the parity-sync is running around ~150mb/sec so everything seems to be allright. So i guess it is a bad idea to write to reiserfs partitions outside the unraid machine? I had around 4TB of data that needed to be transferred to unraid box, and i read somewhere (a thread in this forum if i am not mistaken) that you can just mount the unraid hdd's in another box and transfer the files. Would have done it the other way around (old hdd's to new unraid box) , but the old drivers were formatted in xfs and that is not supported in unraid...

Installed my two unraid reiserfs datadrives to old Linux box and copied all the stuff to the new drivers. After puting the drives back to unraid box and started parity check in, estimated speed is under 500kb/s and estimated finish is changing between 100-300 days! Sync errors corrected is growing, now it sits around 600000. When i was setting up the system the speed of the parity check was good, around 150mb/s according to web ui. Unraid is running on a h55 mb + core i3, 4 gigs of memory and 4tb and 2tb drives connected to LSI SAS 9211-8i SAS-controller (initiator target mode). Unraid v6 b3. Is this normal (propably not??), and is there any way to speed things up? Mar 24 11:45:16 Tower kernel: mdcmd (35): check CORRECT Mar 24 11:45:16 Tower kernel: md: recovery thread woken up ... Mar 24 11:45:16 Tower kernel: md: recovery thread checking parity... Mar 24 11:45:16 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks. Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22072 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22080 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22088 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22096 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22104 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22112 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22120 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22128 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22136 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22144 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22152 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22160 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22168 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22176 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22184 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22192 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22200 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22208 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22216 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22224 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22232 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22240 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22248 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22256 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22264 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22272 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22280 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22288 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22296 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22304 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22312 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22320 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22328 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22336 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22344 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22352 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22360 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22368 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22376 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22384 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22392 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22400 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22408 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22416 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22424 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22432 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22440 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22448 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22456 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22464 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22472 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22480 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22488 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22496 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22504 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22512 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22520 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22528 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22536 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22544 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22552 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22560 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22568 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22576 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22584 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22592 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22600 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22608 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22616 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22624 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22632 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22640 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22648 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22656 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22664 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22672 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22680 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22688 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22696 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22704 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22712 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22720 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22728 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22736 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22744 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22752 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22760 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22768 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22776 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22784 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22792 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22800 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22808 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22816 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22824 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22832 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22840 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22848 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22856 Mar 24 11:45:17 Tower kernel: md: correcting parity, sector=22864 Mar 24 11:45:17 Tower kernel: md: correcting parity, stopped logging

According to the manufacturer's website this is a dual-rail power supply, meaning some of those 300W will not be available to hard drives. Single-rail PSUs are recommended for unRAID. Silverstone has a couple of SFX units that many of us are using. Thanks for the info, i'll have to see how the be quiet! one works out. This is going to be a low power system so i think it should be ok. With out the hdd's power consumption should be around 15-20w and under load no more than ~50w. Hdd's take ~5w each, so total consumption is still pretty low.

I'm building ESXi box based on DS380. Parts list: - Silverstone DS380 - be quiet! SFX POWER 2 300W - Jetway NF9G-QM77 - Core i7 3632qm laptop CPU - 16GB SO-DIMM DDR3 - LSI SAS 9211-8i 8-Port 6Gb/s SAS/SATA PCI-e SAS controller (VT-D passthrough to ESXi) - 4 x Seagate Barracuda XT ST4000DM000 4TB (more to come...) - 2 x SSD for datastore etc Going to be used for Pfsense, Unraid, Security Onion (IDS) and various Linux based servers. Case should arrive in few days, got lucky with a local vendor that got a hold of one DS380...