I have two machines, one with a Draid array and one with a pool with 12 vdevs of 3 way mirrors. I tried moving a couple drives around and tried to start a format of the replacement drive before starting any replace operations. I have noticed any time I call a format command such as sg_format --format --size=512 -v /dev/sdg from the shell, the ui/storage or ui/storage/disks pages refuse to load for a period of time. This happens longer on the mirrored array than the draid array but occors on both.
On the mirrored pool, I believe I started a format on the wrong drive causing the pool to be slightly more degraded. One vdev has a removed drive and another vdev has a faulted drive because I accidentally formatted a drive that was online and part of a pool. Unfortunately I cannot identify which is the correct drive that needs formatted until the format operation finishes or the system becomes responsive again. My data isn’t really at risk due to still having 2 mirrors in each problematic vdev, but it would be nice to get that second format started.
Does anyone have a good shell command to help me identify which drive is not a member of the pool? It seems like unresponsive pages like this during a format operation would be some sort of bug.