axeman

is it OK that the pre-clear marked my 2TB (advanced format) drive with the 512/63 ? see attached.

one more question.. the original posting of the script mentions NOT using anything OTHER than the UnRaid management UI to format the pre-cleared drives. Since I've already installed Simple Features, can I use that? Or do I need to go back to stock to be safe?

One more drive finished . this is my latest - replacing the dead Samsung with.. preclear_finish__13E0B47VS_2013-05-05.txt

interesting. I might do that when I switch to 5.0 Prod. I am undecided about which one I like - both seem to really jazz up UnRaid. Can someone peruse through these and see if there's anything of concern? the Samsung log is super long. incidentally - my other very similar Samsung just croaked. soooo i'm concerned. the replacement for the one that died just got here today - about to fire off the script on that. preclear_finish__S2AEJ1BZ600843_2013-05-02.txt preclear_finish__WD-WCAZAJ087969_2013-05-03.txt preclear_finish__WD-WCAZAJ142017_2013-05-03.txt

ah - i thought unmenu was for 4.x only... meh i guess i'll have to forgo email notifications.

thanks Joe When I run it in screen via putty, I don't see that error; strange thing is, I got it to work, about 2 months ago. either something changed in Unraid or simple features. searched around for mailx... not sure I can get that going easily. going to fire off the first set... these were precleared back a month ago. I wiped everything out and starting fresh. figure i'll just run 1 pass.

grrr. whenever i use the -m [email protected] or -M 4 options, the help/usage text shows on screen if i take those options out, it seems to start the pre-clear process. i've done this in the past, so i can't imagine what i'm doing wrong now.. set email info using SimpleFeatures [1.0.11]; i'm on UnRaid 5.0-rc12a; and pre-clear version 1.13. I am receiving email from SimpleFeatures, periodically; and the command below works fine: echo -e "Subject: a test\n\nThis is the email body." | ssmtp -d root Command line i'm trying to execute: ./preclear_disk.sh -M 4 -c 1 -a /dev/sdd also tried simple: ./preclear_disk.sh -M 4 /dev/sdd anything obvious that i'm missing?

Okay - one more 2TB drive finished its 3rd cycle... can someone look to see if there's anything to be worried about? I see high temp, but otherwise OK? wd_sdc.txt

I would guess you are maxing out your BR10i. yeah - i'm thinking that... surprised, but i guess that's the roll of the dice. I wonder if the whole array not assigned thing is causing issues also..

damnit - the slow read keeps coming back from time to time. syslog attached... sorry it's a 7zip, renamed to .zip syslog-2013-02-18_2.zip

thanks for doing what you do Joe! Still waiting on the WD's to finish. I'll post those too. Again - I appreciate you going through these for me. I'm thinking of keeping 1 of the WDs as a warm spare ... keep it pre-cleared, and attached, but not in array until either I run out of space or one of my other drives fail. I saw that idea floated around somewhere, I can't take the credit for it.

Thanks Joe - this array has never been started, and has nothing on it, data-wise. The two WD green drives are still going, on pass 2 of 3. The Samsungs finished, with what appears to be some red flags. Also - it looks like the slow down is gone again. it seems that the pre-read is the step that this happens at when there's another disk being written to..i thought the BR10i can handle that type of bandwidth, but perhaps it maxes at about 150MB/s ? Can I trouble you to look at these two logs and let me know what I should be freaked out about? Samsung_sdd.txt Samsung_sde.txt

i thought that error was related to not having the array started. If i start the shutdown from the webui, will it cancel the pre-clears? or should i wait for them to finish?

okay - got it - better formatted syslog-2013-02-17.zip

okay - so the issue is back - and i am trying to get a log, whats the best way to do that? Simple features seems to freeze on opening it. I ran this command: cp /var/log/syslog /boot/syslog-2008-04-10.txt on the console, via putty and ended up with the attached.. no carriage returns, etc. I have four pre-clears running at the same time; only one of them is runnign at full speed (about 130MB/s the others are all sub 5MB/s). is there a better way to get a syslog? I had to zip it, it was too large syslog-2013-02-17.zip

