ZFS boot inside on the second partition inside a slice
Zhihao Yuan
lichray at gmail.com
Sat Jun 18 02:18:30 UTC 2011
If this problem can not be solved, I probably have to redo everything
to use GPT-based solution and lose my Windows.............
On Fri, Jun 17, 2011 at 12:37 PM, John Baldwin <jhb at freebsd.org> wrote:
> On Friday, June 17, 2011 1:06:22 pm Henri Hennebert wrote:
>> On 06/16/2011 19:35, John Baldwin wrote:
>> > On Thursday, June 16, 2011 8:45:41 am Zhihao Yuan wrote:
>> >> Exactly. The MFCed ZFSv28 is different from any patch maintained by
>> >> mm at . Maybe some untested changes involved.
>> >
>> > Can you try reverting this change:
>> >
>> > Author: jhb
>> > Date: Thu Apr 28 17:44:24 2011
>> > New Revision: 221177
>> > URL: http://svn.freebsd.org/changeset/base/221177
>> >
>> > Log:
>> > Due to space constraints, the UFS boot2 and boot1 use an evil hack where
>> > boot2 calls back into boot1 to perform disk reads. The ZFS MBR boot blocks
>> > do not have the same space constraints, so remove this hack for ZFS.
>> > While here, remove commented out code to support C/H/S addressing from
>> > zfsldr. The ZFS and GPT bootstraps always just use EDD LBA addressing.
>> >
>> > MFC after: 2 weeks
>> >
>> > Modified:
>> > head/sys/boot/i386/boot2/Makefile
>> > head/sys/boot/i386/common/drv.c
>> > head/sys/boot/i386/zfsboot/Makefile
>> > head/sys/boot/i386/zfsboot/zfsldr.S
>> >
>> I try with this revision (221177) reverted to no avail:
>> same error - 'read error'
>
> Hmm, ok. No other ideas off the top of my head.
>
> --
> John Baldwin
>
--
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___________________________________________________
4BSD -- http://4bsd.biz/
More information about the freebsd-stable
mailing list