mainart1955

Okay, checking some of the docs answers some questions but raises some others. From what I understand files in unraid should exist on either the cache or the array (but usually not both). The "prefer" setting means, as long as there is room on the cache, the data will only be on the cache, and that should stop the array from spinning up. Does all this sound correct so far? The question raised is how do you get data stored on a cache (with prefer or only setting) copied to the array as a "back up"? For example it seems like the "appdata" share holds some important data that needs to be protected if (when) the cache drive fails. It would be desirable if unraid had a "mirror" or "write-through" setting where data would be written to the cache but also to the array and when read it would only need to read from the cache. Thanks - and if you think I'm still not understanding some of this, please point to some sections or things I can search for in the documentation.

A docker based app is causing the array to spin up once every hour. If I stop or pause this specific docker app then the hourly array spin up doesn't occur. It stores data in /mnt/user/appdata/<docker_app_dir> and the appdata share cache setting is "yes". I just need to figure out how to use / configure unraid to prevent these hourly spin-ups. Any ideas on configuration settings, which cache folder etc. I should try?

But accessing the array and causing the drives to spin-up every hour isn't a unraid feature. I don't think that relocating appdata/mealiev1 directory to another place that gets cached can prevent that. After changing appdata so it is cached, the array still spins up if the mealie docker is running. If these hourly spin-up's are unavoidable my only resort is to remove the mealie docker - I can't have a recipe app causing the drives to turn on every hour, forever. Is this a docker / unraid issue or a mealie issue? So really I would like to know if you have any ideas on how to prevent it from doing this every hour. Pausing or stopping the mealie docker is also an option but makes the app less convenient since this would require logging in and restarting the docker app every time to use it then manually pausing or stopping the docker again when done. Adding a small computer / server which could also house mealie and other apps is a better option and there are several available for under $100 - less than the price of just one NAS drive. This would prevent drive failure by avoiding hourly spin-up's, unless there is a setting to prevent it from happening. I do appreciate the support you've been able to provide on these issues.

Okay, I'll look up docs to research moving the mealie appdata folder and SQLite. Alternately, maybe I can do a mealie backup, delete / uninstall, then re-install with a specific folder to use instead of the default then restore the data. In the worst case I don't have a huge amount anyway so could start over after re-installing if needed. I believe the email settings are okay. But the email test hangs, and the reset password doesn't work. So, that's why I have been hoping there is a log file containing what's happening when Mealie is trying to do the email test. I had to generate a app password, so the mail provider is designed to allow 3rd party app access. What about the issue with Mealie causing the array to spin up every hour? I paused the Mealie docker and as expected the drives are no longer spinning up every hour. If there is no way around this issue then I'll probably uninstall the Mealie docker.

"MyPassword" for the password worked so I was able to login. Additional questions: There is a "Logs" for Mealie in the Docker page of Unraid. It doesn't have much in it but there are repeated entries like: 127.0.0.1:58638 - "GET /api/app/about HTTP/1.1" 200 OK in it. Looks like a new one is added about every 30 seconds. I hope this log isn't stored on the array where its adding these entries twice a minute. The most disturbing issue is that after installing the Mealie app docker, my array discs are spinning up once an hour, whether I'm logged in to Mealie or Unraid or not. What needs to spin the drive up every hour and how do I turn this off? Spinning the drivee up and down like this is unnecessary wear and tear on the drives.

Okay - thanks. A) Someone else in this support forum asked about the database and you suggested staying with SQLite so I had to assume there was a way to change it. B) Is SQLite installed in the same Docker as Mealie? I didn't install SQLite so it must be installed with the Mealie docker - so the question is still where is the data C) On the appdata folder, it was already set to not use the cache so it looks like that is how unRaid wanted it set to not cache - I wasn't sure of why or if its okay to make it use the cache. That's why I want to know how to just relocate the mealie folder under appdata. D) I believe the email settings are correct, That's why I would like to see if it stores anything in a log file that I can use to debug the problem. Since email isn't working and I've forgotten my password I'm unable to login to change the email settings anyway at the moment and will probably have to delete and reinstall.

