hi guys i hope someone can help me

 

i have a 200GB SSD Cache drive, i try to upgrade the cache to more space and add 1tb that i have on the parity to the cache drive, but now i having a problem, my original ssd cache drive shows up as unmountable and i have plex and emby docker there, is there a way that i can go back they way it was before without losing any data on my ssd drive or is to late for me and have reinstall everything and lose my data on the cache drive?

 

thanks in advanced and sorry about my inglish

hi guys i hope someone can help me

 

i have a 200GB SSD Cache drive, i try to upgrade the cache to more space and add 1tb that i have on the parity to the cache drive, but now i having a problem, my original ssd cache drive shows up as unmountable and i have plex and emby docker there, is there a way that i can go back they way it was before without losing any data on my ssd drive or is to late for me and have reinstall everything and lose my data on the cache drive?

 

thanks in advanced and sorry about my inglish

 

You could always mount the drive outside the Array using the Unassigned Devices Plugin: https://lime-technology.com/forum/index.php?topic=45807.0

 

Then you can transfer the data off the drive either to the Array (as a backup), to your new cache device (and hopefully have everything run as before if settings have been maintained) or a destination of your choice.

right now unRAID is doing a Data rebuild because i add back that 1TB Drive after i saw the problem i was having, can i stooped the Data rebuild and mount the drive outside the Array?

 

thanks in advanced

right now unRAID is doing a Data rebuild because i add back that 1TB Drive after i saw the problem i was having, can i stooped the Data rebuild and mount the drive outside the Array?

 

thanks in advanced

 

Woah, you took the 1TB drive and tried to add it to the Cache in a BTRFS Pool configuration? Sorry, if that is what you have done I didn't pick that up from your post.

 

Firstly, disabling parity for more space on your Cache IMHO is VERY BAD idea. I would never sacrifice redundancy of your data on the array for more space on your Cache. Just doesn't make sense to me - unless of course you have a Backup - but even then I can't see the upside.

 

To your Cache problem, 256GB for Cache should be more than enough for most cases. If you find that you run out of space some days then just increase the frequency of the mover to something a little more frequent than daily. This setting can be found under: Settings>Scheduler>Mover Settings

 

As for the rebuild, i'd just let it run now. Get your Parity Protection back and then leave it alone. Once your Array is Parity Protected back and working fine, you can stop the array, assign the SSD to a Cache Slot and then Start the Array. Then -  if it is recognised - I think the data should be there if you haven't changed anything.

 

If the Cache drive is not recognised or doesn't mount when you start the Array (which if you haven't touched it - it should I'm sure) then Stop the Array, take the disk from the Cache Slot and then you can use the UD Plugin I suggested to the mount the disk, copy the data off it to a backup location on the Array, Stop The Array and reassign the SSD into a Cache Slot (and let it get formatted if needs be) then copy the data from the array back to the Cache disk as per your previous settings (which hopefully were a Cache ONLY share otherwise things are going to get moved to the Array by the mover at some point).

well i have 24TB of storage so taking off one drive that i have of 1tb dint bother me, anyway im gone fallow your advise and hope everything goes good, i really appreciate you help, thank you very much

well i have 24TB of storage so taking off one drive that i have of 1tb dint bother me, anyway im gone fallow your advise and hope everything goes good, i really appreciate you help, thank you very much

 

As an aside, if I am right, using an SSD with a Mechanical Device in a Cache Pool (which I have never seen done before nor did I know it could be done) would (other than space gain) not be worth it IMHO.

 

If you got it set up, as it would be in a BTRFS RAID-1 configuration I believe you would be bottlenecked for performance by the Mechanical Drive (which would be significantly slower than the SSD). I think in an BTRFS RAID-1 configuration writes are simultaneous to each disk. Therefore I feel the write operation would only be complete once writes to both devices were complete and as such the speed limiting factor would be the write to the Mechanical drive and as such you'd never realise the full speed of the SSD.

 

I might be wrong and If I am I am sure someone will correct me, but I think that makes sense.

yeah you are probably right, im new to unraid and im learning little by little, this is one mistake i wont made again, live and learn, i just hope all my other data on the array is fine

im happy to say i got everything back the way it was before, love the Unraid System