-
[Support] OpenClaw — AI Personal Assistant
I'm also gettting this error
-
new case with backplane can't see the disks
Yeah I think they're toast, can't get them back on unraid. Thanks mate
-
new case with backplane can't see the disks
I don't think that the are spinning but can't really tell because of the vibrations. I tried 2 others that i had lying around and they do get detected and appear as new drives on unraid, I then took 2 of the non working disks and plugged them on a windows pc and i hear the usb drive sound but they don't seem to be spinning, disk management is asking me to choose MBR or GPT. Are the drives probably dead or can I save them somehow?
-
new case with backplane can't see the disks
Also the drives are not detected in the hba bios on the backplane... The psu is a 650w kinda old but working fine before the change but it doesn't use the original cables, I guess I'll try and buy another one tomorrow
-
new case with backplane can't see the disks
I've also tried with 2 sas sff8643 reverse breakout from the backpland to 4 sata each on the motherboard and are also not detected. The backplane lights up on the disks that are occupied but the system don't seem to be detected. I'm a bit perplexed because now I'm trying and bypass 1 drive connecting sata power and a sata cable directly to the motherboard/drive it's not detected
-
new case with backplane can't see the disks
Hi! So I had server running fine but needed to add capacity and changed the case to an unykach hsw4u6508 that has a backplane, added an hba Broadcom LSI 9305-16i supposedly already in It mode connected with 2 sff8643 to sff8643 and 2 molex for power but now the drives aren't recognized. I also added a 2nd gpu but the hba seems to be recognized on unraid. Here's my syslog so that any gentil soul can help me syslog.txt
-
Can't see drives from backplane
@sebastianklingk hi! Did you managed to get this sorted? I'm having the same problem
-
[Support] Comfyui (Nvidia) Docker
I didn't touch any file, I just updated and got those errors, but I re-ran the update and it seems to have fixed it. Thanks!
-
[Support] Comfyui (Nvidia) Docker
Hi! I'm getting this alerts, how do i update or get rid of them? Version Compatibility Warning: Frontend version 1.25.11 is outdated. Backend requires 1.36.14 or higher. Visit https://docs.comfy.org/installation/update_comfyui#common-update-issues for update instructions. Legacy ComfyUI-Manager data migrated. See terminal for details. thank you!
-
[SUPPORT] blakeblackshear - Frigate
detectors: onnx: type: onnx gpu: true input_tensor: nchw input_dtype: float num_threads: 2 model_path: /config/model_cache/yolox_m.onnx Sorry I forgot to post my config, I did have it defined but still gives me the same error. Tried with float and float_denorm
-
[SUPPORT] blakeblackshear - Frigate
Hi! I'm trying a fresh install with an rtx a4000 and the yolox_m.onnx but I'm getting this error: onnxruntime.capi.onnxruntime_pybind11_state.InvalidArgument: [ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Unexpected input data type. Actual: (tensor(uint8)) , expected: (tensor(float)) any ideas why? thanks
-
dns problems?
I just updated and it's working, I'll report back if anything changes. Cheers!
-
renk1 started following dns problems?
-
dns problems?
I've recently started having trouble updating the plugins/dockers, in the fix common problems pluging it says the system can't reach github and that I should add my router gateway adress and/or reboot the router (which usually works for a few minutes). Here's my routing table, I have my router gateway adress there, is there anything wrong? Thank you
-
[SUPPORT] blakeblackshear - Frigate
While browsing closed issues on github I saw some reports of users pointing that they could only run models up to 320 so I changed to yolov7-320 and it seems to be stable. thanks @yayitazale
-
[SUPPORT] blakeblackshear - Frigate
Correct if I'm wrong but in the logs it mentions some gpu stats for a few seconds before the python segmentation fault, doesn't it mean that is being used? Also, on the frigate gui I could see rtx a4000 utilization on the bottom. I'm using the Nvidia Driver Version: 570.153.02 from the production branch, I'm using the tensorrt branch and already added the --runtime=nvidia , corrected the tensorrt part like you recommended and I'm still getting the same error... I also ran nvidia-smi and it seems fine I think EDIT: don't really know if there is anything else I have to do regarding gpu passthrough
renk1
Members
-
Joined
-
Last visited