Version: FreeNAS-9.10.2-U1 (86c7ef5)
zpool list
:
Code:
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
RAIDZ3-01 152T 125G 151T - 0% 0% 1.00x ONLINE /mnt
freenas-boot 29.8G 661M 29.1G - - 2% 1.00x ONLINE -
Meanwhile, I found a way around this thanks to
https://forums.freenas.org/index.php?threads/unable-to-gpt-format-the-disk.49362/page-2 which linked to
https://forums.freenas.org/index.php?threads/operation-not-permitted-hdd-trouble.12208/#post-57090
Temporarily updating sysctl kern.geom.debugflags=0x10 allowed me to dd the device via the CLI or wipe it via the UI.
However, after this my attempts to extend the volume by adding this drive back in as a spare with a different error about not being able to partition /dev/multipath/disk11
From the logs:
/var/log/debug.log
Code:
Apr 13 02:17:47 freenas manage.py: [middleware.notifier:204] Executed: swapoff -a -> 0
Apr 13 02:17:47 freenas manage.py: [middleware.notifier:187] Executing: dd if=/dev/zero of=/dev/multipath/disk11 bs=1m count=32
/
var/log/daemon.log
Code:
Apr 13 02:17:47 freenas notifier: dd: /dev/multipath/disk11: Operation not permitted
/var/log/debug.log
Code:
Apr 13 02:17:47 freenas manage.py: [middleware.notifier:204] Executed: dd if=/dev/zero of=/dev/multipath/disk11 bs=1m count=32 -> 0
Apr 13 02:17:47 freenas manage.py: [middleware.notifier:230] Popen()ing: diskinfo multipath/disk11
Apr 13 02:17:47 freenas manage.py: [middleware.notifier:187] Executing: dd if=/dev/zero of=/dev/multipath/disk11 bs=1m oseek=7630853
/var/log/daemon.log
Code:
Apr 13 02:17:47 freenas notifier: dd: /dev/multipath/disk11: Operation not permitted
/var/log/debug.log
Code:
Apr 13 02:17:47 freenas manage.py: [middleware.notifier:204] Executed: dd if=/dev/zero of=/dev/multipath/disk11 bs=1m oseek=7630853 -> 0
Apr 13 02:17:47 freenas manage.py: [middleware.notifier:230] Popen()ing: gpart create -s gpt /dev/multipath/disk11
Apr 13 02:17:48 freenas manage.py: [middleware.notifier:230] Popen()ing: /sbin/zfs get -r -H -o name,property,value,source -t filesystem,volume compression,compressratio,readonly,org.freenas:description
Another thing to note is the system calls
swapoff -a
first & then tries to partition the drive. It doesn't appear to ever issue
swapon -a
when the partitioning fails so the system ends up having no swap after the operation fails.
I also find a strangely persistent entry in swapinfo that is one of the paths to disk11:
Code:
Device 1K-blocks Used Avail Capacity
/dev/da10 16777216 0 16777216 0%
Attempts to get rid of this also fail:
Code:
swapoff: /dev/da10: Invalid argument
I'm wondering if this is the reason it cannot partition disk11 - because it still thinks da10 is in use for swap.