Got a 3tb hard drive and upgraded to 5.0 rc10 this weekend.  Everything seems to be ok except that every time I try to power down the array, as soon it goes off, it restarts.... Why?

Help please!!

Thanks 

  Was the new drive ADDED to the array or did it replace an existing drive?  Also do you try to do the power down while all drives are not-spinning, or are they already up and spinning at the time of the power down request?  Is it a CLEAN power down of the array, or a very quick power down reboot?  Read below for ideas and suggestions, (or you could skip to the last paragraph for a quick likely possible solution...)

 

  My thoughts... running many tests on purposely UN-RECOMMENDED potentially unstable hardware configurations while testing for fault failure modes and data integrity on unRAID seems to have consistently yielded symptoms like yours ONLY with under-powered power supplies, or with too many drives on a single power rail of a larger power supply, WHEN trying to power down an array without discs already spinning. (tests down with 4.5.x versions)

 

  In the 4.6.x tests, when performing a power down request, (from the console, via the power button, or through the web interface,) when the drive are NOT spinning, ALL DRIVES ARE IMMEDIATELY spun up, which in an under-powered power supply configuration, which can include large multi-rail power supplies, it is common for a computer re-boot instead of powering down.  Under this set of conditions the array has not however performed a clean shut-down, and and initiates a parity check on power up.  (much like a loss of power from a power outage would cause)

 

  Less consistently, a marginally sized, or poorly regulated power supply seems to frequently, but not always, allow a normal power-down, then re-boot.  Under some hardware configurations,  this subsequent system re-boot is normally then due to the voltage fluctuations from the power supply resetting the power-on circuit on the mother board, or the power supply itself seeing the voltage fluctuation as a power switch activation.

 

  Another situation which yields a re-boot after a clean power down is  a marginal power supply condition again, coupled with a BIOS settings being set to either power options being set to SET TO LAST STATE or POWER COMPUTER ON settings in the settings related to restoration of power after power loss.  I suggest it is best to make sure the BIOS settings should ONLY be set to KEEP COMPUTER OFF after power is restored.  (of course wording will vary from BIOS versions and vendors)

 

  Short answer - May be something else, such as sticky power switch, or other unstable hardware, but most likely it is a power supply issue.  I would suggest a test with a larger SINGLE RAIL power supply from a reputable vendor.

 

 

Just to clarify, no modification was made to the array.  I was on 4.2 and went to 4.7.  On 4.7 Everything was fine and I added the 3tb hard drive on a free sata space to preclear it.  After that, the 3tb hard drive was removed and the array was still in its original configuration.  Did the rc10 install folowing this guide "http://lime-technology.com/wiki/index.php/UnRAID_Server_Version_5.0-beta_Release_Notes"  try to do a clean power down to hook up my 3tb drive, but now, the array restart as soon as it stop. 

  Now, probably did a mistake but... will see...  I did the same thing as in the guide but in reverse to but back the 4.7 file.  Now the power down work but all my hard drive are in red saying that they are missing...

anyway, enough for now, will try to put some time in it tommorow!!

 

I'm lost, any idea???  did some test and on 4.7 everything is fine and on rc10 or rc11 the system reboot by itself!!!

I have a ga-ma74gm-s2 motherboard with only 4 hard drive on it.  Bios setting are ok, power supply is fine (750W corsair)

any idea??

Can you provide a 4.7 syslog and an rc11 syslog?  Also a pre-upgrade 4.7 syslog if available, for comparison.  Zip them up and attach.

here is the rc11 syslog.  Don't seems to be able to go back to 4.7 now, got boot error screen.  did copy the make bootable file from 4.7 but don't seems to work.

5rc11syslog.zip

  Here is a possible answer that MAY help.  I have been stumped with the problem being only present with the new 5.0-rc upgrade on your computer, so I did some research on Slackware kernels.  It seems that there have been some changes periodically that have caused various power-down problems with some hardware.  USUALLY it seems that making sure the APM (Advanced Power Management) is disabled in BIOS will allow the proper shut-down when the kernal-hardware problems are exhibited.  Less frequently, enabling APM in BIOS and trying various options seems to yeild the desired power down results.

 

  This is the only other thing I can think of currently...  hope it helps.

 

 

I didn't have time to check your syslog when you posted it, then forgot about it, so it's good someone else 'bumped' this thread.  But I'm not quite sure where we are here, what works and what does not work.  Your syslog is essentially only a minute long, finished right after the array fully mounts but before the networking is setup, so I can't tell much from that.  Nothing appears to be wrong, in this short syslog.  When you next boot, I do recommend going into your BIOS settings and changing the SATA mode to a native SATA choice, preferably AHCI, anything but the IDE emulation mode it is in now.  Apart from that, it looks like it works, under RC11.

 

When you went back to 4.7, did you copy anything else but bzroot and bzimage?  The files ldlinux.sys, menu.c32, and syslinux.exe all need to be from the same distro, the same version.  Did you run make_bootable.bat recently?  A mixup of these files would mess up the booting.

 

To clarify what is happening at these unwanted restarts, do you mean the computer is suddenly rebooting during normal operation, or are you shutting down and just when the machine should be turning itself off, it boots afresh?