Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fresh Installation Failure With Swap Partition #32

Closed
maxsteciuk opened this issue Oct 10, 2018 · 5 comments
Closed

Fresh Installation Failure With Swap Partition #32

maxsteciuk opened this issue Oct 10, 2018 · 5 comments

Comments

Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@maxsteciuk
Copy link

@maxsteciuk maxsteciuk commented Oct 10, 2018

Multiple attempts to configure fresh full disk installation with Swap partition led the overall installation failure. Several values for Swap partition were tested: 520 MB, 1024 MB, 2055 MB. The log indicates the ZFS import trident showing exit error code 1.

pc-sysinstall.log log error message:

cannot import 'trident': invalid vdev configuration

EXITERROR: Error 1: zpool -f -N trident

@RodMyers
Copy link
Contributor

@RodMyers RodMyers commented Nov 11, 2018

RC3, clean install on a 2nd Gen X1 carbon. Swap file created just fine

@maxsteciuk
Copy link
Author

@maxsteciuk maxsteciuk commented Nov 18, 2018

UPDATE:

The following workaround steps worked for :

  1. Clean drive completely as follows:

dd if=/dev/zero of=/dev/ada1 bs-16M

  1. Go to installer
  2. Add swap partition

Bottom line:
Either installer can add this step as a hack, underlying FreeBSD gpart or ZFS utils should purge disk more cleanly

@RodMyers
Copy link
Contributor

@RodMyers RodMyers commented Jan 22, 2019

gpart show
=> 40 468862048 ada0 GPT (224G)
40 204800 1 efi (100M)
204840 466538496 2 freebsd-zfs (222G)
466743336 2097152 3 freebsd-swap (1.0G)
468840488 21600 - free - (11M)

using the RELEASE ISO

@RodMyers RodMyers closed this Jan 22, 2019
@maxsteciuk
Copy link
Author

@maxsteciuk maxsteciuk commented Jan 22, 2019

As per comment above it’s kind of fixed , since prerelease

@RodMyers
Copy link
Contributor

@RodMyers RodMyers commented Jan 22, 2019

I know have close access. forgot who I talked to earlier

thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment