ARECA Owner's Thread (SAS/SATA RAID Cards)

There are also RJ45 based 10G NICs, such as the Intel X540. They cost a little more than the X520 SFP+ based cards, but most large GigE switches use SFP/SFP+ uplink ports, so I went with the SFP+ based NICs.

With RJ45 based 10G, you want to use Cat7 cables and it doesn't like electric interference. Fiber is completely immune to that.

RJ45 based 10G switches are still very expensive, so they are typically not used in home environments.
 
So, I'd ordered some replacement chipset coolers for the ARC-1883ix-12 I bought, I unseated the 4 chipset mounting pins however the factory heatsink appears to be adhesed to the card?

I'm a bit of a noob when it comes to aftermarket cooling for cards like this, has anyone else tried removing their heatsink for these cards?

Tips?
 
So, I'd ordered some replacement chipset coolers for the ARC-1883ix-12 I bought, I unseated the 4 chipset mounting pins however the factory heatsink appears to be adhesed to the card?

I'm a bit of a noob when it comes to aftermarket cooling for cards like this, has anyone else tried removing their heatsink for these cards?

Tips?

IIRC, use a hair-dryer on low-heat/low-speed to gently heat the heatsink until you can wriggle and pull it off.
Be gentle! The CPU (ROC) on at least some of the ARC-188x series is de-lidded (i.e. no metal heatspreader), so excessive force could ruin the chip and basically leave you with a physically broken card that will not be covered under warranty.

Note that if you have issues, sending the card to Areca/Tekram with a modified HSF WILL void your warranty. Be ready to remount it if you ever need service.

Also, do you actually have a temperature problem with the card? IME the stock Areca HSF is good enough for the LSI ROCs on the 188x series, but mine have always been in a server case with decent airflow.
 
Last edited:
MZuGycc.png


I have an ARC-1880i connected to multiple drives via an Intel RES2SV240 expander. The problem is that no matter which drive is concerned, the system log always reports the device as "Enc#2 ArrayDevic" -- I think it's cut off due to a length limitation. The devices as listed in the hierarchy are ArrayDevice00, 01, etc.

The BIOS/CLI/web interface all have this problem. Running latest 1.52 FW. Any solutions?
 
Last edited:
Might be how the expander reports things? On my 1880i with a Supermicro (LSI based) SAS expander backplane, each line item is reported as follows for me:

Enc#2 ###

### being the slot number. Do you have SES2 enabled?
 
Might be how the expander reports things?

You got it, the "device" name appears to be chosen by the expander.

Do you have SES2 enabled?

Yes, but it's a dumb Norco backplane so I've never used it. I just disabled it to see if that changes how the expander reports. But the Areca does show the full device name in the hierarchy, which makes me think it's a hard-coded length limitation in the log entry.

wfG4yPr.png


I'll be migrating to an SC846 soon, so glad to hear its expander reports things succinctly.
 
IIRC, use a hair-dryer on low-heat/low-speed to gently heat the heatsink until you can wriggle and pull it off. The CPU (ROC) underneath has a heatspreader, so you're not likely to damage it. YMMV, of course (I did it on a 1680 back in the day).

Note that if you have issues, sending the card to Areca/Tekram with a modified HSF WILL void your warranty. Be ready to remount it if you ever need service.

Also, do you actually have a temperature problem with the card? IME the stock Areca HSF is good enough for the LSI ROCs on the 188x series, but mine have always been in a server case with decent airflow.

Yea no heat issues as yet. I had read that someone was saying these cards run hot, but it sounds like that may not be the case. I noticed the temps were a little high (55 degrees Celsius) I'll try it again under load and see how it is with the stock HS

Interesting suggestion with the hair dryer, since posting I'd read that putting the card in the freezer would also help with removing the HS but a blow dryer sounds like a better bet.

In either case, I'll wait until I can get a nice array going to put the card under proper load and have another look at the thermals

Thanks again!!
 
I had read that someone was saying these cards run hot, but it sounds like that may not be the case.

This Austrian modified his 1883-ix-12 HSF

jTDfXOe.jpg


Note that the guy above didn't like the fan noise, rather than temps. His mod didn't really make a temp difference.

The chip actually does run hot -- the LSI cards with only a passive heatsink can reach mid-90s under load if not properly cooled by case airflow. The older Intel IOP chips Areca
used in the 1680s and earlier cards used to get hot even with the heatsink, IIRC.

If you do plan to take it off, heat it evenly and then twist/pull it, virtually no risk since there's the big heatsink underneath it.

I would NOT remove the full front-to-back assembly (for warranty purposes) from the 1883ix-XX. If you decide to go that way, note that the ROC doesn't have HSF mounting holes for a dedicated heatsink -- you'll have to use adhesive paste. Here's a "bare" view of the 1883ix-XX with the giant heatsink off:

N2oqBbn.png
 
Last edited:
Wow awesome info thanks!

Yea I bought two crappy $6 chipset heatsinks with little fans that should be marginally better than the stock HS.

Given that the ROC doesnt have conventional mounts, I think i'll just keep an eye on the temps and use the stock HS if the temps stay under 60-70 degrees Celsius.

The 16gb stick of ECC memory I ordered arrived today, I'll give it a shot when I get home in a few hours and let you folks know the results... Standby
 
Yea I bought two crappy $6 chipset heatsinks with little fans that should be marginally better than the stock HS.

The important thing is, the stock heatsink is a blower (sucks air in from the top, expels out of one side along the heatsink fins). So conventional fans (top-to-bottom) won't do much, and will in fact hurt because their will now be much less airflow along the heatsink fins.

Also, since thermally the entire black heatsink serves to draw away heat from the ROC, the location of the fan is arbitrary.

