arf wrote: > Thanks for all the suggestions. It appears to be a > problem with disk block mapping even though LBA mode > is used.
huh? What is the evidence? > In light of the suggestions, this is what I > did today: > > Use dd form /dev/zero to wipe MBR and start of disk. > Check Bios settings - AMI Bios set to "Auto" shows > LBA mode and DMA, etc. > > Downloaded June 10 snapshot and checked md5 sums. > > Installed without problems. The installboot output > was: > boot: /mnt/boot > proto: /usr/mdec/biosboot > device: /dev/rwd0c > /usr/mdec/biosboot: entry point 0 proto bootblock > size 512 > /mnt/boot is 3 blocks x 16384 bytes fs block shift 2; > part offset 63; inode block 24, offset 1704 > using MBR partition 0: type 166 (0xa6) offset 63 (0x3f) > > When I attempted to reboot from disk, the system hung at: > Searching for Boot Record from IDE-0..OK that's worse. It didn't even manage to load the MBR boot loader. Previously, you got the MBR, the partition boot record (PBR), and /boot loaded, it died loading the kernel. That's consistant with having zeroed the MBR (though since you didn't say HOW you did it, I'm not going to say anything is "final" there), but didn't properly restore it (and since you didn't indicate how you did that, I think that's a very safe bet). Let's step back a bit here. If you boot from the CDROM (or floppy), you get to a cdrom> or boot> prompt. What happens if you, at that prompt, tell it boot hd0a:/bsd If it boots properly there, that means your boot code is hosed. Well, actually, I'm convinced your boot code is hosed, it would be nice to see something actually working, though, right? If using the boot floppy or CD that way DOESN'T work, you have multiple problems. Nick.
