Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-12762930881>

Applies to:

Symptoms

The FS1 is not restarting properly after manually restarting it or proceed with a Non Disruptive Upgrade.

Changes

Cause

The problem may be due to hardware interrupts being sent to the Pilot's serial port.
 

Solution

In /boot/grub/grub.conf of both Pilots, "console=ttyS0,9600n8" had been added in kernel parameter line. This change makes Linux kernel print debug messages to its serial port connecting to buddy Pilot. This in turn causes lots of hardware interrupts to delay or hang buddy Pilot boot-up process.  In order resolve this issue, it is necessary to be able to get a clean boot of the Pilots:

1. Remove both of the power cords from both of the Controllers.
2. Remove both of the power cords from both of the Pilots.
3. Reconnect both power cords to Pilot 1 (lower Pilot).
4. Wait for and confirm that Pilot 1 has successfully booted (responds to ping).
5. Reconnect both power cords to Pilot 2 (upper Pilot).
6. Wait for and confirm Pilot 2 has successfully booted (responds to ping).
7. ssh to the active Pilot (Pilot 1), reference Document <Document 2029847.1> FS System: How to Enable SSH Access to the Pilot and <Document 2046703.1> FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System.
   
8. Check the contents of grub.conf:
   
   [root@pilot1 ~]# cd /boot/grub
   [root@pilot1 grub]# grep console grub.conf
   kernel /vmlinuz-3.8.13-68.1.2.el6uek.x86_64 ro root=UUID=d4222f92-885f-4f87-9fc3-69e61bdcf646 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 KEYTABLE=us nodmraid rd_NO_MD crashkernel=auto console=ttyS0,9600n8 SYSFONT=latarcyrheb-sun16 rd_NO_DM console=tty0 hda=noprobe hda=none rhgb quiet nomodeset
   kernel /vmlinuz-2.6.32-504.el6.x86_64 ro root=UUID=d4222f92-885f-4f87-9fc3-69e61bdcf646 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 KEYTABLE=us nodmraid rd_NO_MD crashkernel=auto console=ttyS0,9600n8 SYSFONT=latarcyrheb-sun16 rd_NO_DM console=tty0 hda=noprobe hda=none rhgb quiet nomodeset
    
9. Make a copy of this file:
   
   [root@pilot1 grub]# cp grub.conf grub.conf.orig
    
10. Use vi (or similar editor) to remove the "console=ttyS0,9600n8" fields from the grub.conf file and confirm with the same grep command above:
    
    [root@pilot1 grub]# grep console grub.conf
    kernel /vmlinuz-3.8.13-68.1.2.el6uek.x86_64 ro root=UUID=d4222f92-885f-4f87-9fc3-69e61bdcf646 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 KEYTABLE=us nodmraid rd_NO_MD crashkernel=auto SYSFONT=latarcyrheb-sun16 rd_NO_DM console=tty0 hda=noprobe hda=none rhgb quiet nomodeset
    kernel /vmlinuz-2.6.32-504.el6.x86_64 ro root=UUID=d4222f92-885f-4f87-9fc3-69e61bdcf646 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 KEYTABLE=us nodmraid rd_NO_MD crashkernel=auto SYSFONT=latarcyrheb-sun16 rd_NO_DM console=tty0 hda=noprobe hda=none rhgb quiet nomodeset
     
    
    NOTE: Do NOT, under any circumstances copy the grub.conf file between Pilots.
     
    
11. ssh to Pilot 2 and repeat steps 8-10.
12. Reconnect both power cords to both Controllers.

References

This solution has no attachment