From: hanson@pogo.fnal.gov (Steve Hanson)
Newsgroups: comp.sys.sun.hardware,comp.sys.sun.misc,comp.sys.sun.admin
Subject: Re: Help: Can't boot from Seagate ST41200N 1G disk.
Date: 14 Sep 92 14:58:26 GMT
Followup-To: comp.sys.sun.hardware
Organization: FERMILAB, Batavia, IL

In <1992Sep11.055715.1369@theweav.cts.com> rickf@theweav.cts.com (Rick Flower) writes:

>In article <1992Sep3.074820.4602@usage.csd.unsw.OZ.AU> raymond@vast.unsw.edu.au (Raymond Leung) writes:
>>Have anyone be able to boot from a Seagate ST41200N 1G disk on a SUN ELC?

>No, but I've got one sitting here on my 'ol 3/60 (SunOS 4.0.3)

>>I got the following message from the monitor:
>>
>>    >b
>>    Boot device:/sbus/esp@0,800000/sd@3,0     File and args: vmunix
>>    Can't read disk labe.
>>    Can't open Sun disk label package
>>    boot-block startup failed.
>>    Illegal Instruction.
>>
>>Disk type in format.dat is as followed:
>>
>>    disk-type= "Seagate Wren 7 ST41200N" \
>>		: ctlr = MD21 : fmt_time = 4 \
>>		: cache = 0x11 : trks_zone = 15 : asect = 5 : atrks =  30 \
>>		: ncyl = 1928 : acyl = 2 : pcyl = 1930 : nhead = 15 : nsect = 70 \
>>		: rpm = 3600 : bpt = 41301
>>
>>
>>I have no problem mounting the disk and using it, just can't boot from it.
>>I have run installboot on the new disk. I have also tried installing from
>>SUNOS CD-ROM and all completed successful but the boot still failed.
>>

>I had a heck of a time getting my 41200 formatted the first time... Once I 
>finally got that done, all was well!

>>Any idea?
>>

>Nope.. I did notice that when this drive's got the wrong option settings
>for the termination resistor power (I accidentally read the picture 
>incorrectly) which cause the drive to behave oddly..

>>Raymond Leung

>-- Rick

>-- 
>+-----------------------------------------------------------------+
>| Stimpy : Ren.. Will you Read Me a Bedtime Story??               |
>| Ren    : A Bedtime Stoory.. Go read it yourself!!               |
>+------------------------------------------------------+----------+
This keeps coming up.  It depends on what age of Wren VII drive you
have and what the firmware revision is.  Here is the brief poop on
how to get your system to boot.




marc@Altitude.CAM.ORG provides the appropriate solution which I have also
verified with Sun Technical Support.

 I have encountered the same problem a few months ago, when attempting to
 use a Wren VII as the primary boot disk of my SS2.
 
 The solution was emailed to me by Andy.Bowers@UK.Sun.COM. I no longer have 
 the message in electronic form, but here are the essentials:
 
 Problem is due to a Wren VII firmware bug. There is a simple workaround.
 
 Details:
 
 The Wren VII drive screws up when issued a "spin up" command with the
 "immediate" bit set. Sometime after that command is issued, a subsequent
 command will fail (the particular command which fails is a "read", reporting
 an "internal target error" status).
 
 The problem does not occur if the "spin-up" command does not have the immediate
 bit set. (The immediate bit, when set, means that the device should start the
 operation and then complete the SCSI transaction, without making the CPU wait
 for the operation to complete)
 
 The workaround:
 
 Add the following commands to the NVRAMRC. The effect is to turn off the
 immediate bit on the spinup command:
 
 ok nvedit
 0: true to fcode-debug?
 1: probe-all install-console banner
 2: cd /sd
 3: patch 0 1 sstart
 4: device-end
 ^C
 nvstore
 setenv use-nvramrc? true
 
 Then power cycle. Subsequent attempts to boot from the Wren drive should be
 successful.
 
 -Marc.

--------------------------------------------------------------------------------
Pennie Hall
Fermilab, Batavia, IL
phall@mdtf05.fnal.gov  or  phall@fnal.fnal.gov
--------------------------------------------------------------------------------


-- 
Steve Hanson - FERMILAB, Batavia, Il.
hanson@pogo.fnal.gov or hanson@fnal.fnal.gov