pizeta wrote: ... > Once finished the installation "he" suggested me to type halt and reboot from > hd: > > Using drive 0, partition3; > Loading... > ERR M
yikes. This morning, I responded to a similar message, said this kind of problem almost never happens anymore...and after hitting "SEND", see ANOTHER "ERR M" message. > i read a topic like this so i tried: > > # mount /dev/wd0a /mnt > # mount /dev/wd0f /mnt/usr > (this isn't really necessary because when i mount wd0a i see /usr mounted too, > maybe just because they are on the same partition with different labels) that needs elaboration. You said you had a separate /usr partition, so it would need to be explicitly mounted. Something isn't right here...show us what you are seeing, rather than summarizing it for us... > # rm -rf /mnt/boot > # cp /mnt/usr/mdec/boot /mnt/boot > # /mnt/usr/mdec/installboot -v /mnt/boot /mnt/usr/mdec/biosboot wd0 yep, proper process, HOWEVER this *is* what happened during the install, since it failed there, something is going seriously wrong. Repeating it will most likely result in the same thing going wrong. > the 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 12384 bytes I'm hoping you mistyped that "12384" manually. SHOULD be 16384. :) > fs block shift 2; part offset 63; inode block 24; offset 1576 > using MBR partition 3: type 166 (0xa6) offset 63 (0x3f) > > > booting and holding shift: > !Using drive 0, partition 3; > !Loading;... > ERR M you certainly follwed the instructions. :) > > if i type > boot> boot hd0a:/bsd > booting hd0a:/bsd: \ > and nothing appens ouch. That's bad. Problem is bigger than boot blocks, then. > boot> machine diskinfo > Disk BIOS# Type Cyls Heads Secs Flags Checksum > fd0 0x0 *none* 80 2 18 0x4 0x0 > hd0 0x00 label 524 255 63 0x2 > 0xcada9542 > cd0 0x9f label 0 0 0 0xa 0x0 > > > don't know what to do > > [demime 1.01d removed an attachment of type application/pgp-signature] Were it me, I'd start with a whole different computer -- new disk, new computer, everything different. I think you have a broken computer, but I can't say for sure how. Assuming the other machine works (if it doesn't, I think you are making a subtle error, but I sure can't tell what it is at the moment...) Assuming the other machine works, move the HD from the working machine to the non-working machine, see if that works. If that does, try reinstalling it. I'm guessing you have a bad hard disk, but there is always the possibility of a BIOS incompatability that has escaped thousands of computers of testing so far. Speaking of which, might be worth trying to get a BIOS upgrade for your machine... Nick.
