Re: freebsd / gpt boot
On Tue, 2009-12-15 at 17:11 -0500, Adam Jacob Muller wrote: On Dec 14, 2009, at 10:46 AM, Robert Noland wrote: On Sun, 2009-12-13 at 23:21 +0100, 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 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)? You will need to be doing all of this from a current 8-STABLE. One bug in dealing with larger zfs raidz volumes was fixed and made it into 8.0. Another, which deals with GPT/ZFS and large volumes did not make it and only exists in 8-STABLE, iirc. Also, with the gptzfsboot code from -STABLE, it will request to load /boot/zfsloader by default (and LOADER_ZFS_SUPPORT is no longer required). gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 Have you embedded the correct boot code? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 (for booting from ufs). or gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (for booting from zfs). You may also need to set it active by gpart set -a active -i 1 da0 The above step is no longer needed on -STABLE, the pmbr will be marked active when you install bootcode. Robert, Do either of these bugs affect GPT/UFS, which is what I am using here. I thought that one of them was relevant, but looking back at the patch, I believe that it only impacted gpt + zfs. robert. These bugs are affecting the actual older versions of the tools (IE using the gpart from an 8.0-pre or earlier could cause issues like this)? Also, perhaps not coincidentally, booting the FreeBSD memstick image produces the same error (boot0 can't find loader). -Adam robert. And of course, substitute your arrays device node for da0 in my examples. 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=ufs:/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-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Robert Noland rnol...@freebsd.org FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Robert Noland rnol...@freebsd.org FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
On Dec 14, 2009, at 10:46 AM, Robert Noland wrote: On Sun, 2009-12-13 at 23:21 +0100, 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 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)? You will need to be doing all of this from a current 8-STABLE. One bug in dealing with larger zfs raidz volumes was fixed and made it into 8.0. Another, which deals with GPT/ZFS and large volumes did not make it and only exists in 8-STABLE, iirc. Also, with the gptzfsboot code from -STABLE, it will request to load /boot/zfsloader by default (and LOADER_ZFS_SUPPORT is no longer required). gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 Have you embedded the correct boot code? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 (for booting from ufs). or gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (for booting from zfs). You may also need to set it active by gpart set -a active -i 1 da0 The above step is no longer needed on -STABLE, the pmbr will be marked active when you install bootcode. Robert, Do either of these bugs affect GPT/UFS, which is what I am using here. These bugs are affecting the actual older versions of the tools (IE using the gpart from an 8.0-pre or earlier could cause issues like this)? Also, perhaps not coincidentally, booting the FreeBSD memstick image produces the same error (boot0 can't find loader). -Adam robert. And of course, substitute your arrays device node for da0 in my examples. 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=ufs:/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-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Robert Noland rnol...@freebsd.org FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
The following worked for me on 8TB array: Add slices as needed (modify sizes as required): gpart add -s 128K -t freebsd-boot da0 gpart add -s 1G -t freebsd-ufs -l root da0 gpart add -s 10G -t freebsd-swap -l swap da0 gpart add ... Then for installing the bootcode: gpart bootcode -b /mnt2/boot/pmbr -p /mnt2/boot/gptboot -i 1 da0 From re-reading you initial post the problem seems to be that its not mounting root correctly is that the case, as you don't explicitly say what the error is your getting? Regards Steve - Original Message - From: Adam Jacob Muller freebsd-sta...@adam.gs I'm assuming your referring to FreeBSD 8 GPT install, how? thread you originated? While that thread covers generically installing on GPT, it does not cover this issue. Also, even after adjusting a few things -- using gpart instead of gpt to make partitions and gpart bootcode instead of gpt boot which is the only difference between what these faqs suggest and what I was doing -- I am still encountering the same issue. This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
On Sun, 13 Dec 2009 22:53:44 + Steven Hartland kill...@multiplay.co.uk wrote: The only thing I'd warn you about is to ensure you use the DVD not the CD as the CD doesn't have all the things you'll need on it. FWIW, the memstick image worked nicely, too. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
Possibly the issue we had was the live CD doesn't include dist but you cant remove it once your in it so no way to do the actual install. Using a memstick live would presumably get around this issue due to the fact you can have Disk 0 in the CDROM as well :) Regards Steve - Original Message - From: Torfinn Ingolfsen On Sun, 13 Dec 2009 22:53:44 + Steven Hartland kill...@multiplay.co.uk wrote: The only thing I'd warn you about is to ensure you use the DVD not the CD as the CD doesn't have all the things you'll need on it. FWIW, the memstick image worked nicely, too. This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
On Sun, 2009-12-13 at 23:21 +0100, 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 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)? You will need to be doing all of this from a current 8-STABLE. One bug in dealing with larger zfs raidz volumes was fixed and made it into 8.0. Another, which deals with GPT/ZFS and large volumes did not make it and only exists in 8-STABLE, iirc. Also, with the gptzfsboot code from -STABLE, it will request to load /boot/zfsloader by default (and LOADER_ZFS_SUPPORT is no longer required). gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 Have you embedded the correct boot code? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 (for booting from ufs). or gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (for booting from zfs). You may also need to set it active by gpart set -a active -i 1 da0 The above step is no longer needed on -STABLE, the pmbr will be marked active when you install bootcode. robert. And of course, substitute your arrays device node for da0 in my examples. 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=ufs:/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-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Robert Noland rnol...@freebsd.org FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
On Mon, 14 Dec 2009 15:28:50 + Steven Hartland kill...@multiplay.co.uk wrote: Using a memstick live would presumably get around this issue due to the fact you can have Disk 0 in the CDROM as well :) Err, no. It gets around thia by the very fact that all files required are on the memstick image - no other image required. :) The machine I installed on didn't have an optical drive at all. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
- Original Message - From: Torfinn Ingolfsen torfinn.ingolf...@broadpark.no Err, no. It gets around thia by the very fact that all files required are on the memstick image - no other image required. :) The machine I installed on didn't have an optical drive at all. Noted for future reference, thanks Toffin. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
freebsd / gpt boot
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 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=ufs:/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-unsubscr...@freebsd.org
Re: freebsd / gpt boot
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 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)? gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 Have you embedded the correct boot code? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 (for booting from ufs). or gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (for booting from zfs). You may also need to set it active by gpart set -a active -i 1 da0 And of course, substitute your arrays device node for da0 in my examples. 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=ufs:/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-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
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 = 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 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)? gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 Have you embedded the correct boot code? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 (for booting from ufs). or gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (for booting from zfs). You may also need to set it active by gpart set -a active -i 1 da0 And of course, substitute your arrays device node for da0 in my examples. 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=ufs:/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-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
There's already a thread about this last week, which contains the info you need to set this up. The only thing I'd warn you about is to ensure you use the DVD not the CD as the CD doesn't have all the things you'll need on it. Regards Steve - Original Message - From: Adam Jacob Muller freebsd-sta...@adam.gs To: freebsd-stable@freebsd.org Sent: Sunday, December 13, 2009 8:26 PM Subject: freebsd / gpt boot 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 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=ufs:/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-unsubscr...@freebsd.org This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
I'm assuming your referring to FreeBSD 8 GPT install, how? thread you originated? While that thread covers generically installing on GPT, it does not cover this issue. Also, even after adjusting a few things -- using gpart instead of gpt to make partitions and gpart bootcode instead of gpt boot which is the only difference between what these faqs suggest and what I was doing -- I am still encountering the same issue. -Adam On Dec 13, 2009, at 5:53 PM, Steven Hartland wrote: There's already a thread about this last week, which contains the info you need to set this up. The only thing I'd warn you about is to ensure you use the DVD not the CD as the CD doesn't have all the things you'll need on it. Regards Steve - Original Message - From: Adam Jacob Muller freebsd-sta...@adam.gs To: freebsd-stable@freebsd.org Sent: Sunday, December 13, 2009 8:26 PM Subject: freebsd / gpt boot 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 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=ufs:/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-unsubscr...@freebsd.org This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd / gpt boot
Adam Jacob Muller wrote: On Dec 13, 2009, at 7:45 PM, Rolf G Nielsen wrote: Adam Jacob Muller wrote: On Dec 13, 2009, at 6:35 PM, Rolf G Nielsen wrote: Adam Jacob Muller wrote: Hi Rolf, I am using the gpt boot command right after calling gpart create which should combine the add/bootcode. Sorry, but I can't help you there. I moved to GUID partitions when upgrading to 8.0, and 8.0 doesn't have the gpt command (at least my install doesn't), thus I'm not familiar with it. Interesting, I hadn't realized that gpt was removed in 8.0 and replaced with gpart, I just redid everything I was doing using gpart instead of gpt and unfortunately I have the same result. Things do look right from a gpart show # gpart show = 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 I've never actually tried it myself, because it worked for me without it. I just took it from a tutorial I read after I had made the switch. I didn't bother to keep the address, but I stumbled upon it when reading about booting from ZFS. -Adam Anyway, I saw someone else had replied saying that there recently was a thread about this. I hope you find it, and that it will help you. unfortunately that thread is really not really relevant beyond generic having a few pointers to generic install-howtos. Good Luck! Rolf Nielsen 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 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)? gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 Have you embedded the correct boot code? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 (for booting from ufs). or gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (for booting from zfs). You may also need to set it active by gpart set -a active -i 1 da0 And of course, substitute your arrays device node for da0 in my examples. 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=ufs:/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-unsubscr...@freebsd.org Just a thought. Do you have options GEOM_PART_GPT in your kernel? It's a longshot, as without it you probably wouldn't get as far as you do. It's included in the 8.0 GENERIC kernel, but in case you have a custom kernel whose config you imported from a previous version, it may be worth checking. Yes, it is in there, but I don't see that affecting the boot0 or loader.. -Adam You're right. Shouldn't affect anything before the kernel. Like I said, a longshot. I'm out of ideas. Hope you solve it. Rolf P.S. I just realised I'd been omitting the list in my replies. Apologies. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org