Here's a fairly cheap, no-risk exercise I would do if I had one of these:
  1. I think the space between the DIMM and the edge of the card where the PCI-slot begins is just enough to accommodate a 60mm fan (if not, then definitely 40mm).
  2. Measure it, and get two 60mm (or 40mm) fans, 25mm deep. Also get two finger guards of the appropriate size.
  3. Disconnect the stock fan and just leave it in place.
  4. Screw finger guards onto the the open (air IN) side of the fans, and place them on the main boundaries of the heatsink as in the picture below; use one or two rubber bands going over the top of the fan and around the card to secure the fans.
  5. Plug card into motherboard
  6. Connect fans to Molex adapter (NOT the card's fan connector)
  7. See what kind of difference this makes compared to the built-in fan.

You can also do this experiment with just one fan/finger guard placed towards the rear (furthest from built-in fan).

I think this will be way more effective than replacing the stock fan. As an extreme step, you could remove the black heatsink and re-mount it using a high-quality non-adhesive thermal compound on the ROC and expander chips.

4rFwcrL.jpg
 
Yea that's definitely going to be the easier solution. I'll do just that if the temps aren't ideal when I get some new SSDs to put this card under a bit more load. I don't have a whole ton of airflow where the card is mounted but so far its not running too too hot with just 2 SSD raid members.

Thanks again for your help, I really appreciate it. I wouldnt have realized that the ROC mounts were non conventional until the entire HS had been removed without that tidbit.

Thanks again!
 
Yea that's definitely going to be the easier solution.

Note: I take back my earlier comment about the LSI ROC having a heatspreader making forcible heatsink removal less risky. I recently got an 1883i and the ROC is delidded with no metal heatspreader. There is no thermal compound; the HSF interfaces to the ROC via a thermal pad, and the ROC is also surrounded by a protective rubber boundary to prevent excessive force from the HSF. Removes very easily by just unclipping the white plastic pegs.

I'll post pictures soon. If the larger heatsink is attached similarly (via the plastic pegs and thermal pads -- no adhesive), one more thing to try would be to replace Areca's generic black thermal pad with something like an Arctic Silver thermal pad and remount the heatsink.

Mine is idling around 57C so I might try some "solutions" once the card is put into active service. Current ARC-1880i by contrast is idling around 42C.
 
Yea there's definitely adhesive in addition to the white plastic pegs, I've tried removing the pins but the HS is stuck fast to the chipsets below. applying a small amount of torsion and the hs will rotate ever so slightly (not mechanically fixed [screws]) so it seems like an adhesive of some kind on my 1883ix
 
My [ARC-1883i] is idling around 57C so I might try some "solutions" once the card is put into active service. Current ARC-1880i by contrast is idling around 42C.

So the ARC-1883i HSF interfaces to the bare LSI RoC via a generic black thermal pad. No grease or adhesive involved.

  • Peeled pad off from the back of the HSF
  • Applied a tiny pea of Noctua-NH1 on the LSI RoC
  • Aligned heatsink and pushed pegs in.
  • Gently lifted one springy corner and held up against light to see that the thermal compound had spread properly with no "leaks"
Result: Load temp went from 66C to 46C. Idle from 48C to 40C.
 
stunnel is the easiest solution I found for getting notification emails from the Areca card. Don't have time to write a step by step but I'll post my config file (stunnel.conf) which assumes gmail. I'm using the Windows version, on one of my VM's I have stunnel.exe in windows startup folder. This program listens on port 25 and then tunnels to a secure connection on smtp.gmail.com:465. So you configure the notification page in the Areca web admin for the IP of the machine running stunnel, along with your gmail username and password.

Hi..

I tried the same settings but I cant get archttp to send the email.

I set acrhttp to use smtp to 127.0.0.1:25 with my email and password for gmail.

Can you please show me the config for archttp and for stunnel?
 
Does anyone have the new SuperCap flash backup instead of a regular BBU? If so, can you comment on how it connects to the RAID controller? I'm not a fan of the dummy PCIe form factor - - is the connection long enough to just mount the SuperCap FBU elsewhere in the chassis?

Any general impressions about the SuperCap FBU would be appreciated. Also, any hacks (or available cables) to connect the standard BBU to the new slim connector on the 1883 series?
 
Is the supercap an option without a "CacheVault"/NVM (flash) module? The supercap doesn't have nearly the energy of the Li-Ion battery. Its job is to provide enough power to dump the unwritten cache to NVM (flash) in the event of a power failture, not to keep the cache powered for hours.
 
Is the supercap an option without a "CacheVault"/NVM (flash) module? The supercap doesn't have nearly the energy of the Li-Ion battery. Its job is to provide enough power to dump the unwritten cache to NVM (flash) in the event of a power failture, not to keep the cache powered for hours.

Of course the capacitors are only available in a package with NAND flash and associated circuitry :p

The problem is that unlike the elegant CacheVault package which fits onto the top of the LSI controller, Areca's supercap is an ungainly discrete piece (below). Their batteries have also been similar, but at least they're shorter so they'll fit in that top PCIe slot without being obstructed by the heatsinks common on many mobos.

wpda6af7f6_05_06.jpg
 
hi

i have one ARC-1680ix-16.
yesterday when i turn on the server i find out that the raid array is missing from the OS. i check through web interface and i find out that there are missing slots from the RaidSet Hierarchy section. normally its shows enclosure#1 and #2. now its shows only #1 like the image.
Screenshot%202016-02-20%2023.26.59.png


i try to unplug the card and re-plug but nothing. i have the last firmware 1.51.

anyone knows how to fix the problem?
thanks a lot
 
hi

i have one ARC-1680ix-16.
yesterday when i turn on the server i find out that the raid array is missing from the OS. i check through web interface and i find out that there are missing slots from the RaidSet Hierarchy section. normally its shows enclosure#1 and #2. now its shows only #1 like the image.
Screenshot%202016-02-20%2023.26.59.png


i try to unplug the card and re-plug but nothing. i have the last firmware 1.51.

anyone knows how to fix the problem?
thanks a lot
That's not good. Means the on-board SAS expander isn't being recognized. Do you still have the serial cable that plugs into the RJ11 port on the card? That's the CLI for said expander. Might be able to poke through there to see what's going on.
 
That's not good. Means the on-board SAS expander isn't being recognized. Do you still have the serial cable that plugs into the RJ11 port on the card? That's the CLI for said expander. Might be able to poke through there to see what's going on.

unfortunately i bought this card as used, so i don't have this cable. i can buy one if you think that will help to solve this problem.

edit: i have just realize i don't have serial port. is it ok to buy a rj11 to usb? :)
 
Last edited:
edit: i have just realize i don't have serial port. is it ok to buy a rj11 to usb? :)

NO! Do not buy a "USB-to-RJ11" modem, or worse, a dumb USB-4-pin to RJ11-4-pin adapter.

This is the pinout for the Areca RJ11 expander connector:

njwdfBe.png


To make your own cable, you will need:

  1. USB to RS232 serial male adapter (cheaper ones are available but the FTDI chipset just works)
  2. Modular (i.e. configurable) DB9 female to RJ11 adapter
  3. RJ11 cable
I'm deliberately not including the DB9 pinouts. If you're not confident about figuring those out, you shouldn't be making this cable. Contact Areca Support (or Tekram) and beg/buy a cable.

I don't have an Areca -IX card any more or I'd let you borrow mine.

PS: A lot of motherboards will include a COM1 header on the board, even if there is no serial port connector on the I/O. Those are standardized and instead of the USB, you can get a simpler adapter like this. It's a native serial port which is always preferable to a USB adapter.
 

As an Amazon Associate, HardForum may earn from qualifying purchases.
That's not good. Means the on-board SAS expander isn't being recognized. Do you still have the serial cable that plugs into the RJ11 port on the card? That's the CLI for said expander. Might be able to poke through there to see what's going on.

Good morning :)

i contacted areca and this was the reply
Dear Sir/Madam,
the expander chip on this card is failed.
this card have an expander chip onboard to be able to provide 24 ports. so you will not able to see any drive in manager console if this expander chip is malfunction.
if you would like to RMA this card, you can contact with your original supplier for assist. because our RMA is processed through the distributor which sold the product.
if you do not able to reach the supplier or they are not our distributor. please inform me the information of your supplier and the serial number of your card. we can trace these information to find out the original distributor to assist you RMA.

Best Regards,

i decide to buy a working controller.

thanks a lot for the help
 
Does someone know a brand/model of a fan to change the original one?
It is on the last few days of life and making extreme noise, I want something that would fit in the same place.

Also my Chanbro 23601 has what I believe to be the same size fan and I would fit this new model in both of them.

Edit: I believe they are 40x40x10mm
 
Last edited:
UPDATE: It was a mail white listing issue. Communication is flowing both ways now :).
If anyone is having an issue like I was, I started CCing sales into the emails and I think they forwarded it internally.

Hey, has anyone delt with areca support lately? I have an issue with my ARC-1883I where it is timing out all disks once a volume is created and I start writing data in the os (tested on ESXi6 and win2012R2), previously this raid was running strong for the past 11 months.

I am running 12 Seagate 3tb NAS drives in raid 6. I was originally using a Intel sas expander and a dumb norco chassis.

When I first contacted support they got back to me within a day asking me to try without my Intel sas expander and with new sas cables, running just 8 drives directly also would time out and fail the array instantly. I have since replaced my dumb norco with a supermicro with a expander built in the backplane and 5 of the 12 disks in the array as well as the sas cable.(some of the new disks are also timing out)

