I've been using unRAID since 3.6 and have built up 4 servers along the way - mostly using my old computers.  I built my first 6.6.7 server last month as a replacement for two 5.x servers full of 2TB drives and running on Celerons with 2GB RAM  (time to upgrade, huh?)  The new 6.6.7 server is mostly 10TB drives running on a motherboard with 4 SATA ports (requiring two SATA HBAs to feed the full array) and not much else, so I'm going to move it to some better (still older) hardware.  I'm using a trial license to test the new hardware and preclear a few disks.  I do NOT have an array defined - just using the apps and Tools.

 

Here's the problem (well, two, actually): When I log out of the GUI console, unRAID appears to lock up -- the MBs HDMI video signal shuts down (instead of going back to the login-window) and the server disappears from the network (ping fails though the blinking light on the net connector port still shows something is active.)  The disk activity light is still lit (likely from the preclear), but resuming preclear after a reboot indicates no further "clearing" activity was accomplished during the "lock up."   If I bring up the server with the non-GUI console, logging off does not cause the problem - only when exiting the GUI.  Reboot is the only way I've found to restore the connections.

 

Here's the specs on the hardware I'm testing with:

• unRAID system:     unRAID server Trial, version 6.6.7
• Model:                   Custom
• Motherboard:        ASUSTeK COMPUTER INC. - Z87-DELUXE
• Processor:            Intel® Core™ i7-4770K CPU @ 3.50GHz
• HVM:                    Disabled
• IOMMU:                 Disabled
• Memory:               16 GB (max. installable capacity 32 GB)
• Network:              bond0: fault-tolerance (active-backup), mtu 1500
•                            eth0: 1000Mb/s, full duplex, mtu 1500
•                            eth1: not connected
• Kernel:                 Linux 4.18.20-unRAID x86_64
• OpenSSL:             1.1.1a
• P + Q algorithm:    21085 MB/s + 32449 MB/s

 

Another slight problem which may be related: When I Power Down from the GUI console (using the GUI button), the unRAID server shuts down as expected, but the PC does not.  In the MB BIOS, there are power settings for what to do when power is "restored", but nothing about powering down. 

 

Does the lack of a defined array have anything to do with what I'm seeing?

 

While I'm not new to unRAID, I only ever used it store stuff and stream video, and have only recently begun using 6.6.7, so there may be some settings I'm missing - though, as I mentioned, my working 6.6.7 server doesn't have any of these problems.  I'd sure like to track this lock-up-on-logout problem on the newer hardware before I move my array to it.

 

Thanks for any insight (or solutions) you can provide.

 

Check that the BIOS is not set to something like 'Wake up on LAN'  

 

By the way, no modern Computer is truly shut completely down when you push the 'power button' on the front.  The button merely sends a signal to shutdown the current OS and to remove much of the power to the MB and HD's.  However, certain things are kept alive such as the LAN card and the circuitry which will restart the system when you push the power button again.  To completely remove the power from the MB, you have turn the switch off on the PS or pull the power cord from the wall. 

Thank you.  Yes, I have all my BIOS power up options disabled - only the power button will turn it on.

 

Also, I'm aware of the "not really turned off" power down, but in my situation, lights are still on, fans still spinning, water pump still pumping, but no video signal, no network connection - as if it's on its way down and is hanging on something - it's actually ending up in the same state it's in when I log off the GUI console (original problem.)

 

Some additional info re: "not powering down completely" from the GUI console - If I do it from the web interface, it powers down everything as expected - except, of course for the keep-warm circuits.  It's only when it's powered down from the GUI console that the machine stays powered up after unRAID closes down.

 

This MB's BIOS is UEFI, and I'm not familiar enough with it to know if I'm fighting against it or not.  Settings I'm used to finding are not there or not where I'd expect them to be.  The BIOS has worked perfectly, untouched, for the several years I used the machine as a Windows 7, 10 PC.

 

Maybe I'll just make it headless or stop using the GUI console.  Or maybe I'll keep trying to figure it out.  That sounds like a better path.  At least until the trial license expires. 

 

Thanks, again.

Edited May 2, 20197 yr by robertwallace