HPE EVA Storage
1752729 Members
5812 Online
108789 Solutions
New Discussion юеВ

Re: linux sudden misbehaviour with MSA2000 fc

 
Nima Gh.
Regular Advisor

linux sudden misbehaviour with MSA2000 fc

The device was working well and windows was detecting the luns asd /dev/sdX devices, but when I removed all (unformatted) vdisks and recreated another vdisks and volumes, linux fails detecting the devices and shows them as non-block sgX devices! What is wrong with that?
3 REPLIES 3
Uwe Zessin
Honored Contributor

Re: linux sudden misbehaviour with MSA2000 fc

"sg" devices represent so-called "controller LUNs". Those are special SCSI communication LUNs which do not provide storage. I'm pretty sure Linux has seen them before, because the MSA presents a controller device at LUN address #0 on each controller host port.

It sounds like you have created vdisk(s) and volumes, but did not present the volumes to the host(s).
.
Nima Gh.
Regular Advisor

Re: linux sudden misbehaviour with MSA2000 fc

Thanks for your reply! Do I need to do some extra work? How should I Present the Volumes to hosts? I thought that identifying hosts by MSA2000 is enough!
I remember, Hosts HBA card can detect MSA2000 device! and MSA2000 can see the hosts! but devices are not created successfully!
Nima Gh.
Regular Advisor

Re: linux sudden misbehaviour with MSA2000 fc

Thanks! I performed mapping and the problem is solved now!