5252525111

For those running CP.AI using the gpu docker container. It seems like CP hasn't been building it for about 5 months. What you can do is change it to a cuda container and have the latest version. Simply update `codeproject/ai-server:gpu` to one of the following depending on your GPUs capabilities. - `codeproject/ai-server:cuda11_7` - `codeproject/ai-server:cuda12_2`

You need to create a new variable in your configuration, click `add another path, port, variable, label or device` and choose `variable` set key to `NODE_ENV` and value to `production` and it should work after that.

Change setting under 'Settings > Global Shares Settings' look for Tunable (support Hard Links): and set it to No.

Found this somewhere, has anyone tried this?

So far it's holding up well. I'm having new issues with NFS but don't think that's related to this at all. Long story short, no more panics. That was one of the main fixes for me. I used a range outside my DHCP and reserve that for containers on unraid. If I recall correctly since I currently don't have access to my system, 100-223 is my LAN range, 50-99 I used for static and 224-255 (192.168.99.224/27) I reserve for containers on unraid.

referencing that my issue might be related to this

Sadly I use NFS everyday. Will see if I can find an alternative for my other devices. I'll look into what limetech suggested and set "Settings/NFS/Tunable (fuse remember)" to 0.

adding latest log. tatooine-diagnostics-20211006-2222.zip

noticed this. Not sure what would cause this to happen. d????????? ? ? ? ? ? user/ drwxrwxrwx 1 nobody users 71 Oct 6 16:15 user0/

I've attached my logs in hopes someone can help. 30 days is the most I've ever managed to get unraid to not crash. But the past couple days I've gone back to daily crashes. This time it seems to crash my shares and containers but the gui is still responsive. After a reboot everything is fine again. No hardware changes or new software I can think of. From my limited understanding, the logs are saying the docker network crashed? Any advise is much appreciated. EDIT: Updated title from "6.9.2 I've been running stable for 30days and now daily crashes." to "6.9.2 30 days stable, suddenly unraid unmounts /mnt/user" tatooine-diagnostics-20211005-1600.zip

Followed the drive. Swapped it out and seems to be good now. Thanks for the help!!! Much appreciated.

tatooine-diagnostics-20210510-1346.zip New diags

Just started copying everting back to the pool already have this Tatooine:~# btrfs dev stats /mnt/app_cache/ [/dev/nvme0n1p1].write_io_errs 129163 [/dev/nvme0n1p1].read_io_errs 0 [/dev/nvme0n1p1].flush_io_errs 3 [/dev/nvme0n1p1].corruption_errs 0 [/dev/nvme0n1p1].generation_errs 0 [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 0 [/dev/nvme1n1p1].generation_errs 0 I take it, it could be a failing drive. Specifically `nvme0n1p1`?

Thanks @JorgeB. I put `nvme_core.default_ps_max_latency_us=0` in and decided I may as well do a BIOS update. The cache pool was still read only, but I've back everything up and will be formatting the drives. Hopefully it won't occur again.

ran the btrfs stats. seems like both have numbers there. Tatooine:~# btrfs dev stats /mnt/app_cache/ [/dev/nvme0n1p1].write_io_errs 2350795 [/dev/nvme0n1p1].read_io_errs 953269 [/dev/nvme0n1p1].flush_io_errs 74132 [/dev/nvme0n1p1].corruption_errs 9861 [/dev/nvme0n1p1].generation_errs 0 [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 239 [/dev/nvme1n1p1].generation_errs 0 Is this a btrfs issue or M.2 issue? should i be looking to replace my NVMEs?