Hello, everyone!
This is a case about failure to install OceanStor 5500 V3 hot patch.
Symptoms
When a hot patch fails to be installed on an OceanStor 5500 V3 storage device using SmartKit, the following information is displayed:
0A--Installing the hot patch--Installing the hot patch success |
Cause
The system disk of controller B is abnormal.
The /OSM/coffer_data directory in the file system is read-only.
The rule file /OSM/coffer_data/ioc_firmware.tar.gz fails to be created during user-mode patch loading,
thus the hot patch fails to be installed.
Analysis
1. Collect storage logs, open the (DataCollect\System_log\log_controller_0B\Messages\message_xxx) file of controller B where the patch fails to be installed.
Search for load kernel hotpatch and load usr hotpatch.
The failure cause is that the rule file /OSM/coffer_data/ioc_firmware.tar.gz fails to be created because the file system is read-only during user-mode patch loading.
[2019-09-09 07:12][30648665.154175] cp: cannot create regular file `/OSM/coffer_data/ioc_firmware.tar.gz': Read-only file system [2019-09-09 07:12][30648665.157148] copy /startup_disk/image/boot/hotpatch/patch_temp/ioc_firmware_SPH216_DTS2019021100791.tar.gz to /OSM/coffer_data/ioc_firmware.tar.gz failed [2019-09-09 07:12][30648665.160195] End to load usr hotpatch: ioc_firmware_SPH216_DTS2019021100791.tar.gz /OSM/coffer_data/ioc_firmware.tar.gz 0 coldpatch new, result is 2 [2019-09-09 07:12][30648665.163281] load hotpatch failed[version:SPH216, file:ioc_firmware_SPH216_DTS2019021100791.tar.gz]. |
2. Log in to controller B using the CLI.
Run the mount command in the minisystem view to check the file system status.
The /OSM/coffer_data directory in the file system of controller B is (ro)read-only.
Solution
Replace the faulty controller.
Before installing the hot patch, check the system disk status using SmartKit.
Install the hot patch.
This is my solution, how about yours? Go ahead and share it with us!
