550 crazy 8's after LED 517

[Breslau]

Anyone seen this happen before? i can boot this host into maintenance and import rootvg fine. but a normal boot causes it to halt after displaying 517.

the host was shutdown normally and then later started, no OS or Mcode updates.

any suggestions where to look?

TIA!

 

[p5wizard]

517 is corrupt inittab if I'm not mistaken. Check it out when you have accessed rootvg from maintenance mode.


HTH,

p5wizard

 

[mrn]

LED 517 during a Normal mode boot, it is possible the /etc/filesystems file is corrupt or missing. To temporarily replace the disk-based /etc/filesystems file, run the following commands:

mount /dev/hd4 /mnt
mv /mnt/etc/filesystems /mnt/etc/filesystems.[MMDDYY]
cp /etc/filesystems /mnt/etc/filesystems
umount /mnt

MMDDYY represents the current two-digit representation of the Month, Day and Year, respectively.

Type exit to exit from the shell. The file systems should automatically mount after you type exit. If you receive error messages, reboot into a limited function maintenance shell again to attempt to address the failure causes.


If you have user-created file systems in the rootvg volume group, run fsck on them now. Enter:

fsck /dev/[LVname]

LVname is the name of your user-defined logical volume.



If you used the preceding procedure to temporarily replace the /etc/filesystems file, and you have user-created file systems in the rootvg volume group, you must also run the following command:

imfs -l /dev/[LVname]


If you have file systems in a volume group other than rootvg, run fsck on them now. Enter:

varyonvg [VGname]
fsck /dev/[LVname]

VGname is the name of your user-defined volume group.



If you used the preceding procedure to temporarily replace the /etc/filesystems file, also run the following command:

imfs [VGname]
The preceding commands can be repeated for each user-defined volume group on the system.



If your system was hanging at LED 517 or 518 and you are unable to activate non-rootvg volume groups in Service mode, you can manually edit the /etc/filesystems file and add the appropriate entries.
The file /etc/filesystems.MMDDYY saved in the preceding steps may be used as a reference if it is readable. However, the imfs method is preferred since it uses information stored in the logical volume control block to re-populate the /etc/filesystems file.



If your system has a mode select key, turn it to the Normal position.


Reboot the system into Normal mode using the following command:

sync;sync;sync;reboot

If you followed all of the preceding steps and the system still stops at an LED 517 you may want to consider reinstalling your system from a recent backup.

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."