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). >Have you used any disk tools on the drive >from another OS which might have changed the MBR? - After, and only after I had the problem, I tried using Linux's fdisk a couple of times. But it didn't work, so I gave up. But I hadn't got anywhere near the MBR until the problem occurred for the first time. And, like I said, the slice also loses its OpenBSD ID mysteriously between two reboots of OpenBSD. >Are you loading the >OpenBSD boot directly from MBR, or is there some other bootmanager in >the way? Any chance some program might have decided that the OpenBSD >partition is bogus because it doesn't know the type, and decides to >change it? - I am using Grub with these options: rootnoverify (hd0,1) makeactive chainloader +1 Always worked fine with Windows, Linux, FreeBSD and NetBSD. Thank you again for your attention. -- Luciano ES Santos, SP - Brasil
