1. I have a disk that went bad in a 4 disks RAID10 BTRFS

2. Pulled disk physically

3. Ran full rebalance, current stats:

   1. 

4. In Main tab it still shows disk4 missing:

   1. 

Removing the pool and readd as a 3-disk pool didn't help, it just pops up as a 4-disk pool by itself.

Diagnostics attached just in case cozumel-diagnostics-20250709-0955.zip

Thanks!

Update to 7.1.4, convert the pool to RAID1, and you can then remove it, though possibly now it will need to be done manually.

36 minutes ago, JorgeB said:

Update to 7.1.4, convert the pool to RAID1, and you can then remove it, though possibly now it will need to be done manually.

Thanks for helping!

When you say done manually, do your mean the RAID10->RAID1 conversion needs to be done via CLI and cannot be done in GUI with the balance options?

i.e.:

Edited July 9, 2025Jul 9 by StylishQuoter

@JorgeB I've upgraded to 7.1.4, converted to RAID1.

But in GUI I still can not change the pool from size 4 to 3.

(I'm potentially still running into the bug where emhttpd won't start after a reboot.)

Post new diags please.

cozumel-diagnostics-20250709-2236.zip

tower-diagnostics-20250709-2209.zip

BTW I'm a bit tired of dealing with this so I've formatted clean the disks and recreated a new pool. (The data are backed up)

So far everything seems normal and good

But I do think emhttpd have some issues here.

In one of the logs it's still complaining `emhttpd: pool_state_btrfs 3167 rdevStatus.33 not found` which was the very original issue.

Edited July 10, 2025Jul 10 by StylishQuoter

23 hours ago, StylishQuoter said:

In one of the logs it's still complaining `emhttpd: pool_state_btrfs 3167 rdevStatus.33 not found` which was the very original issue.

This means the pool cfg is not correct, you remove and reimport the pool and it should fix it.

14 hours ago, JorgeB said:

This means the pool cfg is not correct, you remove and reimport the pool and it should fix it.

so I did that.

Recreated the pool with same name, auto as fs.

and the GUI did went up but it went back to the old errornous state:

1. has the emhttpd error in log

2. *cannot* normally reboot, once reboot it will go into the old 500 internal error with the same error

But like I said I've reformatted all the 3 remaining disks with a normal/new btrfs so there's no longer any issue.

OK, since you have reformatted the pool, cannot see what the issue was.