Fireball3

Members
  • Posts

    1355
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Fireball3

  1. I have just been looking for a solution to the same problem. Found this thread where weebotech points to a script in his google code. I can't test it, as I don't have my backup server ready yet.
  2. Oh man, this is horror scenario imho. Even a backup (server) won't save you in this case because the corruption will propagate when syncing... I really wonder if the files were OK from the beginning? Cache drive is irrelevant to this issue.
  3. Bump! Help...anybody... How can I execute smarthistory from commandline?
  4. This looks like a (hardware) raid controller. See if you can set it to JBOD or passthrough mode and try again. According to the hardware list it has not been tested with unRAID until now. You're the first to do this. It may work or (probably) not...(no drivers for unRAID) For the use with unRAID you need an HBA only.
  5. I have almost everything together to build my backup server. I'm planning to preclear some drives but I can start by next week only. I will have 3x 4TB drives (to be harvested) - will post the specs if I have them ready. Also 2x 500GB (identical) but I expect one to have issues. 1x 3TB drive + 1x 2TB drive I intend to run 3 cycles - so I could run it with 5.x and 6.x Prepare the test plan and provide the script and I will let it run for you. Would you mind sharing the differences (in layman terms) between Joe's script and your's?
  6. And here is the issue. UNRAID AUTOMATICALLY STARTS A CORRECTING PARITY CHECK AFTER A CRASH. It doesn't give you the option to evaluate the situation before it starts writing data to the parity disk. I agree! If unRAID detects an error, it should not start the array and it should not automatically conduct a parity check!
  7. Nice monster boxes... But, I wonder how they manage to run 48 drives with that PSU? Staggered spin-up? Must be a hardware set-up to do that when booting cold? At the moment my PSU is totally oversized only to meet the amps requirement when all drives spin-up at once. When idling with all drives up it will probably not even reach 20% load... There is much room for improvement in this specific area.
  8. Classic event of "GUI goes unresponsive"... once more. In that case it's good to have the clean powerdown script installed (see my sig). If not, well - 2 options: 1. search the forum for instructions how to stop the array and unmount the drives (preferred option) 2. hit the reset button (will cause a parity check after unclean shutdown) Take the opportunity to install the powerdown script.
  9. Puh, that's really hardcore... I have to google everything and puzzle something together. http://wiki.bash-hackers.org/scripting/debuggingtips ...munching...
  10. You mentioned that already. Obviously I didn't fully understand it. ...going back and looking up "export"...OK Globally set DEBUG=1 I suppose this debug is different to the script $debug that is used for logging options. The difference is only the way the script is called, isn't it? sh -x -v auto_s3_sleep.sh vs. DEBUG=1 ./auto_s3_sleep.sh Where is the benefit?
  11. OK, I think I can test the modifications now. What is the best way to go for testing. I read something about the debug function. bash -x auto_s3_sleep.sh I have to test that. I would probably need to cycle through each variable...
  12. Thanks for taking your time to write those examples. Finally found some time to work through them. 1. Can we say that there is no possibility to call a function inside an IF without forking? The function has to run prior to the IF and the IF itself is only comparing return values or variables. This is probably the same for while-loops? What would be a workaround to avoid this fork? while [[ $(hour_match) -eq 1 ]] # do Probably starting with "while [1 ]" and calling the hour_match after the first loop-run? 2. check_LockFile hour_match if [[ $? -eq 0 && $LockFile -eq 0 ]] When doing it like this: "$? -eq 0" is working only if the function was called in the prior line? So comparing multiple return codes won't be possible? The second value has to be a variable? 3. Edit: I noticed you use the variables like: if [[ ${HOUR_MATCHED_RC} -eq 0 && $lockfile -eq 0 ]] while in the whole script the variables are within quotes. if [[ "$hourMatch" -eq 0 && "$LockFile" -eq 0 ]] Quotes = string, no quotes = integer? If this is true, then I will have to stick either to the string-writing or to the integer-writing. Then I would have to do: if [[ "$?" -eq 0 && "$LockFile" -eq 0 ]] or if [[ $? -eq 0 && $LockFile -eq 0 ]] Right? 4. Conclusion: While working with return codes seems pretty slight/slender it is not very transparent to the noob user. Working with variables seems better especially if someone else is supposed to decipher it.
  13. Great bonienl! This is working!!! thx
  14. Just tried: FOR /F "delims=^*" %%i IN (%tmpfile%) DO CALL :BODY %%i and FOR /F "tokens=* delims=^*" %%i IN (%tmpfile%) DO CALL :BODY %%i No joy.
  15. Not necessarily. Fast is probably the wrong term - let's say a drive with good throughput. I have an old server grade 160 GB drive that writes @100MB/s. That is enough to max out the GB LAN.
  16. FOR /F "tokens=* delims=;" %%i IN (%tmpfile%) DO CALL :BODY %%i Does not work. Cuts off after blank.
  17. Need help with this for loop - once more... This time it's a batch file in DOS console. I want to process a file line by line but it will always cut/break after a blank in the line. Lines without blanks work perfectly. My code at the moment: FOR /F "delims=*" %%i IN (%tmpfile%) DO CALL :BODY %%i I can't remember the countless possibilities of delims & tokens that I googled & tested. I don't believe it's that complicated but obviously I can't handle it. Appreciate your help!
  18. It often happens that the GUI is going unresponsive. Then you either have to console-fu your way through and unmount the drives or reboot the hard way. The latter will automatically cause a parity check after unclean shutdown - you don't want that. Follow the powerdown link in my sig and install the powerdown script. Make sure it works for you and you're safe next time when you press the power switch or call powerdown on the console. My start-up time is <60s with 11 drives. My transfer speeds via GB-LAN to the protected array varies between 20-45 MB/s. (depends on file size) Use a fast cache drive and you will max out the GB LAN. Then run the mover script when the server is idle. A syslog is always useful so that knowledgable people here can check if there is a basic problem during startup. Follow the "useful sig" link in my sig to learn how to extract the syslog.
  19. Look for settings like "passthrough, or disable RAID" if available.
  20. Well, if you have it for free, then why don't you test it?
  21. That card would be a waste for the use with unRAID since it's a real hardware RAID card (ROC). Despite that, I can't say though if it will work with unRAID - tend to say it won't. You need a simple HBA (host bus adapter) that passes the drives through to the OS. LSI is pricey! Check the reference builds from IBM or SuperMicro. Dell might also work but it seems that not every Dell card can be crossflashed.
  22. It doesn't matter as long as the PSU has a single rail. I'm using an HX650 and have 11 drives connected to one PSU-plug. To connect the next 10 drives I might use a second one though. For these special cases, it would be useful to have a setting - be it in a config file or be it a safe/alt mode of unRAID - so that one can boot without automatically starting the array. Edit: A timer would also be a solution to give some time to cancel the automatic parity check. Can we suggest that to Tom?
  23. Sounds reasonable but I doubt that those Add-On GUIs are tested in such situations. You can really mess things up then. e.g. make a new configuration and assign a data disk to parity because it is not or wrongly displayed ... bye bye data