- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- StoreEasy Storage
- >
- X1600 12TB NAS - Automated Storage Manager Error
StoreEasy Storage
1753611
Members
5791
Online
108797
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
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
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
10-15-2009 01:20 PM
10-15-2009 01:20 PM
X1600 12TB NAS - Automated Storage Manager Error
Running on Windows 2008 Standard x64 Storage Server
I successfully provisioned two shared folders of 2TB a piece using the Automated Storage Manager. The Storage Utilization view correctly shows 7+ TB still available for allocation, but my attempts to create a third shared folder all result in the following error:
Could not find new uninitialized disk that matches LUN.
Viewing the LUN Management via the Server Manager Storage section shows a newly created LUN of the correct size, but shows it as "Not Ready".
In addition, when I look at the ACU, it shows the Logical Drives associated with my two successfully creating volumes in a "Transforming" and "Queued for Transformation" state.
I'm wondering if I am limited somehow in the operations I can perform against the arrays/disks while these logical drives are in this state.
No OS Storage Utility gives me any indication that these logical drives were not 100% ready. I have to view the ACU in order to see this "transformation" process.
So I'm wondering if the process is erroring out in the ASM simply because the ACU cannot queue another operation or because the OS is presenting the disks as unitialized since there are operations pending...or if the error is unrelated...and if so, why I cannot continue to create new shares/volumes.
Any opinions are appreciated...Thanks...
I successfully provisioned two shared folders of 2TB a piece using the Automated Storage Manager. The Storage Utilization view correctly shows 7+ TB still available for allocation, but my attempts to create a third shared folder all result in the following error:
Could not find new uninitialized disk that matches LUN.
Viewing the LUN Management via the Server Manager Storage section shows a newly created LUN of the correct size, but shows it as "Not Ready".
In addition, when I look at the ACU, it shows the Logical Drives associated with my two successfully creating volumes in a "Transforming" and "Queued for Transformation" state.
I'm wondering if I am limited somehow in the operations I can perform against the arrays/disks while these logical drives are in this state.
No OS Storage Utility gives me any indication that these logical drives were not 100% ready. I have to view the ACU in order to see this "transformation" process.
So I'm wondering if the process is erroring out in the ASM simply because the ACU cannot queue another operation or because the OS is presenting the disks as unitialized since there are operations pending...or if the error is unrelated...and if so, why I cannot continue to create new shares/volumes.
Any opinions are appreciated...Thanks...
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