ezhik

Members
  • Posts

    466
  • Joined

  • Days Won

    1

Everything posted by ezhik

  1. Updated 3 servers, no issues. From 6.2.6 to 6.2.8 with nvidia plugin.
  2. Valid points, no argument there. I've asked for a proper multi-user support in the past myself to have a proper RBAC within unRAID - but to no avail. You are spot on - it is a single-user, single-admin system. Honestly, I wouldn't expose this system externally and would not use it outside of the home. For home use - I think it's a pretty solid system. And regarding password strength graphic, they do not. I recently stood up a new system using 6.2.6 - not there.
  3. Absolutely. Make sure your write-cache is enabled, this helps with sustained writes.
  4. Ah, right. Then I would check the "write-cache" settings on the HDDs ### for SATA hdparm -W /dev/sd[a-z] # Sample output: /dev/sdb: write-caching = 1 (on) ### for SATA+SAS sdparm --get=WCE /dev/sd[a-z] # Sample output: WCE 1 [cha: y, def: 1] /dev/sdc: ATA ADATA SU800 8B NOTE: WCE = 1 means write cache is enabled You can also SET the "write-cache" bit to enabled (and save): # Set Write-Cache and SAVE the setting to persist upon reboot sdparm --set=WCE --save $disk
  5. Make sure this is set in Settings ---> Disk Settings Tunable (md_write_method): reconstruct write
  6. Let me paraphrase that then - there is a significant user base that is interested in the 2FA/MFA feature to improve the security posture of their environment. Well noted, thanks. Uff, you would really do that? As such, then I would advocate for the ability to set a password policy on the unRAID server. The default should be a more secure option and if someone wants to relax the PP, then an option should be provided.
  7. +1 for 2FA or MFA support. Has anyone submitted a feature request yet? To have this formally tracked? We are all in agreement it needs to happen, has a feature request been submitted? I also would mention that a password policy should be enforced for the "root" user. (I can set a password 123456, which clearly is not a very bright idea). NOTE: Probably TOTP would be easiest to implement.
  8. But if this is reported as a bug, can't developers turn it into a feature request then?
  9. I think a technical control should be implemented here to account for docker presence.
  10. I see. Shouldn't this be documented somewhere or may be as a guardrail be a warning that it can break things for Docker?
  11. Re-pro steps: 1. Create a cache pool, call it nvme-docker-vms 2. configure shares: appdata and system -> set "Primary storage (for new files and folders)": nvme-docker-vms 3. Docker Configuration: Settings -> Docker -> (Advanced View) Docker data-root: directory Docker directory: /mnt/user/system/docker 3. Create and start dockers (more than 1) 4. Stop dockers 5. Go to Tools -> New Permissions -> Disks -> "nvme-docker-vms" -> START 6. Go to Docker -> START ALL Expected: Dockers launch successfully Result: Dockers fail to start NOTE: When starting an individual docker an error is displayed: "Bad parameter" Workaround: 1. Stop docker service 2. Rename "docker" folder to "docker_old" mv /mnt/system/docker /mnt/system/docker_old 3. Start docker 4. Re-add dockers via saved [User templates] section in the 'Add docker' wizard
  12. And apologies for reporting the issue here, not appropriate. This was separately addressed in the proper plugin support thread! And as always - YOU ROCK!
  13. -- Much appreciate, and I apologize for reporting a plugin issue within the release thread. You are correct, should have been done here. As always, THANK YOU!
  14. No issues, fully upgraded two systems - no problems! NOTE: @ich777 : every upgrade NVIDIA PLUGIN resets to "latest: vNNN.NN.NN" option rather than the one that user selects. Is this something that can be fixed? I keep my version as "PRODUCTION" rather than "LATEST".
  15. Then the icon is not in the right place and should be relocated. The top bar menu options should be consistent, adding and removing icons here is not a good practice.
  16. From a UI/UX perspective it would make sense to grey-out an icon rather than hide and show it between different screens that support it. This is a feature request to update this and retain the icon via either greying it out or crossing it off if it is not available. Thank you.
  17. Confirmed. Updated and rebooted, we are back in business!
  18. No stress, appreciate your work on this!
  19. @ich777 , I got a similar error now. Production branch does not work, always falls back to latest. ---Can't find Nvidia Driver vlatest_prb for your Kernel v5.19.17 falling back to latest Nvidia Driver v530.41.03--- --------Nothing to do, Nvidia Driver v530.41.03 already downloaded!--------- ------------------------------Verifying CHECKSUM!------------------------------ ----------------------------------CHECKSUM OK!---------------------------------
  20. Confirmed. Successfully updated to the latest production branch version - v525.116.03. Cheers!
  21. No stress, take your time. I am currently on: 525.105.17
  22. You got it, please see attached. unraid3-diagnostics-20230428-0848.zip
  23. Seeing this notification lately: Production Branch: Not found for this unRAID version!