Re: Boot Loader Problem
At 12:00 AM 9/18/2005, John Do wrote: Hi guys I still can't boot BSD :( I have tried everything I can and bla bla read etc etc :( Here is the setup (I boot off ad0) ad0 - boot loader and Windows XP ad2 slice 2 - FreeBSD Install Exactly from the emergency shell do I need to type to configure the bootloader so it gives the option of booting to ad2 slice 2? I have tried commands like: boot0cfg -B -s 5 ad0 boot0cfg -B -s 2 ad2 but no change in the boot menu I still see no change in the menu It shows 2 options Drive 1 Both options will boot Windows XP Please help thx! Output from the following commands would be most useful in helping to solve your problem. With the info you've provided so far, any suggestions would be mostly guesswork. fdisk /dev/ad0 fdisk /dev/ad2 bsdlabel /dev/ad0 bsdlabel /dev/ad2 boot0cfg -v /dev/ad0 boot0cfg -v /dev/ad2 -Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Loader Problem
Glenn Dawson <[EMAIL PROTECTED]> writes: >>boot0cfg -B -s 5 ad0 >>boot0cfg -B -s 2 ad2 I don't remember who asked what before, but you should also try: boot0cfg -B -s 5 -o packet ad0 boot0cfg -B -s 2 -o packet ad2 > fdisk /dev/ad0 > fdisk /dev/ad2 > bsdlabel /dev/ad0 I wouldn't bother if you don't have BSD on that disk. > bsdlabel /dev/ad2 and bsdlabel /dev/ad2s1 bsdlabel /dev/ad2s2 bsdlabel /dev/ad2s3 bsdlabel /dev/ad2s4 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Loader Problem
Hi Gary and Glen, I have the output. It was sure tiring to write out and then type back though :) bsdlabel /dev/ad2s1: No Valid Label bsdlabel /dev/ad2s2: 8 partitions # size offset fstype [fsizebsize bps/cpg] a: 8191983 0 4.2BSD 2048 16384 28552 b: 2047155 8191983 swap - -- c: 10239138 0 unused 0 0 #'raw' part don't edit bsdlabel /dev/ad2s3: No Valid Label bsdlabel /dev/ad2s4: No Such File Or Disk bsdlabel /dev/ad2: No Valid Label bsdlabel /dev/ad0: No Valid Label fdisk /dev/ad0 ** Working on device /dev/ad0 ** parameters extracted from in-core disklabel are: cylinders=39709 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=39703 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 7 (0x07), (OS/2 HPFS, NTFS, QNX-2 (16bit) or Advanced Unix) start 63, size 40001787 (19532 Meg), flag 80(active) beg: cyl 0 /head1 /sector 1 end: cyl 1023 /head 254 /sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: fdisk ad2: ** Working on device /dev/ad2 ** parameters extracted from in-core disklabel are: cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 to be used for BIOS calculations are: cylinders=155061 heads=61 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partion 1 is: sysid 7(0x07), (OS/2 HPFS, NTFS, QNX-2 (16bit) or Advanced Unix) start 63, size 133114527 (64997 Meg), flag 0 beg: cyl 0 /head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165(0xa5), (FreeBSD/NetBSD/386BSD) start 133114590, size 10239138 (4999 Meg), flag 0 beg: cyl 986/head 2 /sector 1; end: cyl 903/head 15 /sector 63 The data for partion 3 is: sysid 131 (0x83), (Linux Native) start 143364060, size 48195 (23 meg), flag 0 beg: cyl 1023/head 254/sector 63; end: cyl 1023/head 254/sector 63 The data for partition 4 is: boot0cfg -v /dev/ad0 # flag | start chs | type| end chs | offset | size 1 0x80 0: 1:10x07 1023 254:63 63 40001787 boot0cfg -v /dev/ad2 # flag | start chs | type| end chs | offset | size 1 0x00 0: 1:10x07 1023 254:63 63 133114527 2 0x00 986: 2:10x05 903 15:63 133114590 10239138 3 0x001024 254:630x83 1023 254:63 143364060 48195 --- "Gary W. Swearingen" <[EMAIL PROTECTED]> wrote: > Glenn Dawson <[EMAIL PROTECTED]> writes: > > >>boot0cfg -B -s 5 ad0 > >>boot0cfg -B -s 2 ad2 > > I don't remember who asked what before, but you > should also try: > > boot0cfg -B -s 5 -o packet ad0 > boot0cfg -B -s 2 -o packet ad2 > > > fdisk /dev/ad0 > > fdisk /dev/ad2 > > bsdlabel /dev/ad0 > > I wouldn't bother if you don't have BSD on that > disk. > > > bsdlabel /dev/ad2 > > and > > bsdlabel /dev/ad2s1 > bsdlabel /dev/ad2s2 > bsdlabel /dev/ad2s3 > bsdlabel /dev/ad2s4 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Loader Problem
John Do <[EMAIL PROTECTED]> writes: fdisk, etc, looked good. > boot0cfg -v /dev/ad0 > > # flag | start chs | type| end chs >| offset | size > 1 0x80 0: 1:10x07 1023 254:63 63 > 40001787 OK. > boot0cfg -v /dev/ad2 > > # flag | start chs | type| end chs >| offset | size > 1 0x00 0: 1:10x07 1023 254:63 63 > 133114527 > 2 0x00 986: 2:10x05 903 15:63 133114590 > 10239138 > 3 0x001024 254:630x83 1023 254:63 143364060 48195 The type on line "2" should be 0xa5, not 0x05, but I suspect a typo. I don't know if one of the flag's needs to be 0x80, or not. Both of my disks have one marked 0x80. It's probably OK, and just means you don't have a default slice, eg, set with "-s 2" in boot0cfg. >> I don't remember who asked what before, but you should also try: >> >> boot0cfg -B -s 5 -o packet ad0 >> boot0cfg -B -s 2 -o packet ad2 You didn't say if you tried those, but it doesn't seem to be the problem (yet). You would need -o packet on ad2 and LBA BIOS mode, I think since your FreeBSD slice goes past 1024 cyls. But that 133114590 number looks right, and I see no other problem. So it looks like the the MBR code just doesn't see the second disk. Probably because the BIOS doesn't play well with the MBR code, and I can't think why. It should even have to get the geometry right since it only has to grab the first sector of the disk. And you know other software can see the disk. At this point I'd give up on "boot0" and try to find a Grub (or GAG?) floppy to boot from. It should let you boot both systems. Or try a boot manager from the MSFT world. Sorry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Loader Problem
Hi Gary Thanks for your help. I am perplexed and frustrated by BSD's bootloader :) >> boot0cfg -B -s 5 -o packet ad0 >> boot0cfg -B -s 2 -o packet ad2 I did't try those yet because I wanted to see if you could find a problem first. I'll try those in a bit. In the mean time I created a GRUB ISO boot CD and I can simply boot BSD by booting with the GRUB CD and typing: rootnoverify (hd2,1) makeactive chainloader +1 boot GRUB has always been simple and intuitive for me so I'll stick with that and stay away from the hell of the BSD boot loader :) This really is my only gripe about FreeBSD I think it should include GRUB or they need to create a better native loader. Thanks Gary and I'll let you know what happens with the boot0cfg --- "Gary W. Swearingen" <[EMAIL PROTECTED]> wrote: > John Do <[EMAIL PROTECTED]> writes: > > fdisk, etc, looked good. > > > boot0cfg -v /dev/ad0 > > > > # flag | start chs | type| end > chs > >| offset | size > > 1 0x80 0: 1:10x07 1023 > 254:63 63 40001787 > > OK. > > > boot0cfg -v /dev/ad2 > > > > # flag | start chs | type| end > chs > >| offset | size > > 1 0x00 0: 1:10x07 1023 > 254:63 63 133114527 > > 2 0x00 986: 2:10x05 903 > 15:63 133114590 10239138 > > 3 0x001024 254:630x83 1023 > 254:63 143364060 48195 > > The type on line "2" should be 0xa5, not 0x05, but I > suspect a typo. > I don't know if one of the flag's needs to be 0x80, > or not. Both of > my disks have one marked 0x80. It's probably OK, > and just means > you don't have a default slice, eg, set with "-s 2" > in boot0cfg. > > >> I don't remember who asked what before, but you > should also try: > >> > >> boot0cfg -B -s 5 -o packet ad0 > >> boot0cfg -B -s 2 -o packet ad2 > > You didn't say if you tried those, but it doesn't > seem to be the > problem (yet). You would need -o packet on ad2 and > LBA BIOS mode, I > think since your FreeBSD slice goes past 1024 cyls. > > But that 133114590 number looks right, and I see no > other problem. > > So it looks like the the MBR code just doesn't see > the second disk. > Probably because the BIOS doesn't play well with the > MBR code, and I > can't think why. It should even have to get the > geometry right since > it only has to grab the first sector of the disk. > And you know other > software can see the disk. At this point I'd give > up on "boot0" and > try to find a Grub (or GAG?) floppy to boot from. > It should let you > boot both systems. Or try a boot manager from the > MSFT world. > > Sorry. > __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
