v210 hangs on boot and install

From: synrat (synrat_at_wirewalk.org)
Date: 09/21/05

  • Next message: rajeev.andrews_at_wipro.com: "Slow response in NFS access"
    Date: Wed, 21 Sep 2005 10:15:50 -0400
    To: sunmanagers@sunmanagers.org
    
    

    I'm having some strange issues with new v210 and sol 10.
    it worked fine for a week, but after trying to mirror the
    root device, I rebooted it with root mounted on md device,
    it crashed after 1 minute of uptime. Since then, I switched back
    to booting from standard disk device and removed the md reference
    from /etc/system, however the system won't boot fully. It gets to the
    point of setting the hostname and stops ( I can also ping the system at
    that point, so I just assume it mounts root read only and brings up the
    network, but can't go any further ). Can't get into single user either.

    When I boot into single user from cd, all regular disk partitions fsck
    just fine, with no errors and mount r/w as well, I can open and save
    files just fine.

    What's even more weird is that when attempting a reinstall, it also
    hangs. Below is the output from boot -v and reinstallation attempt.
    It doesn't exactly seem like a problem with disks, controller or
    backpane, since it's all mountable from the cd, but I really don't have
    a clue why wouldn't the boot sequence or the install proceed.

    thank you all in advance.

    >Rebooting with command: boot -v
    >> Boot device: /pci@1c,600000/scsi@2/disk@0,0:b File
    >> and args: -v
    >> The boot filesystem is logging.
    >> The ufs log is empty and will not be used.
    >> Size: 0x704c8+0x1b8d2+0x2e1ba Bytes
    >> module /platform/sun4u/kernel/sparcv9/unix: text at
    >> [0x1000000,
    >> 0x10704c7] data at 0x1800000
    >> module misc/sparcv9/krtld: text at [0x10704c8,
    >> 0x10889e7] data at 0x1849a90
    >> module /platform/sun4u/kernel/sparcv9/genunix: text
    >> at [0x10889e8,
    >> 0x11cd177] data at 0x184ee80
    >> module
    >>

    /platform/SUNW,Sun-Fire-V210/kernel/misc/sparcv9/platmod:

    >> text at
    >> [0x11cd178, 0x11cdc17] data at 0x189ffd0
    >> module
    >>

    /platform/sun4u/kernel/cpu/sparcv9/SUNW,UltraSPARC-IIIi:

    >> text at
    >> [0x11cdc80, 0x11dd58f] data at 0x18a0880
    >> SunOS Release 5.10 Version Generic 64-bit
    >> Copyright 1983-2005 Sun Microsystems, Inc. All
    >> rights reserved.
    >> Use is subject to license terms.
    >> Ethernet address = 0:3:ba:e9:9c:71
    >> mem = 2097152K (0x80000000)
    >> avail mem = 2080268288
    >> root nexus = Sun Fire V210
    >> pseudo0 at root
    >> pseudo0 is /pseudo
    >> scsi_vhci0 at root
    >> scsi_vhci0 is /scsi_vhci
    >> pcisch2 at root: SAFARI 0x1c 0x600000
    >> pcisch2 is /pci@1c,600000
    >> /pci@1c,600000/scsi@2 (glm0):
    >> glm0 supports power management.
    >> /pci@1c,600000/scsi@2 (glm0):
    >> Rev. 0 Symbios 53c1010-33/66 found.
    >> PCI-device: scsi@2, glm0
    >> glm0 is /pci@1c,600000/scsi@2
    >> sd0 at glm0: target 0 lun 0
    >> sd0 is /pci@1c,600000/scsi@2/sd@0,0
    >> root on /pci@1c,600000/scsi@2/disk@0,0:b fstype ufs
    >> pcisch1 at root: SAFARI 0x1e 0x600000
    >> pcisch1 is /pci@1e,600000
    >> PCI-device: isa@7, ebus0
    >> ebus0 is /pci@1e,600000/isa@7
    >> mc-us3i0 at root: SAFARI 0x0 0x0 ...
    >> mc-us3i0 is /memory-controller@0,0
    >> mc-us3i1 at root: SAFARI 0x1 0x0 ...
    >> mc-us3i1 is /memory-controller@1,0
    >> power0 at ebus0: offset 0,800
    >> power0 is /pci@1e,600000/isa@7/power@0,800
    >> rmc_comm0 at ebus0: offset 0,3e8
    >> PCI-device: pmu@6, pmubus0
    >> PCI-device: gpio@80000000, pmugpio0
    >> pmugpio0 is /pci@1e,600000/pmu@6/gpio@80000000
    >> pseudo-device: rmclomv0
    >> rmclomv0 is /pseudo/rmclomv@0
    >> Hardware watchdog enabled
    >> su0 at ebus0: offset 0,3f8
    >> su0 is /pci@1e,600000/isa@7/serial@0,3f8
    >> cpu1: UltraSPARC-IIIi (portid 1 impl 0x16 ver 0x34
    >> clock 1336 MHz)
    >> cpu0: UltraSPARC-IIIi (portid 0 impl 0x16 ver 0x34
    >> clock 1336 MHz)
    >> PCI-device: usb@a, ohci0
    >> ohci0 is /pci@1e,600000/usb@a
    >> pcisch0 at root: SAFARI 0x1f 0x700000
    >> pcisch0 is /pci@1f,700000
    >> PCI-device: network@2, bge0
    >> bge0 is /pci@1f,700000/network@2
    >> [ network/http:apache2 failed (see 'svcs -x' for
    >> details) ]
    >> Hostname: orion
    >> sd1 at glm0: target 1 lun 0
    >> sd1 is /pci@1c,600000/scsi@2/sd@1,0

    and nothing further...

    installation, with "boot cdrom"

    System identification is completed.
    System identification complete.
    Starting Solaris installation program...
    Executing JumpStart preinstall phase...
    Searching for SolStart directory...
    Checking rules.ok file...
    Using begin script: install_begin
    Using finish script: patch_finish
    Executing SolStart preinstall phase...
    Executing begin script "install_begin"...
    Begin script install_begin execution completed.

    nothing further....
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: rajeev.andrews_at_wipro.com: "Slow response in NFS access"

    Relevant Pages

    • RE: Linux hacked
      ... I would also suggest using a simple script in the future that alerts ... Subject: Linux hacked ... To get back into your account you want to use, at the boot manager ... boot normally and you should be able to login as root with your new ...
      (Security-Basics)
    • Re: Solaris bare metal restore with IBM TSM client?
      ... Is it possible to do a wanboot and use flash archives via the ... boot> router-ip=10.3.239.62 ... Using finish script: finish_script.sh ... Executing begin script "begin_script.sh"... ...
      (comp.unix.solaris)
    • Re: Solaris bare metal restore with IBM TSM client?
      ... boot> router-ip=10.3.239.62 ... Starting Solaris installation program... ... Using finish script: finish_script.sh ... Executing begin script "begin_script.sh"... ...
      (comp.unix.solaris)
    • RE: Linux hacked
      ... > script that performs an MD5 hash on certain files and then compares the ... > boot normally and you should be able to login as root with your new ... > crackers break in their account and from there they do more damage. ...
      (Security-Basics)
    • Jumpstart - could not load media /cdrom
      ... So I boot the client using BOOT NET - INSTALL. ... Searching for JumpStart directory... ... Executing JumpStart preinstall phase... ... Using begin script: install_begin ...
      (comp.unix.solaris)