I'm trying to add a Maxtor MXT-540S to a SUN-3/260 and retire the old
XY drive currently in the machine (because it is rapidly
When I opened the CPU tower, I noticed the SCSI board next to the tape
drive had a "spare" ribbon cable near the front of the board (the tape
is connected to a ribbon cable near the back of the board). So, I
crimped a centronix SCSI connector onto the front cable, after
pulling it through the slot for the tape drive.
Then, I was able to format and partition the drive (while booted from
the old xy(0,0,0) partition), as well as copy the data from the old
drive to the new one.
Btw, when I boot with the generic kernel, the disk comes up as `sd2'
(no matter what SCSI id I choose for the disk on the back of the
The problem arises when I try and boot from the new disk, sd2:
scsi: select failed
Given that the drive works fine when I boot from xy(0,0,0) and mount
it, does anyone know why I can't boot from it? Btw, I tried many,
many permutations of X, Y, and Z in "sd(X, Y, Z)" and they all gave
the same result.
The best answer came from Stephen Dowdy <firstname.lastname@example.org>
and is reproduced below. The solution was to get newer PROMs--I ended
up switch CPU and memory boards with another SUN3 to accomplish this
(since my guess as to which of the few chips on the CPU board that
were removable were the PROM(s?) proved fruitless). I had rev 2.7 on
the old board and the one with 3.0 allowed me to boot off the SCSI
Honorable mentions are:
email@example.com (Dan Walsh)
Torsten Metzner <firstname.lastname@example.org>
for suggesting I install the boot block, which I had already done, and
email@example.com (Glenn Satchell - Uniq Professional Services)
for suggesting I crimped incorrectly.
Now, the winner:
Date: Wed, 18 May 1994 21:51:33 -0600
From: Stephen Dowdy <firstname.lastname@example.org>
Subject: Re: need help adding SCSI disk to xy-based SUN-3/260
> Subject: need help adding SCSI disk to xy-based SUN-3/260
> From: Kevin Layer <email@example.com>
> Btw, when I boot with the generic kernel, the disk comes up as `sd2'
> (no matter what SCSI id I choose for the disk on the back of the
This is probably because the SCSI ID selector is not hooked to the drive
internally, and the drive is hard-jumpered to SCSI id=1.
> The problem arises when I try and boot from the new disk, sd2:
> >b sd(0,2,0)
> scsi: select failed
I am guessing that this is because your 4200 BOOT PROM is too low reved.
You probably need at least 2.8.x, but maybe 3.x. It's also possible the
SCSI card you are using is not capable of this in a 4/260.
Check the ROM REV by:
You may need a Sun-3 SCSI card to boot.
Additionally, if the drive is coming up as 'sd2', it is probably jumpered
at SCSI Id=1, and you would boot it:
> b sd(0,8,0)
(The Old SCSI uses 8LUNs per SCSI id, so SCSI ID=0 has 8 addresses, and
SCSI ID=1 would start at unit 8)
I too got bit by this on a "quick" 3/260->4/260 upgrade via a SCSI disk
i built beforehand. Urf! I now have a 4/280 with Sun-3 SCSI and ROM
2.8.3 (?) that i can boot a SCSI disk off.
> Kevin Layer, Franz Inc. 1995 University Avenue, Suite 275
Stephen Dowdy - Systems Administrator firstname.lastname@example.org
Computer Science Dept - University of Colorado, Boulder (303) 492-6196
"Team Spam in '94" (A division of Beatrice)
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:01 CDT