Jack Lin

It seems this issue has the same root cause described in this issue https://github.com/longhorn/longhorn/issues/4959 Engine failed to start because it `failed to unbind initiator target id 1` ``` 2024-08-01T01:20:22.391156796Z [e2e-test-volume-0-e-0]...

hmm, it seems the community is still hitting the issue: https://github.com/longhorn/longhorn/issues/6915

Thanks @PhanLe1010 for the great analysis I will take a look. @yangchiu Are we still running the test in our daily e2e test? If yes, can you help to keep...

When there is IO error, the volume might become Read-Only Currently the workaround is just to reattach the volume

Hi @siddjellali In some case, when the mount point becomes read-only and write-protected, Longhorn won't be able to remount the mount point to read-write. To resolve this issue, you may...

> Same problem here on 1.5.3. Node-Problem-Detector marks the node as tainted due to the readonlyfilesystem. The only way to fix is to reboot the node. > >  Hi...

Hi @siddjellali For the read-only volume, we have the remount mechanism to remount the mount point. However, there is a chance that the remount won't work due to the device...

Hi @derekbit the symptom is described [here](https://github.com/longhorn/longhorn/issues/8508#issuecomment-2136824649) and the [doc](https://longhorn.io/docs/1.7.2/high-availability/recover-volume/#automatic-volume-remounting) I am not sure how to detect if the device is current write-protected But it shows the error message when...