Hi folks,

Would someone happen to know what the ports in use on iDRACs are. Particularly the Virtual Media Port.

Web searches yielded the following but that isn't from any official documentation.

22 Secure Shell, SSH
23 Telnet
80 http
443 https
161 SNMP
3668 Virtual Media Server
5900 Console Redirection
5901 Console Redirection

 It would be most appreciated if you can enlighten me on this matter. :) Thanks.

Bios upgrade attempted via dvd, however when it runs the message below comes up.

Dvd issue?  Or other ideas would be greatly appreciated.

Hello all,

I have a Dell Poweredge 2950 II server. Everything is going well with it. However, the DRAC 5 card is having some issues. Everything seems to work fine, expect the console redirect. I've tried three different browsers, Firefox, Chrome and IE all with errors. All three bark at me about certificate errors of course.

WIth IE and Chrome, I get the message:

With Chrome, I don't get an option to install a plugin, but with IE I do, and I clicked install, restarted the browser and everything, but still no luck.

However, with Firefox, I created a security exception, and when I click connect, the window shows nothing. Just a white screen. 

Any ideas? .

I currently have a PowerEdge 1950 - I had it running on a shelve for about 6-8 months and finally moved it to a 1u wallmount on the wall in my office. I was very careful in moving it and after installing it in the new spot and firing it up, the FANS are just going crazy. I have done some reading on the forums and what i have come to the conclusion on is that its the ESM chip on the motherboard that might be bad. The system is running ESXI 6 and i have 1 Windows 7 VM. Everything boots fine but the OMSA reads the fans at 11-16k and gives the following error on boot. 

so from reading up on that error, i went over to server supply and purchased me a new fan for slot 1 in the server. Was all hopeful and fired the server back up and it is the same error, and loud fans. So i then took the fan from slot 1 and swapped it with slot 4 - thinking that now slot 4 would error out, and it did NOT! so i think either something fried out - just coincidence with the move, or IDK what is going on.

Any Thoughts would help

:: Server INFO ::

Hello:

I have a Dell PE T410 server that I has iDRAC firmware version 1.80.00 (Build 17).  The system tag is <removed>.  I am trying the procedure that was supplied by Eddie on the following post:

I get to step 9 and it keeps failing.  Can you verify that this file is the correct one?

Thank you.

Firmware Rev 2.80.03

I have an r910 with an iDRAC6 enterprises adapter connected, to which I am unable to connect in either dedicated or shared modes.  USBs and NIC1 works as expected for host.  Re-seating the card did not help.

Attempt 1:

The router is configured to bind the assigned dedicated static IP to the MAC of the iDRAC.

iDRAC LAN Parameters:

NIC Selection: dedicated
Active LOM: No Active LOM

Results:
Shell access to host via NIC1: OK
iDRAC: no active LOM, no TLS/HTTPS access


Attempt 2: shared NIC1

Previous MAC-to-static-IP address binding was removed from router.

NIC Selection: shared
Active LOM: LOM1
IP address: set to static IP address of host.

Results:
Shell access to host: OK
iDRAC: no TLS/HTTPS access


Attempt 3: No router

I cabled my laptop NIC directly to the server's shared NIC1.

Results:
Shell access to host: OK
racadm: "ERROR: Unable to connect to RAC at specified IP address."


Attempt 4: Host-to-iDRAC using racadm:

Result:
racadm: "ERROR: Unable to connect to RAC at specified IP address."

Attempt 5: Broadcom's uxdiag utility

The references below indicate some success using "uxdiag -t abcd -mfw 1" via boot-disk to activate the potentially disabled management controller:

en.community.dell.com/.../19604305
en.community.dell.com/.../19378355
permalink.gmane.org/.../42033

Results: No improvement.

Suggestions?

I purchased a used Dell M820 blade with 4x E5-4610, 48x 8GB DDR3 RDIMMs (1.5V), a 10GB mezz card, and a H710P controller. I loaded everything up into the blade, put it in the chassis, and it refuses to POST. The orange light flashes, and the CMC just shows "iDRAC" not ready without any other information in the logs. The blade does not have the management riser, but I was told that it was not required? The moment the blade is placed in the chassis the orange light comes on. The chassis is running CMC FW 5.12. I've ensured that the chassis is set to max performance power. The chassis is running v1.0 midplane, would that be an issue (I don't need 10GB in Fab A)? 

