Re: boot problem. in short
On Fri, Jun 5, 2009 at 6:36 AM, Andrej Elizarov vigilan...@gmail.comwrote: Hi all. I have some situation, my machine will not boot after installing amd64_obsd4.5_stable. amd64, 250G harddrive (first physical). 0. 1 Primary 100G NTFS (WindowsXP), 1 Secondary 100G NTFS (just data) 1. have free 36G at the end of drive. 2. in windows make blank primary partition (with powerquest Partition Manager) at all 36G 3. install obsd in this partition 4. reboot Then BIOS, POST,.. and black screen with blinking cursor. spitball bootloader? e.g., http://www.gnu.org/software/grub/ /spitball (By the way, there was similiar behavior, when i mount ntfs partition in obsd, and forget umount it. After rebooting got black screen. After mount/umount once again all was correct.) Any ideas how to fix?
Re: boot problem. in short
I try some bootloaders to boot this partition, like MagickBoot and some others (from Hiren's BootCD). Nope. I try reinstall windows - it only copy files to hd, then reboot to continue installation from hd - and again black screen. 2009/6/5 Neal Hogan nealho...@gmail.com On Fri, Jun 5, 2009 at 6:36 AM, Andrej Elizarov vigilan...@gmail.comwrote: Hi all. I have some situation, my machine will not boot after installing amd64_obsd4.5_stable. amd64, 250G harddrive (first physical). 0. 1 Primary 100G NTFS (WindowsXP), 1 Secondary 100G NTFS (just data) 1. have free 36G at the end of drive. 2. in windows make blank primary partition (with powerquest Partition Manager) at all 36G 3. install obsd in this partition 4. reboot Then BIOS, POST,.. and black screen with blinking cursor. spitball bootloader? e.g., http://www.gnu.org/software/grub/ /spitball (By the way, there was similiar behavior, when i mount ntfs partition in obsd, and forget umount it. After rebooting got black screen. After mount/umount once again all was correct.) Any ideas how to fix?
Re: boot problem. in short
On Fri, 5 Jun 2009 16:33:17 +0400, Andrej Elizarov wrote I try some bootloaders to boot this partition, like MagickBoot and some others (from Hiren's BootCD). Nope. I try reinstall windows - it only copy files to hd, then reboot to continue installation from hd - and again black screen. [SNIP] Any ideas how to fix? 1. Boot OpenBSD installation media 2. At Install/Update/Shell prompt, select shell. 3. Examine MBR of boot drive: # fdisk boot drive (e.g.: sd0, wd0) Is there an MBR partition table? Is a partition flagged as boot? Repair as necessary, per fdisk(8) man page 4. Install MBR program onto boot drive, preserving repaired MBR table # fdisk -u your boot drive
Re: boot problem. in short
I'd written: 4. Install MBR program onto boot drive, preserving repaired MBR table # fdisk -u your boot drive You probably do not want to use OpenBSD's fdisk to rewrite the MBR program, it will clear the NT disk signature.
Re: boot problem. in short
Thanks, i'll try. Just an idea. Signature is already cleared. How can i test it? 2009/6/5 Josh Grosse j...@jggimi.homeip.net I'd written: 4. Install MBR program onto boot drive, preserving repaired MBR table # fdisk -u your boot drive You probably do not want to use OpenBSD's fdisk to rewrite the MBR program, it will clear the NT disk signature.
Re: boot problem. in short
On Fri, Jun 05, 2009 at 10:53:53PM +0400, Andrej Elizarov wrote: Thanks, i'll try. Just an idea. Signature is already cleared. How can i test it? Step 1. Google for nt disk signature. Step 2. Open the top search result, Windows NT: Disk Management Basics, a link at microsoft.com. Step 3. Search forward for disk signature. Step 4. Read this paragraph. Step 5. Think. Step 6. Search forward for disk signature again. Look at the comments about the disk signature under the section labelled Master Boot Record, that shows a hexdump output of the first sector of a drive. Step 7. Think again. The contents of this first sector can be edited. The dd(1) program included with the ramdisk kernel will allow you copy the sector to a file on removeable media such as diskette or USB stick. A hex editor would be required on another platform could be used, then dd once again could be deployed to write the modified sector back to hard drive.
