Something seems broken with iSCSI since 6.7.0

Still it looks like there's been some fragmentation over time. iSCSI doesn't work well when the volume gets this full.

Frankly speaking, if there has been fragmentation, Netgear has created it by using the data drive as a temporary drive for updates or such. The data drive basically contains ONE FILE (the iSCSI file).

So how do I fix this?

Have you tried replicating the problem?

What is your initiator?

I see a steady stream of messages about the initiator sending FUA requests, but the iSCSI target is configured to claim no support for FUA.  I assume your Sync Writes setting is set to Disabled?  Can you try changing it to Allowed?

Microsoft initiator (on Windows 7 64-bit).

Interestingly, with sync writes enabled, I can now mount the volume again. Thanks for that!

Doesn't solve the space free problem though :catsad: and that clearly happened when upgrading the firmware. Is it risk free in this situation to try rebalancing (from the UI)?

Your status.log shows your volume being over 95% full as far back as April 2016. It's not an issue caused by the upgrade.

Balancing shouldn't be attempted on a volume that full. That's not the solution. For optimal performance you should consider expanding your data volume (after updating your regular backup, of course).

Is there anything in particular this iSCSI volume is doing?  We tried to reproduce the issue, but only got a single FUA write request during mount time, and none after that.

> Your status.log shows your volume being over 95% full as far back as April 2016. It's not an issue caused by the upgrade.

Whatever. As stated before, the volume has been created using Netgear recommendations, and never used for anything but this iSCSI volume.

> Is there anything in particular this iSCSI volume is doing?

No, its only purpose is to host a TrueCrypt volume. Sync Writes has been off for performance reasons for a long time.