Since I haven't seen any response to this, I'll "me too" it in hopes that
it will get some attention drawn to it.

Not only do I have seem to somehow broken my bootblocks so boot0 beeps at
me when I select "F1 FreeBSD", I am now no longer able to write new
bootblocks:

edgemaster# disklabel -r ad1s1
...
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:  1024000  6291456    4.2BSD     2048 16384    90   # (Cyl.  391*-
455*)
  b:  6291456        0      swap                        # (Cyl.    0 -
391*)
  c: 117226242        0    unused        0     0        # (Cyl.    0 -
7296*)
  e: 10485760  7315456    4.2BSD     2048 16384    89   # (Cyl.  455*-
1108*)
  f: 99425026 17801216    4.2BSD     2048 16384    89   # (Cyl. 1108*-
7296*)

edgemaster# disklabel -r ad1s1
...
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:  1024000  6291519    4.2BSD     2048 16384    90   # (Cyl.  391*-
455*)
  b:  6291456       63      swap                        # (Cyl.    0*-
391*)
  c: 117226242       63    unused        0     0        # (Cyl.    0*-
7296*)
  e: 10485760  7315519    4.2BSD     2048 16384    89   # (Cyl.  455*-
1108*)
  f: 99425026 17801279    4.2BSD     2048 16384    89   # (Cyl. 1108*-
7296*)
partition c: partition extends past end of unit
Warning, partition c doesn't start at 0!
Warning, An incorrect partition c may cause problems for standard system
utiliti
es
partition f: partition extends past end of unit

edgemaster# disklabel -B ad1s1
partition c: partition extends past end of unit
Warning, partition c doesn't start at 0!
Warning, An incorrect partition c may cause problems for standard system utilities
partition f: partition extends past end of unit
edgemaster#


I'm not even sure what is going on here, but something is clearly not
right. Like I said, I can't even boot this anymore.

  F1  FreeBSD
  F5  Disk 0
Selecting F1 just beeps at me. Fortunately I can still go to disk 0 and
boot via boot2.

Help :(

On Sun, Dec 22, 2002 at 03:38:37AM +0300, Andrey A. Chernov wrote:
> Now I can't update my bootblocks to new ones using 'disklabel -B da0s1',
> checklabel() disklabel function return error preventing actual write with 
> following diagnostic:
> 
> partition b: partition extends past end of unit
> partition c: partition extends past end of unit
> Warning, partition c doesn't start at 0!
> Warning, An incorrect partition c may cause problems for standard system utilities
> Warning, partition d: size 0, but offset 32
> Warning, partition e: size 0, but offset 32
> Warning, partition f: size 0, but offset 32
> Warning, partition g: size 0, but offset 32
> Warning, partition h: size 0, but offset 32
> 
> In fact, this is exact the same diagnostic as from 'disklabel -r da0s1':
> 
> # /dev/da0s1c:
> type: SCSI
> disk: da0s1
> label: 
> flags:
> bytes/sector: 512
> sectors/track: 32
> tracks/cylinder: 64
> sectors/cylinder: 2048
> cylinders: 17500
> sectors/unit: 35842016
> rpm: 3600
> interleave: 1
> trackskew: 0
> cylinderskew: 0
> headswitch: 0         # milliseconds
> track-to-track seek: 0        # milliseconds
> drivedata: 0 
> 
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   a: 34611200       32    4.2BSD     2048 16384    64         # (Cyl.    0*- 16900)
>   b:  1230816 34611232      swap                      # (Cyl. 16900*- 17500*)
>   c: 35842016       32    unused        0     0               # (Cyl.    0*- 17500*)
> partition b: partition extends past end of unit
> partition c: partition extends past end of unit
> Warning, partition c doesn't start at 0!
> Warning, An incorrect partition c may cause problems for standard system utilities
> Warning, partition d: size 0, but offset 32
> Warning, partition e: size 0, but offset 32
> Warning, partition f: size 0, but offset 32
> Warning, partition g: size 0, but offset 32
> Warning, partition h: size 0, but offset 32
> 
> For comparison see just 'disklabel da0s1' output which indicate no errors 
> and no mysterious offset 32 in the data:
> 
> # /dev/da0s1c:
> type: SCSI
> disk: da0s1
> label: 
> flags:
> bytes/sector: 512
> sectors/track: 32
> tracks/cylinder: 64
> sectors/cylinder: 2048
> cylinders: 17500
> sectors/unit: 35842016
> rpm: 3600
> interleave: 1
> trackskew: 0
> cylinderskew: 0
> headswitch: 0         # milliseconds
> track-to-track seek: 0        # milliseconds
> drivedata: 0 
> 
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>   a: 34611200        0    4.2BSD     2048 16384    64         # (Cyl.    0 - 16899)
>   b:  1230816 34611200      swap                      # (Cyl. 16900 - 17500*)
>   c: 35842016        0    unused        0     0               # (Cyl.    0 - 17500*)
> 
> Please fix this GEOM bug, to allow to update bootblocks at least.
> 
> -- 
> Andrey A. Chernov
> http://ache.pp.ru/
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message

-- 
Sean Kelly         | PGP KeyID: D2E5E296
[EMAIL PROTECTED] | http://www.zombie.org

Attachment: msg50029/pgp00000.pgp
Description: PGP signature

Reply via email to