In the outcome of the preventive maintenance inspection of S2600 with the version of R5, there is the information about the FLASH card inspection isn’t passed. And click the “view”:
It’s a bug of the preventive maintenance inspection, and in fact, the FLASH card is normal, we can consider it as a false software reporting, and don’t need to settle it.
This problem is caused by a bug of the preventive maintenance inspection, it reports the error “ls: /disk_data：No such file or directory” means it hasn’t find the FLASH card’s directory “disk_data”, and the software considers the FLASH card has broken down.
For the S2600 with the version of R1, the catalog save the FLASH card is “disk_data”; but for the S2600 with the version of R2 or R5, there isn’t the “disk_data” catalog, and the catalog save the FLASH card is “startup_disk”.
We can enter in to the CLI to view the FLASH card’s catalog:
Firstly, we must confirm whether the abnormal controller has the FLASH card, enter in to the “degbug” of the corresponding controller and execute “fdisk -l”, and check if the space of the “sda” is between 2G to 4G, if it is, then it illustrates the controller has FLASH card.
Once there is confirmed to have a FLASH card, view the FLASH card’s catalog as the following method.
1. For the R1 version: in the debug mode, execute the command “ls/disk_data”, and generally there will display the following information:
ISM、boot_osp、boot_rescue、grub、test、boot_osp_bak、config、lost found、update catalog, os_boot.conf、boot file.
2. For the R2 & R5 version: in the debug mode, execute the command “ls /startup_disk/image”, and normally there will display the following information:
ISM、boot_osp、boot_osp_bak、boot_rescue、grub、lost found、update catalog and the boot file.
If there isn’t any response after enter the command for a long time or parts of the catalogs or files have lost, it denotes the FLASH card may have some problem.