Jump to content

6.9.2 - Ready to give up! (Unmountable: not mounted)


Recommended Posts

I had a Unmountable: not mounted disk 1 show up a week ago, Copied alll my files over to disk 7 with "btrfs restore -vi /dev/sdi1 /mnt/disk7/restore"

NOW I GET Unmountable: not mounted ON DISK 3! What is going on? My hardware is new, checked alll cables, etc etc. 

Mover kept running and building up my cache, I just want this damn thing to work again.

tower45tb-diagnostics-20211006-1418.zip tower45tb-syslog-20211006-1918.zip

Link to comment
26 minutes ago, BigDaddyMoe said:

why when i swith my share from no to prefer, my cahe fills up rather than get smaller? HELP, PLEASE

tower45tb-syslog-20211007-1503.zip 24.71 kB · 0 downloads tower45tb-diagnostics-20211007-1002.zip 111.85 kB · 0 downloads

The “Prefer” setting means you want mover to transfer files from the array to the cache.

 

The help built into the GUI tells you how the different options work and what action (if any) mover will take.

Link to comment

My point is that i was not copying anything new, my understanding is from the help text as follows:

"

Specify whether new files and directories written on the share can be written onto the Cache disk/pool if present. This setting also affects mover behavior.

No prohibits new files and subdirectories from being written onto the Cache disk/pool. Mover will take no action so any existing files for this share that are on the cache are left there.

Yes indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the Cache disk/pool and onto the array.

Only indicates that all new files and subdirectories must be writen to the Cache disk/pool. If there is insufficient free space on the Cache disk/pool, create operations will fail with out of space status. Mover will take no action so any existing files for this share that are on the array are left there.

Prefer indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the array and onto the Cache disk/pool.

NOTE: Mover will never move any files that are currently in use. This means if you want to move files associated with system services such as Docker or VMs then you need to disable these services while mover is running."

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...