From owner-freebsd-current@FreeBSD.ORG Thu Jun 9 13:10:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0677516A41C for ; Thu, 9 Jun 2005 13:10:17 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFB7243D1F for ; Thu, 9 Jun 2005 13:10:16 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1DgMnY-0000NT-Ay; Thu, 09 Jun 2005 13:10:16 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1DgMnO-0005rJ-Li; Thu, 09 Jun 2005 06:10:06 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17064.16302.164797.404595@roam.psg.com> Date: Thu, 9 Jun 2005 06:10:06 -0700 To: Rainer Duffner References: <17063.34823.866303.74727@roam.psg.com> <42A7F87B.5000308@ultra-secure.de> Cc: FreeBSD Current Subject: Re: problem with boot0cfg on a twe? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 13:10:17 -0000 >> very -current >> >> # boot0cfg -B -d 1 -s 1 -v twed0 >> boot0cfg: write_mbr: /dev/twed0: No such file or directory >> >> # boot0cfg -B -d 1 -s 1 -v twe0 >> boot0cfg: read /dev/twe0: Operation not supported by device >> >> # ls -l /dev/twed0 >> crw-r----- 1 root operator 0, 76 Jun 8 23:32 /dev/twed0 >> >> # df >> Filesystem 1024-blocks Used Avail Capacity Mounted on >> /dev/twed0s1a 253678 67506 165878 29% / >> devfs 1 1 0 100% /dev >> /dev/twed0s1d 126702 7682 108884 7% /var >> /dev/twed0s1e 126702 192 116374 0% /var/spool >> /dev/twed0s1f 28341292 2393116 23680874 9% /usr >> /dev/twed0s1g 4058062 54 3733364 0% /usr/home >> /dev/twed0s1h 63256 858 57338 1% /root >> /dev/twed1s1e 961291472 536501578 347886578 61% /data >> procfs 4 4 0 100% /proc >> /dev/md0 126702 14 116552 0% /tmp >> >> and the current man page for boot0cfg implies that i can install >> boot0 - crt only >> boot0sio - sio only >> >> i have many systems with /boot.config having -P that seem to be >> willing to go either way. what am i not understanding? > > I think the problem is that you can't write onto the disk when you have > it in use (for 5.4 at least). It just gives the wrong error-message. > I had the same problem - booting from CD usually lets you apply boot0cfg. not very useful for remote admin. why should i not be able to write it? > But my real problem is that I can only boot the PC from the SuSE 9.2 CD > ! (2*120GB as RAID1). When I boot from the array, I get a kind of > endless loop of pre-boot panic or just an endless beep at the F1-promt, > depending if I have booteasy or not. > > When I boot from the SuSE9.2 CD, it will recognize that I have a Unix-OS > already installed and boot from HD as default. > That always works. > I have 3 identical PCs with this problem. yechh! i can boot this sucker. though i have to manually go through FreeBSD/i386 boot Default: 0:ad(1,a)kernel boot: 1:ad(1,a)/boot/loader which is what i want to fix randy