However since the first reply I got from areca support I have not been able to get a single reply back.
I have emailed them about once every week for the past 6 weeks.. Both in plain text, from Gmail, my work email account and my ISP provided email address.

I am really hoping this is just a fault with their mail filters and not that I am being ignored. I would hate to go to another raid card provider as they seem to be the only ones with on board management nics.

If anyone has a alternative contact for areca support that would be great.
 
Last edited:
I have an ancient ARC1280 with 24 SATA ports. I have 14 disks connected to it forming one RAID6 volume, 7 disks are connected to ports 1-7 and the other 7 to 18-24. Does it matter to what SATA port on the card the disks are connected? Can I just rearrange and connect the 14 disks to ports 1-14 for example? Will I keep my RAID?
 
I have an ancient ARC1280 with 24 SATA ports. I have 14 disks connected to it forming one RAID6 volume, 7 disks are connected to ports 1-7 and the other 7 to 18-24. Does it matter to what SATA port on the card the disks are connected? Can I just rearrange and connect the 14 disks to ports 1-14 for example? Will I keep my RAID?
Yes, you can. It is a feature called array roaming. One caveat, if you need to ever use any of the Areca special repair procedures you MUST have the drives in the original order the array was created in, though for normal use you can put them in any order.
 
Still have an old ARC1210 banging away with four old WD RE3 1TBs in RAID6 since they were both new things, just for storage on the main rig myself.

Areca does make pretty solid hardware RAID cards.

It's down on the bottom there with all the other ancient things like my X58 still running an OC'd X5680 @ 4.5 :)

ajJnwVI.jpg


Most things have been changed over time I guess.
 
Last edited:
ARC-1882ix-12-2G and Toshiba MD04ACA400(HDETR11GEA51) Fail 6x

This is new setup. Array degrades with failed drives. It happens on 6 of the 7 servers we built.

Even in Bios the Array will not rebuild and fails different drives?

Can't find Areca Support. Email and Phones don't work.

Any help would be appreciated. Newbe to HardForum...
 
ARC-1882ix-12-2G and Toshiba MD04ACA400(HDETR11GEA51) Fail 6x

This is new setup. Array degrades with failed drives. It happens on 6 of the 7 servers we built.

Even in Bios the Array will not rebuild and fails different drives?

Can't find Areca Support. Email and Phones don't work.

Any help would be appreciated. Newbe to HardForum...


Please post specifics about the enclosures you are running, the BIOS/Firmware revisions of both the cards and the drives. Please post the full card log from one of the machines. What kind of power supplies, motherboards and other installed devices are you running? Is it always the same drives dropping out? Do they show as failed or free when they drop? Are the 8087/SATA cables you are using the ones shipped with the cards or did you buy third party cables? Do you have power management enabled on the card? You are aware that none of the MD series Toshiba drives are listed in their HCL, only some of the MG series, right?
 
Please post specifics about the enclosures you are running, the BIOS/Firmware revisions of both the cards and the drives
  • Generic Chassis, 900 Watt Power Supply
  • Gigabyte MB Z97X-UD5H-BK, Bios 04.06.05
  • Controller Name ARC-1882IX-12
    Firmware Version V1.53 2016-02-16
    BOOT ROM Version V1.53 2016-03-16
    PL Firmware Version 19.0.0.0
    Main Processor Intel Core i7-4770
    Memory 8GB
Windows Driver is latest
  • Date: 11/15/2014, Version 6.20.0.31

  • Typical Drives in 10 Disk Raid 6
  • Device Type SATA(5001B4D51C7F101C)
    Device Location Enclosure#2 SLOT 01
    Model Name TOSHIBA MD04ACA400
    Serial Number 85R2KPIOFSAA
    Firmware Rev. FP2A
    Disk Capacity 4000.8GB
    Physical Block Size 4096
    Logical Block Size 512
    Current SATA Mode SATA600+NCQ(Depth32)
    Supported SATA Mode SATA600+NCQ(Depth32)
    Error Recovery Control (Read/Write) Disabled/Disabled
    Disk APM Support Yes
    Device State Normal
    Timeout Count 0
    Media Error Count 0
    Rotation Speed 7200(RPM)
    Device Temperature 32 ºC
    48Bit LBA Support Yes
    SMART Read Error Rate 100(50)
    SMART Spinup Time 100(1)
    SMART Reallocation Count 100(50)
    SMART Seek Error Rate 100(50)
    SMART Spinup Retries 101(30)
    SMART Calibration Retries N.A.(N.A.)
    SSD Reserved Space N.A.(N.A.)
    SSD Wearing Indicator N.A.(N.A.)

