Sun SPARC Enterprise T5140 Server
 

PLA-Support>Sun Systems>SPARC>CMT>SN-SPARC: T5xx0
 

In this Document

Symptoms

Changes

Cause

Solution

Created from <SR 3-8257086691>

Applies to:

Symptoms

 ILOM service processor does not  boot due to File System corruption.

After removing and connect the power cords, the ILOM doesn't boot and never showed the login screen.

tffs: flAbsWrite error 29
end_request: I/O error, dev 64:02 (tffs), sector 554
kjournald starting. Commit interval 5 seconds
EXT3-fs error (device loop(7,2)): ext3_get_inode_loc: bad inode number: 2
EXT3-fs: corrupt root inode, run e2fsck
mount: wrong fs type, bad option, bad superblock on /dev/loop2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
...

tffs: flAbsWrite error 29
end_request: I/O error, dev 64:02 (tffs), sector 2
EXT3-fs error (device tffs(100,2)): ext3_free_blocks: bit already cleared for bock 6657
...
end_request: I/O error, dev 64:02 (tffs), sector 574
12+0 records in
12+0 records out
mke2fs 1.37 (21-Mar-2005)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
3072 inodes, 12288 blocks
614 blocks (5.00%) reserved for the super user
First data block=1
2 block groups
8192 blocks per group, 8192 fragments per group
1536 inodes per group
Superblock backups stored on blocks:
8193

Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: tffs: flAbsWrite errr 29
end_request: I/O error, dev 64:02 (tffs), sector 8818
end_request: I/O error, dev 64:02 (tffs), sector 8820
end_request: I/O error, dev 64:02 (tffs), sector 8822
tffs: flAbsWrite error 29
...
Failed to make directory /conf/sparc_state/, errno=30
Failed to make directory /conf/sparc_state/HOST, errno=2

Changes

 After plugging the power cords into the power supplies the ILOM won't boot.

Cause

Service Processor firmware got corrupted and this is stopping the server from booting
 
After removing power cords from both PSUs nothing changed, the ILOM shows the same file system errors.
 

Solution

The ILOM is integrated at the MB this is the reason why we have to replace the whole system board.

The MB replacement procedure is described in How to Remove and Replace a T5140/T5240 System Board:ATR:1326:2 (Doc ID 1307330.1)
 

This solution has no attachment