Date: Thu, 2 Apr 2020 03:00:59 -0500 From: CyberLeo Kitsana <cyberleo@cyberleo.net> To: Artem Kuchin <artem@artem.ru>, FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: gmirror disks differ at start.no boot from another disk? Message-ID: <0bc315a0-d3f0-bdfa-c446-127f1d3a89dc@cyberleo.net> In-Reply-To: <901cb384-0888-a71c-2816-dff3e29b8119@artem.ru> References: <901cb384-0888-a71c-2816-dff3e29b8119@artem.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/1/20 2:09 AM, Artem Kuchin wrote: > Hello! > > Since i had a bad sector and corrected it i decided also to check how my > mirror is in sync. > > What i found out that two disks have totally dfferent starting bytes. > Cannot for sure what's there, > > but it seems like one disk has a bootloader and anoter one does not. So, > if disk with bootloader fails i will not > > be able to boot from the mirror disk. <snip> It's always a good idea to update your bootcode on all root/boot disks every time you update your operating system, just in case a new feature sneaks in that the bootloader needs to understand. The command 'gpart bootcode' is your friend. Its usage, however, is heavily dependent upon your system's setup, so examples will likely be of little use to you. -- Fuzzy love, -CyberLeo <CyberLeo@CyberLeo.Net> Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Element9 Communications http://www.Element9.net Furry Peace! - http://www.fur.com/peace/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0bc315a0-d3f0-bdfa-c446-127f1d3a89dc>