fdisk - 80G HD

Discussion:

fdisk - 80G HD

Kurt V. Hindenburg

2003-02-08 21:39:32 UTC

My OpenBSD 3.2 is running fine, but the output of fdisk is troubling...
I'm thinking the BIOS is not correctly handling this HD.
How to go about fixing this?

% fdisk wd0
Disk: wd0 geometry: 9729/255/63 [156296385 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: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused

% df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/wd0a 97M 42M 50M 46% /
/dev/wd0d 48M 1.5M 45M 3% /home
/dev/wd0e 991M 251M 691M 27% /usr
/dev/wd0f 350M 8.2M 325M 2% /var

--
Kurt
---
There is no good and evil; there is only power.

Paladdin

2003-02-09 00:37:01 UTC

Permalink

Your MBR seems to be valid, because de signature number '0xAA55' is correct
and, of course, because your HDD is booting right now :)

The BIOS also looks valid, because geometry is detected '9729/255/63', and
shows reasonable values for a 80Gb disk. It's the partition table the one
that seems to be... twisted. So many zeros are anoying.

Is yours a multiboot system?

----- Original Message -----
From: "Kurt V. Hindenburg" <***@cherrynebula.net>
To: "misc-obsd" <***@openbsd.org>
Sent: Saturday, February 08, 2003 10:39 PM
Subject: fdisk - 80G HD

Post by Kurt V. Hindenburg
My OpenBSD 3.2 is running fine, but the output of fdisk is troubling...
I'm thinking the BIOS is not correctly handling this HD.
How to go about fixing this?
% fdisk wd0
Disk: wd0 geometry: 9729/255/63 [156296385 Sectors]
Offset: 0 Signature: 0xAA55
#: 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: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
% df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/wd0a 97M 42M 50M 46% /
/dev/wd0d 48M 1.5M 45M 3% /home
/dev/wd0e 991M 251M 691M 27% /usr
/dev/wd0f 350M 8.2M 325M 2% /var
--
Kurt
---
There is no good and evil; there is only power.

___________________________________________________
Yahoo! Móviles
Personaliza tu móvil con tu logo y melodía favorito
en http://moviles.yahoo.es

Kurt V. Hindenburg

2003-02-09 00:45:50 UTC

Permalink

On Saturday 08 February 2003 7:37 pm, Paladdin wrote:
| Your MBR seems to be valid, because de signature number '0xAA55' is correct
| and, of course, because your HDD is booting right now :)
|
| The BIOS also looks valid, because geometry is detected '9729/255/63', and
| shows reasonable values for a 80Gb disk. It's the partition table the one
| that seems to be... twisted. So many zeros are anoying.
|
| Is yours a multiboot system?
|
No, I installed from the OpenBSD 3.2 CD. No other OS has touched this HD.

Kurt
---
There is no good and evil; there is only power.

Nick Holland

2003-02-09 00:41:18 UTC

Permalink

Post by Kurt V. Hindenburg
My OpenBSD 3.2 is running fine, but the output of fdisk is troubling...
I'm thinking the BIOS is not correctly handling this HD.
How to go about fixing this?

Not a lot of info. Hope you weren't expecting a really good answer.
8-)

It is not the BIOS. The BIOS doesn't handle the disk after the kernel
is loaded.

The only thing the partition table does for you after boot is to keep
different operating systems out of each others way. I'm inclined to
think, however, that your machine is probably not bootable at the
moment, as the BIOS *does* need the partition table to figure out
where the active OS is to be loaded from.

a 'dd' accident, perhaps?

Assuming the system hasn't been halted since you noticed this, DON'T
halt/reboot IT! It probably won't come back up nicely (though a boot
floppy *might* find the disklabel (assuming it wasn't clobbered) and
be able to boot the system. Don't bet on it, though.). Dump the data
to something else and reload the machine.

If you know what caused the incident, if it is contained to just a
dammaged MBR, you can install a new one using fdisk(8) and
installboot(8) (see FAQ 14). disklabel(8) should give you a good idea
how the disk is actually laid out (assuming you didn't do something
easy like "use entire disk for OpenBSD")

HOWEVER, I'd have a backup of everything before going any further.

If the system *IS* booting successfully, we (or at least, I 8-) need
MUCH more info to have any idea what is going on...

Post by Kurt V. Hindenburg
% fdisk wd0
Disk: wd0 geometry: 9729/255/63 [156296385 Sectors]
Offset: 0 Signature: 0xAA55
#: 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: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
% df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/wd0a 97M 42M 50M 46% /
/dev/wd0d 48M 1.5M 45M 3% /home
/dev/wd0e 991M 251M 691M 27% /usr
/dev/wd0f 350M 8.2M 325M 2% /var

Nick.

--
http://www.holland-consulting.net

Kurt V. Hindenburg

2003-02-09 01:04:08 UTC

Permalink

On Saturday 08 February 2003 7:41 pm, Nick Holland wrote:
| "Kurt V. Hindenburg" wrote:
| > My OpenBSD 3.2 is running fine, but the output of fdisk is troubling...
| > I'm thinking the BIOS is not correctly handling this HD.
| > How to go about fixing this?
|
| Not a lot of info. Hope you weren't expecting a really good answer.
| 8-)
|
Well, I just installed a fresh 3.2 a couple of days...everything should be the
standard installation. I'm not sure what info you would need...

|
| a 'dd' accident, perhaps?
No

| Assuming the system hasn't been halted since you noticed this, DON'T
| halt/reboot IT! It probably won't come back up nicely (though a boot
| floppy *might* find the disklabel (assuming it wasn't clobbered) and
| be able to boot the system. Don't bet on it, though.). Dump the data
| to something else and reload the machine.

The machine is bootable...I've already rebooted it twice without ANY problems
whatsoever.

|
| If you know what caused the incident, if it is contained to just a
| dammaged MBR, you can install a new one using fdisk(8) and
| installboot(8) (see FAQ 14). disklabel(8) should give you a good idea
| how the disk is actually laid out (assuming you didn't do something
| easy like "use entire disk for OpenBSD")
I said "no" to entire disk when installing.

|
| If the system *IS* booting successfully, we (or at least, I 8-) need
| MUCH more info to have any idea what is going on...

Let me know what you need.

--
Kurt
---
There is no good and evil; there is only power.

Nick Holland

2003-02-09 02:40:20 UTC

Permalink

Post by Kurt V. Hindenburg
Well, I just installed a fresh 3.2 a couple of days...everything should be the
standard installation.

That is not the result of a standard install...

Post by Kurt V. Hindenburg
I'm not sure what info you would need...

We need what makes your computer (which is messed up) different than
mine (which is working fine). Right now, I know basicly nothing about
your computer or install.
http://www.openbsd.org/mail.html

Post by Kurt V. Hindenburg
| Assuming the system hasn't been halted since you noticed this, DON'T
| halt/reboot IT! It probably won't come back up nicely (though a boot
| floppy *might* find the disklabel (assuming it wasn't clobbered) and
| be able to boot the system. Don't bet on it, though.). Dump the data
| to something else and reload the machine.
The machine is bootable...I've already rebooted it twice without ANY problems
whatsoever.

ok, that gets my curiosity up...

Post by Kurt V. Hindenburg
| If you know what caused the incident, if it is contained to just a
| dammaged MBR, you can install a new one using fdisk(8) and
| installboot(8) (see FAQ 14). disklabel(8) should give you a good idea
| how the disk is actually laid out (assuming you didn't do something
| easy like "use entire disk for OpenBSD")
I said "no" to entire disk when installing.

and then...??
I think this is key...
You got put into fdisk...what did you do?

Post by Kurt V. Hindenburg
| If the system *IS* booting successfully, we (or at least, I 8-) need
| MUCH more info to have any idea what is going on...
Let me know what you need.

The usual...
dmesg, _always_. Don't even think of snipping or editing it. 8)

In this case, since we are dealing with a disk issue, output of
fdisk wd0
disklabel wd0
(and the same for any other disks in the computer).

I'm curious what a DOS/Windows boot disk's FDISK would show -- my
guess: the exact same thing, a blank partition table.

Yes, you provided the fdisk output, but as I have no desire to go
scanning back and forth between multiple e-mails, put it all in one
message. 8-)

So far, I'm going to guess disklabel is going to look, uh,
"interesting".

Nick.

--
http://www.holland-consulting.net

Kurt V. Hindenburg

2003-02-09 04:51:44 UTC

Permalink

Fresh installation from 3.2 OpenBSD CD to an empty and never used 80GB HD.
No other OS has touch it. I'm using this machine as a firewall/gateway to the
internet via ppp. I've installed a few ports dealing with internet apps.
There is only the one HD in this machine.
As far as I remember when using fdisk in the installation everything went
fine. I said 'no' to using the entire HD. I made only one partition 0. I
have done nothing to the BIOS ( I noted that the BIOS upon start says that the
HD is 65535MB).

Problem: fdisk output is incorrect.

% fdisk wd0
Disk: wd0 geometry: 9729/255/63 [156296385 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: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused

The computer is bootable (4+ times) without any problems. I have
noticed no problems whatsoever with the machine.

% disklabel wd0c
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: WDC WD800JB-00C
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 156301488
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:

# size offset fstype [fsize bsize cpg]
a: 204624 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 202)
b: 1048320 204624 swap # (Cyl. 203 - 1242)
c: 156301488 0 unused 0 0 # (Cyl. 0 - 155060)
d: 102816 1252944 4.2BSD 1024 8192 16 # (Cyl. 1243 - 1344)
e: 2097648 1355760 4.2BSD 1024 8192 16 # (Cyl. 1345 - 3425)
f: 740896 3453408 4.2BSD 1024 8192 16 # (Cyl. 3426 - 4161*)

% dmesg
OpenBSD 3.2 (GENERIC) #25: Thu Oct 3 19:51:53 MDT 2002
***@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD K6 ("AuthenticAMD" 586-class) 200 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX
real mem = 66629632 (65068K)
avail mem = 56250368 (54932K)
using 838 buffers containing 3432448 bytes (3352K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 07/15/95, BIOS32 rev. 0 @ 0xfdb80
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev. 2.1 @ 0xf0000/0x10000
pcibios0: PCI BIOS has 5 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371AB PIIX4 ISA" rev
0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc0000/0x8000
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82439TX System" rev 0x01
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x01
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <WDC WD800JB-00CRA1>
wd0: 16-sector PIO, LBA, 76319MB, 16383 cyl, 16 head, 63 sec, 156301488
sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <SONY, CD-ROM CDU76E-S, 1.0c> SCSI0 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 3
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: irq 11
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: vendor 0x0000 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82371AB Power Mgmt" rev 0x01 at pci0 dev 7 function 3 not configured
rl0 at pci0 dev 18 function 0 "Realtek 8139" rev 0x10: irq 9 address
00:50:ba:43:f5:8e
rlphy0 at rl0 phy 0: RTL internal phy
vga1 at pci0 dev 20 function 0 "3DFX Interactive Banshee" rev 0x03
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
isapnp0 at isa0 port 0x279: read port 0x203
pccom3 at isapnp0 "SupraExpress 56i Voice V.90, SUP2490, SUP2040, " port
0x3e8/8 irq 4: ns16550a, 16 byte fifo
biomask c840 netmask ca40 ttymask cac2
pctr: user-level cycle counter enabled
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302

I booted an old DOS floppy I had laying around. The fdisk reported :
"Total disk 8032 Mbytes
No paritions defined."

Output when I booted the OpenBSD floppy disk: (fdisk wd0)
% cat fdisk.wd0
Disk: wd0 geometry: 9729/255/63 [156296385 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: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused

The binary files were ftped last Oct. from the 3.2 tree (The files were
burned on Oct 5). I have not upgraded/patched the system.

Kurt
---
There is no good and evil; there is only power.

Dimitry Andric

2003-02-09 04:59:31 UTC

Permalink

On 2/8/2003 at 22:39:32 Kurt V. Hindenburg wrote:

KVH> My OpenBSD 3.2 is running fine, but the output of fdisk is troubling...

Can you please post the output of:

sudo head -c 512 /dev/rwd0c | hexdump -C

? At least then we'll know what your mbr really contains. :)

Cheers,
--
Dimitry Andric <***@xs4all.nl>
PGP Key: http://www.xs4all.nl/~dim/dim.asc
Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3
Lbh whfg ivbyngrq gur QZPN naq jvyy or cebfrphgrq

Kurt V. Hindenburg

2003-02-09 06:11:53 UTC

Permalink

On Saturday 08 February 2003 11:59 pm, Dimitry Andric wrote:
| On 2/8/2003 at 22:39:32 Kurt V. Hindenburg wrote:
|
| KVH> My OpenBSD 3.2 is running fine, but the output of fdisk is
| troubling...
|
| Can you please post the output of:
|
| sudo head -c 512 /dev/rwd0c | hexdump -C
|
Hmmm,

% head -c 512 /dev/rwd0c | hexdump -C
head: illegal option -- c
usage: head [-n line_count] [file ...]

Did you mean -n ?

The output from
head -n 512 /dev/rwd0c | hexdump -C
is 170+k gzipped. Is this what you want?

I'm not sure I should attached this big of a file to the mailing-list.

%ls -l l /usr/bin/head
-r-xr-xr-x 1 root bin 12288 Oct 3 21:36 /usr/bin/head*

Kurt
---
There is no good and evil; there is only power.

Dan Brosemer

2003-02-09 06:26:55 UTC

Permalink

Post by Kurt V. Hindenburg
|
| KVH> My OpenBSD 3.2 is running fine, but the output of fdisk is
| troubling...
|
|
| sudo head -c 512 /dev/rwd0c | hexdump -C
|
Hmmm,
% head -c 512 /dev/rwd0c | hexdump -C
head: illegal option -- c
usage: head [-n line_count] [file ...]
Did you mean -n ?
The output from
head -n 512 /dev/rwd0c | hexdump -C
is 170+k gzipped. Is this what you want?
I'm not sure I should attached this big of a file to the mailing-list.
%ls -l l /usr/bin/head
-r-xr-xr-x 1 root bin 12288 Oct 3 21:36 /usr/bin/head*

-c might be a -currentism or a GNU-ism, I don't know, but I think you can
accomplish the same thing with:

dd if=/dev/rwd0c count=1 2>/dev/null|hexdump -C

It should be more like 2 or 3k.

-Dan

--
"Burnished gallows set with red
Caress the fevered, empty mind
Of man who hangs bloodied and blind
To reach for wisdom, not for bread." -- Deoridhe Grimsdaughter

[demime 0.98d removed an attachment of type application/pgp-signature]

Kurt V. Hindenburg

2003-02-09 06:36:57 UTC

Permalink

On Sunday 09 February 2003 1:26 am, Dan Brosemer wrote:
| dd if=/dev/rwd0c count=1 2>/dev/null|hexdump -C
|
Ok, here's the output gzipped attached.

--
Kurt
---
There is no good and evil; there is only power.

[demime 0.98d removed an attachment of type application/x-gzip which had a name of rwd0c.dump.gz]

Kurt V. Hindenburg

2003-02-09 06:54:41 UTC

Permalink

On Sunday 09 February 2003 1:36 am, Kurt V. Hindenburg wrote:
| On Sunday 09 February 2003 1:26 am, Dan Brosemer wrote:
| | dd if=/dev/rwd0c count=1 2>/dev/null|hexdump -C
|
| Ok, here's the output gzipped attached.

Seems the ML removes attachments...sorry about that.

% cat rwd0c.dump
00000000 eb 3c 90 4f 70 65 6e 42 53 44 00 00 02 01 00 00 |ë<.OpenBSD......|
00000010 00 00 00 00 00 f8 00 00 00 00 00 00 10 00 00 00 |.....ø..........|
00000020 00 00 00 00 00 00 29 00 00 00 00 55 4e 49 58 20 |......)....UNIX |
00000030 4c 41 42 45 4c 00 55 46 53 20 34 2e 34 00 66 ea |LABEL.UFS 4.4.fê|
00000040 53 00 00 00 c0 07 72 65 61 64 69 6e 67 20 62 6f |S...À.reading bo|
00000050 6f 74 00 fa 31 c0 8e d0 66 bc fc ff 00 00 fb b8 |ot.ú1À.Ðf¼üÿ..û¸|
00000060 c0 07 8e d8 8e c0 8e e0 8e e8 66 be 46 00 00 00 |À..Ø.À.à.èf¾F...|
00000070 e8 bd 00 b8 00 40 8e c0 66 31 db 67 8a 0d 6e 01 |è½.¸***@.Àf1Ûg..n.|
00000080 00 00 0f b6 c9 be 6f 01 51 b0 2e e8 af 00 fc ad |...¶É¾o.Q°.è¯.ü|
00000090 89 c1 ac 88 c6 ac b4 02 50 cd 13 73 1a 66 be a8 |.Á¬.Æ¬´.PÍ.s.f¾¨|
000000a0 00 00 00 e8 8a 00 eb 3a 0d 0a 52 65 61 64 20 65 |...è..ë:..Read e|
000000b0 72 72 6f 72 0d 0a 00 58 66 0f b6 c0 c1 e0 09 01 |rror...Xf.¶ÀÁà..|
000000c0 c3 59 e2 c4 66 be ed 00 00 00 e8 63 00 31 f6 fc |ÃYâÄf¾í...èc.1öü|
000000d0 26 ad 26 ad 3d 01 0b 74 17 66 be e4 00 00 00 e8 |&&=..t.f¾ä...è|
000000e0 4e 00 fa f4 42 61 64 20 6d 61 67 69 63 0d 0a 00 |N.úôBad magic...|
000000f0 fa 67 66 0f 01 15 68 01 00 00 0f 20 c0 66 83 c8 |úgf...h.... Àf.È|
00000100 01 0f 22 c0 66 ea 0c 7d 00 00 08 00 b8 10 00 00 |.."Àfê.}....¸...|
00000110 00 8e d8 8e d0 8e c0 8e e0 8e e8 bc fc ff 00 00 |..Ø.Ð.À.à.è¼üÿ..|
00000120 0f b6 c2 50 68 0d d0 01 c0 ea 20 00 04 00 08 00 |.¶ÂPh.Ð.Àê .....|
00000130 66 50 fc ac 84 c0 74 12 e8 02 00 eb f6 66 50 66 |fPü¬.Àt.è..ëöfPf|
00000140 53 b4 0e 31 db 43 cd 10 66 5b 66 58 c3 00 00 00 |S´.1ÛCÍ.f[fXÃ...|
00000150 00 00 00 00 00 00 00 00 ff ff 00 00 00 9f cf 00 |........ÿÿ....Ï.|
00000160 ff ff 00 00 00 93 cf 00 18 00 50 7d 00 00 05 37 |ÿÿ....Ï...P}...7|
00000170 00 96 09 01 00 97 3f 01 00 98 18 31 00 08 0f 01 |......?....1....|
00000180 00 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............Uª|
00000200

--
Kurt
---
There is no good and evil; there is only power.

Chuck Yerkes

2003-02-09 06:53:57 UTC

Permalink

Well, since I can free presume that you're running
a DecStation 5000/240 and a MIPS R4400 (my default
assumption for defaults), fdisk doesn't get used
on that platform.

Useful information from you gets useful information TO
you. Many items on the website about sending useful mail.

Tobias Weingartner

2003-02-09 07:17:40 UTC

Permalink

Post by Kurt V. Hindenburg
Problem: fdisk output is incorrect.

Well... sort of...

So the partition table got nuked... somehow...

Post by Kurt V. Hindenburg
The computer is bootable (4+ times) without any problems. I have
noticed no problems whatsoever with the machine.

Yeah, so at least portions of block 0 are executable, and doing
the right thing, at least enough to boot you.

Post by Kurt V. Hindenburg
% disklabel wd0c
# size offset fstype [fsize bsize cpg]
a: 204624 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 202)

That is your problem. When you made your obsd partition you made it
start at 0. Then you partitioned things, again, starting at the start,
0. A little bit later, you/install did an installboot. Guess where
that wrote the bootblock? Well, the start of your "a" partition of
course... which is... well, at disk offset... 0... which is... Hmm...
where the MBR is located.

Post by Kurt V. Hindenburg
"Total disk 8032 Mbytes
No paritions defined."

Because it got nuked. You did not setup the openbsd partition
correctly in fdisk.

--Toby.

Continue reading on narkive:

Search results for 'fdisk - 80G HD' (Questions and Answers)

replies

When I try to install Windows XP it can't find my harddrives? Help!?

started 2007-05-05 02:53:11 UTC

desktops

replies

Seagate 160 gb hd only gives 32gb?

started 2006-08-15 05:10:44 UTC

hardware