Jump to content

limetech

Administrators
  • Posts

    10,192
  • Joined

  • Last visited

  • Days Won

    196

Everything posted by limetech

  1. limetech

    Disk Spin up

    Thank you for detailed info, I will try and reproduce.
  2. If you don't see device temperatures upon reboot, just click "spin up all" and everything should be fine until I can release -rc3.
  3. What Unraid OS release? Please update to 6.9 if not already on 6.9
  4. Reporting "-2" as temperature for spun-down disks is not a good idea imho. When I llived in Colorado a server in the garage routinely got to that temperature and below. I once spun up disks on a cold server and lost almost half of them! Since then, put a cardboard box over server which kept it warm enough during winter. lol
  5. Ok found this problem. BTW: you shouldn't have to click Spin Down, should only have to click Spin Up button to establish temps.
  6. Please open separate bug report for this.
  7. limetech

    Disk Spin up

    Please post diags. Not just syslog, need full diagnostics.zip. Also remove sas spindown plugin for now.
  8. Only "-i" reports anything if "-n standby" also specified. Odd because the I/O driver increments "number of sectors read" each time "smartctl -in standby" is executed on a spun down disk. /sys/block/sdX/stat
  9. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Hopefully spin-up/down sorted: External code (docker containers) using 'smartctl -n standby' should work ok with SATA drives. This will remain problematic for SAS until/unless smartmontools v7.2 is released with support for '-n standby' with SAS. SMART is unconditionally enabled on devices upon boot. This solves problem where some newly installed devices may not have SMART enabled. Unassigned devices will get spun-down according to 'Settings/Disk Settings/Default spin down delay'. Updated to 5.10 Linux kernel (5.10.1). Updated docker. Fixed bug joining AD domains. Version 6.9.0-rc2 2020-12-18 (vs -rc1) Base distro: bind: verison 9.16.8 docker: version 19.03.14 krb5: version 1.18.2 Linux kernel: version 5.10.1 Management: emhttpd: fix external 'smartctl -n standby' causing device spinup emhttpd: enable SMART on devices upon startup emhttpd: unassigned devices spin-down according to global default emhttpd: restore 'poll_attributes' event callout smb: fixed AD join issue webgui: do not try to display SMART info that causes spin-up for devices that are spun-down webgui: avoid php syntax error if autov() source file does not exist
  10. I know what it does, just not how this fixed anything because when Unraid OS formats a device we create an entirely new partition structure - no hidden partitions, no hidden files. It's a mystery...
  11. How did running this util fix it?
  12. You had to delete two files and then reboot? Were they config/rsyslog.cfg and /etc/rsyslog.conf? Shouldn't be the case. The 'bug' that got us into this mess was introduced in one of the 6.9-beta's. thanks for reporting and thanks to @Squid for recreating this issue and pointing me in the right direction!
  13. Thank you for the detailed info. If you reboot again is it the same 'disk3' that again reports wrong key?
  14. Ok location of 'emcmd' moved in 6.9, probably you're on 6.8 right? I guess I'm confused about what you're doing. If you have created your own little app to spin up the drives, I assumed you know enough to figure out how to add the csrf token. How were you doing this before and I guess now it's broken? Why not just fire up webGUI and click 'Spin up' button?
  15. Please try this: Stop array, select each data disk and set its file system type to "xfs". Start array, and then click Format, let it complete and observe that all disks 'mounted', everything looks good. Stop array, select each data disk and set file system type to "xfs-encrypted" (all 3 of them). Start array, observe that all 3 data disks should show 'Unformatted'. Enter your encryption key and click Format. At this point, all should show up as encrypted and mounted. Buf if not, please capture diagnostics at this point and post here.
  16. That still works but you are missing the csrf token, look at that emcmd script.
  17. Look at the '/usr/local/emhttp/emcmd' script. You could use like this: emcmd "cmdSpinupAll=apply" # spin up all hdd's emcmd "cmdSpindownAll=apply" # spin 'em down emcmd "cmdSpinup=disk1" # spin up disk1. If disk1 was a member of a spinup group all disks of the group would spin up.
  18. Changed Status to Open Changed Priority to Other
  19. I don't see a kernel panic in your syslog.
  20. Please open a separate report for this.
  21. Settings/Management Access
×
×
  • Create New...