December 18, 20223 yr Community Expert Your cache drive is completely full, corrupting docker.img. Not a good idea to overfill btrfs filesystem. Best to not cache anything for the initial data load. It is impossible to move from fast cache to slow array as fast as you can write to fast cache, so making mover run more often also will not help. One way to speed up initial load is to not install parity until you have completed initial load.
December 18, 20223 yr Author how do i fix this? force mover to empty the drive remove the cache and continue the initial load? will that fix everything?
December 18, 20223 yr Community Expert 4 hours ago, outwar6010 said: how do i fix this? force mover to empty the drive remove the cache and continue the initial load? will that fix everything? Running mover will result in any shares that have Use Cache=Yes setting having any content they have on the cache/pool transferred to the array. You should also ensure you have set the Minimum Fred Space value for any pool to something that suits your usage to help with avoiding overfilling the pools/cache. That will mean that new files will start bypassing the cache/pool when that limit has been reached.
December 18, 20223 yr Author I set the minimum free space to 200gb on the cache and hit mover last night but the cache is still full. IS there anyway a unraid staff to remote in and fix the settings for me?
December 18, 20223 yr Author https://ibb.co/9Y2Qtqq I'll try that but would a setting here be a problem? I don't have any exp with unraid or stuff like this and followed a youtube video for the install
December 18, 20223 yr Community Expert Settings depend on where you want the data in those shares to end up after the mover runs, cache=prefer will stay on cache, cache=yes will be moved to the array, if they are not in use, don't already exist on the array, etc, mover log will show the problem.
December 18, 20223 yr Author I enabled mover logging but can't seem to find a file in the diagnostics logging moving data quantumserver-diagnostics-20221218-1418.zip
December 18, 20223 yr Community Expert The mover logging is sent to the syslog file (which is in the 'logs' section of the diagnostics.
December 19, 20223 yr Community Expert Mover log says read-only filesystem. You have probably corrupted cache by filling it. Check filesystem on cache.
December 19, 20223 yr Community Expert 1 hour ago, outwar6010 said: no errors found how do I fix this? You should always capture the output from check filesystem so you can post it.
December 19, 20223 yr Author After doing the repair with no errors etc. I decided to back everything on the cache drive and then I messed up. I tried to change the file system to xfs thinking that would help but now the drive says Unmountable: Wrong or no file system .
December 19, 20223 yr Author I formatted the drive and now everything seems to be normal. I then removed it from the pool and will add it later once the initial fill is done. Does this all sound right? Edited December 19, 20223 yr by outwar6010
December 19, 20223 yr Community Expert Solution You will also want to wait until you have cache to enable Docker and/or VM Manager. You want appdata, domains, system shares on cache or other fast pool so Docker/VM performance isn't impacted by slower array, and so array disks can spin down since these files are always open.
December 19, 20223 yr Author Thanks for all your help. I'll see you guys in like 6 days after I've transferred all my data xd
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.