From owner-freebsd-questions Tue May 7 8:35: 8 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail2.eagle.ca (mail2.eagle.ca [209.167.16.30]) by hub.freebsd.org (Postfix) with ESMTP id 2A48137B408 for ; Tue, 7 May 2002 08:34:06 -0700 (PDT) Received: from afi (staff.eagle.ca [209.167.16.15]) by mail2.eagle.ca (8.11.3/8.11.3) with SMTP id g47FQKk49567; Tue, 7 May 2002 11:26:20 -0400 (EDT) (envelope-from lists@brenius.com) Message-ID: <002501c1f5dc$9c34a2b0$7b01a8c0@afi> From: To: Cc: References: <020501c1f31c$724d0a90$0200a8c0@afi> <000f01c1f52c$eefa6d00$7b01a8c0@afi> <200205070931.18706.mark.rowlands@minmail.net> <000e01c1f5da$0500aad0$7b01a8c0@afi> Subject: Re: Mylex RAID to Asus Symbios SCSI Card Date: Tue, 7 May 2002 11:34:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "W Ryan M" wrote in message news:... > On Mon, 6 May 2002 lists@brenius.com wrote: > > > Date: Mon, 6 May 2002 18:34:51 +0000 (UTC) > > From: lists@brenius.com > > Newsgroups: mailing.freebsd.questions > > Subject: Re: Mylex RAID to Asus Symbios SCSI Card > > > > I guess the mounting guru's missed this one.. :) > > > > Please help. :) > > > > ----- Original Message ----- > > From: > > To: > > Sent: Friday, May 03, 2002 11:33 PM > > Subject: Mylex RAID to Asus Symbios SCSI Card > > > > > > > Hello, > > > > > > I am new to this situation, so please bare with me. :D > > > > > > Scenario: > > > > > > FreeBSD 4.3R > > > Mylex SCSI/RAID controller w/ x2 Seagate ST318436LW's in RAID1 > > > > > > Controller is removed and is no longer available. Replacement is an Asus > > > Symbios SCSI > > > card which appears to be run at SCSI-3 (40MB/s). > > > > > > Server was shutdown properly, original Mylex card was removed and Asus > > card > > > was > > > inserted. So I knew the OS would yell at me for a totally different HD > > > controller and > > > will obviously not boot up fully, and is currently stuck at: > > > > > > Mounting root from ufs: /dev/mlxd0s1a > > > No such device 'mlxd' > > > Setrootbyname failed > > > ffs_mountroot: can't find rootup > > > Root mount failed: 6 > > > > > > Mountroot> > > > > > > Now, the pause key is not working on the keyboard, but it appears as > > though > > > the SCSI > > > card is seeing the drives OK and seems to be named as sym0. But, of course > > > is stuck at > > > what I typed above. > > > > > > So besides what few keystrokes (which I am baffed on, cause I don`t know > > > this part of > > > the OS) at this prompt, any other things I would need to do for the OS to > > > boot up properly > > > and run as if the Mylex card was back in, minus the RAID? :D > > > > > > Thank you for your help in advance. :D > > > > > > Dan > Catch 22, > > The mountroot prompt want the device name of the new controler, but you > dont have the /dev/sym0 device. You are stuck before the single user > login and can not add the device. Appears that way... but when the dmesg stuff flies by I am pretty sure that the Asus card is detected as sym0. > Go back to the raid controler and plan ahead before removing the Mylex > (DAC 960?) RAID card. The original Mylex card is not available. The resources are not available to have a replica if every peice of hardware contained here. Therefore, a new card, a similar one, or the orignal one is not an option. > OR, Sacrifice your second drive and rebuild with it. With a new Freebsd > system built on /dev/sym0 mount your other drive and update the new > system with the old data. How would I go about starting this? Start a regular install and make sure I somehow distinguish the second drive and setup a new install on it. There must be a way to tell FreeBSD the old controller crapped and I am replacing it with a new. > Proper, prior, planning, prevents, piss, poor, performance. Thanks for the tips, but, I am simply trying to learn how resolve this situation with the resources that I have. In a real world mission critical envrionment I would insist on proper, prior, planning, etc. Thank you for your time, D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message