T5-2 System Board Replacement
Posted: Fri Oct 18, 2013 7:11 pm
After working with Oracle for fmadm faulty issue for some time, they finally decided to send field engineers to replace the /SYS/MB.
Since I was out first two days of this week, I got Ken to come in today (10/18/2013, Fri).
Ken and Jeff both came to help.
Replacing the system board was faster this time than last time we had T3-2's system board replaced. Perhaps because there were 2 people this time than one person last time. Both SP (Service Processor) and EPROM have to be kept and swapped for the new system board.
After the server was powered up, the ILOM was showing "Unrecognized chassis". I had to upgrade the firmware with the same version to get it to work. Luckily, I had done it last month and the upgrade didn't take long.
After firmware was upgraded, I was able to use ILOM to start /HOST/console. Power the machine up took about 25 minutes. After it came up, configurations have to be done from ok prompt. From last experience, I knew the boot-device would need to be reset so I got the boot-device environment variable ahead of time:
When I first got to ok prompt, I ran the following commands:
I then activated the second RAID disk:
After that, reset boot-device from:
To:
Also, made sure auto-boot? is set to true.
A reboot got us back to normal state.
Hopefully, this resolves the fmadm faulty issue.
Since I was out first two days of this week, I got Ken to come in today (10/18/2013, Fri).
Ken and Jeff both came to help.
Replacing the system board was faster this time than last time we had T3-2's system board replaced. Perhaps because there were 2 people this time than one person last time. Both SP (Service Processor) and EPROM have to be kept and swapped for the new system board.
After the server was powered up, the ILOM was showing "Unrecognized chassis". I had to upgrade the firmware with the same version to get it to work. Luckily, I had done it last month and the upgrade didn't take long.
After firmware was upgraded, I was able to use ILOM to start /HOST/console. Power the machine up took about 25 minutes. After it came up, configurations have to be done from ok prompt. From last experience, I knew the boot-device would need to be reset so I got the boot-device environment variable ahead of time:
Code: Select all
{0} ok printenv boot-device
boot-device = /pci@3c0/pci@1/pci@0/pci@2/scsi@0/disk@w338670488b799130,0:a /pci@300/pci@1/pci@0/pci@2/scsi@0/disk@w3a326f3c118fec2e,0:a disk net
Code: Select all
{0} ok select scsi1
{0} ok show-volumes
Volume 0 Target 143 Type RAID1 (Mirroring)
Name BOOT_VOLUME WWID 038670488b799130
Optimal Enabled Inactive
2 Members 1169920000 Blocks, 598 GB
Disk 1
Primary Optimal
Target 9 HITACHI H109060SESUN600G A31A PhyNum 0
Disk 0
Secondary Optimal
Target b HITACHI H109060SESUN600G A31A PhyNum 1
{0} ok 0 activate-volume
Volume 0 is now activated
{0} ok show-volumes
Volume 0 Target 143 Type RAID1 (Mirroring)
Name BOOT_VOLUME WWID 038670488b799130
Optimal Enabled
2 Members 1169920000 Blocks, 598 GB
Disk 1
Primary Optimal
Target 9 HITACHI H109060SESUN600G A31A PhyNum 0
Disk 0
Secondary Optimal
Target b HITACHI H109060SESUN600G A31A PhyNum 1
Code: Select all
{0} ok select scsi
{0} ok show-volumes
Volume 0 Target 143 Type RAID10 (Striped Mirroring)
Name DATA_VOLUME WWID 0a326f3c118fec2e
Optimal Enabled Inactive
4 Members 2339840000 Blocks, 1197 GB
Disk 3
Member 0 Optimal
Target 9 HITACHI H109060SESUN600G A31A PhyNum 0
Disk 2
Member 1 Optimal
Target a HITACHI H109060SESUN600G A31A PhyNum 1
Disk 1
Member 2 Optimal
Target b HITACHI H109060SESUN600G A31A PhyNum 2
Disk 0
Member 3 Optimal
Target c HITACHI H109060SESUN600G A31A PhyNum 3
{0} ok 0 activate-volume
Volume 0 is now activated
{0} ok show-volumes
Volume 0 Target 143 Type RAID10 (Striped Mirroring)
Name DATA_VOLUME WWID 0a326f3c118fec2e
Optimal Enabled
4 Members 2339840000 Blocks, 1197 GB
Disk 3
Member 0 Optimal
Target 9 HITACHI H109060SESUN600G A31A PhyNum 0
Disk 2
Member 1 Optimal
Target a HITACHI H109060SESUN600G A31A PhyNum 1
Disk 1
Member 2 Optimal
Target b HITACHI H109060SESUN600G A31A PhyNum 2
Disk 0
Member 3 Optimal
Target c HITACHI H109060SESUN600G A31A PhyNum 3
Code: Select all
boot-device = disk net
Code: Select all
boot-device = /pci@3c0/pci@1/pci@0/pci@2/scsi@0/disk@w338670488b799130,0:a /pci@300/pci@1/pci@0/pci@2/scsi@0/disk@w3a326f3c118fec2e,0:a disk net
Code: Select all
setenv auto-boot? true
Hopefully, this resolves the fmadm faulty issue.