. Please post the full card log from one of the machines.
  • 2016-05-02 10:00:18 E2 SLOT 03 HotSpare Deleted
    2016-05-02 09:59:57 Proxy Or Inband HTTP Log In
    2016-05-02 09:01:50 H/W Monitor Raid Powered On
    2016-05-02 08:58:12 E2 SLOT 03 HotSpare Created
    2016-05-02 08:58:11 Enc#2 SLOT 03 Device Inserted
    2016-05-02 08:57:36 Enc#2 SLOT 03 Device Removed
    2016-05-02 08:33:24 Raid Set # 000 Delete RaidSet
    2016-05-02 08:33:24 ARC-1882-VOL#000 Abort Rebuilding 000:00:38
    2016-05-02 08:32:46 ARC-1882-VOL#000 Start Rebuilding
    2016-05-02 08:32:43 Raid Set # 000 Rebuild RaidSet
    2016-05-02 08:32:43 E2 SLOT 09 HotSpare Used
    2016-05-02 08:32:42 E2 SLOT 09 HotSpare Created
    2016-05-02 08:32:03 Raid Set # 000 Delete RaidSet
    2016-05-02 08:31:40 Proxy Or Inband HTTP Log In
    2016-04-30 06:36:28 ARC-1882-VOL#000 Complete Rebuild 000:31:30
    2016-04-30 06:04:58 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 06:04:56 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 06:04:56 Enc#2 SLOT 05 Device Inserted
    2016-04-30 06:04:55 Enc#2 SLOT 05 Device Removed
    2016-04-30 06:04:55 ARC-1882-VOL#000 Stop Rebuilding 000:10:49
    2016-04-30 06:04:55 Raid Set # 000 RaidSet Degraded
    2016-04-30 06:04:55 ARC-1882-VOL#000 Volume Failed
    2016-04-30 05:54:05 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 05:54:03 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 05:54:03 Enc#2 SLOT 01 Device Inserted
    2016-04-30 05:54:02 Enc#2 SLOT 01 Device Removed
    2016-04-30 05:54:01 ARC-1882-VOL#000 Stop Rebuilding 001:21:50
    2016-04-30 05:54:01 Raid Set # 000 RaidSet Degraded
    2016-04-30 05:54:01 ARC-1882-VOL#000 Volume Failed
    2016-04-30 04:32:11 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 04:32:09 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 04:32:09 Enc#2 SLOT 01 Device Inserted
    2016-04-30 04:32:08 Enc#2 SLOT 01 Device Removed
    2016-04-30 04:32:08 ARC-1882-VOL#000 Stop Rebuilding 000:05:45
    2016-04-30 04:32:08 Raid Set # 000 RaidSet Degraded
    2016-04-30 04:32:08 ARC-1882-VOL#000 Volume Failed
    2016-04-30 04:26:22 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 04:26:20 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 04:26:20 Enc#2 SLOT 01 Device Inserted
    2016-04-30 04:26:19 Enc#2 SLOT 01 Device Removed
    2016-04-30 04:26:19 ARC-1882-VOL#000 Stop Rebuilding 000:50:52
    2016-04-30 04:26:19 Raid Set # 000 RaidSet Degraded
    2016-04-30 04:26:19 ARC-1882-VOL#000 Volume Failed
    2016-04-30 03:35:27 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 03:35:25 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 03:35:25 Enc#2 SLOT 01 Device Inserted
    2016-04-30 03:35:24 Enc#2 SLOT 01 Device Removed
    2016-04-30 03:35:24 ARC-1882-VOL#000 Stop Rebuilding 000:26:20
    2016-04-30 03:35:24 Raid Set # 000 RaidSet Degraded
    2016-04-30 03:35:24 ARC-1882-VOL#000 Volume Failed
    2016-04-30 03:09:04 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 03:09:02 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 03:09:02 Enc#2 SLOT 01 Device Inserted
    2016-04-30 03:09:01 Enc#2 SLOT 01 Device Removed
    2016-04-30 03:09:01 ARC-1882-VOL#000 Stop Rebuilding 000:55:50
    2016-04-30 03:09:01 Raid Set # 000 RaidSet Degraded
    2016-04-30 03:09:01 ARC-1882-VOL#000 Volume Failed
    2016-04-30 02:13:10 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 02:13:08 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 02:13:08 Enc#2 SLOT 05 Device Inserted
    2016-04-30 02:13:08 Enc#2 SLOT 05 Device Removed
    2016-04-30 02:13:07 ARC-1882-VOL#000 Stop Rebuilding 000:31:51
    2016-04-30 02:13:07 Raid Set # 000 RaidSet Degraded
    2016-04-30 02:13:07 ARC-1882-VOL#000 Volume Failed
    2016-04-30 01:41:16 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 01:41:14 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 01:41:14 Enc#2 SLOT 01 Device Inserted
    2016-04-30 01:41:13 Enc#2 SLOT 01 Device Removed
    2016-04-30 01:41:13 ARC-1882-VOL#000 Stop Rebuilding 000:12:45
    2016-04-30 01:41:13 Raid Set # 000 RaidSet Degraded
    2016-04-30 01:41:13 ARC-1882-VOL#000 Volume Failed
    2016-04-30 01:28:27 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 01:28:25 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 01:28:25 Enc#2 SLOT 04 Device Inserted
    2016-04-30 01:28:24 Enc#2 SLOT 04 Device Removed
    2016-04-30 01:28:24 ARC-1882-VOL#000 Stop Rebuilding 000:26:58
    2016-04-30 01:28:24 Raid Set # 000 RaidSet Degraded
    2016-04-30 01:28:24 ARC-1882-VOL#000 Volume Failed
    2016-04-30 01:01:26 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 01:01:24 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 01:01:24 Enc#2 SLOT 01 Device Inserted
    2016-04-30 01:01:23 Enc#2 SLOT 01 Device Removed
    2016-04-30 01:01:23 ARC-1882-VOL#000 Stop Rebuilding 001:26:26
    2016-04-30 01:01:23 Raid Set # 000 RaidSet Degraded
    2016-04-30 01:01:23 ARC-1882-VOL#000 Volume Failed
    2016-04-29 23:34:57 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 23:34:55 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 23:34:55 Enc#2 SLOT 08 Device Inserted
    2016-04-29 23:34:54 Enc#2 SLOT 08 Device Removed
    2016-04-29 23:34:53 ARC-1882-VOL#000 Stop Rebuilding 000:36:12
    2016-04-29 23:34:53 Raid Set # 000 RaidSet Degraded
    2016-04-29 23:34:53 ARC-1882-VOL#000 Volume Failed
    2016-04-29 22:58:41 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 22:58:39 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 22:58:39 Enc#2 SLOT 08 Device Inserted
    2016-04-29 22:58:39 Enc#2 SLOT 08 Device Removed
    2016-04-29 22:58:38 ARC-1882-VOL#000 Stop Rebuilding 003:16:47
    2016-04-29 22:58:38 Raid Set # 000 RaidSet Degraded
    2016-04-29 22:58:38 ARC-1882-VOL#000 Volume Failed
    2016-04-29 19:41:50 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 19:41:48 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 19:41:48 Enc#2 SLOT 01 Device Inserted
    2016-04-29 19:41:48 Enc#2 SLOT 01 Device Removed
    2016-04-29 19:41:47 ARC-1882-VOL#000 Stop Rebuilding 000:38:26
    2016-04-29 19:41:47 Raid Set # 000 RaidSet Degraded
    2016-04-29 19:41:47 ARC-1882-VOL#000 Volume Failed
    2016-04-29 19:03:21 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 19:03:19 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 19:03:19 Enc#2 SLOT 01 Device Inserted
    2016-04-29 19:03:18 Enc#2 SLOT 01 Device Removed
    2016-04-29 19:03:18 ARC-1882-VOL#000 Stop Rebuilding 000:19:32
    2016-04-29 19:03:18 Raid Set # 000 RaidSet Degraded
    2016-04-29 19:03:18 ARC-1882-VOL#000 Volume Failed
    2016-04-29 18:43:45 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 18:43:43 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 18:43:43 Enc#2 SLOT 08 Device Inserted
    2016-04-29 18:43:42 Enc#2 SLOT 08 Device Removed
    2016-04-29 18:43:42 ARC-1882-VOL#000 Stop Rebuilding 001:18:35
    2016-04-29 18:43:42 Raid Set # 000 RaidSet Degraded
    2016-04-29 18:43:42 ARC-1882-VOL#000 Volume Failed
    2016-04-29 17:25:07 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 17:25:05 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 17:25:05 Enc#2 SLOT 01 Device Inserted
    2016-04-29 17:25:04 Enc#2 SLOT 01 Device Removed
    2016-04-29 17:25:04 ARC-1882-VOL#000 Stop Rebuilding 001:32:18
    2016-04-29 17:25:04 Raid Set # 000 RaidSet Degraded
    2016-04-29 17:25:04 ARC-1882-VOL#000 Volume Failed
    2016-04-29 16:15:16 Enc#2 SLOT 09 Device Inserted
    2016-04-29 16:15:16 Enc#2 SLOT 09 Device Removed
    2016-04-29 16:15:15 Raid Set # 000 RaidSet Degraded
    2016-04-29 16:15:15 ARC-1882-VOL#000 Volume Degraded
    2016-04-29 15:52:45 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 15:52:45 ARC-1882-VOL#000 Complete Init 025:37:39
    2016-04-29 08:32:16 Enc#2 SLOT 03 Device Inserted
    2016-04-29 08:32:00 Proxy Or Inband HTTP Log In
    2016-04-29 08:30:42 Enc#2 SLOT 03 Device Removed
    2016-04-28 15:00:51 Raid Set # 000 Delete RaidSet
    2016-04-28 15:00:26 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:26 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:25 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:25 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:25 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:25 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:25 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:25 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 15:00:23 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:23 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 14:24:48 Enc#2 SLOT 03 Device Inserted
    2016-04-28 14:24:47 Enc#2 SLOT 03 Device Removed
    2016-04-28 14:24:43 Raid Set # 000 RaidSet Degraded
    2016-04-28 14:24:43 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 14:23:42 Proxy Or Inband HTTP Log In
    2016-04-28 14:15:05 ARC-1882-VOL#000 Start Initialize
    2016-04-28 14:15:03 ARC-1882-VOL#000 Create Volume
    2016-04-28 14:15:03 Raid Set # 000 Create RaidSet
    2016-04-28 14:14:41 Raid Set # 000 Delete RaidSet
    2016-04-28 14:14:36 Raid Set # 000 Delete RaidSet
    2016-04-28 14:14:28 Raid Set # 000 Delete RaidSet
    2016-04-28 14:13:43 Proxy Or Inband HTTP Log In
    2016-04-28 10:03:21 Enc#2 SLOT 03 Device Inserted
    2016-04-28 10:03:20 Enc#2 SLOT 03 Device Removed
    2016-04-28 09:47:58 Enc#2 SLOT 03 Device Inserted
    2016-04-28 09:47:57 Enc#2 SLOT 03 Device Removed
    2016-04-28 09:47:57 ARC-1882-VOL#000 Abort Rebuilding 000:44:18
    2016-04-28 09:47:57 Raid Set # 000 RaidSet Degraded
    2016-04-28 09:47:57 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 09:34:06 Enc#2 SLOT 09 Device Inserted
    2016-04-28 09:34:05 Enc#2 SLOT 09 Device Removed
    2016-04-28 09:34:05 Raid Set # 000 RaidSet Degraded
    2016-04-28 09:34:05 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 09:03:39 ARC-1882-VOL#000 Start Rebuilding
    2016-04-28 09:03:36 Raid Set # 000 Rebuild RaidSet
    2016-04-28 09:03:36 E2 SLOT 03 HotSpare Used
    2016-04-28 09:03:36 E2 SLOT 03 HotSpare Created
    2016-04-28 09:02:21 Raid Set # 000 Delete RaidSet
    2016-04-28 08:58:39 Enc#2 SLOT 03 Device Inserted
    2016-04-28 08:57:21 Proxy Or Inband HTTP Log In
    2016-04-28 08:41:42 H/W Monitor Raid Powered On
    2016-04-27 21:37:03 ARC-1882-VOL#000 Complete Rebuild 003:54:11
    2016-04-27 17:42:51 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:42:49 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:42:49 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:42:48 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:42:48 ARC-1882-VOL#000 Stop Rebuilding 000:00:50
    2016-04-27 17:42:48 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:42:48 ARC-1882-VOL#000 Volume Failed
    2016-04-27 17:41:57 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:41:55 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:41:55 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:41:54 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:41:54 ARC-1882-VOL#000 Stop Rebuilding 000:01:29
    2016-04-27 17:41:54 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:41:54 ARC-1882-VOL#000 Volume Failed
    2016-04-27 17:40:25 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:40:23 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:40:23 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:40:21 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:40:05 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:40:04 ARC-1882-VOL#000 Stop Rebuilding 000:24:26
    2016-04-27 17:40:04 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:40:04 ARC-1882-VOL#000 Volume Failed
    2016-04-27 17:15:38 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:15:36 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:15:36 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:15:35 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:15:35 ARC-1882-VOL#000 Stop Rebuilding 000:15:55
    2016-04-27 17:15:35 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:15:35 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:59:39 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:59:37 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:59:37 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:59:36 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:59:36 ARC-1882-VOL#000 Stop Rebuilding 000:38:14
    2016-04-27 16:59:36 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:59:36 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:21:22 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:21:20 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:21:20 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:21:19 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:21:19 ARC-1882-VOL#000 Stop Rebuilding 000:01:54
    2016-04-27 16:21:19 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:21:19 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:19:24 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:19:22 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:19:22 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:19:21 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:19:21 ARC-1882-VOL#000 Stop Rebuilding 000:01:47
    2016-04-27 16:19:21 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:19:21 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:17:33 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:17:31 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:17:31 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:17:30 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:17:30 ARC-1882-VOL#000 Stop Rebuilding 000:04:08
    2016-04-27 16:17:30 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:17:30 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:13:21 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:13:19 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:13:19 Enc#2 SLOT 06 Device Inserted
    2016-04-27 16:13:18 Enc#2 SLOT 06 Device Removed
    2016-04-27 16:13:18 ARC-1882-VOL#000 Stop Rebuilding 000:31:29
    2016-04-27 16:13:18 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:13:18 ARC-1882-VOL#000 Volume Failed
    2016-04-27 15:41:49 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 15:41:47 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 15:41:47 Enc#2 SLOT 08 Device Inserted
    2016-04-27 15:41:46 Enc#2 SLOT 08 Device Removed
    2016-04-27 15:41:46 ARC-1882-VOL#000 Stop Rebuilding 003:48:09
