From: Jennifer Peterson (jpeterso@asf.alaska.edu)
Date: Thu Mar 27 2003 - 11:31:22 EST
I've got a stalled boot process on a solaris 2.6 E3500 box. My original
email follows with the details of exactly where it stall with boot -v.
I should also add that I'm able to boot into single user mode with a
cdrom. While there I can run prtdiag and psrinfo. Prtdiag doesn't
indicate any hardware failure and psrinfo sees all 4 cpus.
At this point, should I be thinking that this is a software problem? The
machine hadn't been rebooted in a long time, and it's possible that some
change took place in the interim that would make the thing not come up.
I just don't have the first clue how to troubleshoot that--not without
knowing what the machine's trying to do at the point that it fails.
Finally, when I do boot off cdrom, my device names are different from
what they normally are. What is (and continues to be) c0t0d0s0 when I
try to boot normally, becomes c1t0d0s0 when I boot off cdrom. I've never
seen that behavior on my other sun boxes.
Thanks,
Jenn
On Wed, 2003-03-26 at 17:02, Jennifer Peterson wrote:
> HI again,
>
> I'm continuing to have problems booting my solaris 6 E3500 box. During
> boot it's getting to
>
> stdout is </sbus@3,0/cgsix@0,0> major <39> minor<0>
>
>
> What is supposed to come after I think is
>
> boot cpu intialization. What happens during that phase of boot?
>
> Thanks,
>
> Jenn
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:04 EDT