O2 boot once then no idea why not

SGI hardware problems, solutions, tips, hacks, etc.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

O2 boot once then no idea why not

Unread postby Dalplex » Fri Jun 16, 2017 12:13 pm

Hi,

I saw this o2 boot to login once but that was the only one.

Before and after, I saw this everyone without clearly understand what was wrong and what to do.

Please help me out.

IMG_0227.JPG


IMG_0226.JPG
:Indigo: :O2: :Octane: :Octane:

User avatar
dexter1
Moderator
Moderator
Posts: 2735
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Re: O2 boot once then no idea why not

Unread postby dexter1 » Fri Jun 16, 2017 1:03 pm

I've seen this on my O2 a couple of months ago. This post helped me out: viewtopic.php?f=10&t=16719244

Try

Code: Select all

setenv console d

followed by

Code: Select all

init

That should set the console correctly so that miniroot install doesn't crash.
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

Re: O2 boot once then no idea why not

Unread postby Dalplex » Fri Jun 16, 2017 1:19 pm

Thanks.

The thread was discussing redirect the console to d instead of g during the installation but my case is starting the system.

I am not sure once it was redirected to d, whether I still have the ability to see anything from display card instead of terminal, which I current do not have.
:Indigo: :O2: :Octane: :Octane:

User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

Re: O2 boot once then no idea why not

Unread postby Dalplex » Fri Jun 16, 2017 1:31 pm

Altering doing this, no more display from monitor and seems keyboard no longer work neither.
:Indigo: :O2: :Octane: :Octane:

User avatar
dexter1
Moderator
Moderator
Posts: 2735
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Re: O2 boot once then no idea why not

Unread postby dexter1 » Fri Jun 16, 2017 2:13 pm

Ah i now notice you had a different error message. Sorry. I was assuming you were booting a miniroot install.

Do you have a serial nullmodem cable? You should be able to enter the serial console and issue a 'setenv console g' again.

Dealing with the instruction bus error, make sure that whatever you do, always unplug the power chord before you attempt inspection or reseating of the O2 mainboard and components, otherwise you risk zapping the machine.
Try to start with a single DIMM pair once you get your console back
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

Re: O2 boot once then no idea why not

Unread postby Dalplex » Fri Jun 16, 2017 2:34 pm

Yes. The console is back after the hyper terminal.

I think the ram is okay as there is no such panic if I dislodge the hdd.
:Indigo: :O2: :Octane: :Octane:

User avatar
dexter1
Moderator
Moderator
Posts: 2735
Joined: Thu Feb 20, 2003 6:57 am
Location: Zoetermeer, The Netherlands

Re: O2 boot once then no idea why not

Unread postby dexter1 » Fri Jun 16, 2017 2:47 pm

Maybe try to perform an IDE diagnostic from the PROM to see if everything is okay. Will take a while though
:Crimson: :PI: :Indigo: :O2: :Indy: :Indigo2: :Indigo2IMP:

User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

Re: O2 boot once then no idea why not

Unread postby Dalplex » Sat Jun 17, 2017 1:58 am

IDE ef command is not available.

The diagnostic from the menu is very short and will result the same panic.

Tried boot -f sash, same result.

May be the hdd was corrupted?
:Indigo: :O2: :Octane: :Octane:

robespierre
Posts: 1552
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: O2 boot once then no idea why not

Unread postby robespierre » Sat Jun 17, 2017 2:37 am

the IDE program may not be located in the volume header which is why it cannot be loaded
the sash may have become corrupted, or hardware fault

try loading sash from an install tools CDROM

Code: Select all

> dksc(0,6,8)sashARCS
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

Re: O2 boot once then no idea why not

Unread postby Dalplex » Sat Jun 17, 2017 3:14 am

Thanks. Will try once bootable cd media became available.
:Indigo: :O2: :Octane: :Octane:

User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

Re: O2 boot once then no idea why not

Unread postby Dalplex » Sat Jun 17, 2017 3:31 am

Just in case, something might be wrong. Here is the env.

I added the diagnose=v but had not made any difference on diagnostic detail.


IMG_0228.JPG
:Indigo: :O2: :Octane: :Octane:

robespierre
Posts: 1552
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: O2 boot once then no idea why not

Unread postby robespierre » Sat Jun 17, 2017 5:28 am

You should be able to run the diagnostics if they are where it says they are.
What happens if you just type

Code: Select all

> ide
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

robespierre
Posts: 1552
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: O2 boot once then no idea why not

Unread postby robespierre » Sat Jun 17, 2017 11:45 am

btw, the diagmode=v only effect is to display the results of power-on self test. It does not change the verbosity of panic messages.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

User avatar
Dalplex
Posts: 81
Joined: Sat Jun 10, 2017 1:25 pm

Re: O2 boot once then no idea why not

Unread postby Dalplex » Tue Jun 27, 2017 5:51 pm

Today, mount it on a working irix.
Delete the password for root.
Reboot, same problem.
Tried boot -f sash. Same proble.
Tried ide, same problem.
:Indigo: :O2: :Octane: :Octane:

robespierre
Posts: 1552
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: O2 boot once then no idea why not

Unread postby robespierre » Tue Jun 27, 2017 7:34 pm

I don't know why you're having a panic. Was the disk originally part of this system?

When you type "boot" at the prompt, the PROM Monitor loads the standalone program in the OSLoader variable from the SystemPartition. This is normally sash. The Irix kernel isn't involved at this stage. The loader prints a line of numbers like you saw above that represent sash.

If you type "autoboot", the PROM Monitor does the same as above, but passes a flag to sash that tells it to: load the kernel named by the OSLoadFilename (or if none is defined, from the bootinfo of the disk) from the OSLoadPartition. This is also what typing "1" for Start System does in the boot menu.
Two lines of numbers are printed: the first for sash and the second for unix.

So we know that the panic occurred inside sash.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:


Return to “SGI: Hardware”

Who is online

Users browsing this forum: Semrush [Bot] and 3 guests