illisis Posted June 1, 2016 Share #1 Posted June 1, 2016 Hi, I am unable to list my ISCSI LUN in disk manager after a hard drive failure. I have replaced the failed drive and the volume that the LUN is on and the volume now reports as normal except the LUN is not available to the 2012 R2 server or my windows 10 workstation. I have tried rebooting the Synology and the 2012 server with no luck. Also I tried to create a new LUN and that also says it is unavailable. The target state is connected. Pictures: http://imgur.com/6bKh7iA http://imgur.com/jwGL3hy Any help is appreciated. thanks Link to comment Share on other sites More sharing options...
illisis Posted June 2, 2016 Author Share #2 Posted June 2, 2016 Fixed with ssh to nas as root mv /var/db/iscsi/EP_JNL /var/db/iscsi/EP_JNL.bak Link to comment Share on other sites More sharing options...
cosooner Posted May 3, 2017 Share #3 Posted May 3, 2017 This unlocked my LUNs after a DSM 6.1.1 update today. I was sweating the data with very old backups. Big thanks! Link to comment Share on other sites More sharing options...
b0fh Posted May 3, 2017 Share #4 Posted May 3, 2017 FWIW, I had a LUN do that, and that fix worked temporarily, but every reboot it would become unavailable again. It was a file-based LUN, so I ended up copying the data and deleting the LUN in order to address it. I've not used file-based LUN since, but I am not sure it was the culprit. I will try again sometime, but for now NFS is working out ok. Link to comment Share on other sites More sharing options...
Recommended Posts