Is it always the same drives dropping out?
  • No, If I rebuild with one that dropped, it can be set to hot spare. And the another drive will drop. What's odd is that you see removed and inserted when we didn't physically pull the drive.

Do they show as failed or free when they drop?
  • They say failed, but can be instantly set to hot spare.

Are the 8087/SATA cables you are using the ones shipped with the cards or did you buy third party cables?
  • 3Ware from Newegg, Item=9SIA24G28N2208, SFF-8087 to 4 Sata

Do you have power management enabled on the card?
  • Here are the settings (Default?) from Hdd Power Management
  • Stagger Power On Control
    0.7

    Time To Hdd Low Power Idle
    Disabled

    Time To Hdd Low RPM Mode
    Disabled

    Time To Spin Down Idle HDD
    Disabled

    SATA Power Up In Standby
    Default

    Delay For PHY To Stable
    Disabled

You are aware that none of the MD series Toshiba drives are listed in their HCL, only some of the MG series, right?

  • Yes, I am, unfortunately I wasn't in on that decision.


Thanks
 
Last edited:
Please post specifics about the enclosures you are running, the BIOS/Firmware revisions of both the cards and the drives. Please post the full card log from one of the machines. What kind of power supplies, motherboards and other installed devices are you running? Is it always the same drives dropping out? Do they show as failed or free when they drop? Are the 8087/SATA cables you are using the ones shipped with the cards or did you buy third party cables? Do you have power management enabled on the card? You are aware that none of the MD series Toshiba drives are listed in their HCL, only some of the MG series, right?

Please post specifics about the enclosures you are running, the BIOS/Firmware revisions of both the cards and the drives
  • Generic Chassis, 900 Watt Power Supply
  • Gigabyte MB Z97X-UD5H-BK, Bios 04.06.05
  • Controller Name ARC-1882IX-12
    Firmware Version V1.53 2016-02-16
    BOOT ROM Version V1.53 2016-03-16
    PL Firmware Version 19.0.0.0
    Main Processor Intel Core i7-4770
    Memory 8GB
Windows Driver is latest
  • Date: 11/15/2014, Version 6.20.0.31

  • Typical Drives in 10 Disk Raid 6
  • Device Type SATA(5001B4D51C7F101C)
    Device Location Enclosure#2 SLOT 01
    Model Name TOSHIBA MD04ACA400
    Serial Number 85R2KPIOFSAA
    Firmware Rev. FP2A
    Disk Capacity 4000.8GB
    Physical Block Size 4096
    Logical Block Size 512
    Current SATA Mode SATA600+NCQ(Depth32)
    Supported SATA Mode SATA600+NCQ(Depth32)
    Error Recovery Control (Read/Write) Disabled/Disabled
    Disk APM Support Yes
    Device State Normal
    Timeout Count 0
    Media Error Count 0
    Rotation Speed 7200(RPM)
    Device Temperature 32 ºC
    48Bit LBA Support Yes
    SMART Read Error Rate 100(50)
    SMART Spinup Time 100(1)
    SMART Reallocation Count 100(50)
    SMART Seek Error Rate 100(50)
    SMART Spinup Retries 101(30)
    SMART Calibration Retries N.A.(N.A.)
    SSD Reserved Space N.A.(N.A.)
    SSD Wearing Indicator N.A.(N.A.)

