|
Joe:
Some definitions:
DMPxxx means the drive is set up for Multipath (MP portion of the drive name) So just to be really confusing in DST that drive will l show up at least twice. At least because if you were on a partition that was served by Dual VIOS and that installation has two Fibre SANs you could see as many as four. All it means is IBM i has multiple ways to get to the disk unit in case one off those methods stops.
If a drive says DPHxxx then the "H" means it's been marked read-only and will need to be formatted prior to use. See: https://www-01.ibm.com/support/docview.wss?uid=nas8N1013838 to fix that. Easy.
The extension to the drive indicates what kind of data protection is on the drive, for instance: -50 means no RAID. It basically tells you about if it is included in a parity set, if so is there striping on that drive or not. 90% of that you simply don't care about.
See:
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzaly/rzalypd
f.pdf
For much more detail.
Basically, unless you are really going to mess with disk space, you really don't need to know much.
Now in the example below, where one drive is not operational, the first question I ask is what hardware failed? My bet on the example below is that drive was removed from the system without using SST, and the system still thinks it should be there. IF you go STRSST, option 1, option 7, then option 4 (from memory so I do this a bit) you'll find non-reporting hardware. Unless you really think that hardware should be there, remove it.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Joe
Pluta
Sent: Tuesday, December 18, 2018 8:27 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Disk drive types: 59C9, 59E1, 5B13
Like it or not, I'm becoming more familiar with our hardware and I'm finding some things that I consider anomalies. Case in point is my DSPHDWRSC display. It turns out we have a combination of SSD and spinny drives on the production partition. I'm just learning the ramifications of that (including the fact that CHGPF has a UNIT(*SSD) keyword!), but in so doing I decided to look at DSPHDWRSC on the development partition.
It seems like we have only spinny drives on the development partition, which is as it should be. However, it turns out on that partition we have cases where the same slot (I'm guessing) has two disk drives defined (I think), one of which is available in that partition and one of which is not (I assume). Yeah, I'm very, very confident of this information. It looks like this:
Resource Type-model Status Text
DMP001 59C9-050 Not detected Disk Unit
DMP073 59C9-099 Operational Disk Unit
They're both in location U5887.001.G78J00V-P1-D2. I have no idea what the -050 or -099 suffix means. But doing a little more research, it turns out the resources that are flagged as not detected show up in DSPHDWRSC on the production partition as Operational. That is, DMP001 is Not detected on the development partition but Operational on the production partition. The reverse is not true. Resources that are Operational on development (such as DMP073) do not show up at all on the production partition in DSPHDWRSC. So which is "normal"?
The resource number could be a red herring, though. Although DMP001 shows on both partitions, DMP001 on development has a different serial number than DMP001 on production. My head hurts.
There's one more thing that bothers me. Knowledge center tells me a
59C9 is a 300GB 15K 4K-block SAS drive, but that it's an AIX/Linux drive, not an IBM i drive. As far as I can tell, the IBM i equivalent is the 59E1, which is a 283GB drive. The main box is all 59C9 (and 5B13 SSD). We also have a remote CBU box with a mixture of 59E1 and 59C9. Is it normal to use the 300GB drive on an i partition? Enquiring minds want to know...
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
