ApriliaEdd

couple more questions kind of linked though. the pool with only 2 drives in is showing as 98.6Gb used. given what you said above about data being mirrored to 2 drives i assume this is because the number of slots is still 3? once I've removed both smaller drives, can I then move/reassign the 2Tb drive to "cache" and change the number of slots to 2 so it will run with 1x 2Tb drive with a spare slot ready for another 2Tb drive when I'm ready?

Hallelujah! its working thanks for your continued help

ok this makes sense stopping array now to try

@JorgeB new diagnostics does it seem weird that there is exactly double the data on the 2Tb drive as each of the two 120's? sag-a-star-diagnostics-20240222-1125.zip

@JorgeB as requested sag-a-star-diagnostics-20240222-1114.zip

@JorgeB Morning, new day same problem. Stopped the array, removed one of the 120Gb disks and hit start 🤞........same thing as yesterday "Wrong Pool State". ran a scrub: no errors, ran a balance which took 20 mins but completed without error, and tried again same story. but, I had the logs open when I deselected the 120Gb drive and noticed this Does it think i have 4 drives in the cache? (sdy) is in another pool and has never been part of the cache So I guess next question is how do I correct this? that pool is used for a specific share for a proxmox backup server VM that didn't like being on the array.

I think you've cracked it! Thanks for your help today I'll try to remove one of the smaller drives tomorrow.

scrub finished Syslog memtest is a problem, server is in the loft without a screen as i lent it to a mate. i will have to run that at a later date how do I go about backing up the pool? do i just share everything and back it up to another PC?

@JorgeB the balance for converting runs for about a second then stops hope the video works convert to raid 1.mp4 sag-a-star-diagnostics-20240221-1407.zip

@JorgeB Diagnostics attached as requested sag-a-star-diagnostics-20240221-1359.zip

I have repeated the removal of all drives, start array, stop array. i figured out that if I reassign all the drives in the same places but before i start the array i can click the "cache" drive and I can change the file system type from "Auto" to "btrfs" and then choose "raid 1" should I apply this or will i lose my data?

still the same situation. I try to remove disk and it wont start the array then

no ssh windows open that i'm aware of. rebooting worked and allowed me to stop the array. before I do this should I set all shares to array primary and run mover to move all data off the cache pool or will data survive this?

I saw this this morning and was thinking the same problem at the moment is it wont stop the array from the gui. I've tried from 2 different pc's sag-a-star-diagnostics-20240221-0915.zip

ok i converted to raid 1, current status is stopping the array and selecting no device for one of the 120gb drives gives this when starting array ive stopped anything i can think of that will use the cache for now while its so small