I am attempting to locate either a third party or Dell tool that will perform an extended diagnostic test on the RAID controller on a PowerEdge 2950. I've attempted to use the Dell Systems Service and Diagnostic Tool but evidently there is a problem with this tool as it is not bootable and Dell will not provide support for the tool itself. Any other ideas? In addition the RAID controller is also not registering in OpenManage on this server.

Hi,

I am wondering...

Is it possible to change my current 136GiB (raid 1) hard drives to 2TiB drives without changing virtual disk configuration in my R710 ver. II server, H700 controller?

My theory:

1. plug out one of the small drive and plug in the first 2TiB, wait until the sync done.

2. Plug out the second drive and plug in the next 2TiB.

After this can i use all space on my 2TiB drives?

Thanks, Robert

Hope this newbie can get some help here!

our poweredge 1800 Raid controller Perc4/dc failed last week.

i installed the exact same controller D9205 and rebooted.

I can now only get this to boot up if I disable the Primary scsi controller and the embedded sata controller.  at which point the system boots up just fine with all system go except for the PowerVault

100T dat72 tape drive. when i check under storage controll, libaries it has a red circle and a white x beside it.

If I reboot and go into setup and change either or both the primary scsi controller and the embedded sata controller, then the system blinks a red light and will not boot up.

i believe there is some type of configuration error in the  bois but not sure? maybe IRQ ASSIGNMENT.

any feed back is more than welcome!!

Running VSphere 5.5 now trying to plan the upgrade to vSphere 6 U2.  Searching for any specific requirements or update necessities prior to performing the upgrade.  Appreciate any experience or insight your willing to share.

Thanks Chris

I have an older Dell PowerEdge R510 I have had laying around. I was going to turn it into a NAS but I need a RAID card. When I picked it up a little bit back it came with a PERC H200 but I need JBOD support. Someone recommend picking up a used PERC H310 since I can make certain drive non-raid and others part of a RAID which would be nice.

The issues I read that the PERC H310 had some performance issues a few years back.

Do the issues being referred to in the thread still exist or have they been resolved?

If they still exist can someone recommend another card in the PERC series I could use?

Server reboot this am to a black screen saying BIOS not installed, no virtual disk found, then goes through the procedures to a network boot.  Can this virtual disk be recovered?  Thanks.

Hi,

I'm trying to work out the correct procedure to replace a drive in a mirror that has had a SMART failure prediction.  The drive is still running and the array is still showing as optimal but the disk is showing as "failure predicted."  

The server is an R720 with embedded PERC H710P Mini.  It's running Linux and we have Dell OMSA and MegaCli64 installed.  I need to do this without downtime.

We have 2x 900GB disks in a RAID-1 volume (virtual disk 0) and 7x 600GB in RAID-6 (virtual disk 1).  We are not using hot spares.  The problem disk is the second disk in the RAID-1 array - 0:1:1 (or [32:1 according to MegaCli).

I've found a walkthrough guide but I'm not sure if this is the correct procedure and I can't afford to "test" it or get it wrong:

Walkthrough: Change/replace a drive

Set the drive offline, if it is not already offline due to an error

MegaCli64 -PDOffline -PhysDrv [32:1] -a0

Mark the drive as missing

MegaCli64 -PDMarkMissing -PhysDrv [32:1] -a0

Prepare drive for removal

MegaCli64 -PDPrpRmv -PhysDrv [32:1] -a0

Change/replace the drive

            Pull out the problem disk and insert replacement disk.

Re-add the new drive to your RAID virtual drive and start the rebuilding

MegaCli -PdReplaceMissing -PhysDrv [32:1] -Array0 -row1 -a0
MegaCli -PDRbld -Start -PhysDrv [32:1] -a0

Some notes/questions about this:

1) Auto-rebuild is enabled on the controller.  Are any of the above steps unnecessary?

2) Any idea how long this might take?  I know it's highly dependant on the rebuild rate setting and the amount of activity on the server but I'm just after some real world examples on similar hardware.

3) With the -PDReplaceMissing command, I've based the values of -ArrayN and -rowN on the following output (cut to show the relevant disk):

# ./MegaCli64 -CfgDsply -aALL

==============================================================================
Adapter: 0
Product Name: PERC H710P Mini
==============================================================================
Number of DISK GROUPS: 2

DISK GROUP: 0
Number of Spans: 1
SPAN: 0
Span Reference: 0x00
Number of PDs: 2
Number of VDs: 1

Physical Disk: 1
Enclosure Device ID: 32
Slot Number: 1
Drive's position: DiskGroup: 0, Span: 0, Arm: 1
Enclosure position: 1
Device Id: 1

From what I've read, the -ArrayN number is the Span Reference from the above output, but examples I've seen show a '0' in the command rather than the 0x00 that I see in my output.

Thanks for your assistance,

Mark

Dell R510-12, PERC H700, 12 x10k SAS drives

I've noticed unknown errors in the controller debug log

04/20/16  8:20:21: MPT_REC: SMP Request Failed rdm 80668800, devId 0100, devHandle ff00, IoReply c0466d00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:22: MPT_REC: SMP Request Failed rdm 808af800, devId 0100, devHandle ff00, IoReply c047ef00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:23: MPT_REC: SMP Request Failed rdm 80526200, devId 0100, devHandle ff00, IoReply c0476c00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:25: MPT_REC: SMP Request Failed rdm 806f7000, devId 0100, devHandle ff00, IoReply c049ed00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:26: MPT_REC: SMP Request Failed rdm 808e1600, devId 0100, devHandle ff00, IoReply c04b7500, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:27: MPT_REC: SMP Request Failed rdm 8071fa00, devId 0100, devHandle ff00, IoReply c0461800, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:28: MPT_REC: SMP Request Failed rdm 8056d200, devId 0100, devHandle ff00, IoReply c049a100, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:30: MPT_REC: SMP Request Failed rdm 805f9200, devId 0100, devHandle ff00, IoReply c04a1000, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:31: MPT_REC: SMP Request Failed rdm 8075ae00, devId 0100, devHandle ff00, IoReply c0470b00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:32: MPT_REC: SMP Request Failed rdm 808df200, devId 0100, devHandle ff00, IoReply c048e400, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:33: MPT_REC: SMP Request Failed rdm 8085a600, devId 0100, devHandle ff00, IoReply c04c5b00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:35: MPT_REC: SMP Request Failed rdm 8089c400, devId 0100, devHandle ff00, IoReply c04c2000, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:36: MPT_REC: SMP Request Failed rdm 8059f200, devId 0100, devHandle ff00, IoReply c04c0a00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:37: MPT_REC: SMP Request Failed rdm 80868800, devId 0100, devHandle ff00, IoReply c0462b00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:38: MPT_REC: SMP Request Failed rdm 80692c00, devId 0100, devHandle ff00, IoReply c0499c00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:40: MPT_REC: SMP Request Failed rdm 80592e00, devId 0100, devHandle ff00, IoReply c0458800, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:41: MPT_REC: SMP Request Failed rdm 80630e00, devId 0100, devHandle ff00, IoReply c048b200, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:42: MPT_REC: SMP Request Failed rdm 8062a600, devId 0100, devHandle ff00, IoReply c0495c00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:43: MPT_REC: SMP Request Failed rdm 80698200, devId 0100, devHandle ff00, IoReply c0489200, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:45: MPT_REC: SMP Request Failed rdm 807a3e00, devId 0100, devHandle ff00, IoReply c0463b00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:46: MPT_REC: SMP Request Failed rdm 807d8200, devId 0100, devHandle ff00, IoReply c04a8c00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:47: MPT_REC: SMP Request Failed rdm 80624600, devId 0100, devHandle ff00, IoReply c045da00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:48: MPT_REC: SMP Request Failed rdm 808aea00, devId 0100, devHandle ff00, IoReply c048f600, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:50: MPT_REC: SMP Request Failed rdm 805a9800, devId 0100, devHandle ff00, IoReply c04be300, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:51: MPT_REC: SMP Request Failed rdm 80771600, devId 0100, devHandle ff00, IoReply c045d100, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:52: MPT_REC: SMP Request Failed rdm 808fbe00, devId 0100, devHandle ff00, IoReply c046de00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:53: MPT_REC: SMP Request Failed rdm 807fda00, devId 0100, devHandle ff00, IoReply c048c400, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:55: MPT_REC: SMP Request Failed rdm 8070c200, devId 0100, devHandle ff00, IoReply c046e900, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:56: MPT_REC: SMP Request Failed rdm 808a5000, devId 0100, devHandle ff00, IoReply c0478600, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:57: MPT_REC: SMP Request Failed rdm 80850c00, devId 0100, devHandle ff00, IoReply c0483400, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:20:58: MPT_REC: SMP Request Failed rdm 8068de00, devId 0100, devHandle ff00, IoReply c0466e00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:21:00: MPT_REC: SMP Request Failed rdm 80850200, devId 0100, devHandle ff00, IoReply c046cd00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:21:01: MPT_REC: SMP Request Failed rdm 807b2600, devId 0100, devHandle ff00, IoReply c04acb00, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:21:02: MPT_REC: SMP Request Failed rdm 805eec00, devId 0100, devHandle ff00, IoReply c0482800, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:21:03: MPT_REC: SMP Request Failed rdm 808e2600, devId 0100, devHandle ff00, IoReply c04a7800, iocSts 0090, IOCLogInfo 00000000
04/20/16  8:21:05: MPT_REC: SMP Request Failed rdm 808bf400, devId 0100, devHandle ff00, IoReply c0462e00, iocSts 0090, IOCLogInfo 00000000

