--On 09 June 2005 19:00 -0600, Tobias Weingartner wrote:
On Thursday, June 9, "Luciano ES" wrote:
Hello, Stuart. The answers to your latest questions:
On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:
> How does 'fdisk wd0' look?
- The second slice (offset 63) was marked as unknown. Then I fixed
it with OpenBSD's fdisk. Now it is marked as OpenBSD. The problem is
that I have done that many times. The OpenBSD gets lost
mysteriously. Often, between two reboots of OpenBSD (without booting
any other system).
Something is overwriting it. Where does your 'a' slice begin?
What is the output of 'disklabel wd0'?
Email from o.p. with URLs to text files with the information doesnbt
seem to have made it to the list, Ibll include it below for reference
and paste in the disklabels for ease of use;
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: ST3120022A
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 234441648
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: 1024065 63 4.2BSD 2048 16384 328 # Cyl
0*- 1015
b: 1024128 1024128 swap # Cyl 1016
- 2031
c: 234441648 0 unused 0 0 # Cyl 0
-232580
d: 1024128 2048256 4.2BSD 2048 16384 328 # Cyl 2032
- 3047
e: 9625392 3072384 4.2BSD 2048 16384 328 # Cyl 3048
- 12596
f: 204624 12697776 4.2BSD 2048 16384 204 # Cyl 12597
- 12799
g: 2054115 12902400 4.2BSD 2048 16384 328 # Cyl 12800
- 14837*
i: 1847475 14956515 MSDOS # Cyl
14837*- 16670*
j: 32004 16804116 ext2fs # Cyl
16670*- 16702*
k: 2618532 16836183 unknown # Cyl
16702*- 19300*
l: 10361862 19454778 ext2fs # Cyl
19300*- 29579
m: 10361862 29816703 ext2fs # Cyl
29580*- 39859*
n: 10329732 40178628 ext2fs # Cyl
39859*- 50107*
o: 31535532 50508423 MSDOS # Cyl
50107*- 81392*
p: 25189857 82044018 MSDOS # Cyl
81392*-106382*
[and from bsd.rd with broken MBR partition table]
c: 234441648 0 unused 0 0 # Cyl 0
-232580
i: 1847475 14956515 MSDOS # Cyl
14837*- 16670*
j: 14956452 63 unknown # Cyl
0*- 14837*
k: 32004 16804116 ext2fs # Cyl
16670*- 16702*
l: 2618532 16836183 unknown # Cyl
16702*- 19300*
m: 10361862 19454778 ext2fs # Cyl
19300*- 29579
n: 10361862 29816703 ext2fs # Cyl
29580*- 39859*
o: 10329732 40178628 ext2fs # Cyl
39859*- 50107*
p: 31535532 50508423 MSDOS # Cyl
50107*- 81392*
------------ Forwarded Message ------------
Date: 09 June 2005 00:42 -0300
From: Luciano ES <[EMAIL PROTECTED]>
To: Stuart Henderson <[EMAIL PROTECTED]>
Cc: misc@openbsd.org
Subject: Re: Sad boot problem (boot.conf: invalid argument)
Hello, Stuart. Thanks for sending me a copy of your reply. I
don't know if anyone else has added anything to this thread
because I subscribe in digest mode. So here is all the info you
told me to post, with comments.
First off, the boot error message:
http://tinyurl.com/8qexk
So I booted with the CD and used the (S)hell. Here is dmesg:
http://tinyurl.com/7wwdg
And here is the first attempt at disklabel:
http://tinyurl.com/8ezsx
That's weird, isn't it? OpenBSD has disappeared completely. So I
ran fdisk and saw that the slice was marked "unknown" instead of
"OpenBSD". Hmmm... That reminds me of a page I read that
actually complains about problems with OpenBSD's fdisk:
http://geodsoft.com/howto/dualboot/
This tutorial makes several complaints about OpenBSD's fdisk.
And, in my own experience, it was clearly difficult not to lose
the slice's ID every now and then with no apparent cause. I
found myself fixing the OpenBSD slice's ID all the time. And it
only happens with OpenBSD. If I boot into Linux and run fdisk, I
see that slice correctly identified as OpenBSD. Then I go back
to OpenBSD and it still won't boot. It still will see the slice
as "unknown". And it does not accept IDs set with Linux's fdisk.
It really must be done by OpenBSD's fdisk. Grrr...
So I did it again: changed the ID with OpenBSD's fdisk and ran
disklabel again:
http://tinyurl.com/bowlc
Ha! There it is now. So I recorded another dmesg, but there was
no difference. So I removed the CD and rebooted. Yay! It worked!
OpenBSD is booting off the hard disk again.
But for how long? How many times will I have to boot with the CD
and fix the MBR over and over? It seems to me that there is
something very wrong with OpenBSD's fdisk, boot loader or both
or yet something else. I don't know what it is, but something
really seems to be wrong.
Thank you for your attention. I hope the info I am submitting
can be useful somehow.
--
Luciano ES
********************************
On 09/06/05 at 02:08, Stuart Henderson wrote in 4K:
Well, you want help with your problem, not someone else's
problem from 2003, with a very different bootloader...
Copy the exact message from your system. Either type it from
the screen, being very careful that you don't miss any
punctuation characters etc., or use a serial console as
described on <http://www.openbsd.org/faq/faq4.html#getdmesg>
Output from disklabel might be useful, and you should include
dmesg too.
********* END OF ORIGINAL MESSAGE *********</-quote->
---------- End Forwarded Message ----------
