Hi guys

Just finish a mother replacement on an PowerEdge R630. iDrac8 can't visualize Storage information:

iDrac cannot display Storage information
RAC0501: There are no physical disks to be displayed.
1. Check if the host system is powered off or shutdown.
2. Check if the physical disks are inserted into the enclosure or attached to the backplane.
3. There are no out-of-band capable controllers detected.

But I could manage the both disks in a RAID 1 virtual disk via BIOS and the machine is working fine. Nevertheless I would like to have the Storage view in iDrac.

Versions are:

BIOS Version 1.5.4
Firmware Version 2.21.21.21
Lifecycle Controller Firmware 2.21.21.21

because of teaming problems I did a reset of WMI. After reset I tried to repair existing OMSA 8.1 and received error: "server administrator installation program could not install the hapi driver"

I can successfully deinstall OMSA 8.1 but when I trie to resetup this message appears again.

How can I rebuild missing WMI-dcim-sysman entries or install the needed HAPI driver?

any ideas?

System: PE R610

OS: Windows 2008 R2 SP1

Hi,

Each time a restart is done on our m620's they spend an enormous time at the Initializing firmware interfaces.... screen.

Even after doing all the updates, the time is extensive.

Is there a fix for this? (I don't really care about using profiles from an m1000e).

Thx,

John Bradshaw

Hello,

I have a PowerEdge 1950 BIOS 2.7.0 with DRAC 5 Firmware Version 1.65 (12.08.16).

When trying to connect to "Console" I am receiving the error  "Error when reading from SSL socket connection".

I did comment the line "#   jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768" at java.security file but still the same.

I am using WIndows 10 with latest FireFox.

Thanks in advanced,

Asaf

Hi, I've installed the H730p RAID into the R630 server, but the SAS cables from the front drive arrays A & B connect to the main board and have no play in them to connect to the RAID card.

I assume I need new SAS cables, but cannot find any reference to these anywhere.. Do I need new cables and what are the part numbers please?

many thanks

Pete

I have an old PE 840 that I got from work.  When I first received it, the power light was flashing amber.  It was still under warranty, and a Dell tech came out to replace the motherboard and/or processor.  He connected to the DRAC 4, and cleared the logs and the server fired right up.  I went to upgrade the processor from a Xeon 3210 to a 3230, and now the dreaded flashing amber light is back.  For whatever reason I cannot connect to the DRAC any longer.  I have tried across the network, and with a cross-over adapter.  

The fans all work, the DRAC and network ports both show activity.  I have removed all cards and RAM DIMMs and still no POST.  When connected to power, the light is initially blue, but quickly goes to the flashing amber.  Any further suggestions?

Hello,

Dealing with an ESX server with VMs giving slow performance. Specifically the SBS server VM. I know SBS is difficult on a good day, but very odd errors have been occurring as of late and it prompted me to take a look at the MegaRAID / PERC log.

Back in late June, drives were replaced in the array. I see that during the rebuild, it mentions that there were uncorrectable errors during the recovery, and several messages along the lines of "Puncturing bad block on PD..."

I am familiar with WHY a punctured array needs to be flushed and rebuild from scratch, and am definitely ready to do so if this is the case.Performing this task and the massive amount of time involved to migrate the VMs, rebuild, then migrate back, is why I'm here to ask to get other's opinions. I'd like to be almost sure that this is the case before we proceed. The Array did finish rebuilding and is in an Optimal state at the moment. Several recent Patrol Reads have passed fine.

Thank you.

Here are some of the messages from the log, I chopped out some of the binary / hex dumps for readability:

Event Sequence Number : 191944
Timestamp : 6/29/2016 ; 20:26:51
Event code : 113
Locale : PD event
Class : Information
Description of the event : Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 cf fb 6d 00 00 13 00, Sense: 3/11/00
Argument Type Value: 1
Argument Type : MR_EVT_ARGS_CDB_SENSE
 Physical Device ID : 0x1
 Enclosure Index : 32
 Slot Number : 1
 Length of CDB : 10
 Length of request sense data : 18
 CDB :

28  00  02  CF  FB  6D  00  00  13  00  00  00  00  00  00  00 

Event Sequence Number : 191945
Timestamp : 6/29/2016 ; 20:26:51
Event code : 111
Locale : PD event
Class : Fatal
Description of the event : Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2cffb6d
Argument Type Value: 12
Argument Type : MR_EVT_ARGS_PD_LBA
 LBA : 23039                MB
 Physical Device ID : 0x1
 Enclosure Index : 32
 Slot Number : 1

Event Sequence Number : 191946
Timestamp : 6/29/2016 ; 20:26:51
Event code : 111
Locale : PD event
Class : Fatal
Description of the event : Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2cffb6d
Argument Type Value: 12
Argument Type : MR_EVT_ARGS_PD_LBA
 LBA : 23039                MB
 Physical Device ID : 0x1
 Enclosure Index : 32
 Slot Number : 1

Event Sequence Number : 191947
Timestamp : 6/29/2016 ; 20:26:51
Event code : 97
Locale : PD event
Class : Fatal
Description of the event : Puncturing bad block on PD 00(e0x20/s0) at 2cffb6d
Argument Type Value: 12
Argument Type : MR_EVT_ARGS_PD_LBA
 LBA : 23039                MB
 Physical Device ID : 0x0
 Enclosure Index : 32
 Slot Number : 0

Event Sequence Number : 191948
Timestamp : 6/29/2016 ; 20:26:51
Event code : 97
Locale : PD event
Class : Fatal
Description of the event : Puncturing bad block on PD 01(e0x20/s1) at 2cffb6d
Argument Type Value: 12
Argument Type : MR_EVT_ARGS_PD_LBA
 LBA : 23039                MB
 Physical Device ID : 0x1
 Enclosure Index : 32
 Slot Number : 1

Event Sequence Number : 191949
Timestamp : 6/29/2016 ; 20:26:53
Event code : 113
Locale : PD event
Class : Information
Description of the event : Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 d0 17 24 00 00 0c 00, Sense: 3/11/00
Argument Type Value: 1
Argument Type : MR_EVT_ARGS_CDB_SENSE
 Physical Device ID : 0x1
 Enclosure Index : 32
 Slot Number : 1
 Length of CDB : 10
 Length of request sense data : 18
 CDB :

28  00  02  D0  17  24  00  00  0C  00  00  00  00  00  00  00  
 

Event Sequence Number : 191950
Timestamp : 6/29/2016 ; 20:26:53
Event code : 111
Locale : PD event
Class : Fatal
Description of the event : Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2d01725
Argument Type Value: 12
Argument Type : MR_EVT_ARGS_PD_LBA
 LBA : 23042                MB
 Physical Device ID : 0x1
 Enclosure Index : 32
 Slot Number : 1

Event Sequence Number : 192303
Timestamp : 6/29/2016 ; 21:7:58
Event code : 271
Locale : LD event
Class : Fatal
Description of the event : Uncorrectable medium error logged for VD 00/0 at 870b05c (on PD 00(e0x20/s0) at 2d03adc)
Argument Type Value: 6
Argument Type : MR_EVT_ARGS_LD_LBA_PD_LBA
 LD LBA : 69142                MB
 PD LBA : 23047                MB
 Logical Drive Target ID : 0
 Firmware LD Number : 0
 Physical Device ID : 0x0
 Enclosure Index : 32
 Slot Number : 0

Event Sequence Number : 192400
Timestamp : 6/30/2016 ; 5:23:48
Event code : 99
Locale : PD event
Class : Information
Description of the event : Rebuild complete on VD 00/0
Argument Type Value: 2
Argument Type : MR_EVT_ARGS_LD
 Logical Drive Target ID : 0
 Firmware LD Number : 0

Event Sequence Number : 192401
Timestamp : 6/30/2016 ; 5:23:48
Event code : 100
Locale : PD event
Class : Information
Description of the event : Rebuild complete on PD 00(e0x20/s0)
Argument Type Value: 10
Argument Type : MR_EVT_ARGS_PD
 Physical Device ID : 0x0
 Enclosure DeviceID : 32
 Slot Number : 0

Event Sequence Number : 192402
Timestamp : 6/30/2016 ; 5:23:51
Event code : 114
Locale : PD event
Class : Information
Description of the event : State change on PD 00(e0x20/s0) from REBUILD(14) to ONLINE(18)
Argument Type Value: 15
Argument Type : MR_EVT_ARGS_PD_STATE
 Physical Device ID : 0x0
 Enclosure Index : 32
 Slot Number : 0
 Previous State : 20
 New State : 24

Event Sequence Number : 192403
Timestamp : 6/30/2016 ; 5:23:52
Event code : 81
Locale : LD event
Class : Information
Description of the event : State change on VD 00/0 from DEGRADED(2) to OPTIMAL(3)
Argument Type Value: 8
Argument Type : MR_EVT_ARGS_LD_STATE
 Logical Drive Target ID : 0
 Firmware LD Number : 0
 Previous State : 2
 New State : 3

06/29/16 19:02:17: ErrLBAOffset (31) LBA(2cffe98) BadLba=2cffec9
06/29/16 19:02:17: EVT#191424-06/29/16 19:02:17: 111=Unrecoverable medium error during recovery on PD 02(e0x20/s2) at 2cffec9
06/29/16 19:02:17: BBMMarkBadBlock: pd=02, pdLBA=2cffec9
06/29/16 19:02:17: EVT#191425-06/29/16 19:02:17:  97=Puncturing bad block on PD 02(e0x20/s2) at 2cffec9
06/29/16 19:02:18: EVT#191426-06/29/16 19:02:18: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 cf fb 40 00 00 40 00, Sense: 3/11/00
06/29/16 19:02:18: Raw Sense for PD 1: f0 00 03 02 cf fb 6c 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:02:18: DEV_REC:Medium Error DevId[1] devHandle c RDM=807a0800 retires=0
06/29/16 19:02:18: DM_PerformSenseDataRecovery: MedErr is for: cmdId=246e, ld=0, src=4, cmd=1, lba=870a9c0, cnt=8, rmwOp=0
06/29/16 19:02:18:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=5 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:02:18:  -> RecParent: cmdId=2482, src=7, cmd=2, lba=86ff140, cnt=140, rmwOp=0, refs=40/7f
06/29/16 19:02:18: ErrLBAOffset (2c) LBA(2cffb40) BadLba=2cffb6c
06/29/16 19:02:18: EVT#191427-06/29/16 19:02:18: 111=Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2cffb6c
06/29/16 19:02:18: BBMMarkBadBlock: pd=01, pdLBA=2cffb6c
06/29/16 19:02:18: EVT#191428-06/29/16 19:02:18:  97=Puncturing bad block on PD 01(e0x20/s1) at 2cffb6c
06/29/16 19:02:19: Invalidating Line due to failed XOR!!! cmd=843f8560
06/29/16 19:02:19: EVT#191429-06/29/16 19:02:19: 113=Unexpected sense: PD 02(e0x20/s2) Path 5000c50053c1e929, CDB: 28 00 02 cf fe ca 00 00 36 00, Sense: 3/11/00
06/29/16 19:02:19: Raw Sense for PD 2: f0 00 03 02 cf fe ca 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:02:19: DEV_REC:Medium Error DevId[2] devHandle b RDM=80785600 retires=0
06/29/16 19:02:19: DM_PerformSenseDataRecovery: MedErr is for: cmdId=2441, ld=0, src=4, cmd=1, lba=8700dc8, cnt=8, rmwOp=0
06/29/16 19:02:19:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=7 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:02:19:  -> RecParent: cmdId=241e, src=7, cmd=2, lba=86ffb98, cnt=168, rmwOp=0, refs=18/7f
06/29/16 19:02:19: ErrLBAOffset (0) LBA(2cffeca) BadLba=2cffeca
06/29/16 19:02:19: EVT#191430-06/29/16 19:02:19: 111=Unrecoverable medium error during recovery on PD 02(e0x20/s2) at 2cffeca
06/29/16 19:02:19: BBMMarkBadBlock: pd=02, pdLBA=2cffeca
06/29/16 19:02:19: EVT#191431-06/29/16 19:02:19:  97=Puncturing bad block on PD 02(e0x20/s2) at 2cffeca
06/29/16 19:02:19: Invalidating Line due to failed XOR!!! cmd=843f77e0
06/29/16 19:02:20: EVT#191432-06/29/16 19:02:20: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 cf fb 6d 00 00 13 00, Sense: 3/11/00
06/29/16 19:02:20: Raw Sense for PD 1: f0 00 03 02 cf fb 6d 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:02:20: DEV_REC:Medium Error DevId[1] devHandle c RDM=807a0800 retires=0
06/29/16 19:02:20: DM_PerformSenseDataRecovery: MedErr is for: cmdId=246e, ld=0, src=4, cmd=1, lba=870a9c0, cnt=8, rmwOp=0
06/29/16 19:02:20:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=5 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:02:20:  -> RecParent: cmdId=2482, src=7, cmd=2, lba=86ff140, cnt=140, rmwOp=0, refs=40/7f
06/29/16 19:02:20: ErrLBAOffset (0) LBA(2cffb6d) BadLba=2cffb6d
06/29/16 19:02:20: EVT#191433-06/29/16 19:02:20: 111=Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2cffb6d
06/29/16 19:02:20: BBMMarkBadBlock: pd=01, pdLBA=2cffb6d
06/29/16 19:02:20: EVT#191434-06/29/16 19:02:20:  97=Puncturing bad block on PD 01(e0x20/s1) at 2cffb6d
06/29/16 19:02:22: EVT#191435-06/29/16 19:02:22: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 cf fb 6e 00 00 12 00, Sense: 3/11/00
06/29/16 19:02:22: Raw Sense for PD 1: f0 00 03 02 cf fb 6e 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:02:22: DEV_REC:Medium Error DevId[1] devHandle c RDM=807a0800 retires=0
06/29/16 19:02:22: DM_PerformSenseDataRecovery: MedErr is for: cmdId=246e, ld=0, src=4, cmd=1, lba=870a9c0, cnt=8, rmwOp=0
06/29/16 19:02:22:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=5 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:02:22:  -> RecParent: cmdId=2482, src=7, cmd=2, lba=86ff140, cnt=140, rmwOp=0, refs=40/7f
06/29/16 19:02:22: ErrLBAOffset (0) LBA(2cffb6e) BadLba=2cffb6e
06/29/16 19:02:22: EVT#191436-06/29/16 19:02:22: 111=Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2cffb6e
06/29/16 19:02:22: BBMMarkBadBlock: pd=01, pdLBA=2cffb6e
06/29/16 19:02:22: EVT#191437-06/29/16 19:02:22:  97=Puncturing bad block on PD 01(e0x20/s1) at 2cffb6e
06/29/16 19:02:24: EVT#191438-06/29/16 19:02:24: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 cf fb 6f 00 00 11 00, Sense: 3/11/00
06/29/16 19:02:24: Raw Sense for PD 1: f0 00 03 02 cf fb 6f 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:02:24: DEV_REC:Medium Error DevId[1] devHandle c RDM=807a0800 retires=0
06/29/16 19:02:24: DM_PerformSenseDataRecovery: MedErr is for: cmdId=246e, ld=0, src=4, cmd=1, lba=870a9c0, cnt=8, rmwOp=0
06/29/16 19:02:24:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=5 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:02:24:  -> RecParent: cmdId=2482, src=7, cmd=2, lba=86ff140, cnt=140, rmwOp=0, refs=40/7f
06/29/16 19:02:24: ErrLBAOffset (0) LBA(2cffb6f) BadLba=2cffb6f
06/29/16 19:02:24: EVT#191439-06/29/16 19:02:24: 111=Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2cffb6f
06/29/16 19:02:24: BBMMarkBadBlock: pd=01, pdLBA=2cffb6f
06/29/16 19:02:24: EVT#191440-06/29/16 19:02:24:  97=Puncturing bad block on PD 01(e0x20/s1) at 2cffb6f
06/29/16 19:02:24: Invalidating Line due to failed XOR!!! cmd=843fdd20
06/29/16 19:09:30: EVT#191441-06/29/16 19:09:30: 113=Unexpected sense: PD 02(e0x20/s2) Path 5000c50053c1e929, CDB: 28 00 02 cf fe 98 00 00 68 00, Sense: 3/11/00
06/29/16 19:09:30: Raw Sense for PD 2: f0 00 03 02 cf fe c9 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:09:30: DEV_REC:Medium Error DevId[2] devHandle b RDM=806d6e00 retires=0
06/29/16 19:09:30: DM_PerformSenseDataRecovery: MedErr is for: cmdId=249f, ld=0, src=4, cmd=1, lba=6900c00, cnt=180, rmwOp=0
06/29/16 19:09:30:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=7 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:09:30:  -> RecParent: cmdId=24ac, src=7, cmd=2, lba=86ffb98, cnt=168, rmwOp=0, refs=18/7f
06/29/16 19:09:30: ErrLBAOffset (31) LBA(2cffe98) BadLba=2cffec9
06/29/16 19:09:30: EVT#191442-06/29/16 19:09:30: 111=Unrecoverable medium error during recovery on PD 02(e0x20/s2) at 2cffec9
06/29/16 19:09:30: BBMMarkBadBlock: pd=02, pdLBA=2cffec9
06/29/16 19:09:30: EVT#191443-06/29/16 19:09:30:  97=Puncturing bad block on PD 02(e0x20/s2) at 2cffec9
06/29/16 19:09:32: EVT#191444-06/29/16 19:09:32: 113=Unexpected sense: PD 02(e0x20/s2) Path 5000c50053c1e929, CDB: 28 00 02 cf fe ca 00 00 36 00, Sense: 3/11/00
06/29/16 19:09:32: Raw Sense for PD 2: f0 00 03 02 cf fe ca 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:09:32: DEV_REC:Medium Error DevId[2] devHandle b RDM=806d6e00 retires=0
06/29/16 19:09:32: DM_PerformSenseDataRecovery: MedErr is for: cmdId=249f, ld=0, src=4, cmd=1, lba=6900c00, cnt=180, rmwOp=0
06/29/16 19:09:32:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=7 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:09:32:  -> RecParent: cmdId=24ac, src=7, cmd=2, lba=86ffb98, cnt=168, rmwOp=0, refs=18/7f
06/29/16 19:09:32: ErrLBAOffset (0) LBA(2cffeca) BadLba=2cffeca
06/29/16 19:09:32: EVT#191445-06/29/16 19:09:32: 111=Unrecoverable medium error during recovery on PD 02(e0x20/s2) at 2cffeca
06/29/16 19:09:32: BBMMarkBadBlock: pd=02, pdLBA=2cffeca
06/29/16 19:09:32: EVT#191446-06/29/16 19:09:32:  97=Puncturing bad block on PD 02(e0x20/s2) at 2cffeca
06/29/16 19:09:32: EVT#191447-06/29/16 19:09:32: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 cf fb 40 00 00 40 00, Sense: 3/11/00
06/29/16 19:09:32: Raw Sense for PD 1: f0 00 03 02 cf fb 6c 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:09:32: DEV_REC:Medium Error DevId[1] devHandle c RDM=80712a00 retires=0
06/29/16 19:09:32: DM_PerformSenseDataRecovery: MedErr is for: cmdId=2449, ld=0, src=4, cmd=1, lba=86f9f10, cnt=c8, rmwOp=0
06/29/16 19:09:32:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=5 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:09:32:  -> RecParent: cmdId=2493, src=7, cmd=2, lba=86ff140, cnt=140, rmwOp=0, refs=40/7f
06/29/16 19:09:32: ErrLBAOffset (2c) LBA(2cffb40) BadLba=2cffb6c
06/29/16 19:09:33: EVT#191448-06/29/16 19:09:33: 111=Unrecoverable medium error during recovery on PD 01(e0x20/s1) at 2cffb6c
06/29/16 19:09:33: BBMMarkBadBlock: pd=01, pdLBA=2cffb6c
06/29/16 19:09:33: EVT#191449-06/29/16 19:09:33:  97=Puncturing bad block on PD 01(e0x20/s1) at 2cffb6c
06/29/16 19:09:33: Invalidating Line due to failed XOR!!! cmd=84404b60
06/29/16 19:09:34: EVT#191450-06/29/16 19:09:34: 113=Unexpected sense: PD 01(e0x20/s1) Path 5000c5007f5273ad, CDB: 28 00 02 cf fb 6d 00 00 13 00, Sense: 3/11/00
06/29/16 19:09:34: Raw Sense for PD 1: f0 00 03 02 cf fb 6d 0a 00 00 00 00 11 00 81 80 00 97
06/29/16 19:09:34: DEV_REC:Medium Error DevId[1] devHandle c RDM=80712a00 retires=0
06/29/16 19:09:34: DM_PerformSenseDataRecovery: MedErr is for: cmdId=2449, ld=0, src=4, cmd=1, lba=86f9f10, cnt=c8, rmwOp=0
06/29/16 19:09:34:  -> recoveryChild: ld=0 orgLi=0 recPhysArm=0 badPhysArm=ff doneFun=5 sRef=ff00 eRef=0 recFlags=0
06/29/16 19:09:34:  -> RecParent: cmdId=2493, src=7, cmd=2, lba=86ff140, cnt=140, rmwOp=0, refs=40/7f

06/30/16  5:21:36: GroupCmds: Fail cmd c=c0f48380 ld=0 start_block=86ff268 num_blocks=28 cmd=1
06/30/16  5:21:36: GroupCmds: Fail cmd c=c0f48380 ld=0 start_block=86ff268 num_blocks=28 cmd=1
06/30/16  5:21:36: GroupCmds: Fail cmd c=c0f48380 ld=0 start_block=86ff268 num_blocks=28 cmd=1
06/30/16  5:21:53: EVT#192397-06/30/16  5:21:53: 103=Rebuild progress on PD 00(e0x20/s0) is 97.94%(32509s)
06/30/16  5:22:47: EVT#192398-06/30/16  5:22:47: 103=Rebuild progress on PD 00(e0x20/s0) is 98.94%(32563s)
06/30/16  5:23:45: EVT#192399-06/30/16  5:23:45: 103=Rebuild progress on PD 00(e0x20/s0) is 99.94%(32621s)
06/30/16  5:23:48: EVT#192400-06/30/16  5:23:48:  99=Rebuild complete on VD 00/0
06/30/16  5:23:48: EVT#192401-06/30/16  5:23:48: 100=Rebuild complete on PD 00(e0x20/s0)
06/30/16  5:23:52: EVT#192402-06/30/16  5:23:51: 114=State change on PD 00(e0x20/s0) from REBUILD(14) to ONLINE(18)
06/30/16  5:23:52: EVT#192403-06/30/16  5:23:52:  81=State change on VD 00/0 from DEGRADED(2) to OPTIMAL(3)
06/30/16  5:23:52: EVT#192404-06/30/16  5:23:52: 249=VD 00/0 is now OPTIMAL
06/30/16  5:23:52: ld sync: 01 unsync'd lds remaining

Event Sequence Number : 192422
Timestamp : 7/23/2016 ; 3:0:0
Event code : 39
Locale : Boot/Shutdown event
Class : Information
Description of the event : Patrol Read started
Argument Type Value: 0

Event Sequence Number : 192423
Timestamp : 7/23/2016 ; 8:34:24
Event code : 35
Locale : Boot/Shutdown event
Class : Information
Description of the event : Patrol Read complete
Argument Type Value: 0

Event Sequence Number : 192424
Timestamp : 7/30/2016 ; 3:0:0
Event code : 39
Locale : Boot/Shutdown event
Class : Information
Description of the event : Patrol Read started
Argument Type Value: 0

Event Sequence Number : 192425
Timestamp : 7/30/2016 ; 17:29:56
Event code : 35
Locale : Boot/Shutdown event
Class : Information
Description of the event : Patrol Read complete
Argument Type Value: 0

DELL BIOS UPGRADE FAIL / NO BOOT / SYSTEM HEALTH INDICATOR FLASHING AMBER

• I am/was Running Windows Server 2012 Standard.
• BIOS was 2.2.3
• I downloaded the latest BIOS for upgrade for x64 OS (Server 2012)
• As Administrator I ran the program T110-II_BIOS_G8T83_WN64_2.8.0.EXE obtained from the DELL URL Drivers and downloads for PowerEdge T110 II BIOS Version 2.8.0
• All  went well and was informed that I would be logged off in less than 1 minute.
• The Server restarted. All good so far!
• I powered off the Server. (pulled the power plug for a cold boot) as instructed.

  Expecting the BIOS to now be version 2.8.......

• Plugged in the power chord
• The Server started normally
• I noticed that the BIOS was still 2.2.3.
• OK, so I logged in as Administrator and ran the procedure again, as you do.
• I followed the bouncing ball, again.
• I was logged off, as before and the server restarted.
• I powered off again. ( pulled the power plug).
• Plugged in the power chord

  This is where is the part where it all turns bad

• Diagnostic lights 1,3,4 are on for a LONG time,
• The the HDD activity indicator comes on and then off (the HDD is spinning up),
• Then a Burst from the CPU FAN to full speed, then slowly to very quiet, fan is turning as I can feel air coming out of the CPU heat sink.
• The 1,3,4 lights go out,
• The System Health indicator comes on steady BLUE for 10 seconds and it turns AMBER and flashes.
• Power button light remains on, it does not work (no power down when pressed).
• I must remove the power chord to start the procedure all over again.
• Cycle repeats as before
• There is nothing on the video display, no beeps, no BOOT.

Everything was normal and working before the BIOS flash "update/fail"

HELP!

Is there a backup BIOS (second copy) is there a "jumper" that will help me out here, or do I have a DELL T110 II "paper weight" now?

Thanks in advance.

Rodney

My original server had 1 TB hard drive with 500GB in Raid 1 configuration. I had purchased two  4 TB hard drives from Dell with the plan to place these 2 hard drives in a RAIDs 1 configuration. Can my current RAID controller support this?  If not what would be the maximum hard disk it can support?  If my RAID controller can handle  less than 4 TB would I have the ability to upgrade my RAID controller then to support these two 4 TB or greater?  Please advise

FAN NUMBER ONE STOP AND THEN STARTS AFTER SHUTDOWN AND DOES NOT STOP

Hi guys

Just finish a mother replacement on an PowerEdge R630. iDrac8 can't visualize Storage information:

iDrac cannot display Storage information
RAC0501: There are no physical disks to be displayed.
1. Check if the host system is powered off or shutdown.
2. Check if the physical disks are inserted into the enclosure or attached to the backplane.
3. There are no out-of-band capable controllers detected.

But I could manage the both disks in a RAID 1 virtual disk via BIOS and the machine is working fine. Nevertheless I would like to have the Storage view in iDrac.

Versions are:

BIOS Version 1.5.4
Firmware Version 2.21.21.21
Lifecycle Controller Firmware 2.21.21.21

It is time to upgrade one of my R710 servers to 2012R2.  I have done this in the past using a DVD with no problem.  The issue is the latest download of the ISO file is 5.2GB.  I can't use a DVD this time.

I'd like to use the Unified Server Configurator so I get all the correct drivers.   I did the updates to the hardware to make this possible.  2012R2 is now an available OS selection.  The problem comes in at the last step when asked to insert the OS media.  I have tried to use a USB stick with no success.

Has anyone been able to do this using a USB stick or other non DVD method with the Unified Server Configurator?

Kris

Hi i'm trying to get my server up and running using a SATA hard drive, yet everytime i get to the windows installation page i receive the "no drives were found" error. Does anyone have any ideas as to what i need to do to get this working ? Installed on server is an SAS 6i/R RAID controller. I'm assuming i need to update the drivers but i can't seem to find the one i need anywhere ? 

Any advice would be greatly appreciated.

Hi, I've installed the H730p RAID into the R630 server, but the SAS cables from the front drive arrays A & B connect to the main board and have no play in them to connect to the RAID card.

I assume I need new SAS cables, but cannot find any reference to these anywhere.. Do I need new cables and what are the part numbers please?

many thanks

Pete

Dear experts:

Our iDrac 6 temperature warning threshold is set from 8°C to 42°C (PowerEdge R710). Is there a way to change these settings?

I would like to lower the upper threshold setting.

Thank you very much!

Hi, can anyone confirm that the correct battery for a perc H700 is P/N 312-0448

Thanks in advance.

I've been reading online about monitoring whether all the disks are ok on our Raid arrays on our Dell servers. The consensus seems to be that Dell Open Manager needs to be installed to get alerts of disk failures.

We recently had some disk issues on our Dell R420 which has idrac6 enterprise installed. It DID notify us of a "punctured" disk, telling us to replace it, but DID NOT alert us when another disk failed completely and degraded the array. Seems strange.

We just installed some R210 servers and the idrac6 enterprise installed on those doesn't seem to show physical disk status even after firmware update of the idrac.

We're really looking for a simple solution.

Unfortunately, I didn't take care of this several years ago.  However, it has become quite annoying.

The iDRAM LCD screen is a very dark blue.  You can barely see some white text scrolling across it, but you cannot read it.

Is there a way to increase the brightness?  Or is there another issue to address here?

Hi,

On iDRAC Details
Integrated Dell Remote Access Controller (iDRAC)
Version 1.0
PowerEdge M600

Java Details
java version "1.7.0_95"
OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)


While loading iDRACView
Display the following error message
"Unable to find certificate in Default Keystore for validation.
Please upload the certificate using the Java Control Panel and try again."

Screenshot of Error

Can anyone guide me to solve this problem and being able to load console normally?
Thanks in advance for your help!


Regards

Hello.

I'd like to upgrade my Dell PowerEdge R510 with 128Gb RAM.

Can I use 16Gb RAM x 8 dual rank? Like this one  <ADMIN NOTE: Broken link has been removed from this post by Dell>

Or I need to order quad rank memory for my upgrade? And if yes, does Dell provide such kind of RAM?

Thanks in advance.