Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


doron last won the day on September 25 2019

doron had the most liked content!

Community Reputation

26 Good

1 Follower

About doron

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Have you looked at the Cooler Master case I pointed to on eBay in the previous post? You might find it interesting (and they still have a few available as I write this). (Curiously, I also have a CM590 which is what I plan to be moving away from... Tight.)
  2. Like the rest of you of this thread, I have also been searching for the thing - a tower with 5.25" bays top to bottom(*). I've bumped on this on eBay and grabbed one. They seem to still have a few left. They are NIB. This one has 9 5.25" bays, all exposed. You can fill them with 5-in-3 or 3-in-2 of your fancy, to get a nice 15 or 12 hotswap 3.5" drives. It's a bit of a beast (full tower, deep, tons of cooling options). It allegedly supports E-ATX mobos but unfortunately does not fit boards like X9DR3-F (which is E-ATX by spec) - the I/O plate and PCI/E slots do not align. Weird. It does take ATX (and smaller FF) boards happily. Thought some of you might find this interesting. (*) I was looking at using a CSE846 but dropped it due to its sound signature - too noisy for its designated location.
  3. Not exactly. I'm saying I've been working only with RDMs for years and years and both SMART and spin down were working just fine. SSDs do not actually spin down. SMART works for them, of course. That is a different question that is unrelated to RDM vs. controller p/t. I'm not authoritative on this one - I do use SSD for cache.
  4. Okay this is very interesting. I just did a brief google study and indeed found references to this claim - e.g. here, here and here. Honestly, I haven't even heard of that claim until this thread. Conversely, I've been running all my drives as RDMs for quite a few years. SMART was fine, spin down worked. Ironically, I've recently moved all my mechanical drives to a passed-through controller; the one drive I left as RDM is my cache drive, which is an SSD, which does not spin down. I just re-tested smartctl again against this drive and it works, as does hdparm. Does anyone have any supporting data to the contrary (i.e. that either of these does not work)? Or could this be some form of "tribal myth" that has been passed on as common wisdom?
  5. Pretty sure. Is there some common wisdom saying that you don't get SMART and spindown with RDMs?
  6. Why would you not get SMART and spin down in RDM? From my experience, you get both.
  7. This command will definitely add a newline char at the end of your passphrase - not what you want. You want: echo -n "passphrase" > keyfile
  8. Quite hard to select one thing I love about Unraid, but if forced to reduce to one, it'll be back to basics: The ability to add drives, in singles or batches, of different sizes, and get them all protected and still recoverable in case of multi drive failure. This has been Unraid's first differentiator, and I think it still is. Now with encryption and dual parity... I'd like to see SAS drives spun down... 🙂
  9. If it would be more convenient for you, you can use this tool to change your pass key into something that's along @limetech's guidance above.
  10. Uneventful upgrade from rc8 here. A thing of beauty. Thanks.
  11. I believe that article is both quite dated (2/2012) and quite inaccurate. It compares things that should not really be compared; the SAS drives considered are the 10KRPM and 15KRPM little beasts, which are indeed very different animals than the 7.2KRPM spindles, in terms of actual drive technology. But this has little to do with SAS per se: They were manufactured only with SAS interfaces, simply because no home user would spend the $$$$ for these ultrafast, yet relatively lower capacity drives. Before SSDs became the rage, those critters have been your tier-1 storage of choice (e.g. cache). When you compare apples to apples, e.g. 7.2KRPM 12TB enterprise-level drives, the difference is only in the attached electronics as @limetechsaid. You can actually buy the same drive and select your electronics. Case in point, check out this datasheet. Check the bottom for ordering options. As mentioned above, the main differences lie with the bus protocol performance and extremely different configuration and topology options. Not the performance or reliability of the actual spindle.
  12. Yes, understood. There are good reasons to prefer SAS over SATA, although admittedly most of them(*) reside in the ballpark of enterprise computing as opposed to home / SOHO, where I'm guessing most of Unraid install base lives. (I'm a diehard veteran of the former, yet my Unraid is the latter, ergo...). I'll concede that in retrospect, I would have been be better off if my 12TB HGST's were SATA - if not for any other reason, for this spindown one. (*) Much larger and more complex drive topologies, including multihomed and multi-tier connections and enclosures, faster bus transfer speeds (12Gb/s on SAS3), more reliable performance in the presence of those complex configurations, and more. Again - most/all reside in the enterprise computing realm. That's a good start, yes. Thanks! It is well understood and appreciated that you have bigger fish to fry at this time. Hence: <plea> Would you consider adding, on top of the above (not attempting to spin them down), an upcall hook - in the spirit of the EVENT scripts calls - for all spindown/spinup actions? This would allow those of us who are knee deep in this (and paying the electricity bills...) to script this up (currently this is Hard™ - as the action takes place in the kernel code). I will definitely take a stab - others might too. Once this is (hopefully) brushed up, you can consider adopting it into the core product. Does this make sense? </plea>
  13. Interesting. When you say the disk did not spin down - how did you test that hasn't actually spun down?
  14. You sure do. I did capitalize, but you're right, should have been Soon™. Mea Culpa.