Here's my troubleshooting steps:

1) Tried power cycling the entire enclosure without any blade seated.

2) I've tried removing individual components (H710P, reducing to minimum required amount of memory, 2 CPUs, no mezzanine card)

3) I have three of these blades so I've tried swapping around boards/CPUs to make sure nothing was "dead".

Any other suggestions?

I have a T110 ii that rebooted from Windows updates on Friday night as scheduled.  On reboot the server did not come back up.

I have complete the following steps:
- Power cycled
- Hardware reset by unplugging power cord and holding power button for 30 seconds
- Reseated RAM, CPU, RAID Controller, HDD and PSU connections
- Pulled and tested CMOS battery, good
- Minimum hardware boot, CPU, 1 stick of RAM, all other hard was disconnected
- Verified VGA cable is good
- Reset NVRAM
- Boot without RAM, no error codes or beeps

I can ping IDRAC but when connecting via browser page will not load. I am leaning towards a failed CPU for that reason.  Does anyone have any additional input?

I have a Dell Poweredge 2600 with 2 Intel Xeon 2.4 GHz processors and 3 GB of RAM. During startup it displays the following error message:

Invalid SCSI configuration; SCSI cable detected on connector SCSI B of the primary SCSI backplane, daughtercard not present.

However, there is no connection made on the SCSI B connector of the backplane. The SCSI A connector on the system board is connected to the optical drive and floppy. The SCSI B connector of the system board is connected to the SCSI A connector on the backplane.

I have attempted to flash the BIOS from a floppy without success. Can you please help me determine what troubleshooting steps I should perform to determine the cause of the error? Thank you for your help.

So i have been browsing around google and the Dell forums to find a solution to this but i am close to returning the server.

I have a Dell r710 with 24GB of RAM, 2 Quad 2.27GHz processors, the BIOS and iDRAC6 have been updated to the newest from a windows server 2008 enterprise.

So my iDRAC6 is on 2.85, i can use and download the boot playback java applet fine, however when i try and do a remote console using java i get the connection failed message box.

I am using IE11 in compatibility mode, the site is added to Intranet security with custom settings to basically allow everything and anything. The site is also added into the java security exception.

I am using Java 8 u77 (1.8.0), this is my console settings:

Not sure what else setting has to be checked/changed, but  i also attached the java console snapshot just in case as well.

What can i try to get this to work? i got the native client to work but i really would rather use the java client.

I had a VD offline due to a firmware bug.

I'm using the latest firmware version.

This is what I can see in our logs:

07/02/16  3:31:57: EVT#30207-07/02/16  3:31:57: 113=Unexpected sense: PD 05(e0x20/s5) Path 5000c500134f0029, CDB: 28 00 0f f1 b4 46 00 00 08 00, Sense: 6/29/cd
07/02/16  3:31:57: Raw Sense for PD 5: f0 00 06 00 23 5f 29 0a 00 00 00 00 29 cd ce 00 00 00
07/02/16  3:31:57: EVT#30208-07/02/16  3:31:57: 113=Unexpected sense: PD 05(e0x20/s5) Path 5000c500134f0029, CDB: 28 00 0a 0a 45 0e 00 00 08 00, Sense: 2/04/01
07/02/16  3:31:57: Raw Sense for PD 5: 70 00 02 00 00 00 00 0a 00 00 00 00 04 01 00 00 00 00
07/02/16  3:31:57: EVT#30209-07/02/16  3:31:57: 113=Unexpected sense: PD 05(e0x20/s5) Path 5000c500134f0029, CDB: 28 00 0b a0 e5 86 00 00 18 00, Sense: 2/04/01
07/02/16  3:31:57: Raw Sense for PD 5: 70 00 02 00 00 00 00 0a 00 00 00 00 04 01 00 00 00 00
07/02/16  3:31:57: EVT#30210-07/02/16  3:31:57: 113=Unexpected sense: PD 05(e0x20/s5) Path 5000c500134f0029, CDB: 28 00 09 88 c5 fe 00 00 02 00, Sense: 2/04/01
07/02/16  3:31:57: Raw Sense for PD 5: 70 00 02 00 00 00 00 0a 00 00 00 00 04 01 00 00 00 00
07/02/16  3:31:57: EVT#30211-07/02/16  3:31:57: 113=Unexpected sense: PD 05(e0x20/s5) Path 5000c500134f0029, CDB: 28 00 0e 90 4e 00 00 00 56 00, Sense: 2/04/01
07/02/16  3:31:57: Raw Sense for PD 5: 70 00 02 00 00 00 00 0a 00 00 00 00 04 01 00 00 00 00
07/02/16  3:31:57: EVT#30212-07/02/16  3:31:57: 113=Unexpected sense: PD 05(e0x20/s5) Path 5000c500134f0029, CDB: 28 00 0f f1 b4 46 00 00 08 00, Sense: 2/04/01
07/02/16  3:31:57: Raw Sense for PD 5: 70 00 02 00 00 00 00 0a 00 00 00 00 04 01 00 00 00 00
07/02/16  3:31:57: EVT#30213-07/02/16  3:31:57: 113=Unexpected sense: PD 05(e0x20/s5) Path 5000c500134f0029, CDB: 00 00 00 00 00 00, Sense: 2/04/01
07/02/16  3:31:57: Raw Sense for PD 5: 70 00 02 00 00 00 00 0a 00 00 00 00 04 01 00 00 00 00
07/02/16  3:31:58: MPI_EVENT_SAS_DISCOVERY: PortBitmap ff - Discovery is in progress
07/02/16  3:31:58: MPI_EVENT_SAS_DISCOVERY: PortBitmap 0 - Discovery is complete
07/02/16  3:31:58: Disc-prog= 0....resetProg=0 aenCount=0 transit=0 
07/02/16  3:31:59: MPI_EVENT_SAS_DISCOVERY: PortBitmap ff - Discovery is in progress
07/02/16  3:31:59:  MPI_EVENT_SAS_PHY_LINK_STATUS - PhyNum 5 DevHandle 6 Link 09
07/02/16  3:31:59:  MPI_EVENT_SAS_DEVICE_STATUS_CHANGE
07/02/16  3:31:59: MPT_EventDeviceStatusChange: Device Removed DevId 5 Tgt 5 Sas 5000c500:134f0029
07/02/16  3:31:59:  curQdepth 0 WaitQCount 4 path 0 flags:f0500005 
07/02/16  3:31:59:  DM_DevicePathRemoved devId 5 Tid 5 Path 0
07/02/16  3:31:59: PD 5 Removed :DeviceCount=6
07/02/16  3:31:59: MPI_EVENT_SAS_DISCOVERY: PortBitmap 0 - Discovery is complete
07/02/16  3:31:59: Disc-prog= 0....resetProg=0 aenCount=0 transit=0 
07/02/16  3:31:59:  DM_PdScsiTypeSet: Pd 5 type 1f isSata 0 
07/02/16  3:31:59: EVT#30214-07/02/16  3:31:59: 112=Removed: PD 05(e0x20/s5)
07/02/16  3:31:59: EVT#30215-07/02/16  3:31:59: 248=Removed: PD 05(e0x20/s5) Info: enclPd=20, scsiType=0, portMap=05, sasAddr=5000c500134f0029,0000000000000000
07/02/16  3:31:59: EVT#30216-07/02/16  3:31:59: 114=State change on PD 05(e0x20/s5) from ONLINE(18) to FAILED(11)
07/02/16  3:31:59: EVT#30217-07/02/16  3:31:59:  81=State change on VD 00/0 from OPTIMAL(3) to PARTIALLY DEGRADED(1)
07/02/16  3:31:59: modify_log_drv_state: oldState: 3  newState: 1  pinned_cache_present: 0  targetId: 0
07/02/16  3:31:59: EVT#30218-07/02/16  3:31:59: 250=VD 00/0 is now PARTIALLY DEGRADED
07/02/16  3:31:59: EVT#30219-07/02/16  3:31:59: 114=State change on PD 05(e0x20/s5) from FAILED(11) to UNCONFIGURED_BAD(1)
07/02/16  3:32:04: EVT#30220-07/02/16  3:32:04: 332=Enclosure PD 20(c None/p0) element (SES code 0x17) status changed
07/02/16  3:32:04: SES_BackplaneMapping: Un-Associated device on enclPd 20 StsCode = 6 elmtType 17 elmtIndex 5 slotPd =5 SasAddr =0
07/02/16  3:32:04: SES_MarkBadElement: enclPd 20 timeDiff e1a1b slot 5 badElmt 1 retryCnt 0 oldTime:0 currentTime:e1a1b 
07/02/16  3:32:07: DM_REC: TUR Failed, devId =5 
07/02/16  3:32:09: SES_BackplaneMapping: Un-Associated device on enclPd 20 StsCode = 6 elmtType 17 elmtIndex 5 slotPd =5 SasAddr =0
07/02/16  3:32:09: SES_MarkBadElement: enclPd 20 timeDiff 5 slot 5 badElmt 1 retryCnt 1 oldTime:e1a1b currentTime:e1a20 
07/02/16  3:32:11: MPI_EVENT_SAS_DISCOVERY: PortBitmap ff - Discovery is in progress
07/02/16  3:32:11:  MPI_EVENT_SAS_PHY_LINK_STATUS - PhyNum 5 DevHandle 6 Link 90
07/02/16  3:32:11:  MPI_EVENT_SAS_DEVICE_STATUS_CHANGE
07/02/16  3:32:11: MPT_EventDeviceStatusChange: Device Inserted Tgt 5 Sas 5000c500:134f0029
07/02/16  3:32:11: MPI_EVENT_SAS_DISCOVERY: PortBitmap 0 - Discovery is complete
07/02/16  3:32:11: DM_DevMgrIsChipInit 0 State 400 
07/02/16  3:32:11: DM: DM_DevSSUCallback TID 5 FAILED Cnt 0 Retry 0 Status 2
07/02/16  3:32:11: DM : DM_DevSSUCallback  SENSE Len 12 Code 70 senseKey 6 asc 29 ascq cd
07/02/16  3:32:11:  DM_DevNotifyRAID: Notify Done. Check for Removal 
07/02/16  3:32:11: gDevInfo=a11ebd20, size=140
07/02/16  3:32:11: Total Device = 7  
07/02/16  3:32:11: PD   Flags    State Type Size     S N Vendor   Product          Rev  P C ID SAS Addr         Port Phy DevH
07/02/16  3:32:11: ---  -------- ----- ---- -------- - - -------- ---------------- ---- - - -- ---------------- ---- --- ----
07/02/16  3:32:11: 0    f0400005 00020 00   22ecb25b 0 0 SEAGATE  ST3300657SS      0008 0 0 00 5000c500094d8a29 00   00  0a
07/02/16  3:32:11: 1    f0400005 00020 00   11177327 0 0 SEAGATE  ST3146356SS      HS11 0 0 01 5000c5001351cf75 01   01  0b
07/02/16  3:32:11: 2    f0400005 00020 00   11177327 0 0 SEAGATE  ST3146356SS      HS11 0 0 02 5000c50013514b99 02   02  0e
07/02/16  3:32:11: 3    f0400005 00020 00   11177327 0 0 SEAGATE  ST3146356SS      HS11 0 0 03 5000c500135178b1 03   03  0f
07/02/16  3:32:11: 4    f0400005 00020 00   22eec12f 0 0 HITACHI  HUS156030VLS600  A5D0 0 0 04 5000cca02a556ded 04   04  0c
07/02/16  3:32:11: 5    f0400005 00020 00   11177327 0 0 SEAGATE  ST3146356SS      HS11 0 0 05 5000c500134f0029 05   05  0d
07/02/16  3:32:11: 20   00400005 00020 0d   00000000 0 0 DP       BACKPLANE        1.07 0 0 20 500240807e894400 09   08  09
07/02/16  3:32:11: 100  00400005 00020 03   00000000 0 0 LSI      SMP/SGPIO/SEP    1909 0 0 ff                0 00   ff  00
07/02/16  3:32:11: PhyId 0 Sas 5000c500094d8a29 Type 1 IsSata 0, Smp 0:0
07/02/16  3:32:11: PhyId 1 Sas 5000c5001351cf75 Type 1 IsSata 0, Smp 0:0
07/02/16  3:32:11: PhyId 2 Sas 5000c50013514b99 Type 1 IsSata 0, Smp 0:0
07/02/16  3:32:11: PhyId 3 Sas 5000c500135178b1 Type 1 IsSata 0, Smp 0:0
07/02/16  3:32:11: PhyId 4 Sas 5000cca02a556ded Type 1 IsSata 0, Smp 0:0
07/02/16  3:32:11: PhyId 5 Sas 5000c500134f0029 Type 1 IsSata 0, Smp 0:0
07/02/16  3:32:11: PhyId 0 Sas 0 Type 0 IsSata 0, Smp 0:0
07/02/16  3:32:11: PhyId 0 Sas 0 Type 0 IsSata 0, Smp 0:0
07/02/16  3:32:11: Load Balance Statistics Path0PDs 0 Path1PDs 0
07/02/16  3:32:11: EVT#30221-07/02/16  3:32:11:  91=Inserted: PD 05(e0x20/s5)
07/02/16  3:32:11: EVT#30222-07/02/16  3:32:11: 247=Inserted: PD 05(e0x20/s5) Info: enclPd=20, scsiType=0, portMap=05, sasAddr=5000c500134f0029,0000000000000000
07/02/16  3:32:11: ArDiskTypeMisMatch : NO_MIXING_VIOLATION  array=0  destPD=5
07/02/16  3:32:11: EVT#30223-07/02/16  3:32:11: 114=State change on PD 05(e0x20/s5) from UNCONFIGURED_BAD(1) to UNCONFIGURED_GOOD(0)
07/02/16  3:32:19: EVT#30224-07/02/16  3:32:19: 332=Enclosure PD 20(c None/p0) element (SES code 0x17) status changed
07/02/16  3:36:53: mfiIsr: idr=00000020
07/02/16  3:36:53: Driver detected possible FW hang, halting FW.
07/02/16  3:36:53: Pending Command Details:

