Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2003016.1
Update Date:2015-04-27
Keywords:

Solution Type  Problem Resolution Sure

Solution  2003016.1 :   OS Bootup on Exadata hangs after GRUB screen, but GUI hostconsole does not show error or accept entry  


Related Items
  • Exadata X3-2 Hardware
  •  
  • Exadata X4-2 Hardware
  •  
  • Exadata X5-2 Hardware
  •  
  • Exadata Database Machine X2-2 Hardware
  •  
  • Oracle Exadata Storage Server Software
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
  •  




Created from <SR 3-10600842621>

Applies to:

Exadata X3-2 Hardware - Version All Versions and later
Exadata X4-2 Hardware - Version All Versions and later
Exadata Database Machine X2-2 Hardware - Version All Versions and later
Exadata X5-2 Hardware - Version All Versions and later
Oracle Exadata Storage Server Software - Version 11.2.3.2.2 to 12.1.2.1.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

OS Bootup on Exadata hangs after GRUB screen, but GUI hostconsole does not show error or accept keyboard entry.

This hang occurs on bootup between grub image selection and OS available for login. 

 

Changes

The system shutdown either on command or node crash and reboot.

Cause

The GUI / JAVA console lags behind (~5-15 lines) behind the text terminal during this time.  Once the OS is available for login, either console is correct and showing the same information.

Unfortunately this causes the GUI console to not display the failing issue or allow you to input prompted info.

In this example the boot was stopping on fsck and required the user to login as root - which was not seen in the GUI console:

EXT4-fs (dm-0): 31 orphan inodes deleted
EXT4-fs (dm-0): recovery complete
EXT4-fs (dm-0): mounted file system with ordered data mode.  Opts (null)
dracut: Mounted root filesystem /dev/mapper/VGExaDb-LVDbSys1
dracut: Loading SELinux policy
dracut: SELinux: Could not open policy file <= /etc/selinux/targeted/policy.26: No such file or directory
dracut: Switching root

 

From SSH Text Console the user was able to see the prompt for login:

EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)

dracut: Mounted root filesystem /dev/mapper/VGExaDb-LVDbSys1

dracut: Loading SELinux policy

dracut: SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.26: No such file or directory

dracut: Switching root

Welcome to Oracle Linux Server

Starting udev: [  OK  ]

Setting hostname ExaMyDB01.mycompany.com:  [  OK  ]

Setting up Logical Volume Management:   4 logical volume(s) in volume group "VGExaDb" now active

[  OK  ]

Checking filesystems

Checking all file systems.

[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/mapper/VGExaDb-LVDbSys1

DBSYS: clean, 123955/1966080 files, 5973973/7864320 blocks

[/sbin/fsck.ext4 (1) -- /boot] fsck.ext4 -a /dev/sda1

BOOT: clean, 38/32768 files, 11984/131072 blocks

[/sbin/fsck.ext4 (1) -- /u01] fsck.ext4 -a /dev/mapper/VGExaDb-LVDbOra1

DBORA: clean, 93992/6553600 files, 6481778/26214400 blocks

[/sbin/fsck.acfs (1) -- /u02/asmfs] fsck.acfs -a /dev/asm/asmvlacfs-999

/sbin/fsck.acfs.bin: error whileGive root password for maintenance

 

Solution

Start the console from an SSH terminal - for example:    ssh root@ExaMyDB01-ILOM

Login to ILOM via SSH windows as root:

Sun(TM) Integrated Lights Out Manager

Version 2.0.2.5
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
->

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

 

This will allow you to see the actual message causing issues and login as needed.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback