gpart bootcode for MBR + ZFS?

Julien Cigar julien at perdition.city
Fri Sep 6 11:55:36 UTC 2019


On Fri, Sep 06, 2019 at 12:06:49PM +0200, Julien Cigar wrote:
> Hello,
> 
> It's a long time since I had to deal with MBR partition scheme..
> I had to replace a disk (ada1) in an old machine with the following
> partition scheme:
> 
> ~/ gpart show
> =>        63  4294967232  ada0  MBR  (3.6T)
>           63           1        - free -  (512B)
>           64  4294967224     1  freebsd  [active]  (2.0T)
>   4294967288           7        - free -  (3.5K)
> 
> =>         0  4294967224  ada0s1  BSD  (2.0T)
>            0     4194304       1  freebsd-zfs  (2.0G)
>      4194304    67108864       2  freebsd-swap  (32G)
>     71303168  4223664048       4  freebsd-zfs  (2.0T)
>   4294967216           8          - free -  (4.0K)
> 
> =>        63  4294967232  ada1  MBR  (3.6T)
>           63           1        - free -  (512B)
>           64  4294967224     1  freebsd  [active]  (2.0T)
>   4294967288           7        - free -  (3.5K)
> 
> =>         0  4294967224  ada1s1  BSD  (2.0T)
>            0     4194304       1  freebsd-zfs  (2.0G)
>      4194304    67108864       2  freebsd-swap  (32G)
>     71303168  4223664048       4  freebsd-zfs  (2.0T)
>   4294967216           8          - free -  (4.0K)
> 
> I did the usual: 
> $> gpart backup ada0 | gpart restore -F ada1
> $> gpart backup ada0s1 | gpart restore -F ada1s1
> $> gpart bootcode -b /boot/boot0 ada1
> 
> My question is: is it enough or do I need to dd /boot/zfsboot somewhere
> ..?
> 
> ZFS pools are:
> 
> ~/ zpool status
>   pool: bootpool
>  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: resilvered 183M in 0 days 00:01:40 with 0 errors on Fri Sep  6 11:13:54 2019
> config:
> 
> 	NAME         STATE     READ WRITE CKSUM
> 	bootpool     ONLINE       0     0     0
> 	  mirror-0   ONLINE       0     0     0
> 	    ada0s1a  ONLINE       0     0     0
> 	    ada1s1a  ONLINE       0     0     0
> 
> errors: No known data errors
> 
>   pool: zroot
>  state: ONLINE
> status: One or more devices is currently being resilvered.  The pool will
> 	continue to function, possibly in a degraded state.
> action: Wait for the resilver to complete.
>   scan: resilver in progress since Fri Sep  6 11:11:33 2019
> 	410G scanned at 138M/s, 210G issued at 70.9M/s, 632G total
> 	210G resilvered, 33.21% done, 0 days 01:41:39 to go
> config:
> 
> 	NAME         STATE     READ WRITE CKSUM
> 	zroot        ONLINE       0     0     0
> 	  mirror-0   ONLINE       0     0     0
> 	    ada0s1d  ONLINE       0     0     0
> 	    ada1s1d  ONLINE       0     0     0
> 
> errors: No known data errors
> 
> and I have the following in loader.conf:
> 
> vfs.root.mountfrom="zfs:zroot/ROOT/default"
> zfs_load="YES"
> zpool_cache_load="YES"
> zpool_cache_name="/boot/zfs/zpool.cache"
> zpool_cache_type="/boot/zfs/zpool.cache"
> 
> Thank you!
> 
> Julien

From what I understand I /boot/boot0 (or mbr) only provides stage 0, for
stage 1 and stage 2 I should use:
$> dd if=/boot/zfsboot of=/dev/ada1s1 count=1
$> dd if=/boot/zfsboot of=/dev/ada1s1a iseek=1 oseek=1024

However I'm getting a "Operation not permitted" even with
kern.geom.debugflags=0x10 .. any idea?

> 
> 
> -- 
> Julien Cigar
> Belgian Biodiversity Platform (http://www.biodiversity.be)
> PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0
> No trees were killed in the creation of this message.
> However, many electrons were terribly inconvenienced.



-- 
Julien Cigar
Belgian Biodiversity Platform (http://www.biodiversity.be)
PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20190906/70ca4b5f/attachment.sig>


More information about the freebsd-questions mailing list