Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Apr 2020 20:56:59 +0300
From:      Artem Kuchin <artem@artem.ru>
To:        CyberLeo Kitsana <cyberleo@cyberleo.net>, FreeBSD Questions Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: gmirror disks differ at start.no boot from another disk?
Message-ID:  <b7911b4d-7e78-5259-04f5-2a82287def80@artem.ru>
In-Reply-To: <0bc315a0-d3f0-bdfa-c446-127f1d3a89dc@cyberleo.net>
References:  <901cb384-0888-a71c-2816-dff3e29b8119@artem.ru> <0bc315a0-d3f0-bdfa-c446-127f1d3a89dc@cyberleo.net>

next in thread | previous in thread | raw e-mail | index | archive | help
02.04.2020 11:00, CyberLeo Kitsana пишет:
>
> It's always a good idea to update your bootcode on all root/boot disks
>
Tried

# sysctl -w kern.geom.debugflags=16
kern.geom.debugflags: 0 -> 16

# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada1
gpart: /dev/ada1p1: Operation not permitted

Stuck now Why not permitted?

ada1 is  a part of gmirror, maybe that's the reason? But then how should 
i do it?

Update mirror/boot ? But then if something goes wrong i would loose all 
boot loaders

and partitions on both disk. I want to do it only on one disk.


Artem




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b7911b4d-7e78-5259-04f5-2a82287def80>