Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by doron

  1. Okay two different things. Re the NVME - unrelated to the plugin. You want to specify spindown delay of "never" for those, or Unraid will try to spin them down (as you saw) and fail. Re the other thing (Child terminated), will try to figure this out.
  2. So now you didn't get the "child terminated" message?!
  3. This might indicate a problem in the syslog hook used to trigger spindown in versions below 6.9. - Can you indicate which version of the plugin is installed? - Are you getting any "SAS Assist" messages in your syslog? - Can you do this, from the Unraid CLI: touch /tmp/spindownsas-debug and then try to spin down a SAS drive and paste the resulting syslog excerpt? After doing that you can just rm /tmp/spindownsas-debug To stop the debug messages.
  4. Thanks for reporting. Do you see any "SAS Assist" messages in the log? Indeed.
  5. I'm not asking that, I'm sure you did. I presume your current situation is that you CAN start the array when typing the passphrase at the GUI, but can not change it using cryptsetup and / or my script. Is my understanding correct? Can you tell me what types of characters are in your passphrase? Not asking to share the phrase obviously, just the type of characters it is comprised of: - Does it have non Alphanumeric characters? - Does it have non-ASCII characters (i.e. from a code page different than Latin)? If so can you give an example of such a character? (ag
  6. Both, and anyone else who is looking to change the LUKS passphrase of their HDDs... 🙂
  7. A slightly simpler way to get what you want might be: 1. Write a short script that just prints the password ("echo mygoodpassword"). Assume you put it at /root/mypass. 2. In /boot/config/go, add: DISPLAY=: SSH_ASKPASS=/root/mypass setsid ssh -N -R 8000:XX.XX.XX.XX:8000 root@XX.XX.XX.XX
  8. Sorry, that was my bad. I forgot you're at 6.8.3 (I'm too deep into 6.9 already). Yeah, 6.9 does this for UD as well. Not sure it's gonna help much, given that your drives refuse spin down 🙂 Very helpful. It's an almost definitive testimonial that these Seagates with this controller would not spin down.
  9. Ah. This might make the testing somewhat less accurate. If the drives are active during the test (with real data moving, or even just filesystem housekeeping), that activity might spin the drive back up while you're waiting between setting and testing. I presume the plugin is installed? You'd not see a "SAS Assist" message if you fiddle with the drives manually. You should see it if, instead, you'd hit the green button next to one of your SAS drives (that are under UD), to cause the drive to spin down. Have you tried that? Do you see a SAS Assist message then? If you d
  10. Thanks for the kind words. What we've been seeing is kind of hit and miss, so no strict verdict re a certain series of HDDs; you may want to just try. Re the specific issue, some of the Seagate documentation seems to imply that power mode 3 (the mode we're setting the drive into) is implemented as needing an explicit command to spin the drive back up. This does not jive too well with how Unraid is expecting things to behave (basically, it is expected that a subsequent i/o to the drive will implicitly spin it back up). Bottom line, you may want to give it a try and see.
  11. Thanks for reporting - that's good to hear. If you could also run: /usr/local/emhttp/plugins/sas-spindown/sas-util and send over the resulting file (pm me or post), that'd be great.
  12. Sure is... Check out the output file (or see below). Thanks for your help! "controller": { "Slot": "01:00.0", "Class": "Serial Attached SCSI controller [0107]", "Vendor": "Broadcom / LSI [1000]", "Device": "SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] [0064]", "SVendor": "Broadcom / LSI [1000]", "SDevice": "9200-16e 6Gb/s SAS/SATA PCIe x8 External HBA [3030]", "Rev": "02"
  13. Thanks for reporting! I'm really happy to hear that. Would you mind running /usr/local/emhttp/plugins/sas-spindown/sas-util and send me the resulting file (/tmp/sas-util-out)? (when run without parameters it doesn't do anything intrusive, just reports the HDD and controller(s) models in JSON format) You can pm me or post here (no sensitive info such as serial numbers etc. is shared). Thanks
  14. Posting in this thread just to follow up, I've just pushed a new version (0.8) of the SAS Spindown plugin, supporting 6.9.0-rc1 and the new spin up/down mechanisms. It's on CA.
  15. I've just pushed a new version - 0.8 - of the plugin, supporting 6.9.0-rc1 and its new spin up/down mechanisms. As always, please report issues.
  16. @SimonF, a new version of the SAS spindown plugin is coming shortly, supporting 6.9.0.
  17. Thanks for doing that. That's great news. Unraid (in kernel upto 6.8 and in userspace in the future) looks at i/o activity to determine spin up of a drive.
  18. Thanks for reporting! Happy to hear it worked well for you.
  19. This is essentially what the plugin does when it tries to spin down SAS drives. So either this does nothing in your setup (combination of hard drive and controller), or something else is going on. Could it be that you have constant i/o against the array - in which case, a spun-down drive will immediately spin back up? Do you see i/o counters (read or write) on the main page moving, during that time?
  20. Excellent news! Thanks @SimonF!
  21. It's identical to pushing the "spin down" button (when the plugin is installed). If there's no massive i/o going on against it, sure.
  22. (sorry for previous misfire, I was reading on a tiny phone) Does this same drive react the same way to direct spindown? e.g.: sg_start -r --pc=3 /dev/sdd sdparm --command=sense /dev/sdd
  23. @nlcjr, can you restart your rsyslog service, then spindown one drive just once, then read sense with sdparm? e.g.: /etc/rc.d/rc.rsyslogd restart mdcmd spindown 2 (wait a couple of seconds, then...) sdparm --command=sense /dev/sdd
  24. Hmm, that Should Not Occur™. Can you share the log lines you get around the time of the spindown (i.e. including and immediately following the "spindown" message for one of your SAS drives)? Do you see any messages at all with "SAS Assist" prefix? Also, can you share your /etc/rsyslog.conf ?