axeman

Members
  • Posts

    538
  • Joined

  • Last visited

Everything posted by axeman

  1. just tried out 2.2.2 looks really good. love to see where the Dashboard will go. Still having the issue with freezing when installing certain plugins. so far, email notify, and the System stats plugins crash on install, whether i download it myself or use plugin control... a reboot doesn't help - web gui never loads, but i can get in via telnet though. btw - this is on a new flash drive. running 5.0.5; Could this be related to running in a VM ?
  2. could UnMenu and the mail script/plug-in being present (but unmenu not started) have anything to do with my installation issue? still cant' get the emailer script to install. I thought perhaps i was being impatient and need to give it a while to install; so I walked away for 30 minutes. it just hangs on the console, and webgui goes down. I am running it in a VM ... could that have anything to do with it?
  3. Are you referring to the warning about the certificates ? These can be ignored, and don't disturb the installation. If not what issues exactly? One advice though: get your system stable first, i.e. get file/disk corruption repaired first before installing plugins. thanks bonienl... the system is stable when i go safemode and/or uninstall the two questionable plugins (ironically the two very same ones that drove me to dynamix). it's weird, when it hits that certificate error, the installation seems to abort - and the console becomes unresponsive. I can open another telnet session and shutdown, etc, but webgui is down, and shares are down.
  4. So I have a couple of issues. Both the email plugin and the system stat plugins cause the same error on install and a reboot causes the lockup that I posted earlier. Regardless whether I install via command prompt or plugin manger The other issue is that disks that have data are constantly polling. The empty disks are spun down properly. Edit: the spindown seems to be ok now. I removed all the other plugins (only have the plugin manager)
  5. "newperms" is the command you want. thanks - that didn't seem to do anything - i tired at root and \boot .. it says successful, but nothing seems to happen. the good news is - that's not it either, because the safemode option boots right up, no issues. i'm going to try deleting the dynamix stuff and try again Sorry - /usr/local/sbin/newperms thanks- i think it's directly related to dynamix; since safemode worked, i removed it and rebooted; and am now re-installing let's see what happens next
  6. "newperms" is the command you want. thanks - that didn't seem to do anything - i tired at root and \boot .. it says successful, but nothing seems to happen. the good news is - that's not it either, because the safemode option boots right up, no issues. i'm going to try deleting the dynamix stuff and try again
  7. thanks Dale - also found this: http://www.linux-faqs.info/general/system-hangs-system-message-bus which kinda makes sense. I noticed earlier that when I tried to reach \\tower\flash i got prompted for a login. Is there a way to run the new permissions script on the flash drive via console? odd enough, I can get a telnet session going
  8. well i went on a plug-in installing binge and screwed something up: That happened when I tried to Install the System stats plug in. Using UnMenu and the console Powerdown command, I was able to shut down gracefully. Upon boot, i'm getting this screen now: This is on UnRaid 5.0.3, in a VM; Any ideas?
  9. hey - thanks for doing this - i'm jumping aboard tonight. just thinking - you should put this in the OP so that it's not buried. One other thing that's not mentioned, but would help de-noobify it: should I uninstall the current webgui-latest.plg ? i'm using that instead of the stock, with no other plug-ins, and don't have many issues. BUT would love to get the other great stuff that dynamix is bringing!
  10. okay - thanks everyone for the informative replies! the parity build succeeded, and as a few pointed out, i'm going to go ahead and run a sync. I still have another 5 drives to add to this array. After the parity succeeded, i ran a pre-clear -n on the original parity drive. After all of this is said and done, my array will be at the 24TB mark :-)... going up from 10TB.
  11. hello - waking this thread up again... so some time passed... and i just added the 4TB to my production array. i'm pretty sure i ran a pre-clear with the -n option way back when after testing... but it's been so long, that I don't remember. Upgrading the parity drive causes a full sync, right? does that mean i'm safe and protected, or if i skipped pre-clearing after testing, am i potentially at risk? Should I stop the array and re-preclear the parity drive with the -n option? as always - guidance is appreciated.
  12. Wouldn't hurt to start discussing it and trying to recruit one the plugin developers. excuse me, mr. bus driver? if i'm in an aisle seat, which window do i lick?
  13. yes - this is important to note, i think one of the few that are used here that don't support it. nice card otherwise. I have one, and just recently upgraded to an LSI 9211-8i because of the limit. I think it'll mount them, but nothing over 2.2 will be exposed, which is well, a waste.
  14. Both the 4TB WD Black and the 4TB WD RE series are 7200rpm drives ... but they're both 5-platter, 800MB/platter densities. I'm sure by "decent 4TB" you mean one with 1TB/platter areal density ... which I've also been watching for Personally, I'm more anxious for the 5TB drives to come out (What would REALLY be nice is if they were 1.25TB/platter units ... but I'm anticipating they'll be 5-platter, 1TB/platter units.) ah didn't realize that about the WDs - good to know. the 5's and 6's wont be here for at least a year; my new 24-bay case will have to deal with 4's until i fill 'em up (or it is no longer economically viable to buy that "small").
  15. Thanks Gary - this makes a lot of sense. In the next day or so, I am going to move the 4TB, 5900RPM disk to my production array; i'll run more tests on that configuration and see how the numbers look. Dying for a decent 4TB at 7200 RPM - but not looking likely anytime soon.
  16. Thanks - I always thought those were only tweaked if/when you suffer massive slowdowns (like that one where people were getting like 12KB/s writes).
  17. Should the output of my DD be higher? I'm still confused on why one system reports 68MB/s while the other reports about half that. The one reporting 35MB/s actually has a faster (7200RPM) parity drive as compared to the 68MB/s machine, which has a parity drive that spins at 5900RPM.
  18. thanks - i did see the release note about this - but also saw that for larger arrays, there's a point of diminishing returns. I have 8 drives in my array now, and within a week or so, will increase to 12. i'm still confused about why the Test array ran a DD faster, and a Parity check faster (160MB/s on Test vs about 80MB/s on PROD) but still transfers are faster to the Prod array. The reason i'm trying to nail this down now is when i do increase to the 12 drives, I will be using a SAS Expander - where i expect a performance hit. far less moving pieces if I can get a solid baseline before that would be great.
  19. just adding more info from the previous thread: i've tried: [*]different HBA PERC H310 and BR10i [*]increased VM ram from 4GB to 8GB with nothing else running [*]running unraid on baremetal (instead of inside VM). [*]changing BIOS settings to ensure AHCI (for built-in ports which I am not using None of these yielded any discernible difference outside of a +/- 3MB/s so I didn't really record the results. So we are left with: Motherboard/PCI-e issue (ports are set to run at x16, x8 and x8; hba being in x16 slot), Parity Drive issue (2TB, 7200 with 64MB cache Link ) or the Norco SS-400 Anything else I can/should check ? I'm tempted to do a survey to see what people are getting and what's acceptable, etc. there are so many combinations and what nots that a centralized "this is what my speed is" would be handy. Is there interest in something like this?
  20. So i've been struggling with trying to get a baseline on what's considered the "average" read/write speed out of UnRaid. I'm splitting this off of CaptainTivo's Thread . I get 25 MB/s to perhaps 35 MB/s when writing to the array. Reading - I max out my gigabit connection, easily. Even if I have the parity drive disabled. Here are two different inputs of hdparm and dd like OP did: One is from running the ever popular TAMs machine with 3x AOC-SAS cards. that's my test array. My production array is actually pitiful. This is a VM, with a Dell H310 HBA; the drives are connected to a Norco ss-400. the above is to a wd green drive. here's to a 7200 spinner on the same machine: Both are running running latest 5.0.4. The Production machine (Rigel) has a 2TB 7200RPM Parity drive (Toshiba, w. 64MB Ram); The Test Machine (Tower) has a 4TB 5900RPM Parity drive. now that's dd tests... but the weird thing is when i'm copying over the network, the test machine is actually slower than the production machine. by about 10MB/s. i'm guessing this has to do with the spindle speed on the parity disk
  21. SimpleFeatures is no longer compatible. Dynamix is the "new" SimpleFeatures. thanks - i saw that - but didn't want to try it due to that potential slow down issue on the polling. though i think that was fixed. anyhooo - i've tried: [*]different HBA PERC H310 and BR10i [*]increased VM ram from 4GB to 8GB with nothing else running [*]running unraid on baremetal (instead of inside VM). [*]changing BIOS settings to ensure AHCI (for built-in ports which I am not using None of these yielded any discernible difference outside of a +/- 3MB/s so I didn't really record the results. So we are left with: Motherboard/PCI-e issue (ports are set to run at x16, x8 and x8; hba being in x16 slot), Parity Drive issue (2TB, 7200 with 64MB cache Link ) or the Norco SS-400 Anything else I can/should check ? Hopefully i'm not jacking the thread from OP - I was thinking of starting this same thread. I'm tempted to do a survey to see what people are getting and what's acceptable, etc.
  22. not much of a difference for me. soo at this point - the only thing i can blame is either the fact that it's a VM, my parity drive is too slow (shouldn't be the case) - Or the norco ss-400 is somehow interfering. at least now i'm on the latest and greatest.
  23. thanks - that sounds like a plan - i was DREADING having to run pre-clear on these drives, AGAIN. on a 4TB drive, it takes a very very very long time (great for stress testing the hell out of the drive while driving my patience into the ground). Almost any writing to a precleared drive would either invalidate its preclear signature OR give you a false sense that parity is correct after adding the drive to the array, when in reality, it is not. Best bet is to test with files first, then to run the preclear. Joe L. thanks Joe - i'm pretty much done with testing, do I need to run a FULL pre-clear? or as gary stated, will the -n option put me back into actually pre-cleared status again?