December 30, 2025Dec 30 Author Is zpool import zmain expected to work after the zpool import command has been run, or do I need to export both pools first?
December 30, 2025Dec 30 Author Nevermind. Looks like zpool import zmain runs without a problem immediately after. Same with the status command:
December 30, 2025Dec 30 Community Expert If that works, GUI should work the same, try reimporting the pool in case there's a configuration issue; export it first with zpool export zmain, then on main click on the first device for that pool and then "remove pool"back on main, create a new pool with the same name and 50 slotsassign the current 50 pool devices, you can assign them in any order, they will be sorted at array startleave the filesystem set to auto, start the array to try and reimport the pool and port new diags.
December 30, 2025Dec 30 Author 8 minutes ago, JorgeB said:If that works, GUI should work the sameFrom previous system logs, it doesn't appear that Unraid has been using the same import command I used in the command line. Let me repost my earlier snippet from the system logs:14 hours ago, Chukwuka13 said:Dec 29 17:32:22 Nebula emhttpd: shcmd (7733): mkdir -m 0666 -p /mnt/zmain Dec 29 17:32:22 Nebula emhttpd: shcmd (7734): /usr/sbin/zpool import -f -m -N -o autoexpand=on -d /dev/sdbf1 -d /dev/sdbg1 -d /dev/sdbh1 -d /dev/sdbi1 -d /dev/sdbj1 -d /dev/sdbk1 -d /dev/sdbl1 -d /dev/sdbm1 -d /dev/sdbn1 -d /dev/sdbo1 -d /dev/sdbu1 -d /dev/sdbv1 -d /dev/sdbw1 -d /dev/sdbx1 -d /dev/sdby1 -d /dev/sdbz1 -d /dev/sdca1 -d /dev/sdcb1 -d /dev/sdcc1 -d /dev/sdcd1 -d /dev/sdce1 -d /dev/sdcf1 -d /dev/sdcg1 -d /dev/sdch1 -d /dev/sdci1 -d /dev/sdcj1 -d /dev/sdck1 -d /dev/sdcl1 -d /dev/sdcm1 -d /dev/sdcn1 -d /dev/sdco1 -d /dev/sdcw1 -d /dev/sdcx1 -d /dev/sdcy1 -d /dev/sddc1 -d /dev/sddd1 -d /dev/sdde1 -d /dev/sddf1 -d /dev/sddg1 -d /dev/sddh1 -d /dev/sdcp1 -d /dev/sdcz1 -d /dev/sdcq1 -d /dev/sdcv1 -d /dev/sdcr1 -d /dev/sdct1 -d /dev/sdcu1 -d /dev/sdda1 -d /dev/sdbt1 -d /dev/sddb1 9455508329953933197 zmain Dec 29 17:33:29 Nebula root: cannot import 'zmain' as 'zmain': out of space Dec 29 17:33:29 Nebula root: Destroy and re-create the pool from Dec 29 17:33:29 Nebula root: a backup source. Dec 29 17:33:29 Nebula emhttpd: shcmd (7734): exit status: 1 Dec 29 17:33:29 Nebula emhttpd: shcmd (7735): rmdir /mnt/zmain Dec 29 17:33:29 Nebula emhttpd: zmain: mount error: wrong or no file systemIs it not possible the /usr/sbin/zpool import -f -m -N -o autoexpand=on ... command behaves differently?12 minutes ago, JorgeB said:on main click on the first device for that pool and then "remove pool"Is there any risk to removing the pool? Will I lose my data in the process?
December 30, 2025Dec 30 Community Expert The Unraid command points to the specific assigned devices, but assuming all are present and OK, it should import the pool normally, a general zpool import is more forgiving; as long as all pool devices are present, it will import the pool.5 minutes ago, Chukwuka13 said:Is there any risk to removing the pool? Will I lose my data in the process?No, worst case it will give the same error as before.
December 30, 2025Dec 30 Author Just now, JorgeB said:No, worst case it will give the same error as beforeOkay. I initialized the export command before my last message. It typically takes some time to run. After the pool has been exported, I will try removing and re-adding the pool from the GUI as you mentioned, then start the array. Edited December 30, 2025Dec 30 by Chukwuka13
December 30, 2025Dec 30 Author The array is still restarting after the suggested removal and re-adding. As I'm monitoring the system logs I see that it is going through the same recovery process I mentioned earlier. I wanted capture the console output real quick for your awareness:Dec 30 09:17:49 Nebula emhttpd: zmain: recover volume Dec 30 09:17:49 Nebula emhttpd: /sbin/blkid /dev/sdbf1 2>&1 Dec 30 09:17:50 Nebula emhttpd: /dev/sdbf1: LABEL="zmain" UUID="9455508329953933197" UUID_SUB="12874290684355378790" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="493f0da2-3976-45eb-bdfa-af47502b1280" Dec 30 09:17:50 Nebula emhttpd: zmain: zfs recover pool Dec 30 09:17:50 Nebula emhttpd: shcmd (9308): /usr/sbin/zpool import -f -m -N -d /dev/sdbf1 -d /dev/sdbg1 -d /dev/sdbh1 -d /dev/sdbi1 -d /dev/sdbj1 -d /dev/sdbk1 -d /dev/sdbl1 -d /dev/sdbm1 -d /dev/sdbn1 -d /dev/sdbo1 -d /dev/sdbu1 -d /dev/sdbv1 -d /dev/sdbw1 -d /dev/sdbx1 -d /dev/sdby1 -d /dev/sdbz1 -d /dev/sdca1 -d /dev/sdcb1 -d /dev/sdcc1 -d /dev/sdcd1 -d /dev/sdce1 -d /dev/sdcf1 -d /dev/sdcg1 -d /dev/sdch1 -d /dev/sdci1 -d /dev/sdcj1 -d /dev/sdck1 -d /dev/sdcl1 -d /dev/sdcm1 -d /dev/sdcn1 -d /dev/sdco1 -d /dev/sdcw1 -d /dev/sdcx1 -d /dev/sdcy1 -d /dev/sddc1 -d /dev/sddd1 -d /dev/sdde1 -d /dev/sddf1 -d /dev/sddg1 -d /dev/sddh1 -d /dev/sdcp1 -d /dev/sdcz1 -d /dev/sdcq1 -d /dev/sdcv1 -d /dev/sdcr1 -d /dev/sdct1 -d /dev/sdcu1 -d /dev/sdda1 -d /dev/sdbt1 -d /dev/sddb1 9455508329953933197 zmain Dec 30 09:19:33 Nebula emhttpd: zmain: zfs verify devices Dec 30 09:19:33 Nebula emhttpd: /usr/sbin/zpool status -P zmain 2>&1 Dec 30 09:19:33 Nebula emhttpd: pool: zmain Dec 30 09:19:33 Nebula emhttpd: state: ONLINE Dec 30 09:19:33 Nebula emhttpd: scan: scrub repaired 27.3M in 8 days 03:08:01 with 0 errors on Thu Dec 11 03:08:02 2025 Dec 30 09:19:33 Nebula emhttpd: config: Dec 30 09:19:33 Nebula emhttpd: NAME STATE READ WRITE CKSUM Dec 30 09:19:33 Nebula emhttpd: zmain ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: raidz2-0 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbf1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbg1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbh1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbi1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbj1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbk1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbl1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbm1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbn1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbo1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: raidz2-1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbu1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbv1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbw1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbx1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdby1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbz1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdca1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcb1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcc1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcd1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: raidz2-2 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdce1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcf1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcg1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdch1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdci1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcj1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdck1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcl1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcm1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcn1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: raidz2-3 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdco1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcw1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcx1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcy1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sddc1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sddd1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdde1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sddf1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sddg1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sddh1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: raidz2-4 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcp1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcz1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcq1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcv1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcr1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdct1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdcu1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdda1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sdbt1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: /dev/sddb1 ONLINE 0 0 0 Dec 30 09:19:33 Nebula emhttpd: errors: No known data errors Dec 30 09:19:33 Nebula emhttpd: zmain: zfs assign devices Dec 30 09:19:33 Nebula emhttpd: shcmd (9309): /usr/sbin/zpool export -f zmainYesterday, after the export finished, the system's next attempt to import the array encountered the out-of-space issue I've been reporting. I'm hoping this time is different. I will post the new diags once the array is started. Edited December 30, 2025Dec 30 by Chukwuka13
December 30, 2025Dec 30 Author It ultimately resulted in the same error. Here are the diagnostics:nebula-diagnostics-20251230-0931.zipLooking at the command used during the recovery step:/usr/sbin/zpool import -f -m -N -d /dev/sdbf1 -d /dev/sdbg1 -d /dev/sdbh1 -d /dev/sdbi1 -d /dev/sdbj1 -d /dev/sdbk1 -d /dev/sdbl1 -d /dev/sdbm1 -d /dev/sdbn1 -d /dev/sdbo1 -d /dev/sdbu1 -d /dev/sdbv1 -d /dev/sdbw1 -d /dev/sdbx1 -d /dev/sdby1 -d /dev/sdbz1 -d /dev/sdca1 -d /dev/sdcb1 -d /dev/sdcc1 -d /dev/sdcd1 -d /dev/sdce1 -d /dev/sdcf1 -d /dev/sdcg1 -d /dev/sdch1 -d /dev/sdci1 -d /dev/sdcj1 -d /dev/sdck1 -d /dev/sdcl1 -d /dev/sdcm1 -d /dev/sdcn1 -d /dev/sdco1 -d /dev/sdcw1 -d /dev/sdcx1 -d /dev/sdcy1 -d /dev/sddc1 -d /dev/sddd1 -d /dev/sdde1 -d /dev/sddf1 -d /dev/sddg1 -d /dev/sddh1 -d /dev/sdcp1 -d /dev/sdcz1 -d /dev/sdcq1 -d /dev/sdcv1 -d /dev/sdcr1 -d /dev/sdct1 -d /dev/sdcu1 -d /dev/sdda1 -d /dev/sdbt1 -d /dev/sddb1 9455508329953933197 zmain Versus the command used during the final import:/usr/sbin/zpool import -f -m -N -o autoexpand=on -d /dev/sdbf1 -d /dev/sdbg1 -d /dev/sdbh1 -d /dev/sdbi1 -d /dev/sdbj1 -d /dev/sdbk1 -d /dev/sdbl1 -d /dev/sdbm1 -d /dev/sdbn1 -d /dev/sdbo1 -d /dev/sdbu1 -d /dev/sdbv1 -d /dev/sdbw1 -d /dev/sdbx1 -d /dev/sdby1 -d /dev/sdbz1 -d /dev/sdca1 -d /dev/sdcb1 -d /dev/sdcc1 -d /dev/sdcd1 -d /dev/sdce1 -d /dev/sdcf1 -d /dev/sdcg1 -d /dev/sdch1 -d /dev/sdci1 -d /dev/sdcj1 -d /dev/sdck1 -d /dev/sdcl1 -d /dev/sdcm1 -d /dev/sdcn1 -d /dev/sdco1 -d /dev/sdcw1 -d /dev/sdcx1 -d /dev/sdcy1 -d /dev/sddc1 -d /dev/sddd1 -d /dev/sdde1 -d /dev/sddf1 -d /dev/sddg1 -d /dev/sddh1 -d /dev/sdcp1 -d /dev/sdcz1 -d /dev/sdcq1 -d /dev/sdcv1 -d /dev/sdcr1 -d /dev/sdct1 -d /dev/sdcu1 -d /dev/sdda1 -d /dev/sdbt1 -d /dev/sddb1 9455508329953933197 zmain I wonder if the issue is with the autoexpand=on flag. If the command is trying to auto-expand a full pool in the import process, it does make sense that it would fail due to the pool being out of space
December 30, 2025Dec 30 Community Expert To rule out any GUI issues, with the pool exported, paste in the CLI:zpool import -f -m -N -o autoexpand=on -d /dev/sdbf1 -d /dev/sdbg1 -d /dev/sdbh1 -d /dev/sdbi1 -d /dev/sdbj1 -d /dev/sdbk1 -d /dev/sdbl1 -d /dev/sdbm1 -d /dev/sdbn1 -d /dev/sdbo1 -d /dev/sdbu1 -d /dev/sdbv1 -d /dev/sdbw1 -d /dev/sdbx1 -d /dev/sdby1 -d /dev/sdbz1 -d /dev/sdca1 -d /dev/sdcb1 -d /dev/sdcc1 -d /dev/sdcd1 -d /dev/sdce1 -d /dev/sdcf1 -d /dev/sdcg1 -d /dev/sdch1 -d /dev/sdci1 -d /dev/sdcj1 -d /dev/sdck1 -d /dev/sdcl1 -d /dev/sdcm1 -d /dev/sdcn1 -d /dev/sdco1 -d /dev/sdcw1 -d /dev/sdcx1 -d /dev/sdcy1 -d /dev/sddc1 -d /dev/sddd1 -d /dev/sdde1 -d /dev/sddf1 -d /dev/sddg1 -d /dev/sddh1 -d /dev/sdcp1 -d /dev/sdcz1 -d /dev/sdcq1 -d /dev/sdcv1 -d /dev/sdcr1 -d /dev/sdct1 -d /dev/sdcu1 -d /dev/sdda1 -d /dev/sdbt1 -d /dev/sddb1 9455508329953933197 zmainIf that fails witht he same error, and it should, try the same command without autoexpand:zpool import -f -m -N -o -d /dev/sdbf1 -d /dev/sdbg1 -d /dev/sdbh1 -d /dev/sdbi1 -d /dev/sdbj1 -d /dev/sdbk1 -d /dev/sdbl1 -d /dev/sdbm1 -d /dev/sdbn1 -d /dev/sdbo1 -d /dev/sdbu1 -d /dev/sdbv1 -d /dev/sdbw1 -d /dev/sdbx1 -d /dev/sdby1 -d /dev/sdbz1 -d /dev/sdca1 -d /dev/sdcb1 -d /dev/sdcc1 -d /dev/sdcd1 -d /dev/sdce1 -d /dev/sdcf1 -d /dev/sdcg1 -d /dev/sdch1 -d /dev/sdci1 -d /dev/sdcj1 -d /dev/sdck1 -d /dev/sdcl1 -d /dev/sdcm1 -d /dev/sdcn1 -d /dev/sdco1 -d /dev/sdcw1 -d /dev/sdcx1 -d /dev/sdcy1 -d /dev/sddc1 -d /dev/sddd1 -d /dev/sdde1 -d /dev/sddf1 -d /dev/sddg1 -d /dev/sddh1 -d /dev/sdcp1 -d /dev/sdcz1 -d /dev/sdcq1 -d /dev/sdcv1 -d /dev/sdcr1 -d /dev/sdct1 -d /dev/sdcu1 -d /dev/sdda1 -d /dev/sdbt1 -d /dev/sddb1 9455508329953933197 zmain
December 30, 2025Dec 30 Community Expert Array can be running, just remember that the GUI will always show the pools as unmountable, even if it's imported successfully using the CLI
December 30, 2025Dec 30 Author Okay, the command is running now. Should hopefully finish within the next 5 minutes. I'm also fairly confident the first command with autoexpand=on will fail.
December 30, 2025Dec 30 Author The command without autoexpand=on worked:Where do we go from here?I'm still curious whether you see any risks in manually expanding the vdev from the CLI.
December 30, 2025Dec 30 Community Expert 1 minute ago, Chukwuka13 said:Where do we go from here?That's strange since the pool should already be expanded to the current devices, but at least we know the issue now.2 minutes ago, Chukwuka13 said:I'm still curious whether you see any risks in manually expanding the vdev from the CLI.Very low risk, basically no risk if the commands are done correctly, just no guarantee it will resolve the issue, but I think it's worth a try.Are the new disks already partitioned, or are they new empty disks? In doubt, post the output from fdisk -l /dev/sdX for one of them
December 30, 2025Dec 30 Community Expert Also, to see the current pool allocation, post the output from zpool list -v zmain
December 30, 2025Dec 30 Author Here is the output from fdisk -l /dev/sdX for one of the new disksHere is the output for zpool list -v zmain :
December 30, 2025Dec 30 Community Expert Yep, all vdevs are at 100%, as expected.To add a new vdev, first you need to partition the disks. You can create a standard Unraid GPT partition with:sgdisk -o -a 8 -n 1:32K:0 /dev/sdXReplace X with the correct identifiers for the new 10 disks; double-check you are doing it on the correct disks.Once that's done for all 10, type:zpool add -f zmain raidz2 /dev/sdX1 /dev/sdY1 etcAfter raidz2, it should contain all 10 new disks, note the 1 at the end, that's to specify the parition, all devices should end in 1After that is added, export the pool using the CLI and try to import it again using the GUI (you would need to reimport the pool as before, now with all 60 devices), or try first using the CLI with autoexpand=on, less work.
December 30, 2025Dec 30 Author On it. I'll let you know how it goes. Same as last time, I imagine I don't need to worry about stopping the array until I'm ready to reimport, correct?
December 30, 2025Dec 30 Author Damn, the issue persists after adding the vdev although the error this time is slightly different:I/O error instead of an out-of-space error.
December 30, 2025Dec 30 Author Actually, this is likely because of the 9455508329953933197 value, which should no longer be accurate since the pool is larger (also never added the 10 missing drives to the command). I can go ahead and try to reimport via the GUI. Edited December 30, 2025Dec 30 by Chukwuka13
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.