Home
Man
Search
Today's Posts
Register

The Solaris Operating System, usually known simply as Solaris, is a Unix-based operating system introduced by Sun Microsystems. The Solaris OS is now owned by Oracle.

Fibre channel link down on booting Solaris server

Tags
solaris

Login to Reply

 
Thread Tools Search this Thread
# 8  
Old 07-23-2018
It does not boot in any of them:

for disk0, just stays like below

Code:
{0} ok boot disk0
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p0  File and args:

for disk disk1 :
Code:
 ok boot disk1
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p1  File and args:
ERROR: boot-read fail


Can't locate boot device

for disk2

Code:
{0} ok boot disk2
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p2  File and args:
ERROR: boot-read fail


Can't locate boot device

and for disk3

Code:
{0} ok boot disk3
Boot device: /pci@400/pci@1/pci@0/pci@2/@0/disk@p3  File and args:
ERROR: boot-read fail


Can't locate boot device

{0} ok

# 9  
Old 07-23-2018
So none of those disks are bootable.

Did the system boot via the FC link which is now down?

Do you know from which disk it should boot?

It is possible that the proper boot disk is local disk0 which has sustained filesystem damage during the power cut. You may need to boot from DVD and fsck this filesystem. If that doesn't work you may need to recover some files from backup. It is likely that the FC link is down as far as the SC is concerned because Solaris isn't running and the QLogic driver isn't therefore loaded.

Last edited by hicksd8; 07-23-2018 at 01:55 PM..
The Following User Says Thank You to hicksd8 For This Useful Post:
fretagi (07-24-2018)
# 10  
Old 07-24-2018
Hi

I have logged in at the ILOM management port of this blade and I found a fault, but I dont know if this fault its hardware or software:

I have started the fault management shell:

Code:
-> start /CMM/faultmgmt/shell
Are you sure you want to start /CMM/faultmgmt/shell (y/n)? y

faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm faulty
------------------- ------------------------------------ -------------- --------
Time                UUID                                 msgid          Severity
------------------- ------------------------------------ -------------- --------
2018-07-11/11:04:55 1a96f137-6015-c606-eaad-f1f971e1caa9 SPX86-8000-1D  Critical

Fault class : fault.chassis.device.fail

FRU         : /CH/BL0
              (Part Number: 541-4197-06)
              (Serial Number: 1005LCB-1126D4037D)

Description : A device necessary to support a configuration is missing.

Response    : The service required LED on the chassis will be illuminated.

Impact      : The chassis may be powered down.

Action      : The administrator should review the ILOM event log for
              additional information pertaining to this diagnosis.  Please
              refer to the Details section of the Knowledge Article for
              additional information.

------------------- ------------------------------------ -------------- --------
Time                UUID                                 msgid          Severity
------------------- ------------------------------------ -------------- --------
2018-07-12/08:17:34 6114a8ae-b70d-6648-be20-867e12d83674 SPX86-8000-1D  Critical

Fault class : fault.chassis.device.fail

FRU         : /CH/BL3
              (Part Number: 541-4197-06)
              (Serial Number: 1005LCB-1126D4037P)

Description : A device necessary to support a configuration is missing.

Response    : The service required LED on the chassis will be illuminated.

Impact      : The chassis may be powered down.

Action      : The administrator should review the ILOM event log for
              additional information pertaining to this diagnosis.  Please
              refer to the Details section of the Knowledge Article for
              additional information.

faultmgmtsp>

/CH/BL3, its the server with this issue.

I have run a few commands:

Code:
-> show faulty
Target              | Property               | Value
--------------------+------------------------+---------------------------------
/CMM/faultmgmt/0    | fru                    | /CH/BL0
/CMM/faultmgmt/0/   | class                  | fault.chassis.device.fail
 faults/0           |                        |
/CMM/faultmgmt/0/   | sunw-msg-id            | SPX86-8000-1D
 faults/0           |                        |
/CMM/faultmgmt/0/   | uuid                   | 1a96f137-6015-c606-eaad-f1f971e1
 faults/0           |                        | caa9
/CMM/faultmgmt/0/   | timestamp              | 2018-07-11/11:04:55
 faults/0           |                        |
/CMM/faultmgmt/0/   | detector               | /CH/BL0/ERR
 faults/0           |                        |
