NEC Express5800/320Fc Manual download pdf (Page 147)

System Boot Problems

Troubleshooting ftServer Systems 9-3

NOTE

If a RAID array fails to start, the boot stops and enters a

debug shell. This is almost always because of a

configuration error in /etc/fstab or

/etc/mdadm.conf. Exiting the shell forces a reboot.

Depending on your system’s RAID configuration, you may see one or more error

messages similar to the following:

md: could not bd_claim sdar1

md: error, md_import_device() returned -16

These messages indicate that md is refusing to start an array that has already been

started. You can safely ignore them.

The recommended configuration has all RAID-1 arrays marked as type 0xfd (Linux

RAID autodetect) so they start early, and all RAID-0 arrays in /etc/mdadm.conf,

so they start later.

•

The operating system checks the file systems.

NOTE

In the case of crash recovery, the file check (fsck) may

take a long time, and it may fail. If it fails, the boot stops

and enters a debug shell. The administrator must

manually repair the problem file systems. Exiting the shell

forces a reboot.

Possible Boot Problems

A problem in booting the system may be associated with missing or corrupt

fault-tolerant drivers, the GRUB boot loader, or RAID.

Missing Drivers Prevent Booting

If required fault-tolerant drivers are not present at boot time, and if the system’s

fault-tolerant policy is set to prevent booting when drivers are missing (the default

setting), the following prompt appears at the console:

This system is not fault tolerant because

reason

Type "NON-FT-BOOT" to allow login for repair:

1 2 ... 142 143 144 145 146 147 148 149 150 151 152 ... 155 156

No comments

NEC Express5800/320Fc Manual Page 147