Re: Trying to recover after losing a disk

Pete, Just like Alex says, this might be a general SAS failure. lsmap says
that they ARE disks so you will need to check the status of all disks. A
full errpt -a looking for mentions of SAS or sissas or hdisk may be useful.
"lsdev -Cc disk" and "lspath" as well to see if it still detects the disks
or if something has blown up.

On Wed, Oct 21, 2020 at 9:30 AM Pete Helgren <pete@xxxxxxxxxx> wrote:

Thanks Roberto,

Below Partition 2 is the 7.2 LPAR amd Partition 3 is the 7.1 LPAR I
just checked with the guys who manage the rack and they mentioned the
power was off for several hours a week ago (I was out of town).
Everything came back up (supposedly). So, again, the error listed in
the IVM is SRC A60C0255 "Description: Contact was lost with the device
indicated" So how do I determine the "device"? I assumed it was the
disk but without knowing for sure, something else could have failed.

It's a development machine so I wasn't really paying attention. The
system error in the AMM is from the 14th: "(10/14/20 16:24:06) (System
Event) system hardware failure" The disk failure that the AMM reported
is now gone as I replaced the disk.


$ lsmap -all
SVSA Physloc Client Partition ID
--------------- --------------------------------------------
------------------
vhost0 U7998.60X.10270CA-V1-C11 0x00000002

VTD vtscsi0
Status Available
LUN 0x8100000000000000
Backing device hdisk2
Physloc U4545.001.07AY127-P1-D1

VTD vtscsi1
Status Available
LUN 0x8200000000000000
Backing device hdisk3
Physloc U4545.001.07AY127-P1-D2

VTD vtscsi2
Status Available
LUN 0x8300000000000000
Backing device hdisk4
Physloc U4545.001.07AY127-P1-D3

VTD vtscsi3
Status Available
LUN 0x8400000000000000
Backing device hdisk14
Physloc U4545.001.07AY127-P1-D4

SVSA Physloc Client Partition ID
--------------- --------------------------------------------
------------------
vhost1 U7998.60X.10270CA-V1-C13 0x00000003

VTD vtopt0
Status Available
LUN 0x8200000000000000
Backing device
Physloc

VTD vtscsi4
Status Available
LUN 0x8100000000000000
Backing device hdisk6
Physloc U4545.001.07AY127-P1-D5

SVSA Physloc Client Partition ID
--------------- --------------------------------------------
------------------
vhost2 U7998.60X.10270CA-V1-C14 0x00000002

VTD vttape0
Status Available
LUN 0x8100000000000000
Backing device rmt0
Physloc U78A5.001.WIH1BE8-P1-C10-T1-L5005076312447387-L0


Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Twitter - Sys_i_Geek IBM_i_Geek

On 10/20/2020 9:20 PM, Roberto José Etcheverry Romero wrote:

I assume the disk is provided by the VIOS, if that is the case you have

to

check the VIOS's filesystems / file based disks / mappings to check

what

is

dead.
lsmap -all will tell you what is mapped to what and from there we can

work

out what is going on. It is weird you say that there are different

disks

mirrored and for only one disk to kill everything. I think that it

might

not be the case and maybe VIOS was providing disk based disks. lsmap

will

tell us.


On Tue, Oct 20, 2020 at 10:26 PM Pete Helgren <pete@xxxxxxxxxx> wrote:

Take a trip on the wayback....

I have a JS12 Blade in a BC-S. Two storage modules with 6 15k 300GB

SAS

drives each. No RAID controller (standard SAS controller). The JS12
has VIOS which is mirrored in rootvg - he seems to be OK. For IBM i I
have two LPARs 1 LPAR running 7.2 has 4 disks but they are "double
mirrored"; that is I have two sets of mirrored drives (don't ask) and
LPAR 2 has one drive. I have a 3rd LPAR running SUSE
on a single drive. I cannot connect at the moment to anything but

VIOS

and the AMM. Using the 5250 console fails to connect to either LPAR.

I

swapped out the bad drive and I have a vague feeling that was the

wrong

thing to do. But the biggest issue issue I that I cannot connect to
either IBM i LPAR.

IVM shows that each LPAR has an SRC. The 7.2 partition has SRC
A6010255 and the 7.1 partition has SRC A6010255 When I looked up

the

7.2 SRC it had this helpful note:

Explanation
Contact was lost with the device indicated.
Response
Do not power off the system.
Perform the procedure indicated in the failing item list.
Failing Item
LICIP13
FI00580
FI00500
FI00302
FI00301
AJDG301

Nice...except how do I find out the "failing item"? When I click on

the

SRC link in IVM it gives me this:

Reference code: A60C0255
Description: Contact was lost with the device indicated
Time stamp (UTC): 10/21/20 12:05:18 AM
Word 2: 0DB08062
Word 3: 00010004
Word 4: 00000027
Word 5: 00000000
Word 6: 000100FF
Word 7: 00FF0280
Word 8: 6B220050
Word 9: B6005120

Nice again....but where is the failing item indicated? I know it's a
hard disk that failed because the AMM told me that. But I am not 100%
sure it failed on one of my IBM i partitions. It failed in the

storage

module but I am not sure the lost drive was used by IBM i. Plus, the
drives are mirrored so they should be degraded, not inaccessible....

Perhaps something else failed rather than only the drive....this guy

is

getting pretty long in the tooth. So if someone could point me as to
how to move forward on this adventure, I would appreciate it.

--
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Twitter - Sys_i_Geek IBM_i_Geek

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com