07/02/16  3:36:53: cmdId= 68: cmd=11, cmdStat=0, num_sg_elements=1, status=1 [PCI_COMMAND]
07/02/16  3:36:53: mfa=cd856800, mf=a041a000, mfSge=a041a028, bytesTransferred=0, next ffff
07/02/16  3:36:53: startTime=0, lines=a17c0680, lineMap=0, activeRecoveryCount=0, lockPromotedByRec=0
07/02/16  3:36:53: ldbbmAlreadyTried=0, ldbbmIssueWriteAsWV=0
07/02/16  3:36:53: ld=0, ioFlags=0, start_block=3fc6d0c6, num_blocks=8, savedNumBlocks=8
07/02/16  3:36:53: group: 0068
07/02/16  3:36:53: start_row=1fe368, start_strip=7f8da1, num_strips=1
07/02/16  3:36:53: ref_in_start_stripe=46, ref_in_end_stripe=4d, num_lines=1, num_lines_to_be_processed=1
07/02/16  3:36:53: wait_q_next_ptr=0, num_lines_in_wait_q=0, immediate_already_tried=0, bbmHead=ffffffff, bbmTail=ffffffff
07/02/16  3:36:53: rmw: op=0, error=0, first_data_arm=0, last_data_arm=0
07/02/16  3:36:53: wt: countRowsNotUsingReadPeer=0


