No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


IT S5600T(V1R1C01) the file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume F

Publication Date:  2016-06-08 Views:  117 Downloads:  0
Issue Description

Fault symptom: The disk mapped in the host can't be read and write, and show error: "disk is full" & "the file system structure on the disk is corrupt and unusable".

Host version:WindowsServer2008 x64

Product  version:V100R001C01
Software version:1200120406
ISM version:ISMV100R003C01SPC009

UltraPath version:5.01.070


Alarm Information

Windows alarm at first time:

windows alarm turns to:

Handling Process

1.1 Storage logs analysis

1.       Check the status of issued LUN of this host:

The LUN mapped to issued file system isLUNACME-Input-”,and this LUN belongs to RAIDSATA_7”,status is normal. And we also checked there is no Bad Sector Block in such RAID.

2.       RAID and disk status confirm

Member Disk List:


All disks status in such RAID are Normal.

3.       IO read/write status confirm

According to storage logs, there is no such IO error record

ConclusionAccording to above analysis, there is no storage error will directly cause such LUN file system corrupt, so we do analyze in host side.

1.2 Host logs analysis

1.       Check Windows event information, we found in 2/15/2016 13:52(UCT +04), the host file system already corrupt, as below shows:

This alarm shows the volume ACME input already corrupt and unusable, system show the alarm "ACME to run chkdsk utility to repair file system". As volume F still could be accessed, so customer didn’t repair such volume.

2.       Until 19th of February, whole volume F file system been damaged, now system notice: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume F:, as below shows:

As the file system of whole volume F had been damaged, so we can’t do any read/write operation to this disk, and even get capacity information, as below shows:


3.       And according to storage log analysis, there is no abnormal from storage could cause LUN data damaged, so the cause reason should be in host or link.

In storage log, we found the iSCSI link unstable, the link from host to storage frequently break down, as below shows


4.       Check the map relationship of issued LUN, the issued LUNACME-Input-mapped to host 0, as below shows:

This wwn of host 0 is: d

Check the host break down record as below

Controller A break down record

Controller B break down record

There is no abnormal alarm in storage logs when break down happen, should confirm the probable reason from host side.


5.       Except the issued LUN host, other hosts also happen such break down records:


6.       Check host system log event, we could find many initiator failed to target issues, as below shows:

The root cause of this break down should be confirmed by host side.

Root Cause
Conclusion:There is no storage abnormality, further need host side analysis the cause for the file system damaged and link break down issues.

  1. Suggest to check the host side parameter.
  2. exclude the link issue,
  3. repair the file system,

Note: file system repair may cause some files damaged.


1. Need stop operate issued disk when system report an error.

2. Need find the OS provider to check the OS system structure issue together