grizzly

Members
  • Posts

    14
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

grizzly's Achievements

Noob

Noob (1/14)

0

Reputation

  1. You can always plug the power lead to the computer into a regular socket the wall/extension lead and then yank the ups power cord to test. That is NOT plug the computer into the ups. If the shutdown works like it should the computer will turn of, but not start again when ups power is back tough. If the shutdown does not work like it should then the computer will stay on, leading to much easier troubleshooting and no need for parity checks if the shutdown does not work like it should. Also are you sure that the battery is ok? Had problem with my then 6-7 year eaton that said the battery status was fine and it worked fine on battery for 15min if shutdown was off and i manually shut it down fine and started fine again after power was back. But shutdown set to 3min like i usually have (to save battery life) it would shutdown but not cleanly and a parity check was waiting on startup. Did not mess with it for a couple of months since my outages is less then 1min 98% of the time. Then i wanted to get it ok again and checked, battery status was still fine. BUT it did not want to work for more then seconds and when started again it was at a very low battery and charged very quick. Ok battery is dead so bought a new ups (since i hated how it tested with a high squeal and fan noise so often) instead of a new battery. A day or two later i connected it to my windows pc and eatons program and even that said the battery was perfectly fine, but NO it was stone cold dead.
  2. I´m pretty sure i read something about to short % or time can cause problems. And also that it can work for a while but then when batteries wear down starts to cause problems. But i´m not 100% sure about this, i can have it mixed up with something else and it was a few years ago. And i think i did have some problem with using a high % on my last ups many years ago, that i solved by using time instead. Since then i have used shut down after 3min and it has worked fine chosed 3min because when power come back here it almost always shuts of again after 10-20sec and come back after 5sec 3-4 times before it stabilize. So try a lower % or try time instead and maybe not to low of a time. And remember when trying this do not have unraid power in the ups (only USB cable). Connect the power to a regular outlet so IF the ups cuts power to early you won´t get a unclean shutdown and a parity check. As long as you connect the USB cable unraid and ups will talk to each other normally and will initiate a shutdown when you yank the cable or use a on/off switch, so just look/listening for when unraid shut off and see if ups turn of before that or not.
  3. No need to at all! Just connect the Unraid power cord to the wall directly instead of the UPS. Then plug in the USB into the UPS and initiate a UPS shutdown for example by yanking the UPS power cord. Everything will behave as if the unraid computer is plugged into the UPS and unraid will still shutdown if all goes ok, besides that IF something goes wrong like UPS battery gets too low unraid still has power and will not shutoff from low battery.
  4. I do not use NUT anymore but i could swear that i got them in the log file when i did. So maybe a power failure test is in order to see if unraid do shutdown like it should?
  5. Before trying anything with a UPS do run unraids power (and/or any other computers) from the wall so when the ups shutdown there is still power to unraid/computers. Shutdown swap power lead/plugs start up test ups. You do avoid some problems this way IF there are a problem like an unclean shutdown and a parity check for hours. Ups functions will still work like normal for example the status and the shutdown (if noting locks the array) since all that is done trough USB/network depending on ups and chosen way.
  6. Do not have an answer for you, only two small tips too try. i would probably have tried running unraid as master and synology/pfsense as slaves and sees how that goes, then if not ok tried pfsense as master. Also when you are testing do NOT have the equipment that you are testing on (synology/unraid/pfsense) power cables in the UPS just plug them in a normal outlet, that way IF the battery runs out and the ups shutsdown the equipment still have power=no more unnecessary parity checks/powercuts. Learned that a few weeks ago while pretty much feeling like a moron that did not think about that my self, i mean after i learned it, it is so obvious!
  7. Ahh THAT help Found name/pass and entered the string and got ok so cut power and one short beep came out then no more. Let unraid and ups shutdown waited around 5min powered up and cut power after unraid was started and the same one beep and no more. Thanks for the help.
  8. Help in the top right corner i assume is the online manual that leads to networkupstools. If so where do you find the name/pass? have looked and searched but cant really find any info on that. The only thing i find is what upsd.users should look like and some example names/passwords that do not work. Also tried searching for upsd.users on unraid when ssh in to ithe box but did not find any upsd.users file. Do i have to create upsd.users file? And if so where should it be since placing it in the "normal" place (somewhere under etc i assume) would not bring it back after a reboot.
  9. Have not tried anything yet and is not at home right now but did the upscmd -l ups anyway. root@Tower:~# upscmd -l ups Instant commands supported on UPS [ups]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use beeper.disable or beeper.mute) beeper.on - Obsolete (use beeper.enable) load.off - Turn off the load immediately load.off.delay - Turn off the load with a delay (seconds) load.on - Turn on the load immediately load.on.delay - Turn on the load with a delay (seconds) shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off shutdown.stop - Stop a shutdown in progress
  10. Thanks! Going to try it in a day or two. Report back what happens.
  11. Turns out that i´m a moron or blind. Have no idè why i did not set the ups to turn off after shutdown. As in "Turn off UPS after shutdown: set to enabled" The shutdown and startup works like it should now. Now only the damn beeping issue is left now!
  12. I have a eaton ellipse pro 850 and nut installed and works but with a few issues. Right now i does shutdown as it should (the important part) at the time/battery level i set (and after a restart for that to take effect). The problem is that the unraid box does not start up again (and i waited for over an hour) if i press the start button on unraid it starts up or if i shutdown and start the ups (as in disable/enable power out from the ups) it also start. The unraid motherboard is set to always start when it gets power which works fine during power outages before i bought the ups. Also tried to disable the damn beeping (don´t need it as the ups fan is loud enough and then some to tell me that power is out). The eaton menu (ON the ups it self) does not work as it should for me you should hold scroll down for 5sec for menu to come up (it works but takes 10s) then hold for 2 sec to go to next menu and it is here it starts to not work. Going from input voltage to output works fine but then it goes back to input voltage again besides one time when i came to eco mode but from eco mode to alarm did not work that time as it went to input voltage again. All in all i cant disable the damn beeping using the ups itself so tried inserting some lines in the nut.cfg under boot/config/plugins/nut. Also tried adding some line for the delayed start and tried 0/1/10 but no change. But none of the two did not seem to work. The ups does work the same if the start delay and beeping line is not there and will change that back after this posting. And the time/battery level is set that high for now when testing but using the default level do not change anything on the startup issue. This will probably be set relatively high (to save the battery some and my sanity from the damn beeping) after my testing as i have no devices that needs or could connect to the unraid box during a power outage anyway. So anyone have any idè why the unraid box do not want to start after a power outage? And is it possible to turn of the alarm using nut? When i tried using a windows 8,1 pc and eatons prg the computer started fine after a outage and i could disable the alarm so to ups seems to work like it should (except for the damn menu). My nut status is battery.charge: 78 battery.charge.low: 20 battery.runtime: 1722 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 850 device.serial: G358F17013 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.3 driver.version.data: MGE HID 1.38 driver.version.internal: 0.39 input.frequency: 50.0 input.transfer.high: 285 input.transfer.low: 165 input.voltage: 229.0 input.voltage.extended: no outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 2 outlet.1.status: on outlet.1.switchable: no outlet.2.desc: PowerShare Outlet 2 outlet.2.id: 3 outlet.2.status: on outlet.2.switchable: no outlet.desc: Main Outlet outlet.id: 1 outlet.switchable: no output.frequency: 50.0 output.frequency.nominal: 50 output.voltage: 227.0 output.voltage.nominal: 230 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.firmware: 01.08.0016 ups.load: 14 ups.mfr: EATON ups.model: Ellipse PRO 850 ups.power: 81 ups.power.nominal: 850 ups.productid: ffff ups.realpower: 75 ups.serial: G358F17013 ups.status: OL ups.timer.shutdown: 0 ups.timer.start: 0 ups.vendorid: 0463 Input transfer is that high and low because i tried the high setting range last time and have not changed it back to low (low=default) yet (will do as soon as i post). cat /boot/config/plugins/nut/nut.cfg gives this. SERVICE="enable" DRIVER="usbhid-ups" SERIAL="" PORT="auto" MODE="standalone" SHUTDOWN="batt_level" BATTERYLEVEL="95" SECONDS="1800" TIMEOUT="1800" UPSKILL="disable" UPS.DELAY.START="10" UPS:BEEPER.STATUS="disabled" I should add that if i update the NUT Settings screen in the browser the stat does update fine and is the same that is seen on the ups screen.
  13. Thanks everybody! I had "Enable user shares" set too no since i do not use them and have no use of the mover for the cache disk i prefer doing it myself. So turned that on and the cache disk showed up . Then the problem i thought i was clever enough too remember too name all folders i have on the cache disk starting with - (for example -download) in the unlikely event that i wanted too use the mover someday. Since i was sooooooooo damn sure that was what i named them when i used unraid around 1-2years ago (been trying other stuff since and now i´m back) but as probably everyone else already knows it is a . that should be in front instead off a - So had too change that and then go in to a bunch off config files for plugins/xen wm´s (and change nfs mounts in all xen machines) and change all the damn - to . after that go too all computers/mediaplayers (have way too many) and change - too . Been doing all that almost since the first answer came in here and i´m finally done, everything even works Do you mean the "Use cache disk: No/Yes/Only" option in each User Shares set to No? If so i already did that.
  14. Under the main tab you can see all array disks plus the flash drive. But the cache drive does not show up sure you can go too dashboard and click on the smart icon for that drive then go to Disk attributes too view for example the drive temp. This is kind off annoying since the cache drive is the one drive i have spinning 24/7 one of the other drives (+parity once in a while) is maybe used 1-3 hours a day and 1-2 times a month more then one other drive is used. Therefore I really want too be able too see the quick status on the main tab (since i have that open all the time). Why is the cache drive so much less important? Sure it is not as important as the array drives but so nonimportant that you don´t want too see status come on? The flashdrive is much less important for me but that is there! In this tread http://lime-technology.com/forum/index.php?topic=38497.0 i did see that "other" drives is not part of the status/temp showing because license and i can understand that (but i think its crazy but can understand). BUT the cache drive IS part off the whole unraid license system and does NOT add any count towards the array drive limits so this argument is therefore not valid for the cache drive right?