Date: Thu, 19 Dec 2002 11:47:44 -0500 (EST) From: Jerry McAllister <jerrymc@clunix.cl.msu.edu> To: sleek@enabled.com (Noah Garrett Wallach) Cc: jerrymc@clunix.cl.msu.edu (Jerry McAllister), freebsd-questions@FreeBSD.ORG Subject: Re: Drive Failure Message-ID: <200212191647.gBJGli000030@clunix.cl.msu.edu> In-Reply-To: <20021219082002.I79285-100000@typhoon.enabled.com> from "Noah Garrett Wallach" at Dec 19, 2002 08:22:00 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > I dont know what this option means - does this matter? > > > > > > -B Install the `boot0' boot manager. This option causes MBR > > > code to > > > be replaced, without affecting the embedded slice table. > > > > Sounds like just what you said you wanted. > > > > Hi Jerry, > > What does "without affecting the embedded slice table" mean? What si the > embedded slice table? And should I make sure that I dont affect it - or > should I affect it? It is the table that specifies the drives slices - 1-4, what it thinks is in them and a flag which says which one is active - to booted from. It is what gets printed when you do fdisk -s ad2 or whatever drive. > also is there anyway to see that, after replacing the MBR on the new > drive with boot0cfg, that it is properly bootable? The above will tell you which slice is bootable, which in this case would only be slice 1 since you are only making one slice. The other possible slice identifiers (2-4) are not being used. But, it can't tell you if it is proper. Only trying to boot it will tell you that. So, do a little smoke testing. Jump. Dive in. If you are doing all this without backing things up, you're courting disaster anyway. ////jerry > > - noah > > > > > By the way, I notice that you have quit CC-ing the questions list. > > You should keep that in so it gets in archives and so I don't become > > the sole counselor - which you don't want, for sure! > > > > ////jerry > > > > > > > > - Noah > > > > > > > > > > > > > > ////jerry > > > > > > > > > ******* Working on device /dev/ad2 ******* > > > > > parameters extracted from in-core disklabel are: > > > > > cylinders=148945 heads=16 sectors/track=63 (1008 blks/cyl) > > > > > > > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > > > > parameters to be used for BIOS calculations are: > > > > > cylinders=148945 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 165,(FreeBSD/NetBSD/386BSD) > > > > > start 63, size 150136497 (73308 Meg), flag 80 (active) > > > > > beg: cyl 0/ head 1/ sector 1; > > > > > end: cyl 464/ head 15/ sector 63 > > > > > The data for partition 2 is: > > > > > <UNUSED> > > > > > The data for partition 3 is: > > > > > <UNUSED> > > > > > The data for partition 4 is: > > > > > <UNUSED> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212191647.gBJGli000030>