Re: bsdlabel question

From: Poul-Henning Kamp <phk_at_phk.freebsd.dk>
Date: Mon, 05 May 2003 07:25:07 +0200
In message <3EB5FC94.7070901_at_myrealbox.com>, walt writes:
>Poul-Henning Kamp wrote:
>> In message <31649.1052067538_at_critter.freebsd.dk>, "Poul-Henning Kamp" writes:
>> 
>>>In message <3EB50F10.3010001_at_myrealbox.com>, walt writes:
>>>
>>>>Hi Poul-Henning,
>>>>
>>>>#bsdlabel  ad0s3
>>>># /dev/ad0s3:
>>>>8 partitions:
>>>>#        size   offset    fstype   [fsize bsize bps/cpg]
>>>>  a: 15321596 140974726    4.2BSD        0     0     0
>>>>  b:  1048576 139926150      swap
>>>>  c: 16370235 139926150    unused        0     0         # "raw" part, don't edit
>>>
>>>Ahh, good point, forgot about that.  Will fix.
>> 
>> 
>> OK, fixed now.
>
>I find that I now have the same problem that Martin had --
>'cannot mount root:5'  Does the :5 mean anything special?
>
>I tried eliminating GEOM_MBR, GEOM_VOL, and GEOM_BSD from my
>kernel config with no improvement.
>
>The kernel from early today still boots normally, and bsdlabel
>still prints the same error messages, so I guess your changes
>were all in the kernel?

No, both kernel and userland changed.

If you cannot mount root, you may want to comment out this
check in sys/geom/geom_bsd.c:

        if ((off_t)rawoffset * secsize != ms->mbroffset)
                rawoffset = 0;



-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Sun May 04 2003 - 20:25:13 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:06 UTC