Date: Mon, 29 Feb 2016 19:25:45 +0100 From: Bernt Hansson <bah@bananmonarki.se> To: Polytropon <freebsd@edvax.de> Cc: questions FreeBSD <FreeBSD-questions@freebsd.org> Subject: Re: boot code Message-ID: <56D48D29.4060608@bananmonarki.se> In-Reply-To: <20160228235850.5051e942.freebsd@edvax.de> References: <56D376F9.10207@bananmonarki.se> <20160228235850.5051e942.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-02-28 23:58, Polytropon wrote: > On Sun, 28 Feb 2016 23:38:49 +0100, Bernt Hansson wrote: >> Hello list! >> >> I need to get the boot code on a hdd. >> Tried boot0cfg and fdisk -B /dev/ada1 >> >> But upon a reboot choosing the hdd it just don´t boot. > > The disk needs to have at least one partition that's marked > as active, if I remember correctly. This is the "old way" > of initializing it: > > # fdisk -BI /dev/ada1 > # bsdlabel -B -w ada0s1 > > Add "-b /boot/boot0" for the fdisk command if you need to > specify the boot code (normal boot or boot manager). > > If you want to use the whole disk as a "dedicated partition", > you can do this: > > # bsdlabel -w ada1 > # bsdlabel -e ada1 > set type "4.2BSD" for 'a' partition > make 'a' same size as 'c' > save > # newfs -m 0 -i 16384 -b 16384 -f 2048 -U -t enable -n disable -L ssdroot /dev/ada1a > # bsdlabel -B ada1 > > Adjust -i, -b and -f according to the expected usage. > But that's not a very kind way to deal with disks. :-) > > You should use gpart today. There is good documentation > in "man gpart", as well as those resources: > > http://www.wonkity.com/~wblock/docs/html/disksetup.html > > https://www.freebsd.org/doc/handbook/disks-adding.html > > http://www.freebsd.org/doc/handbook/geom-glabel.html > > Avoid MBR partitioning if possible - it's considered obsolete, > outdated, old-fashioned, stupid and lame. ;-) > Thank you but no cigar. The machine is amd64 10.2-R so my guess its gpt.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56D48D29.4060608>