It seems that the errors always occur in batches of 36 entries.

What should I do with it?

I found one of the three disks (disk 0:2) status as "Foreign". I am not sure what I have to do.On front of this drive is steady green light but no activity. In OpenManage status of this drive is "Foreign" other two drives are "Online", system is working fine but I know I have to fix this ASAP.

Please help.

Thanks

What is the procedure for this? Can I just plug in the drive and reboot, go into the controller (PERC H710P), break the mirror, add the new drive and former RAID1 drive and create the RAID 5 array?

Will this work?

PowerEdge R610 - Boot from OCZ RevoDrive 350 Mystery

We have a really annoying problem with our PowerEdge R610 and OCZ RevoDrive 350 combo.

Preface

The PowerEdge R610 is absolutely updated from the latest Dell Server Update Utility (Version 16.04.00, A00; Release date: 11 Apr 2016).

The integrated PERC H700 controller is used to manage the 6 SATA SSDs in a RAID5 configuration to a data storage, not host a boot drive or partition.

The server is set to UEFI mode.

The OCZ RevoDrive 350 is in factory default, no firmware update is available at this time, the latest (driver version 2.0.0.4794, release date December 23, 2014) driver is used for the operating system.

The operating system is Windows Server 2012 R2

The Problem

I’ve installed Windows Server 2012 R2 with the UFEI’s Unified Server Configurator and a little help from Working Hard In IT https://blog.workinghardinit.work/2012/08/24/how-to-deploy-windows-server-2012-on-dell-uefi-nownotes-from-the-field/

It was all OK. The EFI partitions was created, Windows was successfully installed, and booted up well. I started to set things up, installed additional roles to the server, updated from windows update, when the first restart came. I was awarded with the automatic recovery mode. I tried all the available options, but none of them helped me out. When I restarted the server, it always brought back the recovery console. So I checked out command prompt and lunched diskpart.

As you can see, Disk 0 is the RAID5 volume from the PERC H700. Disk 1 is a USB drive connected to the back side USB port (contains only the OCZ drivers), Disk 2 and 3 are the iDRAC virtual drives. And YES, there is NO other drive. Especially no OCZ RevoDrive 350, 223 GB. so where could it be? First, I removed it from the slot, reinserted it, checked it if it sits securely in the riser, everything was all right. Put the cover back, and started the machine. Same error, I found myself in the recovery console. Removed the card, inserted in a Precision T5500, no problems at all. The only difference is that the T5500 is not UEFI aware. So I put the card back in the R610 and started the installation process from the beginning. I thought I caused the unbootable state. Back in the USC, OS deployment, next, next, finish. At the end I was convinced the installation will begin after rebooting:

But this is what happened:

If you don’t speak Hungarian, this is the login screen of the Windows Server 2012 R2. It simply booted to Windows. I haven’t seen the Press any key to boot from CD or DVD… line either.

As you can see, the drivers are loaded, the volumes are up and running.

Now I started to dig deeper.

What I found: The PCIe SSD will be lost on boot, if I do anything from the followings:

Update certain things from Windows Update

Install Driver(s)

Update Driver(s)

Update Firmware(s)

Basically anything that triggers a UEFI (re)initialization on boot process.

After this, I have to press F10 and walk through the USC’s OS deployment wizard, to get back in Windows.

But this is not the intended way to operate a server. So ANY idea, help, articles from anywhere are appreciated.

We have a PowerEdge 2950 with a PERC 6/i controller. The six Seagate ST3300656SS drives in the server are configured into one two disk RAID-1 array and one four disk RAID-10 array. One of the disks in the RAID-10 array has failed. The disks in this array are 0:0:2, 0:0:3, 1:0:4 and 1:0:5.

