December 25, 20232 yr Hey, so I updated a few things and now it seems like stuff is constantly being written on the disc (every few secs), causing HDD noise. I've bottled it down to Immich (mostly the postgres service) and Plex creating the most noise. For Plex I've added the no health check parameter previously. Any Ideas? Edited December 25, 20232 yr by MrTing
December 25, 20232 yr Community Expert Solution Your appdata, domains, and system shares have some or all files on disk1. Ideally, these shares have all files on cache or other fast pool with nothing from them on the array. If these are on the array, Docker/VM performance will be impacted by slower array, and array disks can't spin down since these files are always open. Set these shares to Primary storage: cache; Secondary storage: array; Mover action: array --> cache. Nothing can move open files so you have to disable Docker and VM Manager in Settings then run Mover. You can see how much of each disk or pool is used by each user share by clicking Compute... for the share or Compute All button on the User Shares page.
December 25, 20232 yr Author omg thank you so much! the hdd barely makes noise now when on idle. I tried doing the mover stuff before but didn't change the mover action. Another question, so now the writes on my cache drive are going up every few seconds (sometimes 50 writes at a time). Is this something I should be concerned by? By writing stuff, its taking up storage on the cache drive right? Do I enable TRIM on the cache drive if thats even possible? Sorry for the very newbie questions. EDIT: Did some testing. The dockers that are doing the constant writing on the cache are: Immich (postgres service, 460 per minute), Nginx Proxy Manager (30 per minute), and Plex (7 per minute). so 700k writes a day..that doesn't sound good EDIT#2: I have made another noob mistake in thinking the amount of writes meant more data was being written on the drive, which isn't the case. I'll compare the Data Units Written from now and 24 hours later. Edit#3: 20GB was written to the cache drive overnight. Still kind of sounds like a lot but not a concern regarding the endurance of the drive. Edited December 26, 20232 yr by MrTing formatting/further details
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.