weird zpool problem

[TravisT]

So I tried deleting a zpool from the GUI, and it gave me errors about writing to the disks. Kept getting an error about disk belonging to an existing zpool.

I checked the CLI, and the zpool still shows up. If I try to access it (scrub, destroy, etc), I get IO errors for hours and my CPU usage pegs. If I physically remove the drives that belong to the zpool, the zpool still shows ONLINE, but status shows IO failures. How can I destroy this zpool? I have no data on the disks that is important, and the IO errors are caused by faulty seating of the drives in the backplane connectors. I'm going to start working on getting that fixed tomorrow.

 

[paleoN]

When detaching the zpool choose to mark the disks as new. If that's not working under View Disks, wipe the individual disks.

 

[TravisT]

The pool no longer shows up in the GUI. I've tried wiping the disks, but it didn't work. I'll try again and post the error, as I don't recall what it said

 

[TravisT]

Right now the disks are removed from the system. The GUI shows the disks still under "view disks". My CPU usage is pegged at 100 on the reporting tab, and I keep getting the following error:

Code:

root: ZFS: zpool I/O failure, zpool=tank error=6
...last message repeated 13467 times

I tried doing a quick wipe of the disks through the GUI, just so it would remove them, but got a fatal error because the disk isn't physically there. How can I destroy the zpool and remove the disks from the software side if they are not installed (via the CLI)?

 

[paleoN]

I tried doing a quick wipe of the disks through the GUI, just so it would remove them, but got a fatal error because the disk isn't physically there.

There is no point in wiping a disk that isn't there. It won't get wiped.

How can I destroy the zpool and remove the disks from the software side if they are not installed (via the CLI)?

You would need to edit the SQLite database if I'm not mistaken. I would do a Factory Restore or stick the disks back in and delete the pool. Otherwise the FreeNAS database won't properly be in sync.

 

[William Grzybowski]

Did you try rebooting?