Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Now that SQLite issues seem to be fixed....help me understand...

Featured Replies

So when I was running my system on 6.6.7, had had my appdata located in /mnt/user/appdata.   I was told to move that to /mnt/disk1/appdata, which I did.  I've also been told that I should have it on a cache drive (I don't have a cache drive installed at all). 

 

I'm looking for some understanding... (understand...a bit of a noobie when it comes to Unraid, but not to raid systems, or Plex databases). 

 

What is the different  between putting appdata in a different location?  I had ZERO issues with /mnt/user/appdata under 6.6.7.  Should I put it back that way?

 

What are the reasons for having a cache drive when you do not do a lot of writing that requires faster access? 

 

 

Part of it was to eliminate an entire layer. The /mnt/user/ runs through Fuse that runs in User space. Using /mnt/cache/ or /mnt/disk# bypasses that layer.

 

Using cache disk(s) allows all other array drives to spin down, while any reads and writes happen only on the cache drive(s).

5 hours ago, Rich Minear said:

So when I was running my system on 6.6.7, had had my appdata located in /mnt/user/appdata.   I was told to move that to /mnt/disk1/appdata, which I did.

By leaving it on /mnt/disk1, you will get moderately better performance from your apps.

5 hours ago, Rich Minear said:

What are the reasons for having a cache drive when you do not do a lot of writing that requires faster access? 

The cache drive's original purpose of mitigating slow writes to the parity protected array has been largely superseded by the introduction of "Turbo-write", so it's main use now is for the storage of things like Plex databases, application data for other docker containers, the docker.img file itself,  and vdisk images for VMs, all of which benefit greatly from the speed of an SSD, while allowing the array to be used for bulk storage.

Having you application data located at /mnt/user/appdata has the advantage of working (unforeseen and obscure bugs notwithstanding) whether you have a cache disk or not, so it's a good compromise choice for the default path.

  • Author

So with a cache drive...if I move my appdata to it, is there any redundancy?  Can I add two ssd's and have them be mirrored or anything like that?

49 minutes ago, Rich Minear said:

So with a cache drive...if I move my appdata to it, is there any redundancy?  Can I add two ssd's and have them be mirrored or anything like that?

Yes, you can create btrfs cache pools of two or more cache drives.  The default is RAID 1 (mirror) but there are other possibilities as well.

 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.