I/O Error (WARN 80F5) for D390

[Del Babineau]

My D390 will not reboot due to a failure to initialize the boot disk. The chassis window displays the following error:

WARN 80F5 I/O CPU01

My first instinct is that it is a controller or scsi card issue.

Any thoughts?

[Alex Glennie]

boot fails at WARN 80F5 -> check cabling, reseat core I/O, check root
disk.

fyi :

Booting...
WARN 80F9
Cannot find ENTRY_TEST.

Failed to initialize.

ENTRY_INIT
Status = -7 <-- note this status #

00800000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0000350B 00000012 C1000040 02800400 080900D8 00000000 0001F004 00000000
9E030000 0000E9CC 0000E9CC 00000000 FFFFFFFF 00000000 00000000 00000000
WARN 80F5
Failed to initialize.

Main Menu: Enter Command >

RESOLUTION

The majority of ENTRY_INIT errors encountered are: Status = -4 and
Status = -7.

ENTRY_INIT -4 Causes:
- the disk is experiencing hardware faults and needs replacing.
- the path to the disk is experiencing problems. e.g.. Termination,
cabling, SCSI adapter, SCSI adapter seating.
ENTRY_INIT -7 Causes:
- Booting from the wrong path or non-existent device.
- Trying to boot from a device that is not responding.



Troubleshooting Steps:
. Power off the server, then power off the disks - leave all powered
off for at least 30 seconds. Power on disks, then server.

. When server is booting, check access LED's on boot disk, is it being
accessed? Yes - possible bad disk. No - possible bad path to
disk, e.g.. Cabling/termination/adapter. Time to log hardware call.

. If boot disk is in an external disk enclosure, check the cabling is
secure, and access/status lights are normal.

. Attempt to boot from an alternate boot path if you have one,
e.g.. Mirror boot disk, alternate boot disk.

. Double check you have the correct boot path.

. Use the SEArch option at the Boot Menu, does the primary boot path
appear? If not, we cannot see the disk and time to log a hardware call.
If we can see the boot disk, but still get ENTRY_INIT error when booting
we need to log a hardware call.

. We can boot to Recovery Shell and use the chroot option to fsck the
boot disk, but this will always fail if we cannot get to the ISL
prompt of a disk; in most occurrences of this error using the Recovery
Shell (Support Media) is not helpful.

. Perform preliminary steps to reinstall the system; As in most cases this
error means the boot disk is bad and will need to be replaced. If the
system is not mirrored then the recommended recovery method is to
reinstall the system. Is the backup offsite? Do you know what sizes
the vg00 logical volumes are?