kerbys

Ok, I didnt give full info. I was using P4's and an A400. everything just decided to break for me

Just fyi I swapped from p series cards to arc as the p series are now legacy and no longer supported by drivers

Dude! do you have a coffee link or something, What a legend!!

Attached. I have 2 gpus and a couple dockers going for testing to show activity intel_gpu_top -J -n 2.txt

I have the same as above with a A40 Pro. If i open top it shows 3.5% on the compute but the plugin just shows 1% on video at all times. Im on unraid 7.1.2. When i go open top as shown in the screenshot, i think there could be a larger problem with unraid ARC drivers, as this shows incorrect info.

OK Thank you. was only asking as your previous post said 6.12.

Do we know when this is coming as still not in latest update?

What version driver should i be using if i have pascal (p4) and RTX4000?

Necro'ing an old post, but interested if you are working on this?

Thank you anyway, If i get to my colo ill try to remember to update the thread.

I didn't do any changes to the BIOS. Hardware, I did make changes days before it stopped working, but it just decided to unregister itself. Im not 100% that it hasnt just "died", but since ive got this in my colo which isnt easy to get hands on with currently. Was going to try some testing before i go the hands on route. Since others have seen similar problems, also the device is seen in the hardware list. If you are just as confused as me ill wait till im next onsite and ill bring the card home :)

I've been seeing this issue for a few weeks, however haven't had time to diagnose it. Jun 17 08:54:09 Kerbyserver kernel: NVRM: GPU 0000:01:00.0: Failed to copy vbios to system memory. Jun 17 08:54:09 Kerbyserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x30:0xffff:976) Jun 17 08:54:09 Kerbyserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 1 I have a A4000 - This is working fine, the A2000 suddenly dropped off one evening and I can no longer see the card in the nvidia plugin. Ive tried production branch, new feature and latest. All give the same error. I cant see any issue with Bios settings. Im pretty sure this happened very shortly after my update to 6.12.10 kerbyserver-diagnostics-20240617-0854.zip

I know this is abit of a thread revival, however i upgraded to this firmware but seeing so many CRC errors. Disks are going up and down like anything. Did you ever resolve it?

So im still getting the dreaded busy DB - Walls and walls of below. Ive resorted to a restart of the docker every morning at 5am to clear it. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Now i have the docker configured to /mnt/cache/appdata/plex. This is sitting on 2x 2tb nvme drives (samsung 970 and sabrent for abit of fault tollerance). i cant see how its endind up with a busy db as it has plenty of IO. any advice for me to look into next?

Sorry what i mean is in the docker safe new perms i had accidentally added my main media storage to not be touched. Now i cant remove that. ive tried ticking and unticking but it never removes itsself.