QNAP NAS Community Forum

Hi

On a previously working target, we had an issue where the mounted volume went read-only, then when trying to after umount and iscsi logout, we get errors. The client reports and dmesg on the QNAP reports the target .

No other connection is present. After a reboot and update, the web UI shows "Error" for the LUN (File based Thick) and there are errors referencing the target in iscsi_util.log:
Is the data (historic backup sets) recoverable? Is there a known cause or could it just happen to other volumes?

You sure just this host had/has the only connection?

Delete the target, create a new one and try again.
I doubt the data is lost.

The QNAP has a number of volumes with different servers making use of different volumes. Only this particular backup was making use of this target, along with some other targets (volume per backup job). Is there no way to "backup the backup" before we go down the destructive route? The bit that makes me nervous is the error about accessing the file (along with the lack of info about the error in the UI, that the UI didn't show any error for the LUN before the update...), although I've only just started to get my head around how the QNAP is providing storage via iscsi.

Did you try suggested?
I'm assuming you know two or more hosts should never connect to the same LUN unless in a cluster(Hyper-V/ESXI).
Disconnect the LUNs before you do any firmware update. Qnap updates often break ISCSI connections.