On 12/12/11 17:29, Nick Holland wrote:
On 12/12/11 16:11, Jeff Ross wrote:
On 12/12/11 13:18, Diana Eichert wrote:
what is the output of fdisk when booted from bsd.rd?
Hi Diana!
Thanks for the thought.
Disk: sd0 geometry: 487/255/63 [7827456 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
-------------------------------------------------------------------------------
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
*3: A6 0 1 2 - 486 254 63 [ 64: 7823591 ] OpenBSD
Looks okay to me.
Jeff
yeah, that looks fine...
How about your disklabel output?
I can think of a few things you could do wrong to do that...
ERR M indicates that biosboot got installed, but what it was told was
the location of /boot is...uh...not. How that's happening...not sure.
But, we know the MBR is good, the PBR is good, but what the PBR is
pointing at is not.
Next step would be to try 5.0-rel to make sure it is not a recent
regression. The good thing about how OpenBSD handles flash disks is if
something is broke for flash disks, it is typically going to break
everywhere (I hope).
Nick.
Hi Nick!
Here's the disklabel:
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: Nano Pro
duid: 4659f17835a3effa
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 128
sectors/cylinder: 8064
cylinders: 970
total sectors: 7827456
boundstart: 64
boundend: 7823655
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
a: 516032 64 4.2BSD 2048 16384 1
b: 516096 516096 swap
c: 7827456 0 unused
d: 2564352 1032192 4.2BSD 2048 16384 1
e: 516096 3596544 4.2BSD 2048 16384 1
f: 209664 4112640 4.2BSD 2048 16384 1
g: 1540224 4322304 4.2BSD 2048 16384 1
h: 24192 5862528 4.2BSD 2048 16384 1
i: 209664 5886720 4.2BSD 2048 16384 1
j: 516096 6096384 4.2BSD 2048 16384 1
k: 516096 6612480 4.2BSD 2048 16384 1
l: 695072 7128576 4.2BSD 2048 16384 1
I don't see anything wrong here, either.
I'll grab the 5.0 rel bsd.rd and give that a go.
Jeff
