Uploaded image for project: 'TrueNAS'
  1. TrueNAS
  2. NAS-108559

iSCSI corruption with Windows 10

    XMLWordPrintable

    Details

    • Impact:
      High

      Description

      iSCSI mount on Windows 10 become corrupted when accessed. Tried the following combinations with the same result:

      • zVol device and file extents
      • ZFS sync always, standard, and disabled
      • CHAP authentication, no CHAP authentication
      • All logical block sizes
      • Disable and enable physical block size reporting
      • TCP enable and disable
      • Xen compat mode on and off
      • All RPM settings

      Initializing the disk as GPT immediately puts the disk in protected mode.

      Initializing the disk as MBR then formatting as NTFS shows errors.

      Chkdsk Event Viewer output:

      Log Name:      Application
      Source:        Chkdsk
      Date:          12/6/2020 7:27:12 PM
      Event ID:      26214
      Task Category: None
      Level:         Information
      Keywords:      Classic
      User:          N/A
      Computer:      WORKSTATION
      Description:
      Chkdsk was executed in read/write mode.  
      
      Checking file system on R:
      The type of the file system is NTFS.
      Volume label is New Volume.
      
      Stage 1: Examining basic file system structure ...
        256 file records processed.                                                        
      
      File verification completed.
       Phase duration (File record verification): 4.17 milliseconds.
      Deleting orphan file record segment C.
      Deleting orphan file record segment 7E.
      Deleting orphan file record segment 89.
      Deleting orphan file record segment B1.
        5 large file records processed.                                   
      
      Deleting orphan file record segment B2.
       Phase duration (Orphan file record recovery): 0.00 milliseconds.
        0 bad file records processed.                                     
      
       Phase duration (Bad file record checking): 0.79 milliseconds.
      
      Stage 2: Examining file name linkage ...
      The data written out is different from what is being read back
      at offset 0xc0001000 for 0x3000 bytes.
      An unspecified error occurred (6672732e637878 969).
      An unspecified error occurred (6e74667363686b2e 1798).
      
      Event Xml:
      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        <System>
          <Provider Name="Chkdsk" />
          <EventID Qualifiers="0">26214</EventID>
          <Version>0</Version>
          <Level>4</Level>
          <Task>0</Task>
          <Opcode>0</Opcode>
          <Keywords>0x80000000000000</Keywords>
          <TimeCreated SystemTime="2020-12-07T00:27:12.6202733Z" />
          <EventRecordID>10516</EventRecordID>
          <Correlation />
          <Execution ProcessID="0" ThreadID="0" />
          <Channel>Application</Channel>
          <Computer>WORKSTATION</Computer>
          <Security />
        </System>
        <EventData>
          <Data>
      
      Checking file system on R:
      The type of the file system is NTFS.
      Volume label is New Volume.
      
      Stage 1: Examining basic file system structure ...
        256 file records processed.                                                        
      
      File verification completed.
       Phase duration (File record verification): 4.17 milliseconds.
      Deleting orphan file record segment C.
      Deleting orphan file record segment 7E.
      Deleting orphan file record segment 89.
      Deleting orphan file record segment B1.
        5 large file records processed.                                   
      
      Deleting orphan file record segment B2.
       Phase duration (Orphan file record recovery): 0.00 milliseconds.
        0 bad file records processed.                                     
      
       Phase duration (Bad file record checking): 0.79 milliseconds.
      
      Stage 2: Examining file name linkage ...
      The data written out is different from what is being read back
      at offset 0xc0001000 for 0x3000 bytes.
      An unspecified error occurred (6672732e637878 969).
      An unspecified error occurred (6e74667363686b2e 1798).
      </Data>
          <Binary>0001000007000000070000000000000000000000000000000000000000000000</Binary>
        </EventData>
      </Event>

      Copying a file to the MBR partition disk then running a SHA-512 checksum shows the files do not match, the file on the iSCSI volume is corrupt.

      Same iSCSI server hardware running FreeBSD 12.2-RELEASE, ZFS pool, ctl, etc. works with no issues.

        Attachments

          Attachments

            JEditor

              Issue Links

                Activity

                  People

                  Assignee:
                  releng Triage Team
                  Reporter:
                  djflow1951 DJ Flow
                  Votes:
                  1 Vote for this issue
                  Watchers:
                  11 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved: