SUMMARY : Sun-FireV210 hanging on reboot/boot from OK prompt

From: David STAPLETON (davy_stapleton_at_bikerider.com)
Date: 10/27/04

  • Next message: nicholas: "ask sunmanagers: which system configuration auditing tool" 
    To: sunmanagers@sunmanagers.org
Date: Wed, 27 Oct 2004 09:20:50 +0100

    Hi all,

    I actually got no replies to this one at all.

    It's a late summary as the problem was only resolved recently due to site
    moves and project time lines, etc.

    I logged a call with SUN and it looked like it was actually a hardware issue,
    specifically one of the disks.

    The theory was that the disk was ok from a cold boot but failed to properly
    initialise when the server was rebooted or booted from the OK prompt.

    I swapped out the disk, replacing it with a new one and the problem was still
    there.

    It turns out it was a hardware issue but a faulty disk back plane rather than
    disk.

    After this was swapped out the problem disappeared.

    Regards,

    david s.

    ========== Original posting ==========

    Date: Tue, 14 Sep 2004 08:33:44 +0100
    From: "David STAPLETON" <davy_stapleton@bikerider.com>

    Subject: Sun-FireV210 hanging on reboot/boot from OK prompt
    To: sunmanagers@sunmanagers.org

    Message-ID: <20040914073344.AC882790056@ws1-14.us4.outblaze.com>

    Content-Type: text/plain; charset="iso-8859-1"

    Hi all,

    I recently jumpstarted a new Sun-FireV210, actually three, but one is
    giving me problems when I reboot from the OS or try to boot
    (including boot -s) from the OK prompt. BUT if the machine if
    powered down and you do a power-up it boots up directly with no
    problems.

    The jumpstart on all three were identical and the other two do not
    show this issue.

    I have compared the eeprom values and the devalias values one of the
    two machines to the one that is not rebooting and they are the same.
    About the only thing that is different is that the one causing
    problems is in the same building as me and I used a dumb terminal
    plugged directly into the ALOM port to jumpstart it, (the others are
    at remote sites and had the ALOM configured over the network).

    I haven't actually set the netsc_ipaddr, nets_ipnetmask, etc., could
    this be causing it to seemingly lose connection on a reboot or boot,
    if so why not from an initial power-up???

    Any help is very appreciated and I will, as usual, summarise.

    Regards,

    David S. 

    --
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
  • Next message: nicholas: "ask sunmanagers: which system configuration auditing tool"