/CMM/faultmgmt/0/   | fru_part_number        | 541-4197-06
 faults/0           |                        |
/CMM/faultmgmt/0/   | fru_serial_number      | 1005LCB-1126D4037D
 faults/0           |                        |
/CMM/faultmgmt/0/   | chassis_serial_number  | 1126BD0E75
 faults/0           |                        |
/CMM/faultmgmt/1    | fru                    | /CH/BL3
/CMM/faultmgmt/1/   | class                  | fault.chassis.device.fail
 faults/0           |                        |
/CMM/faultmgmt/1/   | sunw-msg-id            | SPX86-8000-1D
 faults/0           |                        |
/CMM/faultmgmt/1/   | uuid                   | 87864a2c-e6f7-ecad-a1cb-c75349fa
 faults/0           |                        | 0735
/CMM/faultmgmt/1/   | timestamp              | 2018-07-23/15:44:44
 faults/0           |                        |
/CMM/faultmgmt/1/   | detector               | /CH/BL3/ERR
 faults/0           |                        |
/CMM/faultmgmt/1/   | fru_part_number        | 541-4197-06
 faults/0           |                        |
/CMM/faultmgmt/1/   | fru_serial_number      | 1005LCB-1126D4037P
 faults/0           |                        |
/CMM/faultmgmt/1/   | chassis_serial_number  | 1126BD0E75
 faults/0           |                        |

->

I also run some repaired commands:

Code:
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repaired /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repaired /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repair /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp> fmadm repair /CH/BL3
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
faultmgmtsp>
faultmgmtsp> fmadm faulty -r
/CH/BL0                                                       degraded
/CH/BL3                                                       degraded
faultmgmtsp>

still in degraded mode.

From this I concluded that perhaps the SP (service processor) is faulty and needs to be replaced. But not sure
# 11  
Old 09-28-2018
I guess it's too late for this response,



but I will leave this comment here in case someone is useful


In case of Solaris boot from SAN, for any Storage Brand, is necessary execute additional steps in the OPENBOOT prompt, basically this steps are related to configure the FC HBA at low level, in order to indicate the FC topology and select the boot disk from the HBA level. When you set the ID disk in the HBA level, then the FC link come up.


The steps to config the HBA in the OPENBOOT prompt depend of any HBA brand/model.


There are manuals of Emulex and QLOGIC with this information.


Only to put a short example, for EMULEX.


NOTE *****
This is just a fragment of the manual, please review the complete procedure.



Code:
 
Specify the topology for the target Fibre Channel boot disk:

a.   At the OK> prompt, type the following and press ENTER
" <device path name>" select-dev
(Example: " /pci@1f,4000/lpfc@4" select-dev)
b.   At the OK> prompt, type the appropriate command and press ENTER:
FC-AL: set-fc-al
FC-SW: set-ptp
c.   At the OK> prompt, type unselect-dev and press ENTER

Follow these steps to set the boot device ID:
At the OK> prompt, type
 " /pci@1f,4000/lpfc@4" select-dev and press ENTER.
At the OK> prompt, type the appropriate command and press ENTER:
FC-AL: did  e4  0  2  set-boot-id
FC-SW: wwpn 5006.0482.bbff.4e0f 0 2  set-boot-id

Login to Reply

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Sun Server not booting into OS br1an Solaris 1 05-16-2014 06:31 AM
Fibre Channel HBA recommendations? atahmass Hardware 1 06-09-2012 06:31 AM
USCSICMD ioctl calls for Fibre Channel(FC) devices on Solaris 10? naveen448 Solaris 0 04-08-2010 09:23 AM
Sun Server: loop while booting snap UNIX for Dummies Questions & Answers 4 02-14-2010 08:09 AM
Server is not booting mokkan Solaris 3 01-26-2010 02:46 AM
Power6 Virtual Fibre Channel Adapter filosophizer AIX 1 06-16-2009 07:36 AM
Fibre channel drivers on RS/6000 aix 5L Zim-Aix-Guru AIX 4 06-10-2008 07:55 PM


All times are GMT -4. The time now is 04:20 PM.

Unix & Linux Forums Content Copyright 1993-2018. All Rights Reserved.
UNIX.COM Login
Username:
Password:  
Show Password