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.

This thread has some useful information. psa-on-sandisk-usbs

I'm already forwarding port 80 to a webserver hosted on a separate (non-unraid) physical machine. As I understand in this scenario, http validation isn't possible unless 80 is forwarded to the SWAG docker. Correct? I tried using dns validation with godaddy api and see this in the letsencrypt log. Any thoughts? Thanks. 2024-04-06 16:07:28,398:DEBUG:root:Actual zone name resolved for domain nextcloud.example.com: example.com 2024-04-06 16:07:28,398:DEBUG:root:Override resolved zone name because --delegated option is set: nextcloud.example.com 2024-04-06 16:07:28,910:DEBUG:certbot._internal.error_handler:Encountered exception: Traceback (most recent call last): File "/lsiopy/lib/python3.11/site-packages/certbot/plugins/dns_common_lexicon.py", line 250, in _resolve_domain with Client(self._build_lexicon_config(domain_name)): File "/lsiopy/lib/python3.11/site-packages/lexicon/client.py", line 168, in __enter__ raise e File "/lsiopy/lib/python3.11/site-packages/lexicon/client.py", line 161, in __enter__ provider.authenticate() File "/lsiopy/lib/python3.11/site-packages/lexicon/_private/providers/godaddy.py", line 62, in authenticate result = self._get(f"/domains/{domain}") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/lsiopy/lib/python3.11/site-packages/lexicon/interfaces.py", line 162, in _get return self._request("GET", url, query_params=query_params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/lsiopy/lib/python3.11/site-packages/lexicon/_private/providers/godaddy.py", line 338, in _request result.raise_for_status() File "/lsiopy/lib/python3.11/site-packages/requests/models.py", line 1021, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://api.godaddy.com/v1/domains/nextcloud.example.com Not sure if my config is wrong or what, but it seems the api call isn't happy with the subdomain in dot format. A manual api call to this endpoint is not successful (same url from lets encrypt log): https://api.godaddy.com/v1/domains/nextcloud.example.com A manually api call to these endpoints are successful: https://api.godaddy.com/v1/domains/example.com https://api.godaddy.com/v1/domains/example.com/records/CNAME/nextcloud This are my docker options: URL: example.com VALIDATION:dns SUBDOMAINS:nextcloud CERTPROVIDER:letsencrypt DNSPLUGIN:godaddy PROPAGATION: EMAIL:[email protected] ONLY_SUBDOMAINS:true EXTRA_DOMAINS: STAGING:true

I haven't experimented much with split leveling, but it sounds like you want to use top two directories as required. That should ensure all files within "newmovie" are written to the same disk under data/media/movies/newmovie Someone can correct me if I'm wrong. https://docs.unraid.net/unraid-os/manual/shares/user-shares/

Most people set the appdata share to Primary-->Cache; Secondary-->None and as mentioned use the Apdata.Backup plugin for backups to the array.

Precisely why I wish I could connect as a limited user, but I get your point and understand why it's not supported; I just wish it was. I believe I can switch from SFTP to Nextcloud and accomplish my goal so I'll try that first since I already have the Nextcloud docker. A dedicated SFTP docker to transfer this one file isn't appealing, but I'll keep it in mind for the future. Thanks for your input!

Other than because I'm connecting as root, why not? Just to be clear, it's a local lan connection, not public.

Will it ever be a thing? It pains me to use the root user for things that don't require root. I need to use SFTP instead of SMB to transfer a file between mobile and Unraid and the only user that can accomplish this is root. The owner, group, and file permissions are reset to root root 644 which creates problems accessing over SMB on Windows machines. I could set a cronjob to periodically set the permissions, but that's a hack. Is there a better way? -rw-r--r-- 1 root root 23998 Dec 7 23:51 myfile.txt

Yes, but it's not a 1:1 copy of your photos. Originals are saved to the "Storage Path" which is typically an array share. The thumbnails are stored inside the "Data Dir" path which is where the container lives. Most likely /mnt/cache/appdata/photoprism/cache/thumbnails.

We think we understand your layout. In this config, it looks like you'll have an array with a 12tb parity disk and a 10tb data disk giving you a total array capacity of 10tb. Then outside the array, you have a 2tb cache disk and a 10tb unassigned device disk (Project Data). The unassigned device is not in the array and therefore is not covered with parity protection. If all data here will truly be backups of stuff stored elsewhere, then this isn't a bad config. There's no built-in feature to handle backups. Various dockers are out there that can help with this though. Lucky backup is popular. Getting yourself familiar with rsync will help you perform manual file operations. The mover is there to manage files between your cache and array disks according to your share settings. You can review here: https://docs.unraid.net/legacy/FAQ/cache-disk/#the-mover

You're better off writing to the array first (drives 1 & 2)(technically parity and data disk1) and then backing up to project data (disk3). Disk3 would be outisde the array and therefore unprotected. Doing it the other way would mean new files would be susceptible to data loss until disk3 is backed up to array. Keep in mind your backup is still in the same physical system. Consider storing backups off-site also. A single parity disk provides fault tollerance due to physical disk failure of up to one disk at a time. From user perspective, this allows the system to operate normally until a replacement disk can be installed and rebuilt. As said, parity is not a backup. It won't save you from theft, disasters, filesystem corruption, or accidental mistakes like writing a script to move thousands of files and forgetting the trailing slash/ in the destination. Yeah, I did that and it wasn't fun. Luckily I had good backups. Parity protection has performance overhead because every array write must also be written to parity. Using a cache disk allows you to initially write to the cache disk at faster speeds. Those files will be moved to the array off hours through a mover script. Dockers and virtual machines are also typically strictly stored on cache. You can add a 2nd cache disk for redundancy. You mentioned cache as main disk. Not sure what you meant by that.