UBS

Members
  • Posts

    14
  • Joined

Everything posted by UBS

  1. I will try on my intel pc, my obvious suspect - is the LENOVO motherboard with that weird BIOS with limited options... that is what I suspected to begin with but its just a guess I will update after results
  2. First of all, thank you for your assistance! Regarding the hard drive in question, do you think it might be defective? It's a brand new disk, but I've noticed it doesn't report temperature or initiate the pre-clear process. If it's indeed faulty, I'll have to return it for a replacement. To further troubleshoot, I disconnected a known working hard drive (the one serving as parity), and swapped its cable and input location (from the motherboard to the ASM1062) with the "non-working" HDD. Now, I see three visible unassigned disks in the system. Could you suggest any additional checks to further diagnose the issue? I've attached the diagnostic file for your reference. Thanks again for your help! unraid-diagnostics-20230614-1438.zip
  3. Hello dear forum experts, I am trying to add a few more hard drives to my server. It is based on the Lenovo P620 workstation, equipped with an AMD Threadripper Pro 3945WX processor. Currently, I have five hard drives attached directly to the motherboard, which still has one spare SATA slot available. I'm using an AXAGON expansion card based on the ASM1062 chipset in a PCIe slot. I can see my m.2 NVMe drives and the five hard disks that are directly attached to the motherboard in the system. Additionally, the PCIe expansion card is listed in my system hardware. However, I cannot see the hard drives that are attached to this expansion card. I have attached the hardware diagnosis, hoping that someone may help me find out the problem and fix it. I've tried altering various BIOS settings, including the PCIe speed and others, but to no avail. I appreciate your help in this matter. unraid-diagnostics-20230613-2012.zip
  4. I will update if I will find any new information
  5. hello again, now containers starting with nvidia runtime... but like I'm not sure how it started - I'm also not very sure how it's now fixed so I removed the GPU statistics add-on went to nerd tools and these packages were installed (not by me, not sure why) and updated them: 3. reboot 4. fixed... by maybe one of these actions... but I have a feeling that I'm not finished with this problem as I don't know how to not make it occur again i attach a new diagnostic from after i got it working in case this may help thanks again for your help ! unraid-diagnostics-20221104-2336.zip
  6. root@UNRAID:~# cat /etc/docker/daemon.json { "runtimes": { "nvidia": { "path": "/usr/bin/nvidia-container-runtime", "runtimeArgs": [] } } } i will continue tomorrow , appriciate tyor kind assistance !! ⭐
  7. rebooted many times, tried force update as well, no new bios or HW changes on my side. i do have many plugins and i will check if nerdtools may be the reson, i had it only for pearl (temp) you think maybe Portainer-EE maybe reason ? I changed from CE as they gave free license
  8. i will update during weeked -as i need to take the server out of the closet for these steps
  9. first of all thank you for quick response ! as for the issue, i have removed SpaceInvador P8 power state script, restarted, and re-OK'd a docker template to make sure its updated... but still all the Nvidia runtime are not starting and showing the same: docker run -d --name='HandBrake' --net='dokernet' . . . . . . . -removed by me . . . . --runtime=nvidia 'zocker160/handbrake-nvenc:latest' e2eeca1ec513824709bbf7e3be1241e0fb39845ad1ffe943f40d675804be4746 docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #1: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: initialization error: open failed: /proc/sys/kernel/overflowuid: permission denied: unknown. The command failed. appriciate your help Uri ----------------EDIT--------------------- OK now I see there is a problem with my one of my virtual machines - so I think it is wider spread than just the Nvidia containers. I will have to dig into it. I will update when I find a solution.
  10. I have the same issue, and it started all of a sudden. may be a recent plug-in update made it, as it was originally working on 6.11.1 unraid-diagnostics-20221103-0008.zip
  11. try to fill UPSNAME@IP format in address
  12. may i ask please - this provide any functionalty difference from the native wayn of makeing share for use in timemachine?
  13. thank you, it is fixed maybe it is also related to un-assigned devices plugging it got an update... 🤕I now have a different problem
  14. got this after updat - picture attaced Lenovo thinkstation P620