Date: Fri, 27 Nov 1998 00:29:14 -0800 From: Mike Smith <mike@smith.net.au> To: curtis <ufkartfm@pacific.net> Cc: "freebsd-alpha@FreeBSD.ORG" <freebsd-alpha@FreeBSD.ORG> Subject: Re: Multia - 3.0-19981124-SNAP - report Message-ID: <199811270829.AAA00656@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 26 Nov 1998 09:00:26 GMT." <365D18AA.BCEB99FE@pacific.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Target Machine: Multia VX42 > 3.0-19981124-SNAP > ftp://mirrors.rcn.com/pub/FreeBSD/alpha/ > > ******* > > kern.flp and mfsroot.gz allow for /stand/sysinstall > > after an Express/Kern-Developer install: > > reboot still causes "Unexpected Machine Check through vector 00000067" NetBSD does this (on my VX40) as well; it seems to be harmless. > (power cycle) > > >>>boot -flags a -file kernel dka0 > (boot dka0.0.0.6.0 -file kernel -flags a) > no such file > file open failed for kernel/dka0.0.0.6.0 Don't know where that message came from; what did you have on the disk beforehand? That's certainly not the FreeBSD bootblocks talking. Looks like you need to do the "standard" disklabelling magic before rebooting but after the install. > Can't open /dev/rda0s1a: Device not configured That's normal too; you need to update /etc/fstab by hand as sysinstall is writing out the sliced version but the SRM console won't boot from a sliced disk. Try: # mount /dev/da0a / ... (other mounts as required) # vi /etc/fstab (remove 'sX' from device names) # disklabel -B da0 (should fix the inability to boot from dka0) # reboot -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811270829.AAA00656>