muddles17

I only had the extra 12tb disk that I tried to do a balance that didn't go well and then had to replace it in the following process (from memory): starting array: device id 1 - 2tb (currently sdb) device id 2 - 4tb device id 3 - 4tb device id 4 - 12tb device id 5 - 12tb I added a 12tb as device 6 and started a balance that errored out - then I couldn't remove device id 3 because it had an I/O error device id 1 - 2tb - sdb device id 2 - 4tb - sdd device id 3 - 4tb - don't remember device id 4 - 12tb - sdg device id 5 - 12tb - sdf device id 6 - 12tb - sdc I started but then stopped a remove of device 6 because I was concerned about it re-distributing the data onto the failed drives I removed device id 1 because it didn't have any data on it device id 2 - 4tb - sdd device id 3 - 4tb - don't remember device id 4 - 12tb - sdg device id 5 - 12tb - sdf device id 6 - 12tb - sdc After the balance, device id 6 had less than 2tb, so I did a replace with the 2tb drive to free up the added 12tb that was device 6. I think somehow it got added as device 7 because of the previously attempted remove. device id 2 - 4tb - sdd device id 3 - 4tb - don't remember device id 4 - 12tb - sdg device id 5 - 12tb - sdf device id 7 - 2tb - sdb I then did a replace on device id 3 with the freed up 12tb drive so that it got rid of the worst drive. That successfully completed. device id 2 - 4tb - sdd device id 3 - 12tb - sdc device id 4 - 12tb - sdg device id 5 - 12tb - sdf device id 7 - 2tb - sdb I then had the array mounted as the post above this one (I'm pretty sure - because I did a remove on device id 1, but I don't have 100% confidence that 6 was the other missing id.) I then unmounted the drives and then added them like this, which then broke the array when I tried to mount it.

Before I mounted them with unraid, they did have the partitions listed when using lsblk, but they aren't there anymore after attempting an unraid mount. There were initially gaps in the grouping, so that may also be why it had an error. I had two failing drives and needed to do a replace and then a remove and then another replace, so I ended up with something like: device id 2 - sdd device id 3 - sdc device id 4 - sdg device id 5 - sdf device id 7 - sdb

I think that unraid got rid of their association as a pool when I tried to mount them through the pool devices frontend. I wish that I copied the data to a different drive before trying to mount it with unraid since I did get it working again on the command line.

Using fdisk, I can seee that some of them show up as having partitions while others don't.

After doing an lsblk, it looks like the sdd1 and sdg1 partitions are missing

I recently spent some time doing a drive replace in BTRFS Raid 1. I needed to use the command line, so the frontend and backend were out-of-sync in terms of the drives used. I did the following to attempt to re-add the devices: Go into storage settings Remove pool Add pool of 5 devices in the same order (the array started on device id 2, which might be the problem) Go back into storage settings for the pool and set filesystem type to btrfs because it didn't mount the first time. Unmount everything after unsuccessful mount and check btrfs filesystem show. The btrfs filesystem show doesn't show all 5 devices or even a placeholder for all of them. Is there a good way to resolve this, or would there potentially also be a different btrfs-specific forum to check?

My server still wasn't running as the latest version after the update. I needed to delete/move the perms.txt file while restarting the container before it would run as the latest version. I put the file back after it restarted. I don't know if it was needed, but I also ended up making a new container with a new directory and copying over the behavior_packs folder from it. Thank you for maintaining this!

oops. I'll have to get that moved. Could I have two zfs arrays in a pool or array that would contain sets of two that would provide the ability to do scrubs? Would those go into pools or do zfs mirrors go into the array? zfs is a bit more confusing from that aspect. The main benefit that I considered with btrfs is that it allowed for slapping everything into a raid and then it would take care of the complicated parts in the background.

Here is a new diagnostics file. You are correct. It is another pool. holonet-diagnostics-20250310-1837.zip

I'm using a BTRFS RAID1 array right now with this https://carfax.org.uk/btrfs-usage/ type of calculation for all of the drives. As-is, it doesn't have any blank space and is just space / 2. I didn't realize that the pools and arrays were completely different when I started. everything. I have the 2x12tb that I still need to add. Should I make a new array and copy everything over? As far as I can tell, it seems like BTRFS has some data integrity that it can run to make sure that everything is running properly / help with bit rot. Does the unraid array have something like that? When I ran scrub on my data, it picked up a significant amount of issues that could be helpful in the future. From what I could read on the documentation, if unraid info is incorrect, it primarily just grabs the data and writes it to parity without trying to correct data.

Ah - what worked was disabling docker in the docker tab, re-selecting the location in the interface, applying and then selecting enabled again and applying again. Everything is back! Thank you for the moral support on getting started.

I tried copying my /config/plugins/dockerMan folder from the backup that I made to the USB drive, and my docker folder is still empty. I am able to get to the docker folder from my file browser. I'll search around a bit to see if I can add it to the UI. If that doesn't work, I'll copy the directory, rebuild it, and then copy everything back in.

I managed to get everything to start up by backing up my flash as-is as an image and then running UNRAID USB creator on it and dragging and dropping the contents of the backup over the contents of the USB. I had to then add the second SSD again to get the BTRFS to start. It's missing all of the docker configs though. Is there a way to get that back?

The flash drive itself still seems to be ok. It's booting up, and I can read it. I didn't quite realize how it's supposed to be setup for a standard unraid setup. I ended up doing a btrfs pool with one SSD and a second btrfs pool with 4 hard drives. I was doing the following: cache pool: 2tb SSD -> 2x 2tb SSD with BTRFS RAID1 storage pool: 2tb HDD + 4tb HDD + 4tb HDD + 1tb HDD to 2tb HDD + 4tb HDD + 4tb HDD + 12tb HDD + 12tb HDD I have a backup of my flash drive, but it is from before I started doing these operations.

Hello Unraid users, I recently had a BTRFS pool that I was trying to remove a 1tb drive from and add two 12tb drives. I was also adding an SSD to a cache pool. During the shutdown process after doing this to add the 12tb drives (I removed the 1tb drive first from the pool, but it wasn't using much storage, so I assumed that it didn't need much time to do it) I waited for a while and then did an ungraceful shutdown as it wasn't seeming to do anything anymore. After rebooting the server, it wasn't bringing back up the server interface. I tried a safe boot and a GUI boot and found that localhost didn't bring anything up. I understand that I messed up by being too impatient. I'm adding the log file that I got from a console login shutdown that I did afterwards. I'm able to boot the device from the USB. I'm currently using Unraid 7.0.1. tower-diagnostics-20250310-1643.zip