🚀 go-pugleaf

> That's correct. You can always check the integrity of your SCSI setup
before
> booting by using the 'probe-scsi' and 'probe-scsi-all' commands which are
> present in the bootROM. This will prove that each device is correctly
> recognised and that each device is set up for the right ID.

Never got "probe-scsi" to work ever...
Always "freezes" the machine until I do L1-A to get back to the prompt.
If I do not do probe scsi the machine boots without problems,
netiher during boot, nor during normal operation.
Have not noticed any other disk problems, or sudden freezes...

If I put the 2932 into the SCSI 2 chassi, it will simply not be detected
and boot continues without other problems.
If I put the disk in a SCSI 1 chassi, it will be detected...

I moved the  SCSI 2 flat cable to the SCSI 1 box and used the external SCSI
2
cable and the disk is then detected.
Conclusion is that neither the external nor internal SCSI2 cable
is bad so that also points to the power supply of the SCSI 2 box.

> >7) During the SCSI scan phase of the boot, the SPARC will
> >    spend extra time at the SCSI Id for the 2932.
> >    Sometimes it continues , sometimes it freezes.
>
> 2932's do not automatically spin up until there is some sort of data
access.
> I noticed this since a 'probe-scsi' reports back the drive data ok, but it
> will not activate the spindle motor until there is some attempt to access
> data on the drive (which in my case was when the kernel had loaded and it
> went to mount partitions on the 2932).


What I have not figured out is why the drive is detected with one power
supply
but not with the other?

--
Best regards,
ulf at atmel dot com
The contents of this message is intended to be my private opinion and
may or may not be shared by my employer Atmel Sweden