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

Any advice would be greatly appreciated.

When booting up the server it freezes at this message  found virtual disks that are degraded, I can press F1 to resume to windows with no issues, I opened the controller it shows that disk 3 of the 3 disks in my array has issues, how can I repair this raid with out any loss ? replace third disk and rebuild the array ? if so how is this part done.

I have a problem with our client's server, a Poweredge T310 (service tag {{{Removed by Moderator}}})
Yesterday its event log was full, because there was a lot of events that indicates "ROMB Battery: Battery sensor, failed was deasserted" and after 10 seconds "ROMB Battery: Battery sensor, failed was asserted".
After cleaning event log, updated bios firmware, and update OMSA version (previous version was 6; now, 8.3), now the errors continue, with this description: "The storage battery has failed" and then "The storage battery is operating normally".
I'm not sure if I can update controller firmware without problems, and I'm not sure if the problem is battery itself or not.
What should I do?

Thanks,

We want to replace a faulty disk in a raid 1 setup. But the new disk is not recognized.

Controller: Dell SAS6/ir 

Old disk:

Dell ST3450856SS   450gb  RPM: 15k Cheetah 15k.6 (see attachment)

New disk: 

Dell ST3450857SS Seagate 450gb  RPM: 15k.7

The only difference is that the new disk has a 6gb/s interface but its backwards compatible.

We don't see the disk in SAS topology in bios or OpenManage.

The disk activity led is flashing but disk led state is offline.

I have a Dell H710 controller which is showing up as a  LSI / Symbios Logic MegaRAID SAS Fusion Controller where I need it to show up as a LSI / Symbios Logic Dell PERC H710 Adapter controller within vCenter.

How do I fix this so that this card is showing up correctly?

Hi

im trying to find out if this ssd hard drive is compatible with my system:

Dell LiteOn LCS-256M6S

can you help?

Buonasera mi chiamo Lino Ambrosio nell'azienda in cui lavoro tempo fa abbiamo acquistato un SERVER dell t610 service tag : 8P9LV4J

il Server è provvisto di 2 dischi rigidi da 500 GB
Da un pò di Giorni il secondo disco rigido lampeggia giallo e poi verde in continuazione. Abbiamo un rallentamento del server incredibile.

Volevo chiedere due cose :

Primo:

Abbiamo un disco rigido SAS 6 Gbps 500 GB RPM 7.2 K F/W KS64 semi nuovo funzionante ma con dati presenti in esso. Si può formattare questo disco ? come facciamo ? dopo averlo formattao quale è la procedura per il reibuilding ?

Secondo :

Dobbiamo acquistarne uno nuovo per forza ? Se si , posso contattarvi per fare l'ordine in tempi brevi ?

spero in una vs. tempestiva risposta.

la mia mail : lambrosio@alice.it

Saluti Lino Ambrosio

I've created a virtual disk in the VRTX and have associated it to two blades. Those two blades, I've installed three different version of ESX from Dell custom ISOs, but I do not see any devices showing up under the Shared PERC 8 Mini in vSphere Storage Adapters.I feel this is actually a VRTX issue at this point. If I go into the Dell iDRAC for the blade, I see this error if I go to Virtual Disks.

RAC0502: There are no virtual disks to be displayed. 1. Check if the host system is powered off or shutdown. 2. Check if virtual disks are created.

There are no errors in the main CMC management interface for the virtual drives. Any ideas?

The server had a disk failure in a Raid 5 configuration and its taken days to discover what the cause was, until this message from the controller surfaced.

Controller ID: 0 Unrecoverable medium error during recovery: PD 1:0

I've not been able to get a good backup so the idea of rebuilding this server is not appealing, any ideas on how to recover from this error?

I had a VD offline due to a firmware bug.

I'm using the latest firmware version.

This is what I can see in our logs:

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

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


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


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


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


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

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

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

I have a RAID 5 and one of the drives went bad. I replaced it with a new drive and entered the Controller Config (cltr r). I went to the foreign disk tab and hit clear instead of import. Now the drive say ready and I cant do anything but make it a Hot Spare. How to I make the disk a foreign disk again?

good morning-

We have 3 740YX in RAID5 on a PERC6i SAS RAID Controller with 1 drive failure (4 years old). 

I slimmed the network share down to 300gb -it is only used for documents and quickbooks... no need for SAS in the first place... ~5gb veem changes a day.

It is now being uploaded to crash plan but I am still considering rebuilding the RAID5.

Computer Model PowerEdge T310

Shipping Date 1/12/2012

341-6175 : PERC6i SAS RAID Controller Internal with Battery

740YX 3 HARD DRIVE, 1T, NL6, 7.2K, 3.5, S-MSKP

1- Would you buy 3 new drives and rebuild the array? Or should I trash the old controller and just stay on crashplan? 

2- Can I get this ST1000NM0023 from cdw and replace the failed drive?

740YX 3 HARD DRIVE, 1T, NL6, 7.2K, 3.5, S-MSKP

Seagate Part# ST1000NM0001

www.cdw.com/.../2961609.aspx

We no longer carry Seagate Constellation ES ST1000NM0001 - hard drive - 1 TB - SAS-2 (ST1000NM0001),
but we found this replacement for you (ST1000NM0023).

Your ideas and expertise are always appreciated :).

.Hi all

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

Does anyone have any ideas?

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

Many thanks

Jamie

Hi,

We have 2 1 TB HDD installed and when trying to configure Raid 1, it does not give us the options to configure Raid 1, Updated the server firmware and still only shows Raid 0

