dboonthego

Figured it out, was missing "amd64-version-" and turns out I needed 4.10.0, not 4.1.0. lscr.io/linuxserver/lychee:amd64-version-v4.10.0

Is there a method to pull an older image? Somehow my container has been updated to latest 7.x, but the database is expecting version 4.1.0 and fails to load and migrations fail. If I can, I'd like to try getting the lychee container back to 4.1.0 and attempt step upgrades from that point. I tried using this but fails. Any ideas? lscr.io/linuxserver/lychee:v4.1.0

It looks like it was removed starting from OS 7.1.0 just over six months ago. https://docs.unraid.net/unraid-os/release-notes/7.1.0/#rolling-back

Just a suggestion to make these instructions more "clear," pun intended. Finding that red X is a challenge if one is focused on UD settings instead of UD Preclear. A precleared disk will appear with a grey "PRECLEAR" button in Unassigned Devices, indicating that the disk contains a preclear signature. If you plan to assign this disk to the Unraid array, you can do so directly. Unraid will recognize it as precleared and will not run the clearing process again. However, if you want to format the disk for use with Unassigned Devices, follow these steps to remove the preclear signature and prepare the disk for use with UD: Navigate to Plugins → Unassigned Devices Preclear, and click the red "X" to remove the preclear report — this enables Unassigned Devices to manage the disk normally. Then in UD, click the red "X" next to the disk’s serial number to remove all existing partitions. After this, the "Format" button will become available, allowing you to choose a filesystem and format the disk for general use via Unassigned Devices. Once the disk is formatted, the "Mount" option will become available.

Only having 3 attached devices, I didn’t need to purchase a Basic → Pro license upgrade for my backup server—but I did it to support a product that’s been rock solid for the last 15 years. Thanks for the quality and dedication. Here’s to many more! 🍻

I purchased this one recently which has unique GUID to replace the failing flash stick on my backup server. It's 16GB and USB 2.0 which is perfect for Unraid OS. I can't speak to longevity since it's new, but so far works as expected. I also like the smaller physical size and is not big and clunky since it is plugged into the back of the server. You can build the new flash stick and and copy the /config folder from old to new flash to retain your server settings if you want to carry them forward. Or, you can just start fresh. Then you can purchase a new license using the GUID of the new flash.

If you own what's now classified as a legacy license (Basic, Plus, or Pro), it means you purchased it on or before March 27th, 2024. If you received the upgrade offer via email, you currently hold either a Basic or Plus license. The cost to upgrade these legacy licenses is increasing as follows on June 2nd, 2025: Basic → Plus: $59 → $89 (increase of $30) Basic → Pro: $99 → $139 (increase of $40) Plus → Pro: $69 → $109 (increase of $40) If you purchased a Starter, Unleashed, or Lifetime license, you did so after March 27th, 2024. This upgrade offer does not apply to those licenses.

Upgrading Unraid OS from 6.12.9 to 6.12.13 resolved it. I found this thread indicating a bug fix in 6.12.10. Thanks for the reply.

Something is definitely strange. The folders contain a single file. I can create a dummy file ex. "dummy.txt" inside each folder and both files appear. If I subsequently delete the dummy file, then it goes back to empty.

First time creating a remote SMB share using UD. I created a read-only mount from my Unraid test-->main server and it mounts fine. When browsing the remotes folder either from SSH or Unraid GUI, some folders are seen as "empty" even though they contain data. UD sees the folder, but no files inside. The permissions are identical to the files/folders that display correctly. I don't have the cache dirs plugin, but do have Dynamix File Manager on the test server. Any ideas?

Thanks for the confirmation. Note to self... 🙂

Looks like an active ssh session was open to the server. That's probably the cause. Thanks!

Not the end of the world, but the system wants a parity check after upgrading to 6.12.13. I kicked off the upgrade from the update check gui. Afterward it said successful and to reboot. I clicked Done and was prompted with option to reboot. Clicked reboot and when it came back up, starting array wants parity check. Seems like the reboot didn't gracefully stop the array. Normal?

As work-around you can untick "email" for each notification type under "Notification Settings" and/or remove the mail server and user credentials from the smtp config.

Of course, figure out the health of the drives first, but if they are in fact toast, you can build vaild parity from the remaining good disks by doing Tools-->New Configuration. You can re-order/re-assign the slots, however be absolutely certain the parity disk is assigned correctly in the parity slot. It should allow you to copy from current assignments. The new config will reset other disk settings like spin down delay etc, so you might want to make note of existing settings first.