We replaced the failed disk, but the new one is stuck in the "Ready" state. When we attempt to add the drive as a hot spare to Virtual disk 1, PERC says that "There are currently no disks that are available, large enough, or of the correct type to be used as a hot spare for this virtual disk."

Looking at the physical disks on connector 1, I can see that there are two drives, 1:0:4 and 1:0:5. They are both Seagate ST3300656SS disks. Disk 1:0:4 has a capacity of 268.38GB and is in the "Ready" state. Disk 1:0:5 has a capacity of 278.38GB and is in the "Online" state. If they are the same model disk, why is one smaller than the other? Better yet, how can I fix this so that we can add the disk to the array?

Any help that you could provide would be greatly appreciated. Thank you.

Hi,

My server won't get beyond this screen.  I've tried starting and choosing F2 and F11, but it always come back to this screen.  And it takes forever to get there too.

No boot drive found?  Shouldn't it find one of the hard drives?  Or is it telling me that the embedded sata controller has died?  The server is 2 hours away, so I can't look at the cable.

Here are the drive specs:  331-2392 : PERC S100 (Embedded SATA Softw are RAID) supporting 2 Hard Drives - RAID 0

What am I missing?

Thanks,

Bruce

Hello all,

Here is the situation.  One of my clients has a Dell PowerEdge T620 that has to RAIDs.  Group 0 is a RAID 1 with hard drives 0 and 1.  Group 1 is a RAID 5 with hard drives 2-6.  The RAIDs are hardware RAIDs and not software ones.  I do CTRL+R to get to the RAID controller system on server boot.

Drive 6 came up with a predictive failure (flash once green, flash once amber, then no flash, repeat).  It is not stating that it is bad in the RAID software.  In the Dell Open Manage software it states that it is a non-critical error.  I called Dell and they are sending a replacement drive of the same type, style, and size.

Here is my question:  since this is a critical server what is the best way to replace the hard drive and have the RAID rebuild itself.  Do not want to lose any data on this since this is an EMR system.

Yes I am assuming that the RAID will rebuild itself, so I must ask if this is also true, will a RAID 5 system rebuild itself when a hard drive is rebooted?

Thanks,
Kelly W

Hello all

I have a Dell R320, I recently purchased a new Intel DC S3700 to fit in my system and run ESXI 6.0. I've noticed that I am not picking up disk health type attributes (I think these are known as SMART) from the IDRAC. Is this normal? Or do I need to do a firmware upgrade to put Dell firmware on? If so how do I upgrade the firmware as I using ESXI and do not have access to another server to do the upgrade on? I am a relative novice to IDRAC, and don't see any errors or exclamation marks anywhere in the GUI but it is quite possible I am looking in the wrong place?

Status
Name Solid State Disk 0:1:0
Device Description Disk 0 in Backplane 1 of Integrated RAID Controller 1
State Non-RAID
Operational State Not Applicable
Slot Number 0
Size 185.75 GB
Block Size 512 bytes
Security Status Not Capable
Bus Protocol SATA
Media Type SSD
Hot Spare No
Remaining Rated Write Endurance Unavailable
Failure Predicted No
Power Status On
Progress Not Applicable
Used RAID Disk Space 0.00 GB
Available RAID Disk Space 185.75 GB
Negotiated Speed 6 Gbps
Capable Speed 6 Gbps
SAS Address 0x4433221104000000
Part Number
Manufacturer ATA
Product ID INTEL SSDSC2BA20
Revision 5DV10265
Serial Number BTTV334601ZB200GGN
Manufactured Day 0
Manufactured Week 0
Manufactured Year 0
Form factor 2.5 inch
T10 PI Capability Not Capable
Controller PERC H310 Mini (Embedded)
Enclosure BP12G+ 0:1

The following output is from the 500GB disk which came with the server, this also doesn't show the SMART info:

Status
Name Physical Disk 0:1:3
Device Description Disk 3 in Backplane 1 of Integrated RAID Controller 1
State Non-RAID
Operational State Not Applicable
Slot Number 3
Size 465.25 GB
Block Size 512 bytes
Security Status Not Capable
Bus Protocol SATA
Media Type HDD
Hot Spare No
Remaining Rated Write Endurance Not Applicable
Failure Predicted No
Power Status Spun Up
Progress Not Applicable
Used RAID Disk Space 0.00 GB
Available RAID Disk Space 465.25 GB
Negotiated Speed 3 Gbps
Capable Speed 3 Gbps
SAS Address 0x4433221107000000
Part Number TH02R42K212335230005A00
Manufacturer ATA
Product ID ST500NM0003 9ZM1
Revision GA0A
Serial Number Z1W3JRZP
Manufactured Day 0
Manufactured Week 0
Manufactured Year 0
Form factor 3.5 inch
T10 PI Capability Not Capable
Controller PERC H310 Mini (Embedded)
Enclosure BP12G+ 0:1

This system was working perfect with ESXi and was simply rebooted during maint window.

Now it fails to boot - at all.

Errors and system inventory below. 

Dell R520

Drac:  Integrated Dell Remote Access Controller 2.30.30.30 (Build 50)

Inventory:
Dell R520:

Integrated Dell Remote Access Controller 2.30.30.30 
Broadcom Gigabit Ethernet BCM5720 - 7.10.64 
Broadcom Gigabit Ethernet BCM5720 - 7.10.64 
BIOS 2.4.2
PERC H710 Mini 21.3.2-0005 
Disk 0 in Backplane 1 of Integrated RAID Controller 1 PA09 - ST2000NM0011 
Disk 1 in Backplane 1 of Integrated RAID Controller 1 PA09 - ST2000NM0011
Backplane 1 1.00 
Lifecycle Controller 2.30.30.30 
Dell 64 Bit uEFI Diagnostics, version 4247, 4247A1, 4247.2 4247A1 
Dell OS Driver Pack, 15.07.07, A00 15.07.07 
OS COLLECTOR 1.1, OSC_1.1, X10-00 OSC_1.1 
System CPLD 1.0.2

Initializing firmware interfaces... 
Initialization complete.

Disconnecting UEFI drivers. Please wait...
ERROR: <HANG HERE>

- OR -

ERROR: Sometimes SOL serial console gives:

Exception Inside the Exception Handler
Type: General Protection Fault (13) Source: Software (UEFI0011)
AX=0000000000000000 BX=0000000000000000 BP=00000000CCA85768 SP=00000000CCA85630
CX=0000000000000008 DX=0000000000000040 R8=0000000000000000 R9=0000000000000008
SI=AFAFAFAFAFAFAFAF DI=AFAFAFAFAFAFAFAF SS=0018 CS=0038 Flags=00010202
IP=00000000CCADA55D

- OR -

ERROR: Sometimes during boot there is this message:

FW could not sync up config/prop changes for sme of the VD's/PD's
Press any key to continue, or 'C' to load the configuration utility.

(this can be bypassed and continues to boot but it still hangs at:
Disconnecting UEFI drivers. Please wait...

-

Hi There,

I've posted a relative question earlier in  this community and now I'm repeating the same. It was all fine after the disk replacement, however 25th which I didn't notice and a drive on the bay went back to fail mode on a span without any issues. This is exactly the same issue earlier as well. Below seen is a screen that I have taken from Dell's OMSA, logs!

I have the failed disk that I have taken out earlier, is there possibility diagnose the disk and put it back by formatting?

I have inherited a Dell PowerEdge 840 with 2x 64GB SAS drives.  I have many SATA 500GB -1TB drives that I'd like to use.  How can I convert this server from SAS to SATA?  I am told that this system can support either SAS or SATA.

Hi,
I have a poweredge 2900 server with a PERC 6/i Integrated controller with 5 hard drives, 2 in Mirror and 3 for raid 5.

So my raid 5 has a failed drive, it clicks (just 1 drive). Anyway i ordered a replacement drive from dell and sent me a new HD, but its a different model from the other 2 drives. I did tell them in my emails this was for a old server and gave them the model of server.

Can this work?   (this new drive is also bigger)

Thanks

Hello All

I'm the I.T. guy for my Dad's small business. I help them on the side.

They recently bought a used PowerEdge 2900 server with 4 internal SCSI disk drives

This server also has a Dell SAS 5/i Integrated Controller

I want to install Windows 2008 R2 standard on this server and use it as a File Server and a place to host QuickBooks Enterprise. 

The problem I'm running into is that I cannot find in the Bios or anywhere in the server boot utilities where I can configure the 4 internal disks to become a RAID 5 array. I want to do that and THEN install the Windows Server OS. I've used the latest Dell Server Build Utility and also updated all the firmware to the latest builds. The Server Build Utility won't let me configure the RAID array.  What am I missing here?

Thank you for your help!!