Bom dia, estou enfrentando uma dificuldade ao instalar o sistema operacional Linux Ubuntu server 14.04 no servidor Dell PowerEdge R900. Consigo fazer todo o processo de instalação porem ao dar o boot o sistema não sobe, pelo que vi ha uma incompatibilidade entre o sistema e a controller. Quando desabilito a controller o hd não é mais reconhecido no decorrer da instalação do Ubuntu, há alguma alternativa de instalar sem a controller ou alguma imagem customizada pela dell para que possamos instalar no R900?

Atenciosamente,

I have a T610 with an internal HW RAID card (linux thinks it's a type of LSI MegaRAID SAS 1078) card.

The slots are 3.5" size, so 8 drives are supported internally.

In 3 of the slots I have a RAID5 of 3 x ~70G  15K SAS disks -- In the other 5 slots, I had some 2GB SATA drives as a RAID5 which have now been relocated to an external box (& 2nd LSI-type controller).

In 4 of the internal slots attached to the Dell-Perc card, I want/have put/ 4x128G SSD's that I thought I might use in a RAID10 -- giving me a 512G HD that I want to use to replace my aging 70G SAS drives.  I figure it should be faster and more secure w/RAID10, but as soon as they power up, the slots they are in start blinking *orange*, and the LCD display says it detects disk errors.  Note -- all of the SSD's are attached to the standard dell disk-cartridges for the T610 and all seem to make good connections.

I booted off the current SAS drives, to try to see what the problem on the SSD's was.

From linux -- the SSD's are not only "visible", but all work "just fine" -- I partitioned all of them, and ran full-disk writes of patterns, and reads of same and got no errors.  All the while, the LCD and slots
 are blinking orange, but I can't find any error messages from the OS regarding the disks.  I can use ipmi to read the log -- and the log isn't specific -- just says "disk error in drive 'x' (all of the 4 SSD's give this error).  Originally I had all of them in use in my work station (with a SAS /iR) in a RAID0 -- they gave no error in that box, and were configurable as a RAID0.

So why am I getting disk error indicators from the HW, but not at the OS level?

Is there any firmware upgrade I need -- AFAIK, they are just normal drop-in SATA replacement sata drives that just happen to store data in flash memory instead of rotating rust.  So why would the Dell HW even know or care what type of SATA drives they are, especially since I know they work?

Help in installing and getting rid of the disk-error indicators would be real helpful.

What do I need to do, or is there  FW upgrade for the internal controller to tell it that these SATA drives are "fine"?

Thanks much!

-linda

I want to add disk storage to an existing Dell PowerEdge T620 (service tag GTPKDV1). It currently has 7 300GB SAS 2.5" hot swap drives, two virtual drives (RAID1 300GB and RAID5 1116GB). There are 16 bays. 

Browsing the Dell store for server upgrade parts I am surprised to see only two form factors for 2.5" 10K rpm SAS drives. Only 300GB or 900GB. Nothing with higher speeds or higher capacity!? And I'm not even sure one of the search results is really 2.5" since the website product description does not indicate the size at all.

300GB  Manufacturer Part# : 15NM6 | Dell Part# : 342-2016 (accessories.dell.com/.../productdetail.aspx

900GB Manufacturer Part# : TPMWF | Dell Part# : 342-4143 (http://accessories.dell.com/sna/products/Hard_Drives_Storage/productdetail.aspx?c=ca&l=en&s=bsd&cs=cabsdt1&sku=342-4143&mfgpid=225343)

The 900GB is described as a Hybrid drive. What is a hybrid drive? Isn't SAS, SAS?

There are several results which all seem to be variations on the 300GB SAS6 10K 2.5" drive. Are they all the same product? Why the different part numbers?

Looking for the inf driver for Dell Power Edge r410, it has a Dell SAS 6IR controller. all the drivers available on Dell Support site are Executable files, and I'm not looking for that.!!

I already unzip restore all this exe files trying to find the files but unfortunately Storage Craft Recovery environment does not take it.

Basically needs the drivers for Power Edge R410 SAS 6/IR controller for Windows SBS 2011 and or Windows server 2008 that is basically the same.

if someone can point me to right direction i will really appreciated

I have a RAID 5 configuration with 4 Seagate Cheetah 10K.7 300GB U320 SCSI HDDs. One drive has failed and another is showing as an impending failure. I have identical replacement drives (ST3300007LC) on hand. Hot swapping the failed drive with a new one did NOT result in an automatic rebuild as it should have. I tried powering down and swapping out the drive, hot swapping it, tried with a different drive, etc. The new drive was not detected in OMSA, even with a global rescan.

I installed the new drive and accessed the PERC BIOS (CTRL+M). With the new drive in the same slot as the failed drive (0:0), it still showed as "Failed." With the new drive in a different slot (0:4) and the failed drive not physically present, 0:0 still showed as "Failed", while 0:4 showed as "Ready", but the drive capacity was 0MB. As a result, I cannot designate the new drive as a hot spare and begin a rebuild. Why would the PERC either not see an exactly identical HDD, or see it as having 0MB capacity? The PERC is not properly detecting the same drives as those that are already attached to the controller.

It's the same issue as was mentioned in this post: http://en.community.dell.com/support-forums/servers/f/906/t/19301482. However, the notion that 300GB HDDs are not supported with this PERC is not valid in my case. Ideas?

I have DELL PE 1950 with a PERC 5/I controller on it that I want to upgrade to lastest firmware, but from a windows server 2008 OS it says upgrade ok, but when I reboot the firmware version is still the old version.

Old version is 5.0.2-0003

New version is 5.2.2-0072

Im thinking that i need the firware verion between, but I cant find it any where on dells site.

Best regards

Lars

Hi , I have a T110 ii server and want to install a SATA SSD drive 
to install Windows Server 2012 R2 and in turn have configured 
( RAID1 ) SAS 2 discs that came with the server. 
So far what I did it is to connect the SATA SSD SATA ports 
on the motherboard and the BIOS change the
settings RAID to AHCI mode, but when it comes
 to install via USB OS recognizes me 
the record but tell me there is no active partition .

I'd appreciate your help. From already thank you very much.

I have a Dell PowerEdge R310 with the following specs:

OS: Windows Server 2008 R2 Standard

Raid Controller: H200

Raid Volume: 500GB

Raid Layout: Raid-1

Basically what I want to know if is it possible is to install a larger drive (I would like to do a 2 TB drive) to replace both 500GB drives and expand the Raid-1 volume to the 2TB size, without losing the current data?

Hi,

I have four (4) SanDisk CloudSpeed 1000's 480gb that I am having trouble with in my R710

Controller : PERC H700 - 12.10.7-0001

System BIOS : 6.4.0

The issue:  Drives will flash but not mount when system is powered on.  If I am in the H700 controller setup, I can re-seat the drives and they appear and act normally.  When I turn the server off and back on, the drives are lost.

Other notes: using Dell drive caddies, checked in the dell server configuration utility and the drives are present ; when you go to the H700 controller, the drives are missing until you re-seat.

Drive lights : when the system is powered on the drives flash quickly, then go out.  when I re-seat the cards after I am in the H700 controller the drives flash quickly, then the top light goes green.

Other Drives:  I have 2x Dell SAS and 2x Samsung SATA's.  These drives work normally.  Top lights turn green during boot process.

Any help appreciated.

Thanks,

-rradkins

Hi,

I have a RAID 1 setup and one of the two disks in the array has failed.  I removed it and replaced it with another disk hoping the Dell Perc H200 adapter would rebuild the mirror automatically but it has not.  In the OpenManage Server Administator the virtual disk is showing as degraded.  The issue I think may be that the replacement disk is SATA where the original one was SAS.

Is there a way you can make the adapter accept a SATA disk or is it just not supported?

Siv

Hi-

We have a failing drive with following info gleaned from MegaCLI...

C:\>megacli64 -PDInfo -PhysDrv [32:13] -a0 -NoLog | grep -E "(Slot Number:|Count:|Firmware state:|S.M.A.R.T)"
Slot Number: 13
Media Error Count: 94
Other Error Count: 0
Predictive Failure Count: 6
Firmware state: Online, Spun Up
Drive has flagged a S.M.A.R.T alert : Yes

Can we force it "Offline" and "Replace Member" - instead, of waiting until it fails completely?

Thanks for any input.

-SP

Hello,

I am looking into replacing a disk on my PowerEdge 2900. The disk is a "600GB, 15K RPM, Serial-Attached SCSI, 6Gbps, 3.5 inch, HotPlug Hard Drive", original part number W347K.

I reached out to my Dell sales rep, and provided them that information and asked for a quote . They sent me a quote for "Hard Drive,600G,SAS6-E,15K,3.5,Seagate,Eagle", part number 5XTFH. Looking into this part number, I'm seeing that it has what’s called “SED” or “Self-Encrypting Drive technology”. I don’t believe the server supports this kind of technology, and I am worried that it might not be compatible. Can any of you fine folks guide me as to if part number 5XTFH is compatible with my PowerEdge 2900?

Thank you!

Hi all, I was wondering if anyone can help me with probably broken RAID1 setup, after many attempts to fixing it, I decide I want zap whole setup and start from scratch, after clearing configuration I'm not able to select disks and create new array. Please see following photo:

This server use SCSI disks, is there any way to clear previous array settings and wipe all disks?

Thanks for any suggestions.

Windows 2012 R2 fully patched
PERC H730 1GB + Battery
All Dell drivers/firmware installed and up to date
OMSA 8.3

Go to OMSA, Storage, PERC, Virtual Disks, Change Policy, Read Policy - only options are 'Read ahead' and 'No read ahead'

I'm missing Adaptive Read Ahead. What am I missing so I can select that in OMSA?

Hello every one

We had server (poweradge R720)

In the first time i had the subject problem, and when i search for the solve i find in

After that I shutdown the server (poweradge R720) and change the place of this driver(4) withe    driver (5) and power  on the server after doing that .

The the drive which i had problem in it now are flashing on green than direct orange flash  

Hi Everyone,

Thanks for reading this.  

I have a Dell Poweredge T6300 with a Perc H730.

It has 8 drives 1TB 7.2k.

It has  a C drive and a D drive.  

Looking at Server manager / File Storage Services both C and D seem to be Raids but I am not sure what type.  One of the drives in the upper set of 4 seems to be offline blinking amber.  

Server seems to be working fine.  

Seems I can't find a way to check Raid type without shutting down and running the (CTRL-R) Perc H730 adapter software.  

Is this true?  
I believe I can hot swap depending on the Raid Type, and I believe the hardware supports that.  

Just wondering if I am thinking in the right direction.

Thanks in advance.

Hi, all

I have a server with RAID-0 mount 9 are all 2T disk, run CentOS6.
in the morning, there has been a lot of disk offline problem.

RAID card Versions
Product Name : PERC H700 Integrated
FW Package Build: 12.10.2-0004

see RAID log time, a lot of the following information(the blue text):

seqNum: 0x00005311
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 2a 00 76 52 03 00 00 00 80 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
002a 0000 0076 0052 0003 0000 0000 0000 0080 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x00005310
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 2a 00 76 52 05 00 00 00 80 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
002a 0000 0076 0052 0005 0000 0000 0000 0080 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x0000530f
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 28 00 20 d9 e7 c0 00 01 00 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
0028 0000 0020 00d9 00e7 00c0 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x0000530e
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 2a 00 76 52 02 80 00 00 80 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
002a 0000 0076 0052 0002 0080 0000 0000 0080 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x0000530d
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 28 00 74 2f 4d c8 00 00 40 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
0028 0000 0074 002f 004d 00c8 0000 0000 0040 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x0000530c
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 28 00 73 2c de c8 00 00 40 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
0028 0000 0073 002c 00de 00c8 0000 0000 0040 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x0000530b
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 2a 00 76 52 04 80 00 00 80 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
002a 0000 0076 0052 0004 0080 0000 0000 0080 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x0000530a
Time: Tue Jun 7 00:09:18 2016

Code: 0x0000010b
Class: 1
Locale: 0x02
Event Description: Command timeout on PD 09(e0x20/s9) Path 500065b36789abf1, CDB: 2a 00 76 52 04 00 00 00 80 00
Event Data:
===========
Device ID: 9
Enclosure Index: 32
Slot Number: 9
CDB Length: 10
CDB Data:
002a 0000 0076 0052 0004 0000 0000 0000 0080 0000 0000 0000 0000 0000 0000 0000 Sense Length: 0
Sense Data:
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x00005309
Time: Tue Jun 7 00:08:53 2016

Code: 0x00000071
Class: 0
Locale: 0x02
Event Description: Unexpected sense: PD 07(e0x20/s7) Path 500065b36789abea, CDB: 2a 00 00 00 01 e8 00 00 08 00, Sense: 6/29/00
Event Data:
===========
Device ID: 7
Enclosure Index: 32
Slot Number: 7
CDB Length: 10
CDB Data:
002a 0000 0000 0000 0001 00e8 0000 0000 0008 0000 0000 0000 0000 0000 0000 0000 Sense Length: 18
Sense Data:
0070 0000 0006 0000 0000 0000 0000 000a 0000 0000 0000 0000 0029 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

seqNum: 0x00005308
Time: Tue Jun 7 00:07:54 2016

Code: 0x00000071
Class: 0
Locale: 0x02
Event Description: Unexpected sense: PD 05(e0x20/s5) Path 500065b36789abe4, CDB: 2a 00 74 45 1a b0 00 00 50 00, Sense: 6/29/00
Event Data:
===========
Device ID: 5
Enclosure Index: 32
Slot Number: 5
CDB Length: 10
CDB Data:
002a 0000 0074 0045 001a 00b0 0000 0000 0050 0000 0000 0000 0000 0000 0000 0000 Sense Length: 18
Sense Data:
0070 0000 0006 0000 0000 0000 0000 000a 0000 0000 0000 0000 0029 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

then I try to find solutions DELL websites
in there see RAID5 disk problem has been fixed in firmware version, did not find repair disk offline RAID-0 firmware version.
disk offline this problem often occurs, how to deal with this problem? which firmware version can fix it?

HDD Failure

Dell PowerEdge T300
service tag: [removed per TOS]
service code: [removed per TOS]

Hard disk :
product id: ST3450857SS
serial: 3SK010YR
part. num: SG0H995N1253197L005QA00
SAS da 450GB

regards

salvatore

I have Dell PowerEdge Server (2009) with Dell SAS 6/ir RAID CONTROLLER

and 2 Dell Branded 250GB WD2502ABYS drives

I restarted my server the other day  to trouble shoot an issue i was having with something else..

I noticed the RAID Errors..

I shut down server... pulled out both drives and tested them on a different computer using WESTERN DIGITAL data lifeguard tester...

I found the BAD drive.. it FAILS quick 2 minute test instantly..

I have since discovered if I dont BUY a DELL branded enterprise drive to replace it .. it will work in SATA1 mode instead of sata 2 or 3...    ( Really DELL)  one of many reasons i would never buy another DELL..

so now my choice is to buy a USED drive or suffer from slow speed from unsupported new drive..

so I bought a few used 250GB Dell branded Enterprise drives for a couple spares...

.. Do i simply turn off server and replace the BAD drive and restart ?

or will i need to enter the DELL SAS6/ir utility on boot up and configure anything?

Thanks for any info or advice..

Dear Sir:

I have checked SAS 12Gbps HDD information from Dell official website,and

it only can support following Servers:

Can it also install on R720, R620 Servers?

Thank you

Chris