yea - it was going at the same time. as for the I/O bandwidth, i wasn't expecting it to be an issue, since the test array was running off a BR10i card and the other is running off the mobo headers. either way - lesson learned. like i said i figured the wd drive was defective until proved otherwise.

You are probably experiencing resource contention of some kind. They are probably each waiting on some resource the other has. Since you did not attach a syslog, I can assume you've already looked there for clues and found nothing. Joe L. Thanks - no i didn't look - actually didn't even think to attach the log, thinking that since the array isn't on, what could the log show.. sorry that was nooby of me. anyhoo - after a little while, it took off agian, and is in the 90MB/s range - i guess knowing it was an EARX, i paniced too quickly. chugging along now. the parity check also finished on my other VM. Glad that the machine didn't croak with all these disks chugging at the same time. *whew*.

Can anyone shed some light on what's happening here? background: Unraid 5-rc; i have simplefeatures plugin installed; Array is not started. I am using the latest version of the script. these are those damn western digital EARX drives. (I got the retail version from Bestbuy). I did not use the wdile3 utility on these; they are connected to a Br10i and are passed through to the UnRaid VM I started a pre_clear of 4 drives at once; two are what you see here, and the other two are Samsung Spinpoint 1TB drives (which seem to be progressing as expected). My prod UnRaid, i've pre_cleared x3 drives at a time, (WDEARS, with idle set to max) - they were direct attached to mobo and given to unraid via the RDM method. Also have a parity check going on my production UnRaid VM, which is also moving as expected. Am I experiencing a dual failure here? Should I wait till the other two are finished, and try to run these, alone?

ty sir - i got excited when i saw it. I know there was some debate in the past.. didn't know if it was an UnRaid issue or card/bios issue. Ty for clarifying. Would've been cool.

just wondering - as of the 5.0beta7, will all 3TB be useable? sounds like it is from this post. i'd need to get two and would hate to only use 2.2TB;

Ok.... so I saw someone on page 3/4 mentioned it (i thought it was Linux specific, so glossed over it). however, for anyone else that has the issue... someone else on the ServeTheHome link had the same issue; the solution was to get a different version of sasflash.exe from here: ftp://ftp.supermicro.com/driver/SAS/LSI/1064_1068/IT/Firmware/B3/L8i/1.30.00/ now it worked - but still can't verify/get into the card's bios. I'll have to wait till I can check it at work next week. Thanks again madburg!

thanks - me too.. and got nothing - still get that no LSI adapters found bit. leaving work in 45 minutes. have friends coming over tonight; but can toy w. it at home.. the only problem is, on my machine at home, i CAN'T get into the card's bios. that's why i figured it should flash "better" at work.

no need to apologize! thanks. I can change the filename or even udpate the .bat files. I'm hoping that you did grab the wrong files or something that makes this new upload work :-) thanks for your hard work.

exactly - there are no drives attached to the card... yes, device manager reports it properly... 1 thing i noticed, is that the batch calls sas2flash.exe but the actual file in the directory is sasflash.exe... i created a directory called p20 and renamed 3Gs_6Gs_SATA_Support_Firmware to 6G. I opened CMD and selected Run as Administrator. CD to P20 then CD to 6G. if i run this: my output is this:

thanks! all my hds are currently sata ii, and i don't even think you can buy a sata i hd anymore aanyhow :-) okay - so what could i be doing wrong? 'sas2flash_x64.exe' is not recognized as an internal or external command, operable program or batch file. same error for _x86. tried on a win7x64; and a win7x86 ... both with admin privs, and both using "run as admin" If i try to run the sas2flash_x86 with the parameters in the first .bat file, it says no adapters found.