Date: Wed, 10 Mar 2010 12:17:39 -0300 From: Paulo Fragoso <paulo@nlink.com.br> To: Zavam, =?ISO-8859-1?Q?Vin=EDcius?= <egypcio@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: freebsd 8.0 stable amd64/x86 needs ~9min to bootup Message-ID: <4B97B813.50102@nlink.com.br> In-Reply-To: <8b5ad0e11002050329n7fe0173aw735211d7eaea731f@mail.gmail.com> References: <8b5ad0e11001270926o19d1701fid30ba5a49cbb39b5@mail.gmail.com> <4B61295F.1030802@incunabulum.net> <8b5ad0e11001280245h703990a3t2085588e141b0ab6@mail.gmail.com> <8b5ad0e11002050329n7fe0173aw735211d7eaea731f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This problem happened with me too. I don't know why boot loader makes
intensive reads when installed on partition created by another fdisk
(windows, linux, etc) and started by GRUB2.
There is a workaround for this, you have to create all partitions with
freebsd sysinstall included windows and linux partitions. After this do
install for all others OSes using those partitions created by sysinstall.
In my case there are 03 OSes installed on same HD:
1: Windows boot loader: 1023MB
2: Windows 7: 50GB
3: PCBSD 8.0: 70GB
* -> 5: Linux 108GB
6: Linux swap
This problem can be tested before install if you run sysinstall and
choses partiotion menu if you receive alerts like this: "Partition X
does not end on cylinder boundary" you will have problem with GRUB2.
I'm using GRUB2 from Ubuntu 9.10 with this entry in file
/etc/grub.d/40_custom:
menuentry "FreeBSD/PCBSD 8.0 AMD64" {
set root=(hd0,3)
chainloader +1
}
All works fine!
Paulo.
Em 05/02/2010 08:29, Zavam escreveu:
> 2010/1/28 Zavam, Vinícius <egypcio@gmail.com>:
>
>> 2010/1/28 Bruce Simpson <bms@incunabulum.net>:
>>
>>> Try GRUB4DOS. I use this so on boxes where I have Windows installed, I can
>>> keep GRUB in the NTFS partition.
>>>
>>> I haven't seen this issue and am tracking -STABLE on an ASUS V-series
>>> machine.
>>>
>>>
>> Simpson,
>> I forgot to mention... but I tested it using boot0 (freebsd's
>> bootmanager) with no success ;<
>>
>> had no shots with grub4dos, gag, lilo or grub2; I assume it may not be
>> a bootmanager issue, but freebsd's btx bootstrap loader.
>> my gentoo and windows o.s. can be loaded using grub or boot0.
>>
>>
>> --
>> Zavam, Vinícius
>>
>
> gentlemen,
> morning.
>
> I just did new fresh installs using 80-STABLE/amd64 and
> 90-CURRENT/amd64 snapshots.
> unfortunately, no success.
>
> when tryied the 90-CURRENT I've created a slice to /boot (d) at the
> beginning of the partition (ad4s4) and grub returned error code 18
> [1].
> strange. even installing in another slice, at the beginning of the
> disk (ad4s1), the bootup process was slow too.
>
> [1] http://wiki.linuxquestions.org/wiki/GRUB#Error_18
>
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B97B813.50102>