iSCSI volume on windows 11 getting corrupted

TrueNAS General
1

Hi,

I connect my Windows 11 machine to my NAS using an iSCSI connection. This setup works well most of the time, especially when using a large MTU size (9000). However, every once in a while, my Windows machine displays an error indicating that the volume is corrupted. I find myself needing to run the Chkdsk command every few weeks to restore read/write access.

I searched online for solutions but only found articles related to older versions of Windows, such as 2012 and 8.

Do you have any suggestions?

Itamar

2

By any chance are there more than one client that is configured to access this iSCSI target? Also hope the filesystem in use is NTFS (just clarifying)

3

Yes, but what I did was to ensure the permission model was to allow everyone full access to the volume.

4

Or at least that I thought I did… I refreshed these permission now. Was the problem?

5

Mounting an iSCSI volume on multiple clients at the same time is akin to an undefined situation and will corrupt data in short order.

Since it’s iSCSI each client assumes it’s the only one working with the volume and whenever anything needs to change, metadata for example, it assumes it is the only one modifying it. If this isn’t the case, and another client is changing things affecting the same metadata, chaos ensues.

There are ways to do multi-user iSCSI but that typically takes specialist software working as a gatekeeper/wrapper, actively preventing above mentioned corruption. This goes far beyond the iSCSI implementation included in TrueNAS and most other similar software.

Edit: I recommend rethinking your approach. Consider if SMB may be a better access method.

2 Likes
6

Thank you very much, I will switch to SMB

1 Like