After Fujitsu RX300 S7 is installed with oracle 10 Gb, the system cannot be started.

After Fujitsu RX300 S7 is installed with oracle 10 Gb, the system cannot be started to solve the problem of so many oracle installations, and this has never occurred, which means it hurts. My installation environment is as follows: hardware environment: Fujitsu RX300 S7 OS: RHEL 6.2 oracle version: oracle 10g according to the previous normal installation order, but oracle can be installed successfully. However, after the installation, the system cannot be started. You cannot enter the single-user mode. Oracle has been installed many times. Except for the first installation on 6.2 of RX300 S7, there is no difference between the installation and installation. In addition, many people have installed on 6.2 on the internet, and I have installed it on 6.2 on a common pc. There is no clue. The system is reinstalled five times in the back and forth, and it is determined that it has nothing to do with the oracle software, so it can only be related to the preparation before installing oracle. Preparations: 1. Modify the/etc/redhat-release file 2. Install the dependency package 3. set parameters (including creating a new oralce user ). During the last installation process, I was really careful. I had an eye-catching problem, but fortunately there was no problem that could not be started: in the preparation process, 1. first, only the following parameters are set: ---> restart, OK. 2. Install the dependency package ---> during installation, I restarted every time a dependency package is installed, and it went smoothly. OK. It's strange. Is it/etc/redhat-release modification. We all know that to install oracle 10 Gb, you need to change/etc/redhat-release to Red Hat Enterprise Linux Server Release 5.4 (Tikanga ). 3. after I have modified/etc/redhat-release, I will install oracle, change/etc/redhat-release back (Red Hat Enterprise Linux Server release 6.2 (Santiago), restart, and OK. The system cannot be started because of the/etc/redhat-release modification. I Googled and found only one person asking questions on itpub. No one answered the question. It is really rare. I don't have time to verify the reason. Sort it out first and remind everyone: it is best to change it back after/etc/redhat-release is modified. PS: * I have verified that the redhat-release can be started normally even if it is not changed back when it is installed on a common PC. So I guess it is related to the server itself. * If the machine is restarted quickly, when the system fails to start, use the CD to enter the rescue mode to check whether/etc/redhat-release can be modified.