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.