Synology lost power supply, had to move drives to a new Synology NAS. Had to scan the Synology for corruption. When the drives finished scan, can't mount the iSCSI target storage.
Customer called, they are having an issue after a Synology DS1515+ system had a power failure.
The customer moved the drives to the new Synology NAS.
Once they did this they powered up and had to check consistency.
The consistency scan ran for 5 or 6 hours. From there when that ended, we could see the iSCSI information on the Synology.
We went into the ESXi console, Tried adding a storage adapter and connection that would target the NAS and see the datastores.
When we add the host name of the iSCSI target, we don't see anything populate. But if we go in and add the IP address of the Synology in question under the Dynamic Discovery, we see 3 disks come up under static. It shows the .25 IP address and an IPv6 address for each of the LUNS. But even with the LUNS showing up in the discovery area, we still can't target the storage and see it under the Storage Adapter as noted in the image attached. How can I get the Synology NAS to show the iSCSI Target so the system will boot again?
2019-01-10_22h46_09.png
2019-01-11_01h07_13.png
The customer moved the drives to the new Synology NAS.
Once they did this they powered up and had to check consistency.
The consistency scan ran for 5 or 6 hours. From there when that ended, we could see the iSCSI information on the Synology.
We went into the ESXi console, Tried adding a storage adapter and connection that would target the NAS and see the datastores.
When we add the host name of the iSCSI target, we don't see anything populate. But if we go in and add the IP address of the Synology in question under the Dynamic Discovery, we see 3 disks come up under static. It shows the .25 IP address and an IPv6 address for each of the LUNS. But even with the LUNS showing up in the discovery area, we still can't target the storage and see it under the Storage Adapter as noted in the image attached. How can I get the Synology NAS to show the iSCSI Target so the system will boot again?
2019-01-10_22h46_09.png
2019-01-11_01h07_13.png
This can be far more tricky than you might imagine.
Moving raw disks between two different versions of Synology may or may not be supported.
This is a function of both types of hardware.
Before doing anything else, contact Synology first + ask if moving raw disks between two enclosures you have is support + will result in a RAID array forming again correctly.
Ask this first before you do anything else.
Also be sure to explain to Synology what's been done so far, as the process you've described may potentially loose all your data.
Moving raw disks between two different versions of Synology may or may not be supported.
This is a function of both types of hardware.
Before doing anything else, contact Synology first + ask if moving raw disks between two enclosures you have is support + will result in a RAID array forming again correctly.
Ask this first before you do anything else.
Also be sure to explain to Synology what's been done so far, as the process you've described may potentially loose all your data.
ASKER
The issues appear to be related to the CHAP function of the iSCSI LUN. The encryption was a partial cause of the issue. We had set the CHAP username and password because the other LUNs on other instances had it set. We put the same thing in place. The difference with these three LUNS were that they did not use CHAP encryption. When the engineer removed the LUNS and the dynamic and static entries from the VMWare ESXi console, and rebooted and rescanned for things this time they showed up under the storage adapters area of the ESXi console.
Note to self: When working with iSCSI first try leaving the CHAP function off.
Everything is good to go now. If I find ay other things that were done I will update this with those.
Thank you everyone for your insight.
Note to self: When working with iSCSI first try leaving the CHAP function off.
Everything is good to go now. If I find ay other things that were done I will update this with those.
Thank you everyone for your insight.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Perhaps you should remove the iSCSI targets (careful, do not remove the LUNs!) and create new targets for the LUNs. In ESX also remove any traces of the old targets and add the new targets.