OceanStor 5600T V1 After the customer upgrade the host's Linux OS, the boot loading is hung up with UltraPath tips

发布时间:  2015-12-15 浏览次数:  243 下载次数:  1

After upgrading the Linux OS version from 6.1 to 6.3, the UltraPath indicates that there are some devices that are not managed by UltraPath during the boot loading, which causes the boot loading hung.


The error tips, as follows:


System kernel upgrade will initialize some key kernel files, it results in UltraPath matching problem as this issue. To slove this issue as following:

Step 1, login OS and uninstall UltraPath thoroughly.

Step 2, reboot the system , after the system resume to re-install UltraPath again.


OS loading is roughly divided into 10 steps, as following:

l  The No.1 Loading step --- load BIOS

l  The No.2 Loading step --- read MBR

l  The No.3 Loading step --- Boot Loader / grup

l  The No.4 Loading step --- load system kernel

l  The No.5 Loading step --- user-layer init, which sets the running level based on the inittab file

l  The No.6 Loading step --- init process executes rc.sysinit

rc.sysinit is the first script of user-layer implemented by the Linux OS, in which UltraPath does disk letter recognition.

l  The No.7 Loading step --- start the kernel module

l  The No.8 Loading step --- execute the scripts with different running level (/etc/rc.d/rc $RUNLEVEL)

UltraPath loads nxup service in this step.

l  The No.9 Loading step --- execute /etc/rc.d/rc.local

l  The No.10 Loading step --- execute the program /bin/login, enter the login mode


UltraPath program loading is divided into 2 stages: The stage 1, which implements in the No.6 Loading step; The stage 2, which implements in the No.8 Loading step.

During the process of UltraPath installation, UltraPath will put the information related with loading into the file rc.sysinit. When running the No.6 Loading step, UltraPath can start and take over the disk letter. After the Linux system kernel upgrade, it will rewrite the rc.sysinit back to the initial state, so in this step UltraPath cant take over the SDX drive normally.

When implementing the No.8 Loading step, UltraPath goes into the stage 2 for loading nxup service. UltraPath finds that rc.sysinit configuration is not correct, which cant correctly manage the disk. Then if UltraPath needs to take over the disk letter SDX, firstly it needs to remove disk device and re-identify the disk letter by UltraPath. After that, UltraPath can take over the disk (in normal situation, this should be completed at the No.6 Loading step). Due to the system service may have used the disk letter SDX, if UltraPath automatically removes disk device, it may cause system service abnormal. So there is the pop-up dialog box which prompts whether remove drive device and take over by UltraPath.

In the case of that the operating system has installed UltraPath, to upgrade the operating system kernel:

Step 1: to uninstall UltraPath in the correct way before upgrading the kernel;

Step 2: to upgrade the kernel;

Step 3: to install the new UltraPath version after the OS upgrade completed;


UltraPath installation will modify some kernel startup items and kernel files related to make UltraPath manage disk letter correctly. Yet system kernel upgrade will initialize some key kernel files, resulting in UltraPath matching problem. When facing with similar upgrade operation case (including application software), with security-related concerns, suggest to uninstall UltraPath firstly, and re-install UltraPath until the upgrade completed.