. Please post the full card log from one of the machines.
  • 2016-05-02 10:00:18 E2 SLOT 03 HotSpare Deleted
    2016-05-02 09:59:57 Proxy Or Inband HTTP Log In
    2016-05-02 09:01:50 H/W Monitor Raid Powered On
    2016-05-02 08:58:12 E2 SLOT 03 HotSpare Created
    2016-05-02 08:58:11 Enc#2 SLOT 03 Device Inserted
    2016-05-02 08:57:36 Enc#2 SLOT 03 Device Removed
    2016-05-02 08:33:24 Raid Set # 000 Delete RaidSet
    2016-05-02 08:33:24 ARC-1882-VOL#000 Abort Rebuilding 000:00:38
    2016-05-02 08:32:46 ARC-1882-VOL#000 Start Rebuilding
    2016-05-02 08:32:43 Raid Set # 000 Rebuild RaidSet
    2016-05-02 08:32:43 E2 SLOT 09 HotSpare Used
    2016-05-02 08:32:42 E2 SLOT 09 HotSpare Created
    2016-05-02 08:32:03 Raid Set # 000 Delete RaidSet
    2016-05-02 08:31:40 Proxy Or Inband HTTP Log In
    2016-04-30 06:36:28 ARC-1882-VOL#000 Complete Rebuild 000:31:30
    2016-04-30 06:04:58 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 06:04:56 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 06:04:56 Enc#2 SLOT 05 Device Inserted
    2016-04-30 06:04:55 Enc#2 SLOT 05 Device Removed
    2016-04-30 06:04:55 ARC-1882-VOL#000 Stop Rebuilding 000:10:49
    2016-04-30 06:04:55 Raid Set # 000 RaidSet Degraded
    2016-04-30 06:04:55 ARC-1882-VOL#000 Volume Failed
    2016-04-30 05:54:05 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 05:54:03 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 05:54:03 Enc#2 SLOT 01 Device Inserted
    2016-04-30 05:54:02 Enc#2 SLOT 01 Device Removed
    2016-04-30 05:54:01 ARC-1882-VOL#000 Stop Rebuilding 001:21:50
    2016-04-30 05:54:01 Raid Set # 000 RaidSet Degraded
    2016-04-30 05:54:01 ARC-1882-VOL#000 Volume Failed
    2016-04-30 04:32:11 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 04:32:09 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 04:32:09 Enc#2 SLOT 01 Device Inserted
    2016-04-30 04:32:08 Enc#2 SLOT 01 Device Removed
    2016-04-30 04:32:08 ARC-1882-VOL#000 Stop Rebuilding 000:05:45
    2016-04-30 04:32:08 Raid Set # 000 RaidSet Degraded
    2016-04-30 04:32:08 ARC-1882-VOL#000 Volume Failed
    2016-04-30 04:26:22 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 04:26:20 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 04:26:20 Enc#2 SLOT 01 Device Inserted
    2016-04-30 04:26:19 Enc#2 SLOT 01 Device Removed
    2016-04-30 04:26:19 ARC-1882-VOL#000 Stop Rebuilding 000:50:52
    2016-04-30 04:26:19 Raid Set # 000 RaidSet Degraded
    2016-04-30 04:26:19 ARC-1882-VOL#000 Volume Failed
    2016-04-30 03:35:27 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 03:35:25 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 03:35:25 Enc#2 SLOT 01 Device Inserted
    2016-04-30 03:35:24 Enc#2 SLOT 01 Device Removed
    2016-04-30 03:35:24 ARC-1882-VOL#000 Stop Rebuilding 000:26:20
    2016-04-30 03:35:24 Raid Set # 000 RaidSet Degraded
    2016-04-30 03:35:24 ARC-1882-VOL#000 Volume Failed
    2016-04-30 03:09:04 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 03:09:02 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 03:09:02 Enc#2 SLOT 01 Device Inserted
    2016-04-30 03:09:01 Enc#2 SLOT 01 Device Removed
    2016-04-30 03:09:01 ARC-1882-VOL#000 Stop Rebuilding 000:55:50
    2016-04-30 03:09:01 Raid Set # 000 RaidSet Degraded
    2016-04-30 03:09:01 ARC-1882-VOL#000 Volume Failed
    2016-04-30 02:13:10 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 02:13:08 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 02:13:08 Enc#2 SLOT 05 Device Inserted
    2016-04-30 02:13:08 Enc#2 SLOT 05 Device Removed
    2016-04-30 02:13:07 ARC-1882-VOL#000 Stop Rebuilding 000:31:51
    2016-04-30 02:13:07 Raid Set # 000 RaidSet Degraded
    2016-04-30 02:13:07 ARC-1882-VOL#000 Volume Failed
    2016-04-30 01:41:16 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 01:41:14 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 01:41:14 Enc#2 SLOT 01 Device Inserted
    2016-04-30 01:41:13 Enc#2 SLOT 01 Device Removed
    2016-04-30 01:41:13 ARC-1882-VOL#000 Stop Rebuilding 000:12:45
    2016-04-30 01:41:13 Raid Set # 000 RaidSet Degraded
    2016-04-30 01:41:13 ARC-1882-VOL#000 Volume Failed
    2016-04-30 01:28:27 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 01:28:25 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 01:28:25 Enc#2 SLOT 04 Device Inserted
    2016-04-30 01:28:24 Enc#2 SLOT 04 Device Removed
    2016-04-30 01:28:24 ARC-1882-VOL#000 Stop Rebuilding 000:26:58
    2016-04-30 01:28:24 Raid Set # 000 RaidSet Degraded
    2016-04-30 01:28:24 ARC-1882-VOL#000 Volume Failed
    2016-04-30 01:01:26 ARC-1882-VOL#000 Start Rebuilding
    2016-04-30 01:01:24 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-30 01:01:24 Enc#2 SLOT 01 Device Inserted
    2016-04-30 01:01:23 Enc#2 SLOT 01 Device Removed
    2016-04-30 01:01:23 ARC-1882-VOL#000 Stop Rebuilding 001:26:26
    2016-04-30 01:01:23 Raid Set # 000 RaidSet Degraded
    2016-04-30 01:01:23 ARC-1882-VOL#000 Volume Failed
    2016-04-29 23:34:57 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 23:34:55 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 23:34:55 Enc#2 SLOT 08 Device Inserted
    2016-04-29 23:34:54 Enc#2 SLOT 08 Device Removed
    2016-04-29 23:34:53 ARC-1882-VOL#000 Stop Rebuilding 000:36:12
    2016-04-29 23:34:53 Raid Set # 000 RaidSet Degraded
    2016-04-29 23:34:53 ARC-1882-VOL#000 Volume Failed
    2016-04-29 22:58:41 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 22:58:39 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 22:58:39 Enc#2 SLOT 08 Device Inserted
    2016-04-29 22:58:39 Enc#2 SLOT 08 Device Removed
    2016-04-29 22:58:38 ARC-1882-VOL#000 Stop Rebuilding 003:16:47
    2016-04-29 22:58:38 Raid Set # 000 RaidSet Degraded
    2016-04-29 22:58:38 ARC-1882-VOL#000 Volume Failed
    2016-04-29 19:41:50 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 19:41:48 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 19:41:48 Enc#2 SLOT 01 Device Inserted
    2016-04-29 19:41:48 Enc#2 SLOT 01 Device Removed
    2016-04-29 19:41:47 ARC-1882-VOL#000 Stop Rebuilding 000:38:26
    2016-04-29 19:41:47 Raid Set # 000 RaidSet Degraded
    2016-04-29 19:41:47 ARC-1882-VOL#000 Volume Failed
    2016-04-29 19:03:21 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 19:03:19 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 19:03:19 Enc#2 SLOT 01 Device Inserted
    2016-04-29 19:03:18 Enc#2 SLOT 01 Device Removed
    2016-04-29 19:03:18 ARC-1882-VOL#000 Stop Rebuilding 000:19:32
    2016-04-29 19:03:18 Raid Set # 000 RaidSet Degraded
    2016-04-29 19:03:18 ARC-1882-VOL#000 Volume Failed
    2016-04-29 18:43:45 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 18:43:43 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 18:43:43 Enc#2 SLOT 08 Device Inserted
    2016-04-29 18:43:42 Enc#2 SLOT 08 Device Removed
    2016-04-29 18:43:42 ARC-1882-VOL#000 Stop Rebuilding 001:18:35
    2016-04-29 18:43:42 Raid Set # 000 RaidSet Degraded
    2016-04-29 18:43:42 ARC-1882-VOL#000 Volume Failed
    2016-04-29 17:25:07 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 17:25:05 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-29 17:25:05 Enc#2 SLOT 01 Device Inserted
    2016-04-29 17:25:04 Enc#2 SLOT 01 Device Removed
    2016-04-29 17:25:04 ARC-1882-VOL#000 Stop Rebuilding 001:32:18
    2016-04-29 17:25:04 Raid Set # 000 RaidSet Degraded
    2016-04-29 17:25:04 ARC-1882-VOL#000 Volume Failed
    2016-04-29 16:15:16 Enc#2 SLOT 09 Device Inserted
    2016-04-29 16:15:16 Enc#2 SLOT 09 Device Removed
    2016-04-29 16:15:15 Raid Set # 000 RaidSet Degraded
    2016-04-29 16:15:15 ARC-1882-VOL#000 Volume Degraded
    2016-04-29 15:52:45 ARC-1882-VOL#000 Start Rebuilding
    2016-04-29 15:52:45 ARC-1882-VOL#000 Complete Init 025:37:39
    2016-04-29 08:32:16 Enc#2 SLOT 03 Device Inserted
    2016-04-29 08:32:00 Proxy Or Inband HTTP Log In
    2016-04-29 08:30:42 Enc#2 SLOT 03 Device Removed
    2016-04-28 15:00:51 Raid Set # 000 Delete RaidSet
    2016-04-28 15:00:26 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:26 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:25 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:25 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:25 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:25 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:25 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:25 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Failed
    2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 15:00:23 Raid Set # 000 RaidSet Degraded
    2016-04-28 15:00:23 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 14:24:48 Enc#2 SLOT 03 Device Inserted
    2016-04-28 14:24:47 Enc#2 SLOT 03 Device Removed
    2016-04-28 14:24:43 Raid Set # 000 RaidSet Degraded
    2016-04-28 14:24:43 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 14:23:42 Proxy Or Inband HTTP Log In
    2016-04-28 14:15:05 ARC-1882-VOL#000 Start Initialize
    2016-04-28 14:15:03 ARC-1882-VOL#000 Create Volume
    2016-04-28 14:15:03 Raid Set # 000 Create RaidSet
    2016-04-28 14:14:41 Raid Set # 000 Delete RaidSet
    2016-04-28 14:14:36 Raid Set # 000 Delete RaidSet
    2016-04-28 14:14:28 Raid Set # 000 Delete RaidSet
    2016-04-28 14:13:43 Proxy Or Inband HTTP Log In
    2016-04-28 10:03:21 Enc#2 SLOT 03 Device Inserted
    2016-04-28 10:03:20 Enc#2 SLOT 03 Device Removed
    2016-04-28 09:47:58 Enc#2 SLOT 03 Device Inserted
    2016-04-28 09:47:57 Enc#2 SLOT 03 Device Removed
    2016-04-28 09:47:57 ARC-1882-VOL#000 Abort Rebuilding 000:44:18
    2016-04-28 09:47:57 Raid Set # 000 RaidSet Degraded
    2016-04-28 09:47:57 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 09:34:06 Enc#2 SLOT 09 Device Inserted
    2016-04-28 09:34:05 Enc#2 SLOT 09 Device Removed
    2016-04-28 09:34:05 Raid Set # 000 RaidSet Degraded
    2016-04-28 09:34:05 ARC-1882-VOL#000 Volume Degraded
    2016-04-28 09:03:39 ARC-1882-VOL#000 Start Rebuilding
    2016-04-28 09:03:36 Raid Set # 000 Rebuild RaidSet
    2016-04-28 09:03:36 E2 SLOT 03 HotSpare Used
    2016-04-28 09:03:36 E2 SLOT 03 HotSpare Created
    2016-04-28 09:02:21 Raid Set # 000 Delete RaidSet
    2016-04-28 08:58:39 Enc#2 SLOT 03 Device Inserted
    2016-04-28 08:57:21 Proxy Or Inband HTTP Log In
    2016-04-28 08:41:42 H/W Monitor Raid Powered On
    2016-04-27 21:37:03 ARC-1882-VOL#000 Complete Rebuild 003:54:11
    2016-04-27 17:42:51 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:42:49 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:42:49 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:42:48 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:42:48 ARC-1882-VOL#000 Stop Rebuilding 000:00:50
    2016-04-27 17:42:48 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:42:48 ARC-1882-VOL#000 Volume Failed
    2016-04-27 17:41:57 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:41:55 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:41:55 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:41:54 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:41:54 ARC-1882-VOL#000 Stop Rebuilding 000:01:29
    2016-04-27 17:41:54 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:41:54 ARC-1882-VOL#000 Volume Failed
    2016-04-27 17:40:25 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:40:23 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:40:23 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:40:21 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:40:05 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:40:04 ARC-1882-VOL#000 Stop Rebuilding 000:24:26
    2016-04-27 17:40:04 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:40:04 ARC-1882-VOL#000 Volume Failed
    2016-04-27 17:15:38 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 17:15:36 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 17:15:36 Enc#2 SLOT 08 Device Inserted
    2016-04-27 17:15:35 Enc#2 SLOT 08 Device Removed
    2016-04-27 17:15:35 ARC-1882-VOL#000 Stop Rebuilding 000:15:55
    2016-04-27 17:15:35 Raid Set # 000 RaidSet Degraded
    2016-04-27 17:15:35 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:59:39 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:59:37 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:59:37 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:59:36 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:59:36 ARC-1882-VOL#000 Stop Rebuilding 000:38:14
    2016-04-27 16:59:36 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:59:36 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:21:22 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:21:20 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:21:20 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:21:19 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:21:19 ARC-1882-VOL#000 Stop Rebuilding 000:01:54
    2016-04-27 16:21:19 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:21:19 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:19:24 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:19:22 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:19:22 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:19:21 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:19:21 ARC-1882-VOL#000 Stop Rebuilding 000:01:47
    2016-04-27 16:19:21 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:19:21 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:17:33 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:17:31 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:17:31 Enc#2 SLOT 08 Device Inserted
    2016-04-27 16:17:30 Enc#2 SLOT 08 Device Removed
    2016-04-27 16:17:30 ARC-1882-VOL#000 Stop Rebuilding 000:04:08
    2016-04-27 16:17:30 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:17:30 ARC-1882-VOL#000 Volume Failed
    2016-04-27 16:13:21 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 16:13:19 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 16:13:19 Enc#2 SLOT 06 Device Inserted
    2016-04-27 16:13:18 Enc#2 SLOT 06 Device Removed
    2016-04-27 16:13:18 ARC-1882-VOL#000 Stop Rebuilding 000:31:29
    2016-04-27 16:13:18 Raid Set # 000 RaidSet Degraded
    2016-04-27 16:13:18 ARC-1882-VOL#000 Volume Failed
    2016-04-27 15:41:49 ARC-1882-VOL#000 Start Rebuilding
    2016-04-27 15:41:47 ARC-1882-VOL#000 Failed Volume Revived
    2016-04-27 15:41:47 Enc#2 SLOT 08 Device Inserted
    2016-04-27 15:41:46 Enc#2 SLOT 08 Device Removed
    2016-04-27 15:41:46 ARC-1882-VOL#000 Stop Rebuilding 003:48:09