07/02/16  3:36:53: cmdId=199: cmd=11, cmdStat=0, num_sg_elements=3, status=1 [PCI_COMMAND]
07/02/16  3:36:53: mfa=cd821c00, mf=a0466400, mfSge=a0466428, bytesTransferred=0, next ffff
07/02/16  3:36:53: startTime=0, lines=a185a190, lineMap=0, activeRecoveryCount=0, lockPromotedByRec=0
07/02/16  3:36:53: ldbbmAlreadyTried=0, ldbbmIssueWriteAsWV=0
07/02/16  3:36:53: ld=0, ioFlags=0, start_block=2e839706, num_blocks=18, savedNumBlocks=18
07/02/16  3:36:53: group: 0199
07/02/16  3:36:53: start_row=1741cb, start_strip=5d072e, num_strips=1
07/02/16  3:36:53: ref_in_start_stripe=6, ref_in_end_stripe=1d, num_lines=1, num_lines_to_be_processed=1
07/02/16  3:36:53: wait_q_next_ptr=0, num_lines_in_wait_q=0, immediate_already_tried=0, bbmHead=ffffffff, bbmTail=ffffffff
07/02/16  3:36:53: rmw: op=0, error=0, first_data_arm=0, last_data_arm=0
07/02/16  3:36:53: wt: countRowsNotUsingReadPeer=0


