Date: Sun, 13 Dec 2009 18:00:38 -0500 From: Adam Jacob Muller <freebsd-stable@adam.gs> To: Rolf G Nielsen <lazlar@lazlarlyricon.com> Cc: freebsd-stable@freebsd.org, Adam Jacob Muller <freebsd-stable@adam.gs> Subject: Re: freebsd / gpt boot Message-ID: <586264AE-3DB3-4999-8F8C-A51329DA2BEA@adam.gs> In-Reply-To: <4B256907.4060805@lazlarlyricon.com> References: <2A3A50FE-13F4-4AA7-976E-37354E5736B5@adam.gs> <4B256907.4060805@lazlarlyricon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Rolf,
I am using the "gpt boot" command right after calling "gpart create" =
which should combine the add/bootcode.
Things do look right from a "gpart show"
# gpart show
=3D> 34 19529727933 mfid0 GPT (9.1T)
34 128 1 freebsd-boot (64K)
162 1048576 2 freebsd-swap (512M)
1048738 19528679229 3 freebsd-ufs (9.1T)
This does not work though,
> gpart set -a active -i 1 da0
# gpart set -a active -i 1 mfid0
gpart: attrib 'active': Device not configured
-Adam
On Dec 13, 2009, at 5:21 PM, Rolf G Nielsen wrote:
> Adam Jacob Muller wrote:
>> Hi,
>> I'm trying to setup a system with a very large RAID array (total =
~10TB), I would ideally like to have the system boot directly off that =
10TB array, so i'm trying to get the system setup with GPT but running =
into an issue.
>> The initial pre-loader (boot0 I think? -- i'm not sure what this is =
called) is unable to find loader at /boot/loader nor can it load =
/boot/kernel/kernel
>=20
> Is the partitioning done correctly (have you created a small boot =
partition, 15 sectors is enough for booting from ufs, but the tutorials =
I've found deal mainly with booting from zfs and they recommend 128 =
sectors to make future bootcode changes easier)?
>=20
> gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0
>=20
> Have you embedded the correct boot code?
>=20
> gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0
> (for booting from ufs).
>=20
> or
>=20
> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0
> (for booting from zfs).
>=20
> You may also need to set it active by
>=20
> gpart set -a active -i 1 da0
>=20
> And of course, substitute your arrays device node for da0 in my =
examples.
>=20
>> Copying /boot/loader to /loader allows me to enter /loader at the =
"boot:" prompt and the loader will load, however, its unable to load the =
kernel.
>> If I do an "ls" at the loader prompt I can see boot listed as a =
directory (with a "d" before it)
>> Trying to do "ls boot" inexplicably it says "boot: not a directory"
>> re-applying my /boot/loader.conf settings (for some reason =
vfs.root.mountfrom=3Dufs:/dev/label/root is required, or else I get a =
mountroot>) and then:
>> load /kernel
>> boot
>> does work, and lets the system boot normally and everything is as =
expected (/boot is a directory etc).
>> Anyone have any ideas about either of these things (the =
vfs.root.mountfrom is minor i guess but i'm curious if they are =
related?)
>> Thanks in advance,
>> -Adam
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to =
"freebsd-stable-unsubscribe@freebsd.org"
>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?586264AE-3DB3-4999-8F8C-A51329DA2BEA>