Thanks for the explanation!
The patch didn't fix it though (as it probably only works against log
partitions).
On Jul 11, 2011, at 4:45 PM, Matt Burke wrote:
On 07/06/11 16:44, Berczi Gabor wrote:
For some reason FreeBSD can't boot automatically:
...
I have two pools, pool2 which
On Jul 6, 2011, at 10:08 PM, Volodymyr Kostyrko wrote:
1. Check that pools have up-to-date boot code.
I tried 8.2 and HEAD. You mean gpart+gptzfsboot+pmbr, right?
2. Try to convince bios to boot from the disk of pool2.
There is no disk with a singular ZFS pool.
3. You can possibly try
On Jul 7, 2011, at 12:19 PM, Volodymyr Kostyrko wrote:
2. Try to convince bios to boot from the disk of pool2.
There is no disk with a singular ZFS pool.
Any disk from bootable pool.
Every disk contains two pools. And the BIOS sees only two (maybe three) of them.
3. You can possibly
Greets,
For some reason FreeBSD can't boot automatically:
ZFS: i/o error - all block copies unavailable
ZFS: can't read MOS object directory
Can't find root filesystem - giving up
ZFS: unexpected object set type 0
ZFS: unexpected object set type 0
FreeBSD/x86 boot
Default:
Thanks, but that did not help.
On Jul 6, 2011, at 6:31 PM, Pan Tsu wrote:
If you're using gptzfsboot try tricking it by marking
partitions with `data' pool as freebsd-ufs, e.g.
$ gpart modify -t freebsd-ufs -iY adX
___
On Jul 6, 2011, at 9:43 PM, Aldis Berjoza wrote:
Any chance, that you forgot to
# zpool set bootfs= ...
?
Nope.
NAME PROPERTY VALUE SOURCE
pool2 bootfspool2 local
NAME PROPERTY VALUE SOURCE
data bootfs- default
___
