SUMMARY: partial: Sunfire V120 hangs during jumpstart
- From: Fergus McMenemie <fergus@xxxxxxxxxxxxxxxx>
- Date: Fri, 15 Sep 2006 07:13:06 +0100
Hi,
Only two useful answers both of which were in the general direction of
getting it to boot from CD-ROM to identify if it was a hardware error.
I also got our software support organisation involved and they went down
a similar path.
Unfortunately the unit had no CD-ROM. But I did move the units disk
and system configuration card to another Sunfire were it booted and
jumpstarted fine. This confirmed that the jumpstart and net boot
configuration was OK.
Replacing the disk and configuration card I obtained a CD-ROM from
another Sunfire. The unit then CD booted with both 5.8 2/02 and 2/04.
However the boot sequence was different. It never looked for:-
su4 at ebus3: offset 0,3f8Instead going for Su0 and Su1. So this was kind of side stepping the
su4 is /pci@1f,0/pci@1,1/isa@7/serial@0,3f8
su5 at ebus3: offset 0,2e8
su5 is /pci@1f,0/pci@1,1/isa@7/serial@0,2e8
issue.
We compared the EEPROM output on a good/bad system. They were the same.
Anyway based on all the above I decided there was something wrong with
the serial port hardware and got the CPU card replaced.
Made no difference at all. System still failed to net boot.
Going through the jumpers and other settings was the next step;
comparing
the good and bad machine. They appeared to be equivalent as the
far service guy was concerned. (I did not look at them.) The LOM
versions
were the same.
The only difference that was found was that the good machine identified
itself as a v120 within the LOM PROM setting while the bad said it was a
Netra of some kind. What this the difference?
=====
PS. The service tech took the Sunfire back to his area and continued to
work on it. As part of doing this he set it up to net boot from his own
jumpstart server. This worked! His jumpstart server went through the
Su1/Su0 sequence not Su4/Su5. What is the difference ? What is causing
this difference?
=====
PS. Ran into a nasty side effect of moving CD-ROM drives from machine
to machine. The sunfires internal disk assignments change depending on
the presence of a CD-ROM drive.
c0t0d0 becomes c1t0d0
This really messes up jumpstart configuration. I have to hard code
the rules files differently as CDrom drives are moved from machine to
machine. A real pain.
======================================================================
Fergus McMenemie Email:fergus@xxxxxxxxxxxxxxxxx
Techmore Ltd Phone:(UK) 07721 376021
Unix/Mac/Intranets Analyst Programmer
======================================================================
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
- Prev by Date: SUMMARY: Q: Solaris 9 Sparc "smpatch", SMC issues -> Recommended Standard Solution(s) ?
- Next by Date: NIS and NFS problem
- Previous by thread: SUMMARY: Q: Solaris 9 Sparc "smpatch", SMC issues -> Recommended Standard Solution(s) ?
- Next by thread: NIS and NFS problem
- Index(es):
Relevant Pages
|
Loading