07/02/16  3:36:53: cmdId=1ab: cmd=11, cmdStat=0, num_sg_elements=2, status=1 [PCI_COMMAND]
07/02/16  3:36:53: mfa=cd833800, mf=a046ac00, mfSge=a046ac28, bytesTransferred=0, next 2b7
07/02/16  3:36:53: startTime=0, lines=a18632b0, lineMap=0, activeRecoveryCount=0, lockPromotedByRec=0
07/02/16  3:36:53: ldbbmAlreadyTried=0, ldbbmIssueWriteAsWV=0
07/02/16  3:36:53: ld=0, ioFlags=0, start_block=2623167e, num_blocks=10, savedNumBlocks=10
07/02/16  3:36:53: group: 01ab
07/02/16  3:36:53: start_row=13118b, start_strip=4c462c, num_strips=2
07/02/16  3:36:53: ref_in_start_stripe=7e, ref_in_end_stripe=d, num_lines=1, num_lines_to_be_processed=2
07/02/16  3:36:53: wait_q_next_ptr=0, num_lines_in_wait_q=0, immediate_already_tried=0, bbmHead=ffffffff, bbmTail=ffffffff
07/02/16  3:36:53: rmw: op=0, error=0, first_data_arm=0, last_data_arm=0
07/02/16  3:36:53: wt: countRowsNotUsingReadPeer=0


07/02/16  3:36:53: cmdId=260: cmd=11, cmdStat=0, num_sg_elements=14, status=1 [PCI_COMMAND]
07/02/16  3:36:53: mfa=cd8e2c00, mf=a0498000, mfSge=a0498028, bytesTransferred=0, next ffff
07/02/16  3:36:53: startTime=0, lines=a18be600, lineMap=0, activeRecoveryCount=0, lockPromotedByRec=0
07/02/16  3:36:53: ldbbmAlreadyTried=0, ldbbmIssueWriteAsWV=0
07/02/16  3:36:53: ld=0, ioFlags=0, start_block=3a413936, num_blocks=a0, savedNumBlocks=a0
07/02/16  3:36:53: group: 0260
07/02/16  3:36:53: start_row=1d209c, start_strip=748272, num_strips=2
07/02/16  3:36:53: ref_in_start_stripe=36, ref_in_end_stripe=55, num_lines=1, num_lines_to_be_processed=2
07/02/16  3:36:53: wait_q_next_ptr=0, num_lines_in_wait_q=0, immediate_already_tried=0, bbmHead=ffffffff, bbmTail=ffffffff
07/02/16  3:36:53: rmw: op=0, error=0, first_data_arm=0, last_data_arm=0
07/02/16  3:36:53: wt: countRowsNotUsingReadPeer=0


07/02/16  3:36:53: Total Pending Commands = 4
[0]: fp=a00bee78, lr=a0c41918  -  _MonTask+1a8
[1]: fp=a00bf0a0, lr=a0cc17e4  -  mfiIdrIsr+124
[2]: fp=a00bf0b8, lr=e401e960  -  dispatchIsrs+c4
[3]: fp=a00bf0e8, lr=e401e9f0  -  external_IRQ+34
[4]: fp=a00bf100, lr=e401e074  -  wrapper__External_IRQ+74
[5]: fp=a00bf150, lr=a0c68358  -  TaskStartNext+12c
[6]: fp=a00bf190, lr=a0c519c0  -  set_state+54
[7]: fp=a00bf278, lr=a0c536d0  -  raid_task+864
[8]: fp=a00bffa0, lr=a0cbd384  -  _main+aa4
[9]: fp=a00bfff8, lr=fe001d58  -  __start+ce0
MonTask: line 3622 in file ../../raid/1078dma.c
UIC_ER=10000ac:5500063, UIC_MSR=0:40, MSR=21000, sp=a00bee78
MegaMon> 
T0: LSI Logic ROC firmware
T0: Copyright (C) LSI Logic, 2004
T0: Firmware version 1.22.52-1909 built on Sep 21 2012 at 15:29:16

T0: pciInit: O_PCI_SERVICE = 00000005
T0: Initializing memory pool size=00300B24 bytes
T0: Press '!' within 3 seconds to enter debugger before INIT
T3: LogInit: Flushing events from previous boot
T3: EVT#30225-07/02/16  3:36:53:  15=Fatal firmware error: Driver detected possible FW hang, halting FW.

T3: EVT#30226-07/02/16  3:36:53:  15=Fatal firmware error: Line 3622 in ../../raid/1078dma.c

R620 server is shutdown with below lifecycle log.

2016-04-19T09:59:13-0400 SYS1001 System is turning off.
2016-04-19T09:59:13-0400 SYS1003 System CPU Resetting.

Firmware versions,

BIOS: 2.5.2 , iDRAC: 2.21.21.21 

Please let me know if further information is required. 

