APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

changing to raid controller btldinstall btld

© December 2004 (various authors)

What is this stuff?

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

From: "D. Thomas Podnar" <tom@microlite.com>
Subject: Re: converting from blad to dpti5 RAID controller
Date: Sun, 31 Dec 2000 22:40:47 GMT

        System: OpenServer 5.0.5
        Motherboard: Asus with built-in Adaptec controller using "blad"
        Disk Drives: 2 IBM 8 GB SCSI 68-pin drives.
        Tape Drive: 50-pin HP SCSI DAT
        The system works fine but since one of the drives is not used, the
        customer wants a RAID1 system set up using a DPT PM2654U2 SCSI RAID
        I made a master backup and recovery diskettes  using Microlite's
        BackupEdge.  Before doing this, I upgraded their copy with the latest
        version from the Microlite's web site.

Good start. Make sure you have two backups, too.
        Next, I changed the SCSI ID of the onboard controller from 7 to 6
        since I didn't want it to interfere with the DPT controller which also
        uses 7.  I rebooted the system to make sure that this wouldn't impact
        the function of the onboard controller.  It didn't.  I also disabled
        the setting in the BIOS which would make force the Adaptec BIOS to be
        seen first.

Misunderstanding. Both adapters can have the same SCSI ID, since they
are separate BUSES. We need to make the DPT adapter 0 and the Adaptec
adapter 1.
        Then I installed the DPT controller, switching the disk drive cable
        from the Adaptec controller to the the DPT controller but leaving the
        tape drive connected to the onboard controller since I didn't have a
        50-pin to 68-pin converter with me.
        I then configured the DPT controller for RAID 1 (mirroring) and
        watched -- pleasently surprised -- as the controller saw the first
        drive as O.K. and proceeded to rebuild the second drive to match the
        first.  This was fine as the customer had not used the second drive at
        Next, I booted the system and watched to make sure that the DPT
        controller was seen first making its BIOS the dominant on.  At the
        boot prompt, I entered: 
        defbootstr link=fd(60)dpti5 Sdsk=dpti5(0,0,0,0) Stp=blad(0,0,3,0)
        I was asked for the btld diskette and everything seemed O.K.
        The system continued with the boot procedure but in the section where
        it lists the hardware which it recognized, it did not recognize the
        DPT controller.  The message was: WARNING: SCSI boot option(s)
        ignored; Unknown host adapter driver.  It then halts ungraciously with
        the "Press Any Key to Reboot" message.

The error indicates that there is no driver labeled "dpti5" on the
BTLD floppy. I'm going under the assumption here that that is the right
name and that you made the BTLD diskette properly.

Let's try the following procedure.

1) Get the system to recognize the DPT as primary.
2) Link the kernel to do that.
3) Add the Adaptec as the second host adapter.

First, make a copy of the Adaptec version of /stand/unix

  btmnt -w
  cp /stand/unix /stand/unix.adaptec
  btmnt -r

Attach the drive(s) to the DPT as you did before.
>From the hard drive, try this boot string...

  defbootstr link=dpti5 Sdsk=dpti5(0,0,0,0) disable=blad

Insert the BTLD diskette when prompted.

If this works, go into single user mode. If dpti5 currently exists
on the hard drive...

a) edit /etc/conf/sdevice.d/dpti5 and turn the driver on.
b) edit /etc/conf/cf.d/mscsi and replace all instances of blad
   with dpti5
c) Relink and reboot.

Otherwise, use the "btldinstall" command to install the driver
from your floppy. Use the btld instructions from our web site.

If that works, you'll be booted from the hard drive under the dpti5
driver. You can use mkdev to "install" the blad as the second
adapter and turn your tape drive back on. You can disable
the BIOS on the Adaptec at this point.

None of what you are trying to this point involves the BackupEDGE
tape or RecoverEDGE diskettes. They're just nice to have around
in case...

If this DOESN'T work, try using BTLDinstall to pre-install the
DPTI driver and make it the primary and the Adaptec the secondary.

Then do the hardware change.

I'd leave the Adaptec on ID7.

  D. Thomas Podnar - President  tom@microlite.com
  Microlite Corporation         724-375-6711 Voice
  2315 Mill Street              724-375-6908 Fax
  Aliquippa PA 15001-2228       888-257-3343 Toll Free Sales
|             The Crash Recovery Company(sm)               |
|Makers of                                                 |
| BackupEDGE  -  Data Archiving Software For Unix & Linux  |
| RecoverEDGE -  Network-Enabled Smart Disaster Recovery   |
|                for Linux, UnixWare 7.1, OpenServer 5.0.x.|
|https://www.microlite.com           ftp://ftp.microlite.com|

        I also tried booting from the BackupEdge diskettes using the same
        defbootstr but without the "fd(60)".  Again it seemed to go through
        all the motions but came up with the same error message.
        I then tried numerous combinations such as disabling the Adaptec
        controller altogether but nothing worked.  I removed the DPT
        controller, put everything back and was again pleasantly surprised
        that the system booted and everything worked.  I had expected that the
        DPT controller's RAID creation would have destroyed the data.
        The customer is up and running again but he still doesn't have a RAID
        system.  I know that I am not supposed to ask for ideas or suggestions
        as per instructions in other posts :-) but I am asking for help even
        if it is in the form of suggestions as to things to try.
        Happy New Year everyone.
        Harold Knopke

Got something to add? Send me email.

(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> changing to raid controller btldinstall btld ––>Re:converting from blad to dpti5 RAID controller


Inexpensive and informative Apple related e-books:

El Capitan: A Take Control Crash Course

Take Control of Upgrading to El Capitan

Take Control of Apple Mail, Third Edition

Take Control of Parallels Desktop 12

Take Control of Automating Your Mac

Mon Jun 2 14:49:29 2008: 4284   anonymous

Can you please me with the steps to change the SCSI controller ID from "0" in below output?
Attached devices:
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: PE/PV Model: 1x6 SCSI BP Rev: 1.0
Type: Processor ANSI SCSI revision: 02
Host: scsi0 Channel: 02 Id: 00 Lun: 00
Vendor: MegaRAID Model: LD 0 RAID5 349G Rev: 521S
Type: Direct-Access ANSI SCSI revision: 02


Mon Jun 2 14:54:44 2008: 4285   TonyLawrence

Changing a scsi ID is almost always a jumper on the drive itself. Consult the manufacturers web page to find documentation.

Tue Jun 3 15:13:02 2008: 4290   BigDumbDinosaur

Direct-Access ANSI SCSI revision: 02

What kind of device is this? SCSI-2 sounds like an older tape or CD-ROM.


Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

Printer Friendly Version

It has become appallingly obvious that our technology has exceeded our humanity. (Albert Einstein)

Linux posts

Troubleshooting posts

This post tagged:



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode

SCO Unix Sales, Support, & Service

Phone:  707-SCO-UNIX (707-726-8649Toll Free: 833-SCO-UNIX (833-726-8649)