FreeMan Posted March 4, 2023 Share Posted March 4, 2023 Fix common problems has reported that "Invalid folder addons contained within /mnt". This is an old machine that was just restarted after being out of service for > 1 year. I'm pretty sure that it was on 6.x when last booted, but that's as detailed as I can get. In my backup server, I've got /mnt/addons, but do not have an "addons" directory on my main server that's been running and kept up to date quite regularly. Is this the invalid directory that it's reporting? backup-diagnostics-20230303-1925.zip Quote Link to comment
dlandon Posted March 4, 2023 Share Posted March 4, 2023 An update to UD created that folder. FCP is detecting it now. Update FCP. Quote Link to comment
Salzgablah Posted March 4, 2023 Share Posted March 4, 2023 I'm in the same boat, error just popped up after the most recent UD update (2023.03.03). Now I've updated all plugins including FCP but there error remains. Should I just "ignore error"? What's next step? Quote Link to comment
dlandon Posted March 4, 2023 Share Posted March 4, 2023 Ignore it, or wait for another FCP update. Quote Link to comment
Salzgablah Posted March 4, 2023 Share Posted March 4, 2023 Perfect. Thanks for the advice! Quote Link to comment
ronin688 Posted March 4, 2023 Share Posted March 4, 2023 Just had this error in FCP as well. I went googling for answers and found this thread. Ignored for now. Thanks for posting about it, I just recently updated to 6.11.5. from 6.9.2 and was worried it was somehow related. Was happy to see this thread was only 6 hours old. Quote Link to comment
Nacho1545 Posted March 4, 2023 Share Posted March 4, 2023 Thank you all for posting. I had the same error and am new to unraid. So we don’t need to try and delete the addons folder? I tried several times and can’t get it to delete. so just ignore I guess? Quote Link to comment
FreeMan Posted March 4, 2023 Author Share Posted March 4, 2023 12 hours ago, dlandon said: An update to UD created that folder. FCP is detecting it now. Update FCP. That might just make sense. I just took a look at all my plugins and I'm running versions dated between 2017 and 2020. Told you this machine was just being recommissioned after a long period of inactivity. I'll update all plugins before asking any other questions... Quote Link to comment
Salzgablah Posted March 4, 2023 Share Posted March 4, 2023 The new unassigned devices creates the folder and the current version of fix common problems does not have an exception listed for the new folder. Once it's updated, the error should go away. Don't think you'll be able to remove the folder unless you remove unassigned devices plugin. 1 Quote Link to comment
wtmsvw Posted March 4, 2023 Share Posted March 4, 2023 This Community is great !! Ran into this issue this morning and went to work worried, Now I can focus on work. 🤣 1 Quote Link to comment
Moparman371 Posted March 4, 2023 Share Posted March 4, 2023 I had the same problem. Was scratching my head because I woke up yesterday to a server that wouldn't boot due to another power blip no thanks to my lousy electric company. (A new Full Sine Wave UPS is on it's way LOL!) Just when I thought I had it all straightened up and flying right... This error pops up. Anyway I just updated FCP and all is well! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.