Solaris W/S with Blank screen and no boot.

Dear Friends,

I have a problem at work and need help immediately.  I normally don't deal with Solarismachine, but now, I am ask to check out.  One of my Solaris W/S, the monitor screens went blank.  It does not reboot nor does it come to the OK prompt.  The screen is blank, the screen light is constantly blinking, CDROM light is constantly blinking and the system does not boot from the disk.

Diagnostic steps tried:

I took healthy disk from one other workstation and put it to the faulty workstation.  It didn’t give any results and problem still persisted.

In order to check the integrity of the hard disk of the faulty machine, I put the hard disc from the faulty machine and put it to other healthy machine. The disk is physically seen but gives the following errors:

Unable to repair the / filesystem.
Run fsck manually (fsck –F ufs /dev/rdisk/c0t0d0s0)

When I run the suggested command, it gave a couple of errors like:
Cannot read: BLK 23303072
The following sectors could not be read:

While Control-D pressed, it gave the following:
Mount: the state of /dev/dsk/c0t0d0s0 is not okay
And some other INIT errors.

Attempted different good monitors connected to the faulty W/S – no result.

Removed hard drive from faulty W/S and inserted known good hard drive into the faulty workstation – no boot, similar result.

Assumption is that that the BIOS might have some sort of problem, but that is my guess. What is the next step to repair this computer?  Please help.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


You posted in the Windows 98 TA when you should have posted here:

Will ask for this question to be moved to the correct TA.

You may have gone forward too many steps.

If you are not getting the ok prompt, it doesn't matter if the disk is bad or not, since the ok prompt comes from the obp on the mother board.

Not getting an ok prompt can be caused by many things, and most of them are broken hardware.  

Check the graphics adapter making sure it is properly seated.  Make sure that all other connections are properly seated.

Are you sure that the box didn't boot?  If the graphics adapter is bad, the machine may still boot up and you may be able to get to it through the network via telnet or ssh.

When you put the disk in another box, the first thing to to is run the format command (not to actually format the disk, but to determine the layout) in the format after you have sellected the proper disk, type par (partition) then pr (print) this will show you the disk layout.  

It is very possible that you cannot fix the root (/) partition because it is not on slice 0 some folks put swap on 0 or use some other non-standard layout.

If you post the model of the Sun box, we may be able to give you more trouble shooting tricks...

You harddisk is faulty, and you box might have other problem as well.

Find a monitor you know if works and plug it in the Sun box, and make
sure that keyboard & mouse are plug in as well.

power on the box, then type in: (need to do it fast!)

<Stop> N
to reset your NVRAM

to see if you can get to the OBP (ok prompt).

If not, you might have prolrm with the NVRAM chip or mainboard, or memory. open the box,  resit the memory chips and make sure all
the cable are connect properly and try again.

If you have the same model of the box, you can try to replace the NVRAM
chip to see if it can help.

Have a look at the hareware manual for your box in:

to see how to replace the part, if you are not sure what to do, get some one with experience to do it for you. (or contact Sun).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
samadduAuthor Commented:
Thank youi guys for the help.  Your suggestion lead me to the solution.  problem resolved.  RAM was the culprit.  Thnak you.

yuzh's answer is mostly correct, but I would not write off the hard drive until you preformed the test that I mentioned above.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.