[chulofiasco]

I haven't powered up the tezro for a long time. The last time I've used the machine it booted IRIX fine.

First I noticed some VRM problem messages(don't know if this is a problem):

INFO: Cannot enable VRM: 9
INFO: Cannot enable VRM: 10
INFO: Cannot enable VRM: 11


SGI SN1 L1 Controller
Firmware Image B: Rev. 1.40.6, Built 01/06/2006 13:16:50


001c01-L1>

This is normal -- i think those VRMs might be on an IP59 board, and as you've got the IP53, you won't have them.

But it doesn't detect the IO9 board also:
001c01-L1>pwr up
001c01-L1>
entering console mode  001c01 CPU0, <CTRL_T> to escape to L1
Starting PROM Boot process
io_config_space: Found 0 Qlogic devices BASEIO; expected 1 or more.
io_config_space failed:
RSLT io_config_spac FAIL                diag_rc = 53
diag_io6confSpace_sanity: /hw/module/001c01/xtalk/15: FAILED


IP35 PROM SGI Version 6.210  built 02:33:51 PM Aug 26, 2004
Testing/Initializing memory ...............            DONE
Copying PROM code to memory ...............            DONE
Discovering local IO ......................            DONE
Discovering NUMAlink connectivity .........
Local hub NUMAlink is down.
*** Local network link down
DONE
Found 1 objects (1 hubs, 0 routers) in 5887 usec
Waiting for peers to complete discovery....            DONE
No other nodes present; becoming global master
Global master is /hw/rack/001/bay/01
Intializing any CPUless nodes..............            DONE
Checking partitioning information .........            DONE
No other nodes present; becoming partition master
Local slave entering slave loop
Local slave entering slave loop
Local slave entering slave loop
Loading BASEIO prom .......................            DONE

BASEIO PROM Monitor SGI Version 6.210  built 02:30:38 PM Aug 26, 2004 (BE64)
4 CPUs on 1 nodes found.

NVRAM checksum is incorrect: reinitializing.
Automatic update of PROM environment disabled
Graphics diagnostics

Odyssey board #0 found on nasid 0
Running Odyssey xtalk sanity diag...
        Board version 1 - Buzz revision 3B
        On board sdram size: 128 Mb
        Cas latency: CAS 3
        4 banks by sdram module
Running Odyssey Buzz registers diag...
Device passed diagnostics

Installing PROM Device drivers ............
On-board (IO9) tigon3 1000BaseT interface
Base I/O Ethernet set to /dev/ethernet/tg0
Installing Graphics Console...
graphics install: searching for pipe 0
Probing IOC4 ATA adapter 2
IOC4 RevId = 83
Initializing PROM Device drivers ..........
  Initializing Base I/O Ethernet Interface...Failed.  MII Status Register = 0x7949
Done.
  ---------------Interface Configuration Summary----------------
  ASIC|Revision|MAC Address      : 5701|B5|08:00:69:11:dc:4b
  Link Negotiation|Advertisement  : On|<H10 F10 H100 F100 F1000>
  Link|Speed|Duplex|Rx/Tx FlowCtrl: Down|10|Half|Off/Off
  --------------------------------------------------------------
DONE
Cannot connect to keyboard -- check the cable.
Cannot open /dev/input/ioc4pckm0 for input
Cannot connect to keyboard -- check the cable.
Cannot open /dev/input/ioc4pckm0 for input
Checking hardware inventory ...............
WARNING: hardware inventory is invalid.  Reinitializing...
Writing 5 records..... DONE
Updated new configuration. Wrote 5 records.

**** System Configuration and Diagnostics Summary ****
CONFIG:
        No. of NODEs enabled    = 1
        No. of NODEs disabled  = 0
        No. of CPUs enabled    = 4
        No. of CPUs disabled    = 0
        Mem enabled            = 4096 MB
        Mem disabled            = 0 MB
        No. of RTRs enabled    = 0
        No. of RTRs disabled    = 0

DIAG RESULTS:
        ALL DIAGS PASSED.
**** End System Configuration and Diagnostics Summary ****

Any help will be appreciated.

Best regards,
kokoboi

This might sound dumb, but have you checked the cable connection on the node board side to ensure the HDD bays are actually connected to the cable you've plugged into the IO9?  Check the power as well... if the drives aren't powering up, they won't be seen.

Also, the Dallas on the PCI side of the Tezro, I'm pretty sure that's used only for the L1 controller -- if this is bad, you'll know it, the LCD display will not power on or you'll get different errors on the console.