Bug 227772

Summary:

regression: gptzfsboot sees remains of old pools and fails to boot

Product:

Base System

Reporter:

emz

Component:

bin

Assignee:

freebsd-bugs (Nobody) <bugs>

Status:

New ---

Severity:

Affects Only Me

Keywords:

regression

Priority:

---

Version:

11.1-STABLE

Hardware:

Any

OS:

Any

Attachments:

Description	Flags
boot screen with loader stuck, initial screen	none
boot screen with loader stuck on custom pool/kernel path	none

Description emz 2018-04-25 15:29:08 UTC

Using 11.1-RELEASE I was getting the "cannot read MOS" message concering the old deleted pool (which labels for some reason persist on the new vdevs) but this didn't lead to the inability to boot.

Using recent STABLE r332095 gptzfsboot it now does.

I'm getting various messages (see attached screenshots) but the most fatal semmms to be "ZFS unexpected object set type 0", then booting process hangs, gptzfsboot seems to see the pool, but entering the pool name and path to the kernel does nothing - progress bar stucks.

The workaround is to use old 11.1 gptzfsboot loader.

Comment 1 emz 2018-04-25 15:30:11 UTC

Created attachment 192810 [details]
boot screen with loader stuck, initial screen

Comment 2 emz 2018-04-25 15:30:41 UTC

Created attachment 192811 [details]
boot screen with loader stuck on custom pool/kernel path

Comment 3 emz 2018-04-25 15:32:14 UTC

Follow-up: zfsroot is the actual live pool, esx is the old non-existent pool. gamestop is the old-non-existent pool with one device from it (it actually contain full fragment since it's the old spare disk), zroot is the old non-existent pool.