jessielw

Overview: Support for image Reclaimerr Application: Reclaimerr Image Repository: https://github.com/jessielw/Reclaimerr/pkgs/container/reclaimerr Documentation: Reclaimerr

Thank you

Hello, I submitted a template to CA > 30 days ago. I wasn't sure if this was still being managed or if Squid has some IRL stuff etc. Just wanted to see if there are any other users that manage this or if there is anything else I need to do. https://forums.unraid.net/topic/196057-support-jessielw-mp4forge/ Thanks!

I run all of my self hosted stuff from UnRaid including Plex and Jellyfin

Congrats and welcome!

Overview: Support for image Mp4Forge Application: Mp4Forge Image Repository: https://github.com/jessielw/MP4Forge/pkgs/container/mp4forge Documentation: Mp4Forge

Is there anyway to spin down my external hdd attached via USB using this plugin on the default Unraid spin down timer?

Just updated from 6.12.15 to 7.2.1 and the WebUI is pretty slow sometimes. It's intermittent, can load for like 20 seconds, sometimes like 4 seconds, sometimes it's instant. Pre-update it was pretty much instant no matter what.

I just got my server back online after the flash drive died. Unfortunately UnRaid Connect had just grabbed a backup from the flash drive and was corrupt. I was unable to boot from that backup no matter what I tried. It simply wouldn't boot or if I used Rufus it would boot but the webui wouldn't do anything. Thankfully I have a user script CRON job running to back up the flash drive to gdrive every 3 days and I was able to directly use the backup from my most recent one.

Sorry to hear that. Maybe one day this will be resolved, but I wouldn't count on it very soon it appears.

Fingers crossed, but it is inevitable and random. I went for days to weeks and ever over a month with no failures with it coming back always.

Firmware doesn't matter in this case. I tried different variants of the drive, they simply don't work well with UnRaid/Kernel/HW we have. I have a buddy that just has to use the command and it fixes his. Once I get to a file or something that causes the error, it can be reproduced. However, it's random when it hits a file like that. Also update for the dongle. The dongle was stable for along time, but I ended up having a failure today. It was a different error but I have no doubt it was related to this. So there is no actual good work around for this. Grab yourselves a WD drive for UnRaid I guess. Today I took the secondary storage drive out of my general use/game/work pc (was a WD black 1tb) and just slotted the 980 Pro 2 TB in it's place. I'll just take the storage amount loss on the drive and quit worrying about it.

I'll make a new post in case anyone was following the above issue... I ordered the above dongle and put my Samsung 990 Pro 2TB and ran the same work flow as before that was making the error happen and everything appears to be working great. It has completed a long long version of that work flow. I went ahead and tested the previous drive Samsung 980 Pro 2TB (in the dongle) and did the same work flow where it would have crashed on the motherboard. On this dongle both drives are working flawlessly. Speed testing this dongle I'm getting around 3GB's read and 1.5ish GB's write speed (it could just be the test I am doing that is limiting them), so it's plenty fast and good enough for me. I'll report back if I have any more of those errors at all with this configuration. EDIT: 27 hour job completed with that drive on the dongle. EDIT2: Another 12 hours of jobs completed. Appears stable to me.

Both of my problem drives worked great in Windows and even testing on Ubuntu. So it has something to do with the hardware/kernel/unraid. I am not 100% sure what this might be. Tomorrow my USB 3.1 NVME enclosure comes in, I'll report back and let you know it it resolves the solution for now. EDIT: I am updating UnRaid to 6.12.11 to see if the kernel fixes might have any relevance to this issue. EDIT 2: Job failed with same bug. I'll report back with results of the USB 3.1 NVME Enclosure.

Update: after nearly a month of running well the same error came back with the new drive (Samsung 990 Pro 2TB) in the 2nd slot of my motherboard. I'm going to grab this enclosure to try to use a work around until a newer kernel. I will update everyone when I get it and to see if it solves the issue as a work around for now.

Perhaps you could buy a reputable usb 3.1 adapter to install it in and see if that can get you by in the mean time. I was going to do this but ended up finding a solution that worked for me.

Updating this, it was the change to the Virtio from Virtio-Net that caused the issue!

Docker custom network type: ipvlan It might be due to the fact that my VM was set from Virtio-Net to Virtio. I changed it while I was testing things a few weeks back and I completely forgot about it (it did give me a massive throughput boost), I will swap it back and see if it's stable and I'll report back here and let you know if that was the cause.

I've had a rare crash, happens once every week or so. I logged the syslog to storage so I could attempt to figure out what exactly is causing it. I'll include the full logs from today (when it crashed) and hopefully someone here can help me out! I looked over it and can't see anything that jumps out to me, other than what appears to be a <task> that is failing. july5th.txt

Ultimately my issue was solved by swapping the drives around on the board. Looking at the bug tracker for the kernel (I posted above) there is simply just a bug causing this. UnRaid is several kernels behind and the fix won't be in UnRaid for a while. I can confirm I tested this solution with both a Samsung 980 Pro and a Samsung 990 PRO (2 TB). Since making the change I've ran about 150+ hours of encoding off of the drive and it's been rock solid.

I've read through this thread and got things setup to try to mitigate an issue when using my nvme over share to the VM that keeps happening here https://forums.unraid.net/topic/164041-does-your-device-have-a-faulty-power-saving-mode-enabled-nvme-issues/#comment-1422896. On AMD (5900x x570), the speeds are terrible. Around 55MB's, but I might stick with this for the stability for now. When the drive is in use it seems to hit a single thread. EDIT: Didn't resolve the above issue (not related to this), but yeah the speeds wasn't worth it.

Update: replaced it for a Samsung 990 Pro 2TB. It initially did really well, but I just got the same error. I will reboot and try to apply the line `nvme_core.default_ps_max_latency_us=0 pcie_aspm=off` and report my findings. Edit: Update, made no difference. Seems like the issue happens when the drive gets > 1gb of files on it. EDIT 2: So I swapped the NVME's around. In M.2_1 I had another NVME (different brand), this was directly connected to the CPU lanes. In M.2_2 I had the Samsung NVME, this is connected via AMD's chipset. It appears that it might have resolved the issue. I'll report back. EDIT 3: Looks like this resolved the issue. So I assume it has to do with the linux kernel, samsung drives (tested 2), and AMD's chipset. The same drives that was failing in the top slot of the motherboard directly connected to the CPU lanes, is working perfectly in all tests.

My buddy has a similar setup to mine and he has a Samsung 990 Pro, I think I have Samsung talked into trading out since i provided error messages and stuff again. Thanks for the information on this! I'll report back here when I get the new drive and let everyone know if things are stable.

Unfortunately, I am past return period to get a different drive. Do you think just putting it into a USB enclosure would resolve this issue? https://bugzilla.kernel.org/show_bug.cgi?id=218455 The issue for this was resolved in kernel 6.9, UnRaid's kernel is far behind. I know there isn't anything that can be done about this, but I appreciate the help. I might try the USB enclosure as a way to use the drive for now.