Sun Blade 100 and Symbios 22801

I take it that you installed the OS on the scsi drive? are there any ide drives in the machine?

I would think if the box saw the drive and was able to install the OS, then it should boot.

you could do a Stop + N (holding the keys down until the splash screen), that would set everything to defaults...

I have not tried using a non-Sun scsi card(I imagine this is the case) in a Sun box... I don't have a blade 100..

I just thought I would throw out some possibilities.

haroldkarl

haroldb at 2007-7-6 13:40:46 >

HI, having exact same problem..

- Uisng 2 sym22801 cards

- usining 2 different size scsi hard drives:

- Latest OBP

Hi,

The SCSI card SYM22801 SE is suposed to be compatible with SUN Pc's, I have a Sun Blade 100,756MB memory, 500MHz, running SOlaris 10, I wanted to swap the IDE drives for SCSI drives, The card was detected and it seems to be OK (btw, this a NEW card).

I connected one drive to be used as a secondary drive (QUANTUM ATLAS 10K 3.5series 18.2 ULTRA160M/LVD/SE), The drive was deteced, formated and working just fine (this drive is connected on the second internal 68pin connected:

1. c2t1d0 <QUANTUM-ATLAS10K18WLS-UCH0 cyl 9943 alt 2 hd 12 sec 298>

/pci@1f,0/pci@5/scsi@2,1/sd@1,0

Now, I wanted to replace the boot primary drive for a 36gb scsi drive: Quantum Atlas II 36.7GB Ultra160 LVD/SE 10K SCSI

Made the necesary correction so I can use the cdrom to install and be able to see the new primary scsi drive:

OK nvalias cdrom /pci@1f,0/ide@d/cdrom@0,0:f

OK nvalias disk /pci@1f,0/pci@5/scsi@2/disk@0,0

Bot from cdrom and install Solaris 10... so far so good, no problems at all...

Once it finishes installing Solaris, the machine wont boot...

It sees the device, it gives me the normal boot screen, recognizes the host name, configures the Net link... and then the Hard drive 'stops' and the I get an error on the screen saying something like scsi disconnects and it can not contact the drive (disk not responding to selection and some other messages - sorry I can recall exactly) .. what's gong on?... I installed Solaris 3 times with the same result, it installes all the way with no problem, I even went thru and formated and sliced the drive before installing solaris..

I tried a 73GB Fujitsu drive with the same result... installing twice on this drive...

What seems to be the problem? I know the drives are OK and the scsi card is OK too, I can install one drive and boot from the ide drive and be able to see everything on thos drives... It just that machine does not want to boot from a scsi drive?

I even used the card on a windows machine and I can see it works perfectly...

I have 2 of this cards, I swaped the scsi card and the same thing happens.... I waisted 3 days on this and I cant find any answer to this...

Any help?

Here is some messages showing that the card inf fact is working:

- Using primary IDE drive

- Using secondary SCSI drive (pci@5/scsi@2,1)

Apr 16 08:20:19 Blade scsi: [ID 365881 kern.info] /pci@1f,0/pci@5/scsi@2,1 (glm1):

Apr 16 08:20:19 Blade Rev. 5 Symbios 53c876 found.

Apr 16 08:20:19 Blade pci_pci: [ID 370704 kern.info] PCI-device: scsi@2,1, glm1

Apr 16 08:20:19 Blade genunix: [ID 936769 kern.info] glm1 is /pci@1f,0/pci@5/scsi@2,1

Apr 16 08:20:19 Blade scsi: [ID 193665 kern.info] sd17 at glm1: target 1 lun 0

Apr 16 08:20:19 Blade genunix: [ID 936769 kern.info] sd17 is /pci@1f,0/pci@5/scsi@2,1/sd@1,0

This is my eeprom (note that use-nvramrc?= is set to 'false' so it does not try to boot from the new scsi drive since I have the IDE connected now.):

$ /usr/sbin/eeprom

test-args: data not available.

diag-passes=1

pci-probe-list=7,c,3,8,d,13,5

local-mac-address?=false

fcode-debug?=false

silent-mode?=false

scsi-initiator-id=7

oem-logo: data not available.

oem-logo?=false

oem-banner: data not available.

oem-banner?=false

ansi-terminal?=true

screen-#columns=80

screen-#rows=34

ttyb-rts-dtr-off=false

ttyb-ignore-cd=true

ttya-rts-dtr-off=false

ttya-ignore-cd=true

ttyb-mode=9600,8,n,1,-

ttya-mode=9600,8,n,1,-

output-device=screen:r1024x768x75

input-device=keyboard

load-base=16384

auto-boot?=true

network-boot-arguments: data not available.

boot-command=boot

diag-file: data not available.

diag-device=disk

boot-file: data not available.

boot-device=disk

use-nvramrc?=false

nvramrc=devalias disk /pci@1f,0/pci@5/scsi@2/disk@1,0

devalias cdrom /pci@1f,0/ide@d/cdrom@0,0:f

security-mode=none

security-password: data not available.

security-#badlogins=0

diag-script=none

diag-level=max

diag-switch?=false

error-reset-recovery=boot

$

Sorry for the long post... Any help on this? I am frustrated a this point..

murilloa

murilloa at 2007-7-6 13:40:46 >

HI..

Looking into some information, I found this note:

**********************************

If you can boot from the CD-ROM, but still cannot mount it manually in multi-user mode, check the /kernel/drv/sd.conf file to make sure that it contains four atapi entries for the CD-ROM device:

name="sd" class="scsi" class_prop="atapi"

target=0 lun=0;

name="sd" class="scsi" class_prop="atapi"

target=1 lun=0;

name="sd" class="scsi" class_prop="atapi"

target=2 lun=0;

name="sd" class="scsi" class_prop="atapi"

target=3 lun=0;

***********************************************

Is it possible that the scsi drive has to be on a target ID different fom 0-3?

The /kernel/drv/sd.conf file lists as follows:

$ more /kernel/drv/sd.conf

#

# Copyright (c) 1992, by Sun Microsystems, Inc.

#

#ident "@(#)sd.conf1.998/01/11 SMI"

name="sd" class="scsi" class_prop="atapi"

target=0 lun=0;

name="sd" class="scsi" class_prop="atapi"

target=1 lun=0;

name="sd" class="scsi" class_prop="atapi"

target=2 lun=0;

name="sd" class="scsi" class_prop="atapi"

target=3 lun=0;

name="sd" class="scsi"

target=4 lun=0;

name="sd" class="scsi"

target=5 lun=0;

name="sd" class="scsi"

target=6 lun=0;

name="sd" class="scsi"

target=8 lun=0;

name="sd" class="scsi"

target=9 lun=0;

name="sd" class="scsi"

target=10 lun=0;

name="sd" class="scsi"

target=11 lun=0;

name="sd" class="scsi"

target=12 lun=0;

name="sd" class="scsi"

target=13 lun=0;

name="sd" class="scsi"

target=14 lun=0;

name="sd" class="scsi"

target=15 lun=0;

$

What does this part mean?

"class_prop="atapi" on the first 4 target statements?

murilloa at 2007-7-6 13:40:46 >