lanlawr

Totally forgot to follow up. After following the rest of the instructions properly, everything is all good and the new cache is happy. Thanks!

Okay, the cache did mount properly, here are the diagnostics Diagnostics.zip

Label: none uuid: 12860a44-93b2-4324-9eab-67904c1378fc Total devices 3 FS bytes used 46.49GiB devid 3 size 111.79GiB used 30.00GiB path /dev/sdh1 devid 4 size 111.79GiB used 30.03GiB path /dev/sdi1 devid 7 size 119.24GiB used 38.03GiB path /dev/sde1

Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdi: 111.79 GiB, 120034123776 bytes, 234441648 sectors Disk model: OCZ-REVODRIVE350 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0x235667ee. Created a new partition 1 of type 'Linux' and of size 111.8 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o: ^C root@StuffNThings:~# sfdisk /dev/sdi Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdi: 111.79 GiB, 120034123776 bytes, 234441648 sectors Disk model: OCZ-REVODRIVE350 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 Created a new DOS disklabel with disk identifier 0xc03fe7ed. Created a new partition 1 of type 'Linux' and of size 111.8 GiB. /dev/sdi1 : 64 234441647 (111.8G) Linux /dev/sdi2:

Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdd: 111.79 GiB, 120034123776 bytes, 234441648 sectors Disk model: KINGSTON SA400S3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Old situation: Device Boot Start End Sectors Size Id Type /dev/sdd1 2048 234441647 234439600 111.8G 83 Linux Type 'help' to get more information. >>> 64 Created a new DOS disklabel with disk identifier 0x3b99b2fc. Created a new partition 1 of type 'Linux' and of size 111.8 GiB. /dev/sdd1 : 64 234441647 (111.8G) Linux /dev/sdd2:

Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdd: 111.79 GiB, 120034123776 bytes, 234441648 sectors Disk model: KINGSTON SA400S3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Old situation: Device Boot Start End Sectors Size Id Type /dev/sdd1 2048 234441647 234439600 111.8G 83 Linux Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0x50c9ee1c. Created a new partition 1 of type 'Linux' and of size 111.8 GiB. /dev/sdd1 : 2048 234441647 (111.8G) Linux /dev/sdd2:

Yeah it looked like I could do that, apparently not, that's on me Label: none uuid: d82a2777-eb96-4d7f-95e1-5658d0b0289f Total devices 1 FS bytes used 412.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop2 warning, device 4 is missing Label: none uuid: 12860a44-93b2-4324-9eab-67904c1378fc Total devices 3 FS bytes used 46.49GiB devid 3 size 111.79GiB used 30.00GiB path /dev/sdh1 devid 7 size 119.24GiB used 38.03GiB path /dev/sde1 *** Some devices missing

So I removed the first two Revodrive drives one at a time, letting it do a balance after every one. Then I swapped the positions of the new SSDs to the top, one at a time with a balance as well. That left me with the two new SSDs in the cache1 and cache2 positions, and 3 and 4 were still Revodrives. I then went to remove the Revodrive in position 4, but when I started the array again it now says 'Unmountable: Unsupported or no file system' on the cache drives. I tried re-adding the drive I just removed but that didn't change the unmountable status. Not sure why the removal of that drive made it unmountable all of a sudden... Is there anything I can do to fix that? I did take a backup of the cache just before doing the drive shuffling, but I think it only backed up docker related things... Diagnostics.zip

Here is the diagnostics. How does one safely remove them with the CLI? diagnostics.zip

Until recently I have been using an OCZ Revodrive 350 480GB PCIE SSD as my cache drive. In Windows it shows up as a single 480GB drive, but in Unraid it appears as 4x 120GB drives because I think on Windows its driver makes it appear as one. Anyways, I had it setup as a BTRFS RAID 0, but because it is old and I want a little redundancy, I decided I wanted to replace it with 2x 120GB SATA SSDs. I have added the new 120GB SSDs to the cache pool and set the pool to RAID 1 and would like to now remove the Revodrive all together, which will logically remove 4 of the 6 cache drives. However, from what I understand, this is NOT okay because BTRFS RAID 1 does not just mirror across all disks exactly the same, which seems to be supported by the fact that the cache is reporting a size of 364GB. My question is, how can I remove the 4x 120GB from the Revodrive from the cache safely?

Hi @ich777, I have been using the OpenVPN-Client docker with qbittorrents network routed through it with '--net=container:OpenVPN-Client', and that has been working well. But it appears I had a leak at some point recently, is there something I am missing? As far as I understand, if the OpenVPN container loses connection to the VPN or there are any other disruptions, anything else that uses it should also lose connection, right? Thanks in advance!

After leaving it do whatever it was doing all day while at work it seems to have sorted itself out. I tried starting the array to do the data rebuild but the whole system became completely unresponsive and I had to hold a pillow over its face, but after that it's now doing the rebuild, so things are good now I suppose. Thanks!

And then just run with the dead drive emulated I suppose, okay

How would I do that with docker? The array can't run normally so I can't run docker right?

After about 4 hours it was still 1% which seems quite excessive for a 3TB drive I would think. I stopped it and started it again just to make sure and that didn't do anything