topic Re: MSA iSCSI volume Failed. in HPE Morpheus VM Essentials

MSA iSCSI volume Failed.

VBS2 — Tue, 07 Oct 2025 04:42:04 GMT

Hello,

I have build a 3 node VM Cluster. The cluster is fine. I try to add two iSCSI MSA volumes.

On each Host i can see the MSA volumes:

When i look at the multipathing, everything looks ok, on all the three nodes:

In the manager we see the storage devices on all the nodes:

We made two volumes, the 1st one is for the image library Store:

After that, the volume won't come online. I don't see any error messages:

Does anybody have an idea what goes wrong?.

Re: MSA iSCSI volume Failed.

Arnout_Verbeken — Mon, 06 Oct 2025 13:30:35 GMT

Strange.
I would remove them, open the logfile on the manager with

sudo tail -f -n 500 /var/log/morpheus/morpheus-ui/current

and add them again.
Check in the log file for possible clues.

Also, "Image Target" is NOT your "Virtual Image Store", but some sort of caching that is done for images before deploying them.
For "Virtual Image Store", you need to go to Infrastructre-Storage and add a bucket of File Share.

Re: MSA iSCSI volume Failed.

VBS2 — Mon, 06 Oct 2025 14:06:34 GMT

Hi Arnout.

Thanks for your reply. I found out two things. You need the same name in VM essentials as the name for the volume in the MSA.

So i am a step further. Looked in the log file. Now i get the following error:

It's starting the formatting (Thats one step further). But now i receive the I/O error

Re: MSA iSCSI volume Failed.

PeterTzvetanov — Sun, 23 Nov 2025 14:17:36 GMT

Hi VBS2,

if I see it currectly the storage is an MSA 1040? If yes, could you reduce on the ubuntu servers the MTU size of the iSCSI uplinks to MTU 8900 on all of them. Also do afterwards an "fdisk --wipe always /dev/mapper/the_uui_of_your_device" and try again. I have seen similar issues with the MSA 2040 iSCSI where the max MTU is 8900 and 9000 lead to "weird" results.

With regards

Re: MSA iSCSI volume Failed.

VBS2 — Fri, 28 Nov 2025 21:07:47 GMT

Hi Peter.

Thanks for your answer. We solved our problem. We had first exported the MSA Volume with Lun ID 0. After a lot of troubleshooting we found out that the MSA controller also use Lun 0 within the OS. So we had a conflict with that. After we exported the MSA volume with Lun ID 1, we could use the volume.

But thanks again for the tips for the MTU size.

Regards, Peter.

Re: MSA iSCSI volume Failed.

PeterTzvetanov — Sun, 30 Nov 2025 12:47:23 GMT

Hello VBS2,

glad to read that I was helpful, even if partially.

With regards