jbuszkie

http://www.norcotek.com/product/ss-500/ They had a couple iterations...

I think so.. But you have to call.. There was no option for "Replace" only "refund" Jim

zero issues with the return process. I even clicked the waive free return but the sent me a label anyway.. I did talk to them on the phone. The label does say bill sender... So I don't know if they will bill me? I don't know how they could? It seems like I could have done it online too pretty easy..

I have 3 of the norco drive cages. I recently got an 8T drive. I precleared it in the middle cage and all was well. After I set it as parity I wanted to move it to the upper cage that's connected to MB slot 0. When I plugged it in, It wasn't recognized!! I moved it to the far slot in that cage and it was recognized? I plugged my old parity drive in back in the slot and it was recognized. I've never had any sensitivity issues before. Is there anything I look for? I'd like to not have to worry about one cage slot working better than another! Jim

My second drive from them was a dud! Wasn't recognized! :-( So back it goes. Jet wouldn't send me another. I think they figured I got the 20% off deal twice! but I had a 15% off code from them and the drive was a little more.. so instead of $177... I paid $195. Still a good deal, I think. Hopefully this one is better! Jim

Well.... I'm 50% with the 8T Drives... I got 2 of them and one doesn't post! crap. Jet won't send me a new one.. Just will refund my money! :-( So I'll have to try and buy it again and try to work around the one per household deal! *pout* Now I have an 8T parity system with a 4T max drive! Jim

two of my 2T drives are 500G platters and the 3rd is 3x 667G My 4T drives are 5x 800G platters. I didn't bother to look up my 3T drives.. The 2T's will be next to be replaced when I fill up my array again.. Which shouldn't be for a while since I will soon add a 2nd 8T drive to go with my 8T parity!

To answer my own post I found this.. http://rml527.blogspot.com/2010/09/hdd-platter-capacity-database.html Now there may be something better.. but this had the info..

I"m not too concerned with the parity check speeds... I just didn't want it to be worse with the shingled drive... But.. Can I tell from the smart data what my densities are? or do I have to look it up online by model number? Jim

I'd love to have a pair of those for my cache drives! :-)

I do! It was bugging me!

So I went back and put my 4T back in as parity and rebuilt parity just so I could have a comparison. 13h 37m to build parity. Since I didn't have an exact point where I crossed the 4T mark with the 8T parity build, I estimated 13h 30m.. I'll say +/- 15 minuted on that number. So now I can conclude that the 8T Shingled did not take noticeable time longer or shorter. The preceived slowness WAS all in my head! And now back to the 8T parity drive!

Considering it could be months between powercycles.. The syslogs could get big. I know the mover generates a lot of syslog entries.. If you've got a crapload of files that get moved.... But that might be a good idea anyway to do the diagnostic thing.. Jim

The only log archived on the flash drive is the latest. hmm.. Maybe I'll have to try and hack it so it will save all of the syslogs.. Thanks for the confirmation. Jim

Settings - Display Settings - Page Update Frequency (set to Disabled) Will that cover all open pages on all machines? I assume yes... Jim

This is, of course, normal. As a drive moves to the inner cylinders, the transfer rate drops significantly. Since a parity check is always limited by the slowest drive current active in the check, when you have a mixed set of drives, each different size will result in another "inner cylinder slowdown". So, in your case, it will slow down as it gets close to the 2TB point; then speed up somewhat until the 3TB drives reach their inner cylinders; and then slow down again as the 4TB drives reach their inner cylinders; and finally slow down for the last time as the 8TB drive reaches its inner cylinders. As it passes each of those boundaries, the speed will bump up a bit. Yeah.. I'm aware of the inner cylinder slowness.. I should have put an "as expected" at the end of my last post! I'm not quite ready to get rid of my 2T drives yet. I'm eventually replacing them. Once they hit the 5 year mark they are put next on the list to be replaced. Jim

Ah... I didn't save the old config.. I guess That is necessary to this. I'll have to remember that if I want to put my 4T back a parity to test the speed and be covered...

I have done the nr_requests.. but how do you disable the gui updates? (I may have it open a on couple machines..) Jim

What OS is giving you that speed graph during the copy? Is that win10?

I do have some 4T drives. My whole thought process is that maybe the "shingled" Archive drive might have a negative effect in my case. My guess is that it doesn't.. But I'd love to prove myself right or wrong by putting my old parity disk back in! I can see in my hourly status reports that the speed slows down every hour until it gets rid of a drive.. Then it briefly speeds up then slows down until the next drive(s) finish.. Damn! I really wish I had an older parity check speed for comparison!

Not really.. I have automatic backups that occur every night. I'd rather not have to remember to disable them... only to forget to enable them again. Yes this is what I'm referring to.. And I do know of the auto party sync when trust parity thing is invoked. But isn't the old way still valid with the setinvalid slot thing? Couldn't that still be used to recover the failed disk? Jim

This might be a dumb question... But does this powerdown script handle multiple log files for archiving? Doesn't unraid move the syslog file to something like syslog_0 (I can't remember what it actually is) when the file gets to a certain size? does the power down script attempt to copy those files too to the log directory on the flash drive? I was looking at the code and it doesn't not appear to.. unless I'm missing something...

Motherboard port. This perceived slower sync.. May all be in my head. I can't locate any logs that give my any insight to older parity check times. I need to look at my log retention scheme...

Something I grumble about every time I hit that "New Config" button. Me too! +1 to that as well... But I agree that changing the default behavior needs to be don't do a correcting parity check is the first priority.

Yes.. I'm aware of that.. but I'm comparing to when it gets to the 4T point where my old parity sync would have finished.