> I think you're probably right about this being a BIOS problem.
> Does the gptzfsboot 'status' command show the same output when you run it
> with and without the F12 workaround? Here's what I see from FreeBSD and from
> gptzfsboot:
> [root ~]# zpool status
> pool: glamdring
> state: ONLINE
> scrub: none requested
> config:
>
> NAME STATE READ WRITE CKSUM
> glamdring ONLINE 0 0 0
> raidz2 ONLINE 0 0 0
> label/glamdring-0 ONLINE 0 0 0
> label/glamdring-1 ONLINE 0 0 0
> label/glamdring-2 ONLINE 0 0 0
> label/glamdring-3 ONLINE 0 0 0
> label/glamdring-4 ONLINE 0 0 0
> label/glamdring-5 ONLINE 0 0 0
>
> errors: No known data errors
> ...
>
> /boot.config: -Dh
> Default: glamdring:/boot/zfsloader
> boot: status pool: glamdring
> config:
>
> NAME STATE
> glamdring ONLINE
> raidz2 ONLINE
> label/glamdring-0 ONLINE
> label/glamdring-1 ONLINE
> label/glamdring-2 ONLINE
> label/glamdring-3 ONLINE
> label/glamdring-4 ONLINE
> label/glamdring-5 ONLINE
> Matt
I'm seeing some difference in the bootloader output between using the
F12 workaround or not:
F12 workaround mode:
FreeBSD/i386 boot
Default: zroot:/boot/zfsloader
boot: status
config:
NAME STATE
zroot ONLINE
gpt/disk0 ONLINE
No F12 key pressed:
FreeBSD/i386 boot
Default: zroot:/boot/kernel/kernel
config:
NAME STATE
zroot ONLINE
gpt/disk0 ONLINE
What's up with the differences between the Default boot setting?
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[email protected]"