Is it always the same drives dropping out?
  • No, If I rebuild with one that dropped, it can be set to hot spare. And the another drive will drop. What's odd is that you see removed and inserted when we didn't physically pull the drive.

Do they show as failed or free when they drop?
  • They say failed, but can be instantly set to hot spare.

Are the 8087/SATA cables you are using the ones shipped with the cards or did you buy third party cables?
  • 3Ware from Newegg, Item=9SIA24G28N2208, SFF-8087 to 4 Sata

Do you have power management enabled on the card?
  • Here are the settings (Default?) from Hdd Power Management
  • Stagger Power On Control
    0.7

    Time To Hdd Low Power Idle
    Disabled

    Time To Hdd Low RPM Mode
    Disabled

    Time To Spin Down Idle HDD
    Disabled

    SATA Power Up In Standby
    Default

    Delay For PHY To Stable
    Disabled

You are aware that none of the MD series Toshiba drives are listed in their HCL, only some of the MG series, right?

  • Yes, I am, unfortunately I wasn't in on that decision.


Thanks[/QUOTE]
 
So I just bought an ARC-1284ML-24 card and I'm ver new to the world of Areca.
I haven't updated the firmware, just running it stock for now (v1.52 2014-12-12).
I've created my first RAID1 set (2x 3tb WD RED drives) and pairing them takes 10 hours.
I've just installed my second set of idential drives (2x 3tb wd red) and expanding now I see that progress is only sitting at 5.5% in two hours.
This seems excessively... I don't know.... slow? Does anyone happen to have any ideas why it takes so long to do this? The drives are blank so there's no media/data to shunt around. At this rate, it's going to take about two days to simply expand from 3tb to 6tb raid1 mode and I'm hoping there's just something I'm missing here. :(

In case anyone needs to know, the "background priority" is set to 80% and has been since day 1.


So.. new thought: My raid that's currently expanding right now was in ONLINE mode (although I'm only in the BIOS itself).
If I were to set the RAID to an OFFLINE status and then begin expansion, will this expansion occur as a FOREGROUND process/initialization or still count as background? I believe this might get me a bit of a better result as I think if the raid is in online mode, it automatically processes things as a background task?
 
