can't install onto disk with freenas installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
Medium
|
Unassigned | ||
subiquity |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Server 18.04 LTS
Installing to USB drive that already has freenas 11.1-U4 installed.
Installer crashes and recommends filing bug on Launchpad. No visible way to extract logs, only option was to close and reboot.
Dropping to shell, fdisk new partition map allowed installation to proceed normally on next boot.
Unfortunately I didn't write down the error log output but I recall the curtin package being unable to export a pool because it didn't exist. Perhaps the name of the pool is hard coded in that script and it's incorrect? And/or perhaps that step isn't necessary at all, if the user has explicitly stated that overwriting the whole disk is what's desired, why bother exporting the boot pool at all.
Let me know if I can help at all with this ,it was a new install of FreeNAS with zero customization - was just testing a zfs receive.
Related branches
- Server Team CI bot: Approve (continuous-integration)
- Scott Moser (community): Approve
-
Diff: 73 lines (+15/-2)5 files modifiedcurtin/block/clear_holders.py (+3/-1)
curtin/block/zfs.py (+1/-1)
examples/tests/dirty_disks_config.yaml (+6/-0)
tests/unittests/test_clear_holders.py (+1/-0)
tests/vmtests/test_zfsroot.py (+4/-0)
affects: | debian-installer (Ubuntu) → subiquity |
Changed in curtin: | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
Changed in subiquity: | |
status: | New → Fix Released |
Changed in curtin: | |
status: | Fix Committed → Fix Released |
This seems to be a problem in curtin. For easy reproduction, I've uploaded a raw disk image that was formatted by freenas to https:/ /people. canonical. com/~mwh/ target2. tgz (it's a 10G image, but sparse). Then run "kvm -m 1024 -boot d -cdrom ~/isos/ bionic- live-server- amd64.iso -hda ~/images/ target2. img" or whatever paths required on your system and try to install do the disk; it will fail with errors in the logs about zpool not being installed, but really curtin should be wiping the disk by writing zeros, not by trying to carefully dismantle the zfs setup.