- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- URGENT! NSM-160 volume offline with Unrecoverable...
StoreVirtual Storage
1819857
Members
3118
Online
109607
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
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
09-20-2009 06:05 AM
09-20-2009 06:05 AM
URGENT! NSM-160 volume offline with Unrecoverable I/O
I'm seriously hoping someone can help me with this.
We have an NSM-160 that was acting as our interim "backup" SAN while we were provisioning a new NSM-2120. It was running fine for several weeks until yesterday when the following occured:
scsi0: PCI Parity Error
scsi0: Unrecoverable I/O
Since then, SAN/iQ has brought the Volume down with a status of "Unrecoverable I/O" and nothing we do will bring it back up. The storage node itself says "not ready" so I can't even repair it in the CMC.
We've got ~500GB of very sensitive data stored on that volume. The volume was used by two VMware vSphere servers and contains a VMFS filesystem.
Is there any tool, utility, or process to bring the volume back online so I can extract the contents?
Can dbd_store be invoked in such a way that "forces" the volume back online, even in read-only mode so I can recover our data?
PLEASE HELP!
Thank you everyone.
Paul
We have an NSM-160 that was acting as our interim "backup" SAN while we were provisioning a new NSM-2120. It was running fine for several weeks until yesterday when the following occured:
scsi0: PCI Parity Error
scsi0:
Since then, SAN/iQ has brought the Volume down with a status of "Unrecoverable I/O" and nothing we do will bring it back up. The storage node itself says "not ready" so I can't even repair it in the CMC.
We've got ~500GB of very sensitive data stored on that volume. The volume was used by two VMware vSphere servers and contains a VMFS filesystem.
Is there any tool, utility, or process to bring the volume back online so I can extract the contents?
Can dbd_store be invoked in such a way that "forces" the volume back online, even in read-only mode so I can recover our data?
PLEASE HELP!
Thank you everyone.
Paul
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2009 05:40 PM
09-20-2009 05:40 PM
Re: URGENT! NSM-160 volume offline with Unrecoverable I/O
Some further information... looks like some I/Os didn't get committed out. Anybody know how to clear the journal log and get things back up and running?
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0x0a1f8c87 does not equal calculated checksum 0x632469a5
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fafa00 invalid block
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0xd208042c does not equal calculated checksum 0xe4756f7c
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fafc00 invalid block
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0xe91500a2 does not equal calculated checksum 0x802ee580
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fafe00 invalid block
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0x00000000 does not equal calculated checksum 0xffffffff
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fbfe00 invalid block
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0x0a1f8c87 does not equal calculated checksum 0x632469a5
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fafa00 invalid block
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0xd208042c does not equal calculated checksum 0xe4756f7c
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fafc00 invalid block
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0xe91500a2 does not equal calculated checksum 0x802ee580
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fafe00 invalid block
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:block checksum 0x00000000 does not equal calculated checksum 0xffffffff
Sep 20 21:36:10 NSM160-NODE1 dbd_store[9710]: DBD_STORE_JOURNAL_V1:/dev/scsi/host0/bus0/target0/lun0/part2 ofs=0x18fbfe00 invalid block
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP