Phenomenon:

scheduled maintenance at a weekend XX business system, OS version redhat 6.x, unable to start. The following error is reported:

Kernel panic - not syncing:Attempted to kill init! Pid: 1, comm: init Not tainted ..

One thing to mention here is that some server staff think it is a storage problem, so they have to throw the pot and say this string0C74Bxxxx is it a fiber card WWN no., is there something wrong with your storage? This should have the judgment and quality of the storage professionals. Don't be blamed. At first glance, it is not, there are two main types of fiber card industry, one is qlogic, one is Emulex, known E card and Q card, anyone who has done storage O & M or implementation knows it, generally qlogic card and Emulex card wwn usually21XX start or10XX at the beginning, you must resolutely throw the pot in the first second. If you don't believe it, go to the data center and have a look. It may be used to connect the storage. HBA there is no card, this place can be installed13...

Solution:

still see the Echo: Kernel panic - not syncing:Attempted to kill init! Pid: 1, comm: init Not tainted ...

Isn't it obvious that the kernel has crashed?

At this time, the server administrator and the business are discussing whether to reinstall or not. This time, let's reinstall the storage service.13, don't worry, du Niang search to see if it is necessary to reinstall, to find.

GRUB in the guide interface, select the second item and press e key, enter the edit state, append at the end enforcing=0 press enter key return, press B press the key to start the system.

Select the second item and press e key to enter the edit state

Append**= 0, press enter to return, press B to continue to start the system.

Summary:

to do storage, you must have a wide range of knowledge. You must know a little about hosts, networks, storage, operating systems, databases, virtualization, and so on.

-- Stop work--