UBS
-
Posts
14 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by UBS
-
-
18 hours ago, JorgeB said:
Controller is being initialized correctly, but then fails to correctly detect the disks, there's also issues with this disk connected to the onboard SATA controller:
Model Family: Western Digital Black Device Model: WDC WD4005FZBX-00K5WB0 Serial Number: V3086S8FCheck/replace cables for the disk above and move one of the working disks, e.g. parity, including the SATA cable, to the Asmedia controller and post new diags
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!
-
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.
-
1 minute ago, ich777 said:
I have a few users that reported such an issue, most of them solved it by uninstalling some unnecessary pacakges installed by the Nerd Pack. I really don't know what the issue here.
Simply search this thread for your error (not the whole but the part with OCI... and you will find a few posts.
The first issue like yours IIRC came up on Unraid 6.9.2 but what it caused I really don't know, I also was able to once reproduce the issue but only once.
I will update if I will find any new information
-
1
-
-
23 hours ago, ich777 said:
I really don't know because I don't use it.
Maybe it messes with Docker or changes some kind of runtime. What is the output of:
cat /etc/docker/daemon.json
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 helpthanks again for your help !
-
10 minutes ago, ich777 said:
I really don't know because I don't use it.
Maybe it messes with Docker or changes some kind of runtime. What is the output of:
cat /etc/docker/daemon.json
root@UNRAID:~# cat /etc/docker/daemon.json { "runtimes": { "nvidia": { "path": "/usr/bin/nvidia-container-runtime", "runtimeArgs": [] } } }i will continue tomorrow , appriciate tyor kind assistance !! ⭐
-
1
-
-
5 minutes ago, ich777 said:
Have you yet tried to reboot?
Oh, can you try to force an update from a container which is affected. Also please make sure that you uninstall any packages installed through nerd pack IIRC one user has had an issue where he had installed a extra package which causes the same issue.
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
-
4 minutes ago, ich777 said:
Have you yet tried to boot with Legacy (CSM) mode?
The issue with the VM should be unrelated to that, but please maybe try to reboot.
Also make sure that you've disable C-States in the BIOS and also make sure that you enable Above 4G Decoding and Resizable BAR support in your BIOS.
This issues occure most of the times on AMD systems, I'm not 100% sure what's causing that.
Did you recently update the BIOS or anything similar?
i will update during weeked -as i need to take the server out of the closet for these steps
-
1
-
-
14 hours ago, ich777 said:
Do you run the script from SpaceInvaderOne?
Please remove that script, reboot and see if it's the same.
If that doesn't help, please go in the container template from a affected container change something and change it back so that you can press the Apply button and see if anything changes after pressing Apply.
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.
-
On 10/30/2022 at 3:43 PM, ich777 said:
Please post your Diagnostics.
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
-
1 hour ago, sailingbikeruk said:
I have V2 from https://github.com/gawindx/WinNUT-Client
Are you using NUT on Unraid as the Server or is that a client with the NUT Server somewhere else? I'll try as you suggest and see if I an get it to work
try to fill UPSNAME@IP format in address
-
may i ask please - this provide any functionalty difference from the native wayn of makeing share for use in timemachine?
-
11 hours ago, agh1701 said:
Yes, been having the same problem. Reported it here.
6.10-RC5 and up Waiting 30 sec for device with label ...
A power off seem to fix it.
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
-
got this after updat - picture attaced
Lenovo thinkstation P620
Help with ASM1062 PCIe on Lenovo P620 - Cannot See Attached HDDs
in General Support
Posted
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