Can't export/disconnect pool
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity

William Gryzbowski December 3, 2020 at 4:50 PM
This should be fixed in upcoming 20.12 ALPHA

Dan Christensen December 1, 2020 at 5:13 AM
Attached debug-truenas-20201130230148.tgz which was just after experiencing a similar failure. I reproduced this failure by:
installing TrueNAS-SCALE-20.10-ALPHA using all defaults, installing to nvme0n1
rebooted, pulled installation media, let the system come up
logged into the webui, created a pool named data, exported that pool without issue
created a new pool named data2
disabled atime on the pool
rebooted from the webui
logged back into the webui, tried to export the pool, got the error while the status indicated it was reconfiguring the system pool (something like that)
generated the debug archive
I imagine the reboot is the catalyst since the data pool I created the first go around didn't have a problem exporting. But I didn't run through another reinstall and test just to bottom that out. Sorry.

Bonnie Follweiler November 30, 2020 at 2:00 PM
Thank you for the report . Can you please provide a debug by navigating to System -> Advanced, click save debug, and upload attachment to this ticket?
Details
Details
Assignee

Reporter

In testing out TrueNAS SCALE (20.10-ALPHA), I created a pool of 8 disks ("data") and wanted to change the vdev layout. The export failed (I did not check the 'destroy data' box, not sure if that should matter but I subsequently learned given my intention to reorganize I should have) and I don't remember exactly how I was able to remove disks from the pool (I may have rebooted and pulled the physical disks)... Ultimately I removed the record from storage_volume in /data/freenas-v1.db to get the UI to forget about it.
I then made a new pool ('data2") and saw a similar, maybe the same, traceback when trying to export it to rename it (back to data after cleaning up the storage_volume entry):
It seems like this could be related to NAS-106673 but that change had landed and sure seemed to be present in spot-checking my system.