doron

Community Developer
  • Content Count

    472
  • Joined

  • Last visited

  • Days Won

    3

doron last won the day on September 20 2020

doron had the most liked content!

Community Reputation

74 Good

2 Followers

About doron

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. What Simon said. Basically, as of 6.9.2, some SAS drives (mainly Seagates) and also some SATA drives have an issue with spindown. Essentially they appear to spin down but then immediately spin back up. Not sure yet re the source of this issue, might be kernel/driver related, probably not related to the plugin (as (a) it happens with SATA drives as well and (b) some SAS drives spin down and up perfectly under 6.9.2).
  2. doron

    Soon™️

    jefcpdcavmmqn.
  3. Hi, thanks for posting. Sure, they're generally decent drives. But you will probably need to live with them spinning 24x7 😞 Basically, there's conflicting data as to their behavior. I started with excluding them, then started a mini-project of collecting data points from users. Since I did receive a couple of positive data points for these drives, I commented the exclusion out, "for now". My controller is based on the same chip. I use HGST drives. They spin down/up without a hitch. So it could be a combination of the controller/HDDs, or just the latt
  4. Either the BP will not physically accept SAS drives to begin with (as noted by @JorgeB above) due to the connectors being SATA only, or the controller will see a SAS drive(*). Neither the cables nor the BP will change the protocol spoken by the drive from SAS (essentially, SCSI) to SATA (essentially, ATA). (*) In some cases, speed might be negotiated down (e.g. 6Gb/s SAS instead of 12Gb/s SAS).
  5. Yes, it does. That's why you would opt for New Config - which will have Unraid see the new IDs. The important thing is that the data on the drives, as seen by Unraid, will be bit-identical, and with the presumption above holding, it should be. And of course, you'd need to make very sure the drives maintain their Unraid slots - Or Else 🙂
  6. I'm not overly familiar with Proxmox specifically, but assuming its HDD passthrough passes the entire physical drive to the VM, you should be fine with the process you described (also check the "parity is valid" checkbox). If the drive seen by Unraid is block/sector-wise identical to what it was seeing previously, this should work. The remaining question would be whether you would actually be able to pass the SATA controller. Not all on-board controllers can be passed through; this would be mobo-dependent. But you'll figure that one out pretty quickly 🙂
  7. @BurntOC, here are some related messages from this forum: This and this.
  8. Not quite. You can pass your SATA drives as RDM (see other posts in this subforum, can't link right now). I've been doing that for years and it worked very well. SMART, Spindown, performance,gthe works. There's a "tribal knowledge" thing going around that these things do not work in that scenario. Not the case in my experience.
  9. doron

    Soon™️

    Will wait for 6.10 to solve.
  10. Limiting the passphrase characters in a very conservative way was a response to some difficulties people experienced when inputting these phrases via GUI, through various, not 100% compatible, versions of Unraid. I decided then to make it quite restrictive; can't recall whether the underscore was a deliberate omission or not. At any rate, you can enter any passphase you want, with any characters you like, by using a keyfile.
  11. It is a 6.9.2 issue. See above for an open bug thread about it. The issue occurs with both SATA and SAS drives (although not all drives), and is seemingly unrelated to this plugin.
  12. Running Unraid under ESXi 6 for quite a few years. It's been rock solid. I haven't done any scientific performance measurements iron vs. VM but have not seen any performance issues. One small oddity that I haven't fully investigated is what appears to be high CPU usage sometimes when an array drive spins up from standby. Not consistently reproducible and not a real issue so haven't taken the time.
  13. Thanks for reporting. Just to make sure you're seeing an instance of the recently reported 6.9.2 issue (you probably are; see above for more details): In your system log, do you see the "SAS Assist" spindown messages, immediately followed by a "Read SMART" message for same drive?
  14. I'd check the CMOS battery. From the manual of your mobo: Losing the System's Setup Configuration 1. Make sure that you are using a high-quality power supply. A poor-quality power supply may cause the system to lose the CMOS setup information. Refer to Chapter 2 for details on recommended power supplies. 2. The battery on your motherboard may be old. Check to verify that it still supplies ~3VDC. If it does not, replace it with a new one. 3. If the above steps do not fix the setup configuration problem, contact your vendor for repairs.
  15. @bonienlfyi - this is still the case - probably worth moving from "prereleases" to proper bug reports?