RAID Set and Volume Missing on Areca 1880

Discussion in 'SSDs & Data Storage' started by Isoparm, Aug 5, 2013.

  1. Isoparm

    Isoparm n00b

    Messages:
    10
    Joined:
    Aug 5, 2013
    I have a RAID 5 (12x3TB) array that is no longer showing for me. I'm pretty sure I bumped a drive power cord on the array when I was removing and reinserting a system drive, causing that drive not to power up. I've since reconnected the power cord on the drive, and even though all the drives show up in the web manager the Raid Set and Volume are missing. The drives are all listed now as "Free".

    If I run "LeVeL2ReScUe" I will get a Raid Set listed, but the OS does not see it.

    Running "LeVeL2ReScUe" originally showed the Volume State as "Normal"... but after leaving the machine on for a few hours now I get "Need Check".

    I've been reading through the forums and it seems like this is a common problem that often can be fixed, I'm just not sure which command I should issue first...

    - Should I continue with "LeVeL2ReScUe", or should I use just plain "Rescue"?

    - Should I try and activate the Raid Set?

    - Should I try and create a RAID Set with the exact settings?


    Any help would be very appreciated.

    This is an Areca 1880xi-12
    There are 12x3TB HDD's in RAID 5
    The stripe is 128
    I have the latest FW/BIOS/etc installed.
     
  2. mwroobel

    mwroobel [H]ardness Supreme

    Messages:
    4,915
    Joined:
    Jul 24, 2008
    Before you do ANYTHING, do you have a dozen spare 3TB drives to make an image set of the drives you currently have installed. If the data you have is truly valuable to you, before you make any attempt to repair the damage you should make a complete image of each of the drives you currently have. This will allow you to attempt any avenues you choose and still have the ability to go back to where you are right now if you need to attempt another strategy.
    I will forgo my normal RAID is not a backup speech, but will suggest once you get your array back up that you SERIOUSLY consider moving to RAID6 on this card ASAP (once you have a backup in place.) You don't want to have that size array with just one parity drive (both in physical size AND quantity of drives.)

    If you take a look at this (just one example from just a few days ago), you will see how beneficial making an image set of your drives prior to recovery attempts can be.

    Do you have the complete layouts of your RAID and volumesets from when you created them? Please post a complete log from your Areca card.

    What have you done so far since the drives became listed as free? You mentioned doing a LeVeL2ReScUe, but then asked if you should continue it? Did you recreate the RAID with the settings you had?
     
    Last edited: Aug 6, 2013
  3. staticlag

    staticlag [H]ard|Gawd

    Messages:
    1,675
    Joined:
    Mar 26, 2010
    From Areca's FAQ:

    A quick googling shows power loss and this error is pretty common with this card.

    From reading these descriptions it would seem "Rescue" should work, since none of the drives were changed or altered.

    But as mwroobel says, RAID5 for those drives is a disaster waiting to happen. And if you care about your data you should do a 1:1 backup first.
     
  4. Isoparm

    Isoparm n00b

    Messages:
    10
    Joined:
    Aug 5, 2013
    At the moment I don't have access to 12 - 3TB drives to do a bite for bite backup unfortunately. - And yes, I will definitely move it to a RAID 6.

    I did LeVeL2ReScUe - which then showed a Volume and said that it was in "normal" state, but the OS doesn't see that Volume so I can't access the data at all.

    So is there something else I should do after LeVeL2ReScUe? Should I try activating the RaidSet? Or should I try just the "rescue" command?

    I haven't done anything other than run the LeVeL2ReScUe command at this point.


    The details are:

    RAID 5 - 12x3TB
    Single 33TB Volume
    128KB Stripe
    Latest FW/Bios
     
  5. mwroobel

    mwroobel [H]ardness Supreme

    Messages:
    4,915
    Joined:
    Jul 24, 2008
    Again, before you do anything else... as asked before PLEASE post your full log... and screencaps of your config and raidset screens would help as well. The most likely reason you can't see it in windows is that the raidset is currently inactive, but please post more info before you do anything. One last question, what brand/model drives are you using?
     
    Last edited: Aug 6, 2013
  6. Isoparm

    Isoparm n00b

    Messages:
    10
    Joined:
    Aug 5, 2013
    Below is the log:

    Code:
    2013-08-06 20:11:35 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:08:51 H/W Monitor  Raid Powered On     
    2013-08-06 20:07:41 H/W Monitor  Raid Powered On     
    2013-08-06 20:05:44 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:05:13 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:04:43 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:03:34 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:03:03 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:02:30 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:01:59 Proxy Or Inband  HTTP Log In     
    2013-08-06 20:01:19 Proxy Or Inband  HTTP Log In     
    2013-08-06 19:59:59 H/W Monitor  Raid Powered On     
    2013-08-06 19:57:48 Proxy Or Inband  HTTP Log In     
    2013-08-06 19:55:06 H/W Monitor  Raid Powered On     
    2013-08-06 19:51:15 H/W Monitor  Raid Powered On     
    2013-08-06 18:58:08 H/W Monitor  Raid Powered On     
    2013-08-06 18:56:22 Proxy Or Inband  HTTP Log In     
    2013-08-06 18:56:05 Proxy Or Inband  HTTP Log In     
    2013-08-06 18:50:46 H/W Monitor  Raid Powered On     
    2013-08-06 18:12:26 Proxy Or Inband  HTTP Log In     
    2013-08-06 03:17:53 Proxy Or Inband  HTTP Log In     
    2013-08-05 23:22:12 Proxy Or Inband  HTTP Log In     
    2013-08-05 23:20:36 H/W Monitor  Raid Powered On     
    2013-08-05 23:18:22 Proxy Or Inband  HTTP Log In     
    2013-08-05 23:16:50 H/W Monitor  Raid Powered On     
    2013-08-05 23:15:02 H/W Monitor  Raid Powered On     
    2013-08-05 23:07:51 Proxy Or Inband  HTTP Log In     
    2013-08-05 23:04:36 H/W Monitor  Raid Powered On     
    2013-08-05 23:02:44 Proxy Or Inband  HTTP Log In     
    2013-08-05 23:00:37 H/W Monitor  Raid Powered On     
    2013-08-05 22:45:13 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:45:13 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:45:13 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:45:10 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:45:01 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:45:01 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:45:00 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:44:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:44:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:44:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:44:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:44:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:44:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:44:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:42:44 H/W Monitor  Raid Powered On     
    2013-08-05 22:41:18 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:41:18 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:41:18 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:41:00 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:47 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:47 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:45 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:38 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:40:38 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:39:07 H/W Monitor  Raid Powered On     
    2013-08-05 22:21:02 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:17:45 H/W Monitor  Raid Powered On     
    2013-08-05 22:15:20 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:13:42 H/W Monitor  Raid Powered On     
    2013-08-05 22:12:00 RS232 Terminal  VT100 Log In     
    2013-08-05 22:11:22 H/W Monitor  Raid Powered On     
    2013-08-05 22:09:24 Proxy Or Inband  HTTP Log In     
    2013-08-05 22:08:05 H/W Monitor  Raid Powered On     
    2013-08-05 21:45:56 Proxy Or Inband  HTTP Log In     
    2013-08-05 21:42:59 H/W Monitor  Raid Powered On     
    2013-08-05 21:34:06 Proxy Or Inband  HTTP Log In     
    2013-08-05 21:28:10 Proxy Or Inband  HTTP Log In     
    2013-08-05 21:23:52 Proxy Or Inband  HTTP Log In     
    2013-08-05 21:22:19 H/W Monitor  Raid Powered On     
    2013-08-05 21:16:19 H/W Monitor  Raid Powered On     
    2013-08-05 21:09:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 21:04:20 H/W Monitor  Raid Powered On     
    2013-08-05 21:01:42 H/W Monitor  Raid Powered On     
    2013-08-05 20:58:34 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:58:03 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:58:02 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:58:02 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:58:01 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:19 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:19 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:19 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:14 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:14 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:14 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:11 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:11 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:11 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:10 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:05 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:05 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:05 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:05 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:05 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:05 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:04 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:54:04 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:35 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:26 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:17 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:17 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:17 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:11 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:07 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:53:04 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:39 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:27 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:27 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:27 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:25 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:25 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:25 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:24 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:24 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:24 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:21 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:21 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:52:21 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:54 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:54 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:54 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:50 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:50 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:50 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:48 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:48 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:48 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:45 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:45 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:45 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:37 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:37 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:37 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:36 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:28 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:28 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:28 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:24 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:24 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:24 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:14 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:14 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:14 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:12 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:11 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:11 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:10 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:03 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:03 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:03 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:03 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:03 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:03 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:02 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:51:02 Proxy Or Inband  HTTP Log In     
    2013-08-05 20:49:16 H/W Monitor  Raid Powered On     
    2013-08-05 19:13:09 H/W Monitor  Raid Powered On     
    2013-08-04 22:22:24 H/W Monitor  Raid Powered On     
    2013-08-04 22:18:44 RS232 Terminal  VT100 Log In     
    2013-08-04 22:18:23 H/W Monitor  Raid Powered On     
    2013-08-04 22:14:44 H/W Monitor  Raid Powered On     
    2013-08-04 22:09:11 H/W Monitor  Raid Powered On     
    2013-08-04 22:02:48 H/W Monitor  Raid Powered On     
    2013-08-04 21:59:47 RS232 Terminal  VT100 Log In     
    2013-08-04 21:59:17 H/W Monitor  Raid Powered On     
    2013-08-04 21:56:13 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:56:09 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:56:09 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:56:09 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:56:04 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:57 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:57 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:57 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:45 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:44 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:41 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:39 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:06 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:05 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:05 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:05 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:05 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:55:05 Proxy Or Inband  HTTP Log In     
    2013-08-04 21:50:56 H/W Monitor  Raid Powered On     
    2013-08-04 14:04:37 H/W Monitor  Raid Powered On     
    2013-08-04 13:51:02 H/W Monitor  Raid Powered On     
    2013-08-04 13:48:33 H/W Monitor  Raid Powered On     
    2013-08-04 13:46:41 H/W Monitor  Raid Powered On     
    2013-08-04 13:43:44 H/W Monitor  Raid Powered On     
    2013-08-04 13:40:31 H/W Monitor  Raid Powered On     
    2013-08-04 13:35:55 H/W Monitor  Raid Powered On     
    2013-08-04 13:33:50 H/W Monitor  Raid Powered On     
    2013-08-04 13:32:10 H/W Monitor  Raid Powered On     
    2013-08-04 20:23:01 H/W Monitor  Raid Powered On     
    2013-08-04 20:21:48 Enc#2 SLOT 04  Time Out Error     
    2013-08-04 20:20:04 Raid Set # 000  RaidSet Degraded     
    2013-08-04 20:20:04 ARC-1880-VOL#000 Volume Degraded     
    2013-08-04 20:19:44 Enc#2 SLOT 04  Time Out Error     
    2013-08-04 20:13:32 H/W Monitor  Raid Powered On     
    2013-08-04 05:10:33 ARC-1880-VOL#000 Abort Checking 003:07:14 0 
    2013-08-04 02:03:19 ARC-1880-VOL#000 Start Checking     
    2013-08-04 01:15:44 H/W Monitor  Raid Powered On     
    2013-08-03 01:37:38 ARC-1880-VOL#000 Start Checking     
    2013-08-03 00:41:03 H/W Monitor  Raid Powered On     
    2013-08-03 00:37:30 H/W Monitor  Raid Powered On     
    2013-08-02 23:26:03 ARC-1880-VOL#000 Start Checking     
    2013-08-02 22:47:28 H/W Monitor  Raid Powered On     
    2013-08-02 22:44:44 H/W Monitor  Raid Powered On     
    2013-08-02 22:40:52 ARC-1880-VOL#000 Stop Checking 000:20:58 0 
    2013-08-02 22:19:54 ARC-1880-VOL#000 Start Checking     
    2013-08-02 21:38:18 H/W Monitor  Raid Powered On     
    2013-08-02 21:29:40 H/W Monitor  Raid Powered On     
    2013-08-02 14:22:04 H/W Monitor  Raid Powered On     
    2013-08-02 03:15:50 H/W Monitor  Raid Powered On     
    2013-08-02 03:13:28 H/W Monitor  Raid Powered On     
    2013-08-02 03:10:35 H/W Monitor  Raid Powered On     
    2013-08-02 03:08:58 H/W Monitor  Raid Powered On     
    2013-08-01 19:37:33 ARC-1880-VOL#000 Start Checking     
    2013-08-01 18:58:57 H/W Monitor  Raid Powered On     
    2013-08-01 18:57:30 H/W Monitor  Raid Powered On     
    2013-08-01 18:54:03 H/W Monitor  Raid Powered On     
    2013-08-01 18:52:09 H/W Monitor  Raid Powered On     
    2013-08-01 12:18:48 ARC-1880-VOL#000 Complete Check 008:37:17 0 
    2013-08-01 03:41:30 ARC-1880-VOL#000 Start Checking     
    2013-08-01 02:59:56 H/W Monitor  Raid Powered On     
    2013-07-31 22:24:21 H/W Monitor  Raid Powered On     
    2013-07-31 22:22:46 H/W Monitor  Raid Powered On     
    2013-07-31 22:20:33 H/W Monitor  Raid Powered On     
    2013-07-31 21:09:06 H/W Monitor  Raid Powered On     
    2013-07-31 21:07:16 H/W Monitor  Raid Powered On     
    2013-07-31 19:50:46 H/W Monitor  Raid Powered On     
    2013-07-31 19:49:09 H/W Monitor  Raid Powered On     
    2013-07-31 19:46:27 H/W Monitor  Raid Powered On     
    2013-07-31 11:22:46 ARC-1880-VOL#000 Complete Check 008:37:17 0 
    2013-07-31 02:45:28 ARC-1880-VOL#000 Start Checking     
    2013-07-31 02:00:54 H/W Monitor  Raid Powered On     
    2013-07-29 21:57:08 H/W Monitor  Raid Powered On     
    2013-07-29 21:55:11 H/W Monitor  Raid Powered On     
    2013-07-29 21:43:28 H/W Monitor  Raid Powered On     
    2013-07-29 21:40:07 H/W Monitor  Raid Powered On     
    2013-07-29 21:37:46 H/W Monitor  Raid Powered On     
    2013-07-27 08:19:46 ARC-1880-VOL#000 Complete Check 008:37:22 0 
    2013-07-26 23:42:23 ARC-1880-VOL#000 Start Checking     
    2013-07-26 22:42:48 H/W Monitor  Raid Powered On     
    2013-07-23 13:20:30 ARC-1880-VOL#000 Complete Check 007:04:21 0 
    2013-07-23 06:16:09 ARC-1880-VOL#000 Start Checking     
    2013-07-23 04:55:07 ARC-1880-VOL#000 Stop Checking 001:32:58 0 
    2013-07-23 03:22:09 ARC-1880-VOL#000 Start Checking     
    
    Here is a screen capture of the RaidSet Hierarchy before running "LeVeL2ReScUe":
    [​IMG]

    Here is a screen capture of the RaidSet Hierarchy after running "LeVeL2ReScUe":
    [​IMG]

    Here is a screen capture from the System Information screen:
    [​IMG]
     
  7. mwroobel

    mwroobel [H]ardness Supreme

    Messages:
    4,915
    Joined:
    Jul 24, 2008
    At this point, given the caveats mentioned above, activate the raidset and reboot. See if windows sees it properly and back up all important data as soon as possible. Once that is complete, run a consistency check and see if there are any errors. As suggested, you may want to add an additional drive and migrate the array to RAID6, but I would do a backup of all data (or at least all data you can't replace/replicate) before you attempt it.
     
  8. Isoparm

    Isoparm n00b

    Messages:
    10
    Joined:
    Aug 5, 2013
    If I select "Activate Incomplete RAID Set" menu item and click "submit" I get "Raid Set Already Active".

    Is there another way to activate the Raid Set?
     
  9. mwroobel

    mwroobel [H]ardness Supreme

    Messages:
    4,915
    Joined:
    Jul 24, 2008
    That is not good, it means your current set is active. What do you see in Windows Disk Management for the volume? If it tells you it needs to write a signature, format or anything else, DO NOT do it and report back with a screenshot.
     
    Last edited: Aug 7, 2013
  10. Isoparm

    Isoparm n00b

    Messages:
    10
    Joined:
    Aug 5, 2013
    That's the thing it doesn't show up in Windows Disk Management either:

    [​IMG]
     
  11. mwroobel

    mwroobel [H]ardness Supreme

    Messages:
    4,915
    Joined:
    Jul 24, 2008
    Please reinstall the Storport drivers for your card. Do you see the card in Device Manager and is it in normal mode (no yellow exclamation mark or red X through the icon?) When you went into disk manager did it pop up a message that it found a volume and needed to write a signature, format etc?
     
  12. Isoparm

    Isoparm n00b

    Messages:
    10
    Joined:
    Aug 5, 2013
    Reinstalled the drivers. Tried it in two different OS versions. No luck.

    The card is running normal in Device Manager. Nothing pops up in Disk Manager and I've even tried to rescan for new hardware and new disks.
     
  13. staticlag

    staticlag [H]ard|Gawd

    Messages:
    1,675
    Joined:
    Mar 26, 2010
    sounds like the pci-e port is hosed. change ports for the card and re-try