solaris hangs after booting

Hi,

We've got a Sun Fire V245 that's failing to boot from either boot disk (mirrored using SVM). It simply hangs after loading a few modules:

Sun Fire V245, No Keyboard
Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.22.22, 1024 MB memory installed, Serial #74521658.
Ethernet address 0:14:4f:71:1c:3a, Host ID: 84711c3a.



Rebooting with command: boot -avr /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
Boot device: /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a  File and args: -avr /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
krtld: Unused kernel arguments: `/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0'.
module /platform/sun4u/kernel/sparcv9/unix: text at [0x1000000, 0x10a096d] data at 0x1800000
module /platform/sun4u/kernel/sparcv9/genunix: text at [0x10a0970, 0x12615bf] data at 0x1867cc0
module /platform/SUNW,Sun-Fire-V245/kernel/misc/sparcv9/platmod: text at [0x12615c0, 0x1261e4f] data at 0x18be088
module /platform/sun4u/kernel/cpu/sparcv9/SUNW,UltraSPARC-IIIi: text at [0x1261e80, 0x1272f0f] data at 0x18be900

Once it get's to this stage, we get nothing. This occurs when trying to boot fom either of the mirrored disks. We're getting someone onsite with Solaris media, so we can boot from CD into single user. In the meantime, can anyone shed any light as to what could be the issue here?

After these modules are loaded, am I correct in assuming the kernel tries to mount the root filesystem? I guess if we're having this issue on both boot disks, the root filesystem has become unusable/corrupted in SVM?

Thanks in advance.

Was there any change in server's hardware or software configuration recently?

not that I know of. I only provide assistance to the admins of this sytem anyhow :rolleyes: I've been told nothing was changed, and the box crashed, and went down sometime over the weekend.

I was really trying to figure out where this was hanging - just so I've got an idea of where to troubleshoot once we're able to get it into single user. I think it's hanging just before the init phase. So the kernel is initialised, and modules loaded.

Maybe try running extensive POST test...

Why was "-ar" added to the boot options? Where you having problems with /etc/path_to_inst?

I haven't done a boot -v on a SPARC box in a long time, but hanging right after loading that CPU module doesn't look like a good sign to me. Offhand, I'd guess there's a hardware problem.

As bartus11 said, up the diag level in POST.