I have (4) 1 TB SATA drives setup in a RAID 5 array. Heard a drive fail and system blue screened. Restarted system and Perc configuration utility showed drive 00 failed, drive 01 missing (foreign config) and drives 02 and 03 online.

I don't understand how the second drive (01) could be missing unless this had previously failed (?) and I have been running on only 00,02,03.

What can I do with the 01 foreign drive? I replaced failed drive 00 with a new used drive but have no options to try to rebuild or try to restore the array. Is there any possibility to restore the array? Should I try to clear the foreign config on the 01 drive?

Any help / suggestions appreciated.

Hello all,

I have a PowerEdge T330 server with 8 drive slots and currently have 3 SATA drives running a raid 5 configuration.  I have a virtual disk configured for the Raid (you have to).

The operating system recognizes the disk and is able to use the resources..

My desire is to add another hard drive to the array (all hard drives same size, same make, etc) making 4 drives without losing any data.

I have looked in the iDrac settings and the only setting was to add the new drive as a global spare or a dedicated hotspare for the virtual drive.

I have also looked in the BIOS and do not see a way to add the new drive.

Does anyone know how to expand the capacity?  I can blow away the virtual drive if needed and start over without issue.  I have plans to incrementally perform this act until adding 8 drives.(5 additional times).

Help!

We just replace a drive 1 on the Server. We did the manual rebuild on the drive and it say is online. Raid (10) is not say degrade anymore, is optimal. But we have the active led allays on on this disk. Is this led active light on indication of issue ?

We had a six drive R10 VD that was in production for about a year at which time one drive reported failed.  Drives in question are Samsung 850 Pro 1TB SSD's.  We pulled the failed drive a replaced with a brand new drive.  Rebuild reached ~12% and then a 2nd drive went offline.  We thought the 2nd drive failed as well and had full data loss, so we proceeded with restore from backup.  Later found that all data was intact after we forced the 2nd drive back online.  Do not believe there was any data loss or corruption as this was a VMware VMFS volume and the VM's contained on it started without issue.

Other steps attempted:

1. Updated BIOS and all firmware to latest versions.  (PowerEdge R730xd)

2. Attempted a 2nd rebuild of the VD and we got the same results.

3. Deleted the VD and created a new R10 VD.  Background init fails.

4. Deleted the VD and created a R5 array with only four disks.  A new drive is in a failed state but the VD is online in a degraded state.

It seems unlikely that there are actually any failed drive since we ran one of the VM's for about a week without issue after we forced it back online.

Any suggestions for getting back to our original state of a six disk R10 VD?  

Incidentally, we have a 2nd H730P in this system with an identical configuration (6 x Samsung 850 Pro SSD in R10) that is running without issue.

I have a PERC H700 with a 7x3TB RAID5 array where one of the disks had recently failed. I went to replace the failed drive and now it appears that I have lost everything.

I am currently panicing because I fear that I have lost *EVERYTHING*. I am seriously up the creek if I have lost everything.

OS: Windows Server 2012 R2 Datacenter
Adapter: Dell PERC H700 - (I'll check the firmware, it's oem dell)

Here's what I have:

Controller0: PERC H700 

 Drive Group: 0, RAID 0
   Virtual Drive(s):
      Virtual Drive: 1 Ksys, 118.625 GB, Optimal
   Drives
       Slot: 4, SSD (SATA), 119.243 GB Online
 Drive Group: 1, RAID 5
   Virtual Drive(s):
      Virtual Drive: 0, bigboss, 16.371 TB, Degraded
   Drives
       Slot: 0, SATA, 2.729, MISSING
       Slot: 1, SATA, 2.729, Online, (512 B)
       Slot: 2, SATA, 2.729, Online, (512 B)
       Slot: 3, SATA, 2.729, Online, (512 B)
       Slot: 5, SATA, 2.729, Online, (512 B)
       Slot: 6, SATA, 2.729, Online, (512 B)
       Slot: 7, SATA, 2.729, Online, (512 B)

So I purchased a 4TB SATA drive to replace the dead drive. I booted up into Windows, loaded MegaRAID Storage Manager.

Right clicked on the unconfigured 4TB drive and selected "Replace Missing Drive"

The storage manager then associated this new 4TB SATA drive in Slot 0 with Drive Group: 1, RAID 5.

I then right clicked on the drive and selected "force online" -- I've been able to do this before and all was fine.

Walked away from the machine, for ~5 minutes. Told windows to shut down, waited for windows to do it's thing, then when the machine powered off, I moved it backed to my closet connected the network cables, plugged it back in, and powered it back on.

A few minutes later I RDP'd into the machine. The file systems on that Drive group were no longer there.

I loaded up "Computer Management", the partition tool in Windows, and it appeared as this

Disk 0 - 16.374 TB
[ 3.xx TB Healthy Partition ] [ 12.xx TB Unallocated ]

I paniced. I opened up the MegaRAID Storage Manager and aborted the operation.

Normally I see a rebuild??????

I then tried to clear and re-import the configuration. Since I boot from the 128 GB SSD that's connected to Slot 4 on the controller, it wouldn't let me clear the configuration.

So I rebooted, loaded up the PERC BIOS utility, went to clear the configuration (thinking that I'd surely be able to re-import it)

And now everything is gone!??!!?!?!?

I'm freaking out and I don't know what to do. If any of you have any suggestions please, please advise.

For what it's worth, I've got an extra PERC H310 here that I can possibly cross flash to official LSI firmware if needed.

Looks like it's time for me to make a pot of espresso, and start my coffee percolator. Cause it's going to be a long night of researching to see if there's anything that can be done. :( :(