Last edited:
Hello I recently installed an Areca 1883ix 12 internal 4 external 4gb Ram Raid controller in my Dual 12core 2.5ghz Dell Precision 7910 workstation. I am using this controller to internally raid together 8 Samsung Pro 850 SSDs in Raid 0 (256 Stripe Size, write through (also tried write back) formatted as 64k in Windows 10) currently for image sequence caching.
Getting good read speeds at a little over 4000MBs but write speeds are really off at 1300MBs. (Aja speed test 2k DPX, 10bit 4GB). So I'm trying to figure out what might be the cause of such lob sided readings?

Any help would be much appreciated!
 
NO! Do not buy a "USB-to-RJ11" modem, or worse, a dumb USB-4-pin to RJ11-4-pin adapter.

This is the pinout for the Areca RJ11 expander connector:

njwdfBe.png


To make your own cable, you will need:

  1. USB to RS232 serial male adapter (cheaper ones are available but the FTDI chipset just works)
  2. Modular (i.e. configurable) DB9 female to RJ11 adapter
  3. RJ11 cable
I'm deliberately not including the DB9 pinouts. If you're not confident about figuring those out, you shouldn't be making this cable. Contact Areca Support (or Tekram) and beg/buy a cable.

I don't have an Areca -IX card any more or I'd let you borrow mine.

PS: A lot of motherboards will include a COM1 header on the board, even if there is no serial port connector on the I/O. Those are standardized and instead of the USB, you can get a simpler adapter like this. It's a native serial port which is always preferable to a USB adapter.


I made a cable up for my ARC-1680 using these instructions - I connected them like so:

RJ11_________DE9
Pin 1 ----------- Pin 7 (RTS)
Pin 2 ------------- Pin 2 (RXD)
Pin 3 -------------- Pin 3 (TXD)
Pin 4 -------------- Pin 5 (GND)
(Pin 5 & 6 not connected)

I can get to a prompt when I plug it in to the expander that says "Password" however it seems to send too many characters at once and "*" when I press enter - not sure if I'm getting the password wrong or there is some other issue.

My terminal settings are VT102 (no vt100 in minicom, should be compatible anyway) 115200 8 N 1

Anyone have experience with getting in to the expander CLI console?


Cheers!

Edit:
This is what happens when I type the default "0000" password and press enter until it actually sends the enter key:
Code:
 Password:**
  Password:**
  Password:****
  Password:*******
  Password:****
  Password:*******
  Password:**************
  Password:**
  Password:
  Password:****
 
Last edited:

As an Amazon Associate, HardForum may earn from qualifying purchases.
I am planning a custom NAS case and I am trying to work out the individual (not global) LED Activity pin-outs on the ARC-1203-8i (8-port) controller.

Looking at the manual it illustrates where the pin-outs are for the LED connectors (which I'm assuming are positive?).
LED Pinouts.PNG


The global LED pin-out is clear as daylight however it is a bit vague as to where the negative side for the individual LED's connect back to?
The only mention of negative (highlighted below) is referring to the "EPLD CTL output pin" which it doesn't really say where it is on the raid controller, or if it 's referring to something else? Maybe it's a typo for "LED CTL" instead?
LED Pinouts 2.PNG

I am assuming the right diagram is for individual activity LED's. The positive side is referring to some +3.3V source and a 330k resistor, while the negative side goes back to a "CTL Output" AND a "LED CTL"
LED Pinouts 3.PNG


I guess I can say "yes indeed I have read the manual", but now I'm quite stuck.
 
I have an Areca 1882 with 4GB, I use it in my home network, with 4 disk raid5-sets. It is mainly used for streaming and so on, usually no more than 2-3 user at the time. Is there a way to keep the performance a bit more consistent? With my settings (more or less default), transfers are very quick for maybe 15-30 seconds (300-400 MBs per second from the array), then it grinds to a halt for a little while, and the speed then picks up. Is there any settings that sacrifices som top performance for more consistently good and snappy performance.
 
Just joined this forum, first time OP here...

Dell PowerEdge R900 - VMware ESXi 5.5 U3 - Areca 1882 X configured as RAID attached to Proavio DS316J enclosure with 16 3 TB Seagate SV35

1 RaidSet 14 disks with 2 hot spares

1 RAID5, 40 TB VolumeSet on this RaidSet

7/20: E#2SLOT#09 failed, hot spare picked up, rebuild begins to E#2SLOT#11

Rebuild ran through the night

7/21: 6:00 AM this morning, E#2SLOT#11 failed

Both E#2SLOT#9 and E#2SLOT#11 showed as failed on the enclosure

I pulled both the failed drives and replaced them, and added them as hot spares

Areca Raid Storage Manager shows RaidSet as 'Rebuilding'', VolumeSet as 'Failed', 1 slot as failed, 2 hot spares, and 1 free disk. See pics, please.

In addition, I had an 1883X configured as JBOD in the same R900. PCIe Fatal Error started flashing on the server. I shut it down, and pulled the RAID controller - reboot - still PCIe error. Put in 1882 as a replacement, pulled 1883 JBOD - no more PCIe Fatal Error.

Areca1.png Areca2.pngAreca3.png

So the questions I have are:
1) Why didn't the second hot spare pick up when the second drive failed?
2) What is the real status of the drives?
3) Am I shooting myself in the foot trying to run 2 PCIe controllers in this server?

Any advice/information is appreciated.
 
Back
Top