- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: MSA 2050 iscsi not map volume
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago by support_s
3 weeks ago - last edited 3 weeks ago by support_s
MSA 2050 iscsi not map volume
Hi all, this is the problem of iscsi connections between the storage and the server, but there's no attached volume, Please tell me the correct way to grant access on the storage side, if you could elaborate on the instructions, thank you
supplement
storage MSA 2050 iscsi direct cable connection (previously everything worked before OS reinstallation) server on windows
- Tags:
- msa HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
3 weeks ago
Re: MSA 2050 iscsi not map volume
Hi,
in that case, you get a new iSCSI Initiator Name on the Server.
Check the Name in the iSCSI Settings on the Server and Edit, or add in the Host Setting on the MSA.
See here https://www.informaticar.net/how-to-configure-hpe-msa-2050/ under Hosts.
Cali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
3 weeks ago - last edited 3 weeks ago
Re: MSA 2050 iscsi not map volume
HI @Cali
It's more about the fact that I think all the settings are correct, exactly no volume that was created a long time ago, Now if you create a new volume and also give access to it, it will appear without problems in the disks on the server, with similar actions the old volume does not appear for some reason,
maybe there are some HPE engineers here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
3 weeks ago
Re: MSA 2050 iscsi not map volume
Can you post Screenshots of the Host Settings and Volume Presentation from the MSA and the iSCSI Initiator Setting of your Host?
(You can use the Camera Symbol above.)
Otherwise, we are groping in the dark.
Cali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
3 weeks ago - last edited 3 weeks ago
Re: MSA 2050 iscsi not map volume
update, @Cali
managed to get a normal connection
only the volume is now in this state (50Tb which), how can I fix it without losing data?
as I remember there should be a file system there REFS