- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: linux sudden misbehaviour with MSA2000 fc
HPE EVA Storage
1752729
Members
5812
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-09-2010 06:30 AM
тАО06-09-2010 06:30 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2010 07:18 AM
тАО06-09-2010 07:18 AM
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).
It sounds like you have created vdisk(s) and volumes, but did not present the volumes to the host(s).
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2010 11:44 PM
тАО06-11-2010 11:44 PM
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!
I remember, Hosts HBA card can detect MSA2000 device! and MSA2000 can see the hosts! but devices are not created successfully!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2010 02:44 AM
тАО06-13-2010 02:44 AM
Re: linux sudden misbehaviour with MSA2000 fc
Thanks! I performed mapping and the problem is solved now!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP