I have an older R900 with a Perc 6/i controller with six 500gb SAS (Seagate ST9500430SS) drives configured in a RAID 5 array.  Recently Drive 0 failed so I replaced it with an identical drive.  The replacement drive showed up and after I inserted it I got the E1810 Fault error on the LCD display so I assumed that it was also defective.  I exchanged it with the seller and inserted a 2nd replacement.  Same E1810 error.  I booted into the controller utility and it showed that the drive is missing so I naturally assumed that I'm a victim of bad luck and received two faulty drives.  The vendor sent me a 3rd drive and it also shows the E1810 Fault error.

I cut my losses with that vendor and assumed they were selling junk drives so I bought a brand new drive from another vendor.  Popped the drive in, E1810 Fault error.

What is going on here?  I have never seen this behavior before.  Could the slot somehow be bad?  If so, can I keep all of my data and move the disk from slot 0 to slot 7?  I need to find a solution fast because the array is not configured with a hot spare.  Another failed disk means all of my data is gone.  Any suggestions other than wiping the config and starting over?

why is my hdd still blinking green after rebuild?

how can i fix this?
Can do it with megacli?

it is a 2 hdd raid 1

megacli -LDInfo -Lall -aALL

Adapter 0 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name :
RAID Level : Primary-1, Secondary-0, RAID Level Qualifier-0
Size : 67.75 GB
Sector Size : 512
Mirror Data : 67.75 GB
State : Optimal
Strip Size : 64 KB
Number Of Drives : 2
Span Depth : 1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy : Disk's Default
Encryption Type : None
Is VD Cached: No

Exit Code: 0x00

megacli -PDList -aALL

Adapter #0

Enclosure Device ID: 32
Slot Number: 0
Drive's position: DiskGroup: 0, Span: 0, Arm: 0
Enclosure position: N/A
Device Id: 0
WWN:
Sequence Number: 2
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
PD Type: SAS

Raw Size: 68.366 GB [0x88bb93a Sectors]
Non Coerced Size: 67.866 GB [0x87bb93a Sectors]
Coerced Size: 67.75 GB [0x8780000 Sectors]
Sector Size: 0
Firmware state: Online, Spun Up
Device Firmware Level: D906
Shield Counter: 0
Successful diagnostics completion on : N/A
SAS Address(0): 0x500000e1190dcf12
SAS Address(1): 0x0
Connected Port Number: 0(path0)
Inquiry Data: FUJITSU MBE2073RC D906D5A4PBC02PM8
FDE Capable: Not Capable
FDE Enable: Disable
Secured: Unsecured
Locked: Unlocked
Needs EKM Attention: No
Foreign State: None
Device Speed: Unknown
Link Speed: Unknown
Media Type: Hard Disk Device
Drive Temperature :28C (82.40 F)
PI Eligibility: No
Drive is formatted for PI information: No
PI: No PI
Port-0 :
Port status: Active
Port's Linkspeed: Unknown
Port-1 :
Port status: Active
Port's Linkspeed: Unknown
Drive has flagged a S.M.A.R.T alert : No

Enclosure Device ID: 32
Slot Number: 1
Drive's position: DiskGroup: 0, Span: 0, Arm: 1
Enclosure position: N/A
Device Id: 1
WWN:
Sequence Number: 17
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
PD Type: SAS

Raw Size: 68.366 GB [0x88bb93a Sectors]
Non Coerced Size: 67.866 GB [0x87bb93a Sectors]
Coerced Size: 67.75 GB [0x8780000 Sectors]
Sector Size: 0
Firmware state: Online, Spun Up
Device Firmware Level: D905
Shield Counter: 0
Successful diagnostics completion on : N/A
SAS Address(0): 0x500000e11755cde2
SAS Address(1): 0x0
Connected Port Number: 1(path0)
Inquiry Data: FUJITSU MBE2073RC D905D5A4PB201C1U
FDE Capable: Not Capable
FDE Enable: Disable
Secured: Unsecured
Locked: Unlocked
Needs EKM Attention: No
Foreign State: None
Device Speed: Unknown
Link Speed: Unknown
Media Type: Hard Disk Device
Drive Temperature :29C (84.20 F)
PI Eligibility: No
Drive is formatted for PI information: No
PI: No PI
Port-0 :
Port status: Active
Port's Linkspeed: Unknown
Port-1 :
Port status: Active
Port's Linkspeed: Unknown
Drive has flagged a S.M.A.R.T alert : No

Exit Code: 0x00

Dear Support ,

One of the HDD in the PowerEdge R710 is degrade and indicate error in front panel. 

I ordered a new HDD and tried to replace it. However , the new HDD could not be detected.

Please advise

Hi guys,

I have a Poweredge 2950 at home but I cannot boot the server.

The power light are working but the power button is not working. A week ago it was working but now it is not working. Nothing were broken, just thr entire power button and the dislay monitor is not working. How can I fix it? Thanks.

Every day at 1:25 a log message is generated.

today error for Physical Disk 1:0:7

yesterday error for Physical Disk 1:0:6

over and over again the same mistakes

What is the reason ?

How to disable it ?

LOG:

    2092    Sun Nov 12 06:48:36 2017    Storage Service    Physical disk Rebuild completed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2158    Sun Nov 12 06:48:36 2017    Storage Service    Physical disk online: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 06:48:36 2017    Storage Service    Device returned to normal: Virtual Disk 1 (Virtual Disk1) Controller 0 (PERC 6/i Integrated)    
    2124    Sun Nov 12 06:48:36 2017    Storage Service    Redundancy normal: Virtual Disk 1 (Virtual Disk1) Controller 0 (PERC 6/i Integrated)    
    2065    Sun Nov 12 02:05:54 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 02:05:54 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 02:05:53 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 02:05:53 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 02:05:53 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 02:05:52 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 02:04:11 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 02:04:11 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 02:04:11 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:07 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:07 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:07 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:07 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:07 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:07 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:07 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:04:05 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 02:03:20 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 02:03:20 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 02:03:20 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 02:03:19 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 02:03:19 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 02:03:19 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 02:03:06 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 02:03:06 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 02:03:06 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 02:03:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 02:01:48 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 02:01:48 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 02:01:48 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2299    Sun Nov 12 02:01:47 2017    Storage Service    Bad PHY Slot 7.: Connector 1 Controller 0    
    2052    Sun Nov 12 02:01:47 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 02:01:47 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 02:01:47 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:59:25 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:59:25 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 01:59:25 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:18 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2095    Sun Nov 12 01:59:02 2017    Storage Service    Unexpected sense. SCSI sense data: Sense key: 6 Sense code: 29 Sense qualifier: 0: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:59:01 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:58:58 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:56:38 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:56:37 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:56:37 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:56:37 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:56:37 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 01:56:36 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 01:56:36 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:33 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:33 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:33 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:33 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:33 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:33 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:33 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:56:33 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:56:33 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:56:32 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:56:02 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:56:02 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:56:02 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 01:56:01 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:56:01 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:56:01 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:55:58 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:55:58 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 01:55:58 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:51 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:51 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:55:51 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:55:06 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:55:05 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:55:05 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:55:05 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:55:05 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 01:55:04 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2299    Sun Nov 12 01:54:56 2017    Storage Service    Bad PHY Slot 7.: Connector 1 Controller 0    
    2348    Sun Nov 12 01:52:44 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:43 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:43 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:52:43 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:52:43 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:41 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:41 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:41 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:41 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:41 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:52:40 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:52:00 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:52:00 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:52:00 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:52:00 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 01:51:59 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:51:59 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 01:50:01 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:50:00 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:50:00 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:50:00 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:49:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:49:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:49:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:49:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:49:58 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:49:58 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:49:58 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:47:23 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:47:22 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:47:22 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:47:22 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:47:22 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 01:47:21 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2299    Sun Nov 12 01:46:26 2017    Storage Service    Bad PHY Slot 7.: Connector 1 Controller 0    
    2049    Sun Nov 12 01:44:05 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:44:05 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 01:44:05 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:44:00 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:44:00 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:44:00 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:44:00 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:43:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:43:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:43:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:43:59 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:41:23 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:41:22 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:41:22 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:41:22 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:41:22 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 01:41:21 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:39:24 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:39:24 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 01:39:24 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:23 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:23 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:23 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:22 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:22 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:22 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:22 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:21 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:20 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:20 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:20 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:20 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:19 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:19 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:19 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:19 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:18 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:18 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:18 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:18 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:12 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:12 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:12 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:11 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:11 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:11 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:11 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:39:10 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:36:53 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:36:53 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2052    Sun Nov 12 01:36:52 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:36:52 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:36:52 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:36:52 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:36:32 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:36:32 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2348    Sun Nov 12 01:36:32 2017    Storage Service    The rebuild failed due to errors on the target physical disk.: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:30 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:30 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:30 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:30 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:30 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:30 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:30 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:36:26 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:25:55 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2050    Sun Nov 12 01:25:55 2017    Storage Service    Physical disk offline: Physical Disk 1:0:7 Controller 0, Connector 1    
    2065    Sun Nov 12 01:25:55 2017    Storage Service    Physical disk Rebuild started: Physical Disk 1:0:7 Controller 0, Connector 1    
    2121    Sun Nov 12 01:25:55 2017    Storage Service    Device returned to normal: Physical Disk 1:0:7 Controller 0, Connector 1    
    2049    Sun Nov 12 01:25:54 2017    Storage Service    Physical device removed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2048    Sun Nov 12 01:25:54 2017    Storage Service    Device failed: Physical Disk 1:0:7 Controller 0, Connector 1    
    2123    Sun Nov 12 01:25:54 2017    Storage Service    Redundancy lost: Virtual Disk 1 (Virtual Disk1) Controller 0 (PERC 6/i Integrated)    
    2057    Sun Nov 12 01:25:54 2017    Storage Service    Virtual disk degraded: Virtual Disk 1 (Virtual Disk1) Controller 0 (PERC 6/i Integrated)    
    2052    Sun Nov 12 01:25:54 2017    Storage Service    Physical device inserted: Physical Disk 1:0:7 Controller 0, Connector 1    
    2359    Sun Nov 12 01:25:54 2017    Storage Service    Disk found is not supplied by an authorized hardware provider: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:53 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:52 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:48 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:48 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:48 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:48 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:47 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:47 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:47 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:46 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:46 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:46 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:46 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:45 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:45 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:45 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1    
    2405    Sun Nov 12 01:25:45 2017    Storage Service    Command timeout on physical disk: Physical Disk 1:0:7 Controller 0, Connector 1

I have t T330 that came with 4 HD's/RAID 10.

I have added a smaller RAID1 array that I want to boot from after I install the OS on it.

I can't see how to change the system to boot from the newer RAID array. 

I have tried the lifecycle controller - it shows the option but it is grayed out and says it is only applicable to legacy not UEFI.

I cannot see an option to change either in OMSA or using the F2 key.

I know there is a command line interface for the PERC controller but I am not sure that'll work.

Any suggestions? Thanks

Replaced  Virtual Disk with 2 Dell certified Seagate ST9500620NS SATA drives on T610 w/Perc H700 set up in RAID 1 for OS but for some reason OMSA reports one drive as negotiated & capable speed of 3.0 Gbps and the other drive at 6 Gbps. Firmware revision on the 3 Gbps drive is AA0E & AA63 for the 6 Gbps drive.

ID            0:0:0
Status   OK
Name    Physical Disk 0:0:0
State     Online
Power Status     Spun Up
Bus Protocol       SATA
Media   HDD
Revision               AA63
T10 PI Capable  No
Certified              Yes
Capacity               465.25GB
Used RAID Disk Space     465.25GB
Available RAID Disk Space             0.00GB
Hot Spare            No
Vendor ID            DELL(tm)
Product ID           ST9500620NS
Serial No.             9XF3K817
Part Number      TH0609Y52123353H0654A0
Negotiated Speed           6.00 Gbps
Capable Speed  6.00 Gbps
Sector Size          512B
SAS Address       4433221107000000
Non-RAID HDD Disk Cache Policy               Not Applicable

ID            0:0:1
Status   OK
Name    Physical Disk 0:0:1
State     Online
Power Status     Spun Up
Bus Protocol       SATA
Media   HDD
Revision               AA0D
T10 PI Capable  No
Certified              Yes
Capacity               465.25GB
Used RAID Disk Space     465.25GB
Available RAID Disk Space             0.00GB
Hot Spare            No
Vendor ID            DELL(tm)
Product ID           ST9500620NS
Serial No.             9XF449GC
Part Number      TH000X3Y2123367601S6A0
Negotiated Speed           3.00 Gbps
Capable Speed  3.00 Gbps
Sector Size          512B
SAS Address       4433221106000000
Non-RAID HDD Disk Cache Policy

Would be grateful if anyone has any suggestions.

Hello !

We have R720 with a PERC H710 Mini configured in RAID 10 with Two spans ( each span has two HDD ). and I want to increase the number of spans or just adding one more span.

so i just want to know before proceeding with this, Is it Possible to increase the number of Span in H710 MINI RAID 10 on online system without losing any data ?

Thanks

Sarmad

Good day,

I am attempting to install these SAS HD into a fresh R710. I can create a VD, but when I initialize, it does not work. These were working drives from another system.

Trying to update the firmware using the Linux Bootable ISO says "Inventory Collection Failed" for this firmware/hardware, despite other FW being update fine.

I booted into the Lifecycle controller and performed the updates via ftp.dell.com, but it did not list the drives at all.

I have tried to manually install the FW bin file from command prompt - again, inventory collection failed.

Everything else is up to date, LCC, BIOS.

We have a Dell PowerEdge T410 with Dell PERC 6/i Adapter.

I tried to update the firmware (Version 6.3.3-0002, A-00) from within Windows which failed (all the icons in the desktop dissapeared and then the screen went blank & the server rebooted before the update was complete.

The server now displays "Raid adapter firmware failed validation" on boot.

I tried copying the driver files (Hard drive option) to a bootable USB stick but it says:
"No supported controllers present or detected."

I downloaded the firmware from here:
www.dell.com/.../driversdetails

Help!

To sort out the current replacement disk issue on defrnrlpidhb11.

/dev/sdk - Physical Disk 0:1:11 - Fault detected on drive 11 in disk drive bay 1. We believe this is linux mount point /data/8

I was brought into a Skype chat with Mark Pollack, Balaji Narasimhachari & Panagiotis Makridis regarding HD 11 replacement not going as anticipated. After HD was replaced, server was not booting up due to cached configuration within the raid controller cache. HD 11 was not being seen in the raid controller, let alone getting past the raid controller boot up, due to the cached information. In my experience, this is older, archive information that is used in case of battery failure, which can become corrupted. In order to get HD 11 online, I deleted the cached info which allowed the HD to be seen.

Was able to see HD 11 as READY at this point but was not coming ONLINE. Only options for the HD were Global Hot Spare or Non-Raid HD. Toggling the HD to Global HS changed nothing. So asked in the chat on how to proceed. As the other 1.8 TB HDs were RAID 0, figured that HD 11 should be as well. Based on the virtual disks on the server already, confirmed that data10 was missing. So configured HD 11 as disk10, with the OK from Balaji. Saved the config and allowed the server to boot to the OS.

Balaji and Mark took over troubleshooting once the server was up in the OS but brought me back into the chat sometime later stating that there was an issue with the HD. Taking a look at defrnrlpidhb10, noticed that I had in error created a virtual disk with the name disk10 instead data10. With permission, had the server rebooted and renamed the virtual disk to match defrnrlpidhb10.

Balaji and Mark continue to troubleshoot but are still having issues. Mark believes that the HD could be incompatible, but aside from the company name on the HD, all specs are a match to the other 1.8 TB HDs in the server. Also, the RAID 0 configuration created by me matches, from what I can see, to all the others. I do not think this is a hardware issue but perhaps an issue with the configuration of the HD, but as I am unfamiliar with this system's setup, I am at a loss. Found looking on teh new SAS Drive the Text 12Gb following of the SAS 1.8TB which not on the old drives ...strange or just new definition...pls help...

We have a server (Service Tag: SVC TAG REMOVED BY MODERATOR Express Service Code: ) that we have been trying to put in production to replace an older SQL server for a few years now but we have never been able to get it to run as fast as the old machine.  I think I have narrowed it down to the disk speed which seems to be around 600 MB/s in real life.  The SSD (P/N: 0PHJ5) we are using is rated much faster and the PERC controller seems to only be rated for 750 MB/s.  

Am I on the right track here?

Are there better options for this machine that the H710 mini or should I cut my losses and get another machine?

Sincerely,

Ben Putnam

Hello,

I need to know the part number for the cable that connects this card 405-AADX to my 4 hard drives (there is no backplane).

Thanks and best regards,

Sameh

Hi fellas,

I have an old server with a CONTROLLER, PERC6II, SERIAL ATTACHED SCSI

The battery of the controller is failing, so I need to replace it, but according to Dell, those batteries are EOL.

I have another old server that's the same R710, but instead of that card, it has PERC6I-INTG,NOSLED, and this one hasn't battery.

My question is, can I replace the PERC6II with that other controller?

Thanks for helping.

Kind regards

Matias

Hi,

I have a need peculiar to install Redhat Enterprise Linux 7.2 on a new R740 with a H740 Raid Card. The hard drives are not detected. An R740 with H730 installs with no problems. Is there a way I can install Redhat 7.2 on the R740 with the H740 RAID Card. RHEL 7.4 installs fine but my vendor has a specific requirement for 7.2

We have Dell Power Edge R530 server (RAID Enabled). We have 2x1000GB SAS hard drives on server, But there is no application to manage RAID for Windows Server 2012 R2 . So in case of failure how could we not which HDD fails.

We are in the process of upgrading the RAID controller in an R410 that came from the factory with a 6/ir card. 

• Is X394K the correct cable for the conversion?
• Is the battery and battery cable necessary?
  • Is the correct battery P/N: FR463?
  • Is the correct battery cable P/N: RF289?

Any help would be greatly appreciated!

PERC6i SAS RAID Controller with a predicted failed drive.  I've ordered a replacement drive for the system and I'm wondering if I can simply pull the failed drive out, hot, and put the new one in and allow it to sync without any other steps.  Also the new drive is larger capacity than the failed due to the legacy drive being discontinued but Dell informs me that the larger drive will partition back to match the legacy capacity.  I'm ok with the drive size mis-match - what I need to know is if I need to take the server down and then Ctrl+R to replace the failed drive or if it is simply physically swapping the drives and going back to the couch.

Thanks in advance.

Darin

I recently installed OMSA on this PowerEdge T110, to easily check the RAID/Drive status. It is showing that the driver version is out of date.

I am unable to find 2.0.0-0162 online, on Dell's site, or elsewhere to update it to. Does anyone know where to find this firmware update?

Currently one of our Dell servers is showing a preictive failure indicated by flashing gren and amber leds on the disk, as well as showing a S.M.A.R.T alert.  The server is running esxi 5.1 and has 3 VM's running that I can't shutdown. What is the correct procedure for replacing the failing drive?  I was thinking of using MegaCli to do the hard drive swap.  Does Dell recommend another procedure.

I was going to use the following commands in MegaCli

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

MegaCli -PDOffline -PhysDrv [E:S] -aN

Mark the drive as missing

MegaCli -PDMarkMissing -PhysDrv [E:S] -aN

Prepare drive for removal

MegaCli -PDPrpRmv -PhysDrv [E:S] -aN

Change/replace the drive

If you’re using hot spares then the replaced drive should become your new hot spare drive:

MegaCli -PDHSP -Set -PhysDrv [E:S] -aN

In case you’re not working with hot spares, you must re-add the new drive to your RAID virtual drive and start the rebuilding process

MegaCli -PdReplaceMissing -PhysDrv [E:S] -ArrayN -rowN -aN
MegaCli -PDRbld -Start -PhysDrv [E:S] -aN