×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Roberto,
This continues to get more interesting. I decided to shut down the 7.1
LPAR, to see if I could get it going again. About the time I shut it
down, drive 2 shows a fault in the AMM. So I shut down the 7.2 LPAR
and I got Drive 4,5 and 1 faulting. So, I doubt it was the drives
(although its *possible*). I am going to pull the storage module, blow
the dust out of it and re-insert it and see if that takes care of it.
The other storage module has hs21 blades connected to a logical volume
in the SM and, so far, nothing has faulted there. So, we'll see what a
little cleaning does......
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Twitter - Sys_i_Geek IBM_i_Geek
On 10/21/2020 8:26 AM, Roberto José Etcheverry Romero wrote:
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.
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