Are there any known issue?

Hi all,

I'm going to run a deep learning project with Nvidia GeForce GTX Titan X GPU.

One of my options is utilizing a PowerEdge T630 server.

So, I have two questions:

1- Does T630 support Ubuntu OS?

2- Does T630 support Nvidia GeForce GTX Titan X?

Regards,

.Hi all

I have a Dell PowerEdge 2950 and when you power it on and press CRTL R to load the integrated raid bios it comes up with the below message (screenshot) and the raid bios config utility does not load at all.

Does anyone have any ideas?

Current BIOS version 2.7.0 / 2x 146gb 15k SAS drives installed (blank). The Integrated perc controller is set to Enabled in the system bios

Many thanks

Jamie

Hi all,

I'd like to start by saying that I'm somewhat new to building out my own server environment as my PowerEdge T300 is the first piece of actual server purpose-built hardware that I've owned so I apologize in advance for my ignorance. So here's my dilemna...

The plan is to set up ESXi 6.0 on this T300 and if possible also install the OMSA 8.2 VIB into ESXi 6.0. Upon reviewing the documentation listed for the different ESXi VIB releases here I've found that only the ESXi 5.1 VIB lists the PowerEdge T300 as being compatible.

So my underlying question here is, is the "compatible systems" listing just purely for technical support reasons, is there software/hardware limitations, or is this just some type of feel-good type of deal? Any help is greatly appreciated. Thanks!

Got a T110 running Win2K3 SP2 Standard x86, but not totally content with the on-board Broadcom gigabit Ethernet adapter.  Tempted to upgrade to something Intel based, found one, but realized there might be some conflict caused by using it.  I originally wanted to get the "INTEL PRO 1000 CT PCIe 1x" from Amazon for like $30 for the price, but found 2 reviews that specifically said that their T110 servers could not take the card because of some motherboard/boot error after installing the card.  I'm guessing this might have something to do with multiple network boot agents on BIOS startup, but I'm not sure. I'm thinking of maybe just getting it, and making it a point to disable the onboard Ethernet before installing the cards to see how it goes.  But there is some hesitation ...

Has anyone here upgraded from their onboard Ethernet to something more robust?  Recommendations? Many Thanks in Advance!

Hello. Tell me please compatible models of SSD drives to 400 GB for the server FC430. If it is possible eMLC. Notified uSATA 1,8in drives, and I'm confused.

Hello,

we have a PowerEdge R510 server with Perc H700 Raid controller  installed, configured to run with Raid-5. So far we have configured 2 virtual disks. The first virtual disk consists of 4 hdd x 2 TB each, configured with Raid-5.

The second virtual disk has 4 hdds  x 3 TB each. 

We have noticed that 2 hard disks (of 2 TB each), from the first pool, blink orange. We run the ESET tool,  and smart tool (the server runs centos), and get from the report, that the hard disks are in predicted failure. Also from the report we noticed that the battery of the controller is in failed state

What are the proper steps to follow to replace the battery and the drives?

Best regards

Maria

Maria

I have a Win 2008 R2 (and then upgraded to 2012 R2) DHCP server which was getting loads of BAD_ADDRESS filling up the scope in vlan1.  All other scopes for other vlans were unaffected.  Wireshark indicated a the dell mac address for the management of IOA which the switch showed on our PortChannel3 (two 10gbe fiber optic interfaces).

But in our IOA config we have a static IP set of 10.1.0.103/16. The DHCP server is at 10.1.1.1/16 and also offers ip's in other scopes (vlan2 10.2.1.1/16, vlan3 10.3.1.1/16, vlan4 10.4.1.1/16 and vlan5 10.5.1.1/16).

I had to put the Dell IOA mac address in the DHCP deny filter list and enable it so that it would not respond and plug up our address space full of BAD_ADDRESS.

Any idea why the IOA is doing dhcp requests even though we set it for a static IP?

Just purchased a new R230 and trying to setup. One of the steps is Update the Firmware. We do not use Windows, so I downloaded the firmware file Firmware_635G9_WN64_2.23_A00-00.EXE from the product support site to my laptop. I then from Firefox on my laptop logged into the iDRAC on the server. I went to iDRAC Settings -> Update and Rollback and uploaded the file. After I upladed the file I got the following Status: Unable to complete the firmware update operation because the specified firmware image is for a component that is not in the target system inventory. How do I update the firmware?