Bug 248907 - zpool doesn't boot anymore on 12.1-STABLE after pool expansion
Summary: zpool doesn't boot anymore on 12.1-STABLE after pool expansion
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.1-STABLE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-25 18:12 UTC by Charles Goncalves
Modified: 2020-08-26 11:38 UTC (History)
3 users (show)

See Also:


Attachments
zpool doesnt boot (75.46 KB, image/png)
2020-08-25 18:12 UTC, Charles Goncalves
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Goncalves 2020-08-25 18:12:20 UTC
Created attachment 217522 [details]
zpool doesnt boot

Hi there,

I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I added two more disks to expand my pool. BTW I already did it many time with no issues.

I ran: 

# zpool status
  pool: zroot
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
	still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
	the pool may no longer be accessible by software that does not support
	the features. See zpool-features(7) for details.
  scan: none requested
config:

	NAME         STATE     READ WRITE CKSUM
	zroot        ONLINE       0     0     0
	  gpt/disk0  ONLINE       0     0     0

errors: No known data errors

# zpool add -f zroot da1
# zpool add -f zroot da2
# zpool status
  pool: zroot
 state: ONLINE
  scan: none requested
config:

	NAME         STATE     READ WRITE CKSUM
	zroot        ONLINE       0     0     0
	  gpt/disk0  ONLINE       0     0     0
	  da1        ONLINE       0     0     0
	  da2        ONLINE       0     0     0

errors: No known data errors
# reboot

Then my system doesn’t boot anymore, i got the following error:

See errors in my attachment

I can import my pool with no problems using the lived, but I could not fix it.

Seems a bug after 12.1-STABLE. Please, anyone can take a look ok that?

Thanks.