I'm fairly new with unraid and docker in general and need some help installing and configuring. (a) the Mealie website pages mention different possible databases, like SQLite and Postgres, but how do you set which one with this unraid Mealie docker? Its not in the settings page. (b) how do you control where the recipe data is stored in case I want it on a specific drive and directory? I've already installed and added a few things - can I just move the directory and change it in the settings? (c) The default path looks like it came up as /mnt/user/appdata/mealiev1 (I didn't notice that at first). But my unraid system shows the share "appdata" does not use the cache pool. In order to avoid unnecessarily spinning up and writing to the drives how do I safely move data storage to a different location so it will use the cache pool. It doesn't make sense to be doing a ton of writes to the array as I'm adding and editing recipes - that should all be done on a cache drive. (d) The test did not work so something is wrong but how do I debug why mail isn't working, does it write information into any log files to see what is failing? Thanks for any assistance - those are the more pertinent questions but there might be more later on.

What is the status of the StandardNotes unRaid docker app? There are a couple forum entries related to Standard Notes but I don't see anything conclusive. I was hoping to be able to run StandardNotes on my unRaid server and use it as the sync server with standard notes on all my devices. Are there any detail instructions for installing the StandardNotes docker and getting this to work on unRaid? For example I believe a different person mentioned needing to install a DB like MariaDB to get StandardNotes running as the server, but I don't see that mentioned on the StandardNotes app description.

Ah, okay thanks for the clarification. I had planned for using the Unraid array for backups of some other devices too.

Are you saying unraid should not be used for backups? Since unraid, RAID, or other NAS, can get huge what would you use for backups of the arrays?

Ok, it looks like there are different ways data can be stored. What is recommended based on useage, disk sizes, number of disks, MTBF etc. There are going to be tradeoffs like using more smaller disks has a higher chance that some drive will fail, but a smaller amount of data is on the failed drive. Having a lower number of drives means a lower chance of a drive failure but when one does fail more data is at risk. Example - which is better: System 1 has four 4TB drives (12TB data, 4TB parity). System 2 has two 12TB drives (12TB data, 12 TB parity).

I want to build a new Unraid server and want to start off the best way. Should I look for ECC memory or non-ECC ? I am starting with an AMD CPU - which requires a "Pro" version to support ECC. Because of that there are limited options but for example I can get a Ryzen Pro 7 4750 or a Ryzen Pro 5 4650 within my budget. Part of the use of the Unraid server would be for backups so data integrity is important. A database like mySQL for some large data, maybe a VM or two. Should I get a CPU supporting ECC, like the Ryzen 5 4650 for hopeful data integrity or go for ease, speed and cost benefit like a Ryzen 7 5700G?

While doing research to build a new Unraid server for my home and small business, I'm hitting some questions. One area is disks - I could get higher capacity disks like 12TB or smaller capacity like 4TB. For a while, at least a year or likely longer, I could start with four 4TB drives (12TB data) such as Ironwolf at $75 and could buy a spare too. Or I could go with 12TB Exos manufacturer recertified drives at $110 and could get up to four of them. So say I buy four of the 12TB Exos drives. I could: (A) start with two 12TB drives in the system, keeping two as spares and adding more with failures or growing storage needs, Or, (B) put all four in at the start and buy more to replace failed ones along the way. How is say 6TB of data stored in case (A) vs case (B)? If there are four drives does Unraid spread storage across them or does it fill one drive first then start filling the others? Alternately buy four or five new 4TB Ironwolf drives and (C) put four in the new system right away, or (D) put 2 or three in and save the rest as spares or expansion Is it always better to buy and install the biggest capacity you can afford - even if there's a possiblity it will be unused for a long period?

Greetings, I am new in this room and don't have Unraid experience. But since my server is not built yet, there is an opportunity to start off on the best foot. Also, even though it might be like 4-letter words here, I could consider straight raid 1 or TrueNAS if anyone thinks those fit better, but from my own reading think unraid will fit just fine - with a couple questions. Planned use is personal and very small business use for backups, media server, file transfer, and then as a database server with either plain file and mySQL DB. It will only be me accessing the DB so high performance isn't an issue. Over a few years the DB and overall storage could grow to several TB, potentially over 30TB. My biggest questions are (1) should I configure the components for ECC memory or non-ECC? and (2) since initially huge storage isn't needed should I look for more smaller drives then upgrade over time or start with a lower number of bigger drives. Some price range info is a little further below and, importantly, price will be driving my decisions. I can give up some performance for cost but don't want to go too far. On ECC: Should I pick ECC or non-ECC? From both reading and looking for parts, the AMD Ryzen series has limited CPUs to support ECC, in my price range, which is trying to limit the CPU cost to under $200 at the beginning - I can upgrade the CPU later if needed. This means I could go with a Ryzen 5 Pro 4650G (supports ECC) or a Ryzen 7 5700G (non-ECC). Memory price between ECC and non-ECC is near the same - I found both ECC and non-ECC DDR4 at almost the same price so the decision really is the CPU. On HD's: How should I begin the selection of HD's? In the first few weeks there will probably only be around 5TB or less used. Over time, say 2 years maybe, there might be 10TB to 15TB - I have some use plans but don't really know for sure, it could be more or less. I am trying to not overspend at the start (probably obvious since most people aren't looking to waste money...) but am not sure how to get the full picture on this due to all the tradeoffs. There are server class manufacturer-recertified drives for great prices - like 12TB seagate exos for $110 or 14TB WD Ultrastar for $135. Then on the smaller side there are new 4TB seagate ironwolf drives for $75 From what I've read the Exos, Ultrastar and maybe Ironwolf could have a lifespan, or MTBF, from 5yrs to even over 10yrs. Because of the long MTBF I'm thinking that getting the bigger recertified drives is a better choice since the cost per TB is so low. A lot of the space might be unused for a long time though - so I am not sure that bigger early on is better. Another question on how data gets written to the data drives. Is Unraid spread data across the data drives or does it fill the drives one at a time? Like, if I have 3 12TB data drives and have stored 4TB data is it all on one drive or are different files on different drives? Depending on how data is stored, should I get say 5 12TB drives but only start off with 2 or 3 with one as parity and the other as data then hold the other drives on the side as spares and/or data drive upgrades? Sorry for the long post and lots of questions and twists and turns in my question-post. Thanks in advance for any and all opinions, advice and information - all is greatly appreciated!