- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: looking for method of identifying a bad/failed...
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
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
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
тАО10-24-2005 10:48 AM
тАО10-24-2005 10:48 AM
I found a few options, but am wondering if there are any others?:
use the following, and check for Removed?
# /usr/symcli/bin/symdev -sid 00 list -v | grep "Device Service State "
Device Service State : Normal
Device Service State : Normal
Device Service State : Normal
maybe use the following, and check for NR?
# /usr/symcli/bin/symdev -sid 00 list
Symmetrix ID: 000
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA :P DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
0000 Not Visible ***:* 01C:C0 2-Way Mir N/Grp'd VCM WD 23
0001 /dev/rdsk/c41t0d0 04A:0 01C:C0 2-Way Mir Grp'd RW 8632
0002 /dev/rdsk/c41t0d1 04A:0 16B:C0 2-Way Mir Grp'd RW 8632
0003 /dev/rdsk/c41t0d2 04A:0 01A:C0 2-Way Mir Grp'd RW 8632
0004 /dev/rdsk/c41t0d3 04A:0 16D:C0 2-Way Mir Grp'd RW 8632
0005 /dev/rdsk/c41t0d4 04A:0 16A:C1 2-Way Mir Grp'd RW 8632
0006 /dev/rdsk/c41t0d5 04A:0 01D:C1 2-Way Mir Grp'd RW 8632
0007 /dev/rdsk/c41t0d6 04A:0 16C:C1 2-Way Mir Grp'd RW 8632
or maybe this would work?
If I lost a drive, would the following command return a value?
# /usr/symcli/bin/symdev -sid 00 list -hotspare
Symmetrix ID: 000
Could not select any Symmetrix devices to list.
any assistance is appreciated,
manuel
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 12:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 02:04 AM
тАО10-25-2005 02:04 AM
Re: looking for method of identifying a bad/failed EMC drive (sym/DMX)..
You wouldn't happen to have an example of what the output looks like when a hot spare is invoked?
manuel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 10:03 PM
тАО10-25-2005 10:03 PM
Re: looking for method of identifying a bad/failed EMC drive (sym/DMX)..
at the moment we dont have any failed disk, and we never saved the output of the command in the past. so, no, we don't have an example output available.
I think it is something like "SymDev DA:IT Config Attrib MB..." but not exactly sure about the correct syntax.
If we encounter a failed disks the next days (you never know ;) i'll post it here.
regards,
bernd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 02:07 AM
тАО10-26-2005 02:07 AM
Re: looking for method of identifying a bad/failed EMC drive (sym/DMX)..
wouldn't it be nice if we all had a small dmx to play with :D
I was recently introduced to symdisk, It seems this would allow me to associate LUNs w/physical DRIVES...
thanks again,
manuel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-11-2005 10:14 PM
тАО12-11-2005 10:14 PM
Re: looking for method of identifying a bad/failed EMC drive (sym/DMX)..
it has been more than just a few days... but today we encountered a failed disk drive.
symdev Output:
symdev -sid 21 -hotspare list
Symmetrix ID: 000285701721
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA :P DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
031B Not Visible ???:? 07A:D3 RDF2+Mir N/Grp'd (M) WD 17263
0352 Not Visible ***:* 07A:D3 2-Way Mir N/Grp'd (M) RW 17263
0389 Not Visible ???:? 07A:D3 RDF2+Mir N/Grp'd (M) WD 17263
03C0 Not Visible ***:* 07A:D3 2-Way Mir N/Grp'd (M) RW 17263
03F7 Not Visible ???:? 07A:D3 RDF2+Mir N/Grp'd (M) WD 17263
042E Not Visible ***:* 07A:D3 2-Way Mir N/Grp'd (M) RW 17263
0465 Not Visible ???:? 07A:D3 RDF2+Mir N/Grp'd WD 8632
049C Not Visible ***:* 07A:D3 2-Way Mir N/Grp'd (M) RW 17263
In this output you cann see the Symmdevicenames and the physical disk location "DA:IT". In this case the failed disk was 07A:D3
Regards,
Bernd