Firmware on This Sas1066e 05 Appears Broken Res2sv240

#2,481

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

With RJ45 based 10G, you lot want to use Cat7 cables and information technology doesn’t similar electric interference. Fiber is completely allowed to that.

RJ45 based 10G switches are yet very expensive, so they are typically not used in abode environments.

#2,482

So, I’d ordered some replacement chipset coolers for the ARC-1883ix-12 I bought, I unseated the 4 chipset mounting pins notwithstanding the factory heatsink appears to be adhesed to the carte du jour?

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?

#2,483

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

I’thou a flake of a noob when information technology 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 depression-heat/depression-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 forcefulness could ruin the chip and basically get out you with a physically broken card that will not be covered nether warranty.

Notation that if yous have problems, sending the carte du jour to Areca/Tekram with a modified HSF WILL void your warranty. Be set up to remount it if you e’er need service.

Likewise, do you really have a temperature trouble with the card? IME the stock Areca HSF is proficient enough for the LSI ROCs on the 188x series, just mine take always been in a server example with decent airflow.

#2,484

I have an ARC-1880i connected to multiple drives via an Intel RES2SV240 expander. The trouble is that no affair which drive is concerned, the organization log ever reports the device as
“Enc#2 ArrayDevic”
— I think it’due south cutting off due to a length limitation. The devices as listed in the hierarchy are ArrayDevice00, 01, etc.

The BIOS/CLI/spider web interface all have this problem. Running latest 1.52 FW. Any solutions?

#two,485

Might exist 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. Practice you take SES2 enabled?

#2,486

Might exist how the expander reports things?

Y’all got it, the “device”
name appears to exist chosen by the expander.

Do yous take SES2 enabled?

Yes, but it’s a impaired Norco backplane so I’ve never used it. I merely disabled it to see if that changes how the expander reports. Just the Areca does show the full device name in the hierarchy, which makes me recollect it’s a difficult-coded length limitation in the log entry.

I’ll be migrating to an SC846 soon, so glad to hear its expander reports things succinctly.

#2,487

IIRC, apply a hair-dryer on low-estrus/low-speed to
gently
heat the heatsink until yous can wriggle and pull it off. The CPU (ROC) underneath has a heatspreader, so you’re not likely to harm it. YMMV, of grade (I did it on a 1680 back in the day).

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

Likewise, practise you lot actually have a temperature problem with the carte du jour? IME the stock Areca HSF is good enough for the LSI ROCs on the 188x serial, just mine take ever been in a server instance with decent airflow.

Yea no heat issues as yet. I had read that someone was saying these cards run hot, merely it sounds like that may not exist the instance. I noticed the temps were a niggling high (55 degrees Celsius) I’ll try it again nether 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 similar a better bet.

In either case, I’ll wait until I tin can get a dainty array going to put the card under proper load and have some other look at the thermals

Thanks once again!!

#2,488

I had read that someone was saying these cards run hot, only it sounds like that may not be the example.

This Austrian modified his 1883-9-12 HSF

Note that the guy above didn’t like the fan noise, rather than temps. His mod didn’t actually brand a temp difference.

The bit actually does run hot — the LSI cards with only a passive heatsink can accomplish mid-90s nether load if not properly cooled by example 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 lot exercise program to take information technology off, heat it evenly and then twist/pull it, virtually no risk since in that location’southward 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 accept HSF mounting holes for a defended heatsink — yous’ll have to apply agglutinative paste. Here’s a “blank” view of the 1883ix-Twenty with the giant heatsink off:

#2,489

Wow awesome info thanks!

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

Given that the ROC doesnt take conventional mounts, I think i’ll just proceed 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 information technology a shot when I go dwelling house in a few hours and permit you lot folks know the results… Standby

#2,490

Yea I bought two crappy $half-dozen 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 elevation, expels out of i side along the heatsink fins). So conventional fans (top-to-bottom) won’t do much, and will in fact hurt because their will now exist much less airflow along the heatsink fins.

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

Here’s a fairly cheap, no-run a risk exercise I would do if I had one of these:

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, and then definitely 40mm).
Measure information technology, and get two 60mm (or 40mm) fans, 25mm deep. Likewise get ii finger guards of the appropriate size.
Disconnect the stock fan and just leave it in place.
Screw finger guards onto the the open (air IN) side of the fans, and place them on the master boundaries of the heatsink as in the picture show below; use one or ii rubber bands going over the top of the fan and around the card to secure the fans.
Plug bill of fare into motherboard
Connect fans to Molex adapter (Not the card’s fan connector)
See what kind of difference this makes compared to the built-in fan.

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

I recall this volition exist way more effective than replacing the stock fan. Equally an extreme step, you lot could remove the black heatsink and re-mountain information technology using a loftier-quality non-adhesive thermal compound on the ROC and expander chips.

#2,491

Yea that’south definitely going to be the easier solution. I’ll do just that if the temps aren’t ideal when I go 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 likewise besides hot with just 2 SSD raid members.

Thanks once 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 over again!

#2,492

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 chemical compound; the HSF interfaces to the ROC via a thermal pad, and the ROC is also surrounded by a protective safety purlieus 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 fastened similarly (via the plastic pegs and thermal pads — no adhesive), i more thing to effort would be to supersede Areca’s generic black thermal pad with something similar an Chill Silver thermal pad and remount the heatsink.

Mine is idling around 57C so I might endeavour some “solutions” in one case the menu is put into agile service. Electric current ARC-1880i past contrast is idling around 42C.

#2,493

Yea there’southward 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-scale amount of torsion and the hs will rotate ever so slightly (not mechanically fixed [screws]) then it seems like an adhesive of some kind on my 1883ix

#ii,494

My [ARC-1883i] is idling around 57C so I might try some “solutions” one time the card is put into agile 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 agglutinative 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 confronting light to encounter that the thermal compound had spread properly with no “leaks”

Consequence: Load temp went from 66C to 46C. Idle from 48C to 40C.

#two,495

stunnel
is the easiest solution I institute for getting notification emails from the Areca card. Don’t accept fourth dimension to write a pace past step only 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 plan listens on port 25 then tunnels to a secure connection on smtp.gmail.com:465. So you configure the notification page in the Areca spider web admin for the IP of the car running stunnel, along with your gmail username and countersign.

Hullo..

I tried the aforementioned settings but I deceit get archttp to ship the e-mail.

I set up 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?

#ii,496

Does anyone have the new SuperCap wink backup instead of a regular BBU? If so, can yous comment on how it connects to the RAID controller? I’m not a fan of the dummy PCIe form cistron – – is the connectedness long plenty to simply mountain the SuperCap FBU elsewhere in the chassis?

Any full general impressions about the SuperCap FBU would be appreciated. Also, whatsoever hacks (or available cables) to connect the standard BBU to the new slim connector on the 1883 serial?

#2,497

Is the supercap an option without a “CacheVault”/NVM (flash) module? The supercap doesn’t accept nearly the free energy of the Li-Ion battery. Its job is to provide enough ability to dump the unwritten cache to NVM (flash) in the event of a power failture, not to keep the cache powered for hours.

#2,498

Is the supercap an option without a “CacheVault”/NVM (flash) module? The supercap doesn’t have almost the energy of the Li-Ion battery. Its task is to provide enough ability to dump the unwritten cache to NVM (flash) in the event of a power failture, not to keep the enshroud powered for hours.

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

The problem is that dissimilar the elegant CacheVault package which fits onto the acme of the LSI controller, Areca’south supercap is an ungainly detached slice (below). Their batteries have also been like, simply at least they’re shorter then they’ll fit in that superlative PCIe slot without being obstructed by the heatsinks mutual on many mobos.

#2,499

hi

i have one ARC-1680ix-xvi.
yesterday when i plough on the server i observe out that the raid array is missing from the Bone. i check through spider web interface and i find out that in that location are missing slots from the RaidSet Hierarchy section. normally its shows enclosure#ane and #two. now its shows simply #1 like the image.

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

anyone knows how to gear up the trouble?

thanks a lot

#2,500

howdy

i have i ARC-1680ix-16.
yesterday when i plow on the server i detect out that the raid array is missing from the Bone. i check through spider web interface and i find out that in that location are missing slots from the RaidSet Hierarchy section. normally its shows enclosure#1 and #2. at present its shows just #1 similar the image.

i try to unplug the card and re-plug but nil. i accept the last firmware one.51.

anyone knows how to fix the problem?
cheers a lot

That’southward not good. Means the on-lath SAS expander isn’t existence recognized. Exercise you lot withal have the serial cable that plugs into the RJ11 port on the carte du jour? That’s the CLI for said expander. Might exist able to poke through at that place to see what’southward going on.

#2,501

That’southward not good. Means the on-board SAS expander isn’t being recognized. Exercise you lot still have the series cable that plugs into the RJ11 port on the card? That’south the CLI for said expander. Might be able to poke through there to see what’south going on.

unfortunately i bought this menu every bit used, so i don’t take this cable. i can purchase one if you call up that will help to solve this problem.

edit: i have just realize i don’t have serial port. is information technology ok to purchase a rj11 to usb?

Last edited:
Feb 21, 2016

#two,502

edit: i have simply realize i don’t take serial port. is it ok to buy a rj11 to usb?

NO!
Do non buy a “USB-to-RJ11”
modem, or worse, a dumb USB-four-pivot to RJ11-4-pin adapter.

This is the pinout for the Areca RJ11 expander connector:

To brand your own cable, you will need:

USB to RS232 serial male person adapter
(cheaper ones are available only the FTDI chipset just works)
Modular (i.due east. configurable) DB9 female person to RJ11 adapter
RJ11 cable

I’m deliberately not including the DB9 pinouts. If you lot’re not confident about figuring those out, you shouldn’t exist making this cablevision. Contact Areca Support (or Tekram) and beg/buy a cable.

I don’t have an Areca -Nine carte whatever more or I’d permit yous 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 lot can become a simpler adapter like
this. It’s a native serial port which is e’er preferable to a USB adapter.

#2,503

That’s not expert. Means the on-board SAS expander isn’t being recognized. Practise yous still take the serial cablevision that plugs into the RJ11 port on the card? That’southward 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 respond

Dear Sir/Madam,
the expander chip on this card is failed.
this bill of fare have an expander chip onboard to be able to provide 24 ports. and so y’all will non able to encounter any drive in managing director console if this expander chip is malfunction.
if you would similar to RMA this card, y’all can contact with your original supplier for assist. considering our RMA is processed through the distributor which sold the production.
if y’all do not able to achieve the supplier or they are not our benefactor. delight inform me the information of your supplier and the serial number of your card. we tin trace these information to observe out the original benefactor to aid you RMA.

Best Regards,

i decide to buy a working controller.

thanks a lot for the help

#2,504

#two,505

Does someone know a make/model of a fan to alter the original one?
It is on the concluding few days of life and making extreme racket, I desire 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

#two,506

I inherited an sometime supermicro server and low and behold, an ARC 1880i.

Setup my RAID6 yesterday.

#2,507

UPDATE: Information technology was a post white listing upshot. 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 take 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 stiff for the past 11 months.

I am running 12 Seagate 3tb NAS drives in raid half-dozen. 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 endeavor without my Intel sas expander and with new sas cables, running merely 8 drives straight also would fourth dimension out and fail the array instantly. I have since replaced my impaired norco with a supermicro with a expander built in the backplane and 5 of the 12 disks in the assortment as well as the sas cable.(some of the new disks are as well timing out)

However since the commencement reply I got from areca support I accept not been able to go a single reply back.
I have emailed them about once every calendar week for the by 6 weeks.. Both in patently text, from Gmail, my piece of work email account and my Internet access provider provided electronic mail address.

I am actually hoping this is just a fault with their mail filters and non that I am being ignored. I would hate to get to another raid carte du jour provider as they seem to be the merely ones with on board management nics.

If anyone has a alternative contact for areca support that would be groovy.

Last edited:
Apr 19, 2016

#2,508

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 i-7 and the other 7 to xviii-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?

#2,509

I have an aboriginal ARC1280 with 24 SATA ports. I have fourteen disks connected to it forming one RAID6 volume, seven disks are connected to ports 1-seven and the other 7 to eighteen-24. Does it matter to what SATA port on the card the disks are connected? Tin can I only rearrange and connect the 14 disks to ports 1-xiv for case? Volition I keep my RAID?

Yes, you tin can. It is a characteristic called array roaming. One caveat, if y’all need to ever use whatever of the Areca special repair procedures you MUST have the drives in the original guild the array was created in, though for normal utilize yous can put them in any gild.

#2,510

All the same have an former ARC1210 banging away with 4 old WD RE3 1TBs in RAID6 since they were both new things, just for storage on the primary rig myself.

Areca does make pretty solid hardware RAID cards.

Information technology’s downwardly on the bottom there with all the other ancient things like my X58 still running an OC’d X5680 @ 4.5

Virtually things accept been changed over fourth dimension I guess.

Last edited:
Apr 18, 2016

#two,511

ARC-1882ix-12-2G and Toshiba MD04ACA400(HDETR11GEA51) Fail 6x

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

Even in Bios the Assortment volition not rebuild and fails different drives?

Can’t observe Areca Back up. Electronic mail and Phones don’t piece of work.

Any help would be appreciated. Newbe to HardForum…

#ii,512

ARC-1882ix-12-2G and Toshiba MD04ACA400(HDETR11GEA51) Neglect 6x

This is new setup. Assortment degrades with failed drives. It happens on 6 of the seven servers nosotros congenital.

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

Tin can’t find Areca Support. E-mail and Phones don’t work.

Any assist would exist 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 mail service the full card log from one of the machines. What kind of power supplies, motherboards and other installed devices are you running? Is information technology always the same drives dropping out? Practise they bear witness every bit failed or costless when they drop? Are the 8087/SATA cables you lot are using the ones shipped with the cards or did you buy third political party cables? Do you lot have ability direction 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 serial, right?

#ii,513

Please postal service specifics well-nigh 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
Chief Processor Intel Core i7-4770
Memory 8GB

Windows Driver is latest

Date: xi/15/2014, Version vi.20.0.31

Typical Drives in 10 Disk Raid six

Device Blazon SATA(5001B4D51C7F101C)
Device Location Enclosure#2 SLOT 01
Model Name TOSHIBA MD04ACA400
Series Number 85R2KPIOFSAA
Firmware Rev. FP2A
Deejay Chapters 4000.8GB
Concrete Block Size 4096
Logical Cake Size 512
Current SATA Mode SATA600+NCQ(Depth32)
Supported SATA Mode SATA600+NCQ(Depth32)
Mistake Recovery Command (Read/Write) Disabled/Disabled
Deejay APM Support Yes
Device Land Normal
Timeout Count 0
Media Error Count 0
Rotation Speed 7200(RPM)
Device Temperature 32 ºC
48Bit LBA Support Yes
SMART Read Mistake 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.(Northward.A.)
SSD Wearing Indicator N.A.(North.A.)

. Please mail the full card log from one of the machines.

2016-05-02 x:00:18 E2 SLOT 03 HotSpare Deleted

2016-05-02 09:59:57 Proxy Or Inband HTTP Log In

2016-05-02 09:01:l H/W Monitor Raid Powered On

2016-05-02 08:58:12 E2 SLOT 03 HotSpare Created

2016-05-02 08:58:eleven Enc#ii SLOT 03 Device Inserted

2016-05-02 08:57:36 Enc#2 SLOT 03 Device Removed

2016-05-02 08:33:24 Raid Fix # 000 Delete RaidSet

2016-05-02 08:33:24 ARC-1882-VOL#000 Arrest 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:forty 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 Showtime Rebuilding

2016-04-xxx 06:04:56 ARC-1882-VOL#000 Failed Volume Revived

2016-04-30 06:04:56 Enc#ii SLOT 05 Device Inserted

2016-04-30 06:04:55 Enc#ii SLOT 05 Device Removed

2016-04-thirty 06:04:55 ARC-1882-VOL#000 Cease 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 Book Failed

2016-04-30 05:54:05 ARC-1882-VOL#000 Beginning 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 Finish Rebuilding 001:21:50

2016-04-thirty 05:54:01 Raid Prepare # 000 RaidSet Degraded

2016-04-30 05:54:01 ARC-1882-VOL#000 Volume Failed

2016-04-xxx 04:32:11 ARC-1882-VOL#000 Start Rebuilding

2016-04-30 04:32:09 ARC-1882-VOL#000 Failed Book Revived

2016-04-30 04:32:09 Enc#ii SLOT 01 Device Inserted

2016-04-30 04:32:08 Enc#2 SLOT 01 Device Removed

2016-04-xxx 04:32:08 ARC-1882-VOL#000 Stop Rebuilding 000:05:45

2016-04-30 04:32:08 Raid Prepare # 000 RaidSet Degraded

2016-04-thirty 04:32:08 ARC-1882-VOL#000 Volume Failed

2016-04-30 04:26:22 ARC-1882-VOL#000 Showtime Rebuilding

2016-04-xxx 04:26:xx ARC-1882-VOL#000 Failed Book Revived

2016-04-30 04:26:twenty Enc#2 SLOT 01 Device Inserted

2016-04-30 04:26:19 Enc#two 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-xxx 03:35:27 ARC-1882-VOL#000 First Rebuilding

2016-04-thirty 03:35:25 ARC-1882-VOL#000 Failed Book Revived

2016-04-xxx 03:35:25 Enc#ii 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:twenty

2016-04-xxx 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 Showtime Rebuilding

2016-04-30 03:09:02 ARC-1882-VOL#000 Failed Book Revived

2016-04-30 03:09:02 Enc#2 SLOT 01 Device Inserted

2016-04-30 03:09:01 Enc#two SLOT 01 Device Removed

2016-04-xxx 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-xxx 03:09:01 ARC-1882-VOL#000 Volume Failed

2016-04-30 02:13:10 ARC-1882-VOL#000 Start Rebuilding

2016-04-thirty 02:xiii:08 ARC-1882-VOL#000 Failed Volume Revived

2016-04-30 02:13:08 Enc#two SLOT 05 Device Inserted

2016-04-30 02:thirteen:08 Enc#2 SLOT 05 Device Removed

2016-04-30 02:13:07 ARC-1882-VOL#000 Cease Rebuilding 000:31:51

2016-04-xxx 02:13:07 Raid Set # 000 RaidSet Degraded

2016-04-30 02:13:07 ARC-1882-VOL#000 Volume Failed

2016-04-xxx 01:41:16 ARC-1882-VOL#000 Start Rebuilding

2016-04-30 01:41:xiv ARC-1882-VOL#000 Failed Volume Revived

2016-04-30 01:41:14 Enc#2 SLOT 01 Device Inserted

2016-04-30 01:41:thirteen Enc#2 SLOT 01 Device Removed

2016-04-xxx 01:41:13 ARC-1882-VOL#000 End Rebuilding 000:12:45

2016-04-30 01:41:thirteen Raid Set up # 000 RaidSet Degraded

2016-04-thirty 01:41:xiii 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-thirty 01:28:25 Enc#2 SLOT 04 Device Inserted

2016-04-30 01:28:24 Enc#2 SLOT 04 Device Removed

2016-04-xxx 01:28:24 ARC-1882-VOL#000 Stop Rebuilding 000:26:58

2016-04-thirty 01:28:24 Raid Set # 000 RaidSet Degraded

2016-04-30 01:28:24 ARC-1882-VOL#000 Volume Failed

2016-04-xxx 01:01:26 ARC-1882-VOL#000 Start Rebuilding

2016-04-30 01:01:24 ARC-1882-VOL#000 Failed Book Revived

2016-04-30 01:01:24 Enc#two SLOT 01 Device Inserted

2016-04-thirty 01:01:23 Enc#2 SLOT 01 Device Removed

2016-04-xxx 01:01:23 ARC-1882-VOL#000 Finish Rebuilding 001:26:26

2016-04-30 01:01:23 Raid Gear up # 000 RaidSet Degraded

2016-04-xxx 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#two 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 Cease 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:fifty ARC-1882-VOL#000 Offset Rebuilding

2016-04-29 xix:41:48 ARC-1882-VOL#000 Failed Volume Revived

2016-04-29 19:41:48 Enc#two SLOT 01 Device Inserted

2016-04-29 nineteen:41:48 Enc#ii SLOT 01 Device Removed

2016-04-29 19:41:47 ARC-1882-VOL#000 End 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 nineteen:03:nineteen 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:xix:32

2016-04-29 19:03:18 Raid Ready # 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#ii 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 xviii: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:xviii

2016-04-29 17:25:04 Raid Set # 000 RaidSet Degraded

2016-04-29 17:25:04 ARC-1882-VOL#000 Book Failed

2016-04-29 16:15:16 Enc#ii SLOT 09 Device Inserted

2016-04-29 16:15:16 Enc#ii SLOT 09 Device Removed

2016-04-29 sixteen:fifteen:15 Raid Prepare # 000 RaidSet Degraded

2016-04-29 xvi:xv: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 Consummate Init 025:37:39

2016-04-29 08:32:sixteen 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 Fix # 000 Delete RaidSet

2016-04-28 xv:00:26 Raid Set # 000 RaidSet Degraded

2016-04-28 xv:00:26 ARC-1882-VOL#000 Volume Failed

2016-04-28 15:00:25 Raid Set # 000 RaidSet Degraded

2016-04-28 fifteen:00:25 ARC-1882-VOL#000 Volume Failed

2016-04-28 xv:00:25 Raid Set up # 000 RaidSet Degraded

2016-04-28 15:00:25 ARC-1882-VOL#000 Book Failed

2016-04-28 15:00:25 Raid Prepare # 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 xv:00:24 ARC-1882-VOL#000 Book Failed

2016-04-28 xv:00:24 Raid Set # 000 RaidSet Degraded

2016-04-28 fifteen:00:24 ARC-1882-VOL#000 Book Failed

2016-04-28 15:00:24 Raid Ready # 000 RaidSet Degraded

2016-04-28 15:00:24 ARC-1882-VOL#000 Volume Failed

2016-04-28 fifteen:00:24 Raid Set # 000 RaidSet Degraded

2016-04-28 fifteen:00:24 ARC-1882-VOL#000 Book Degraded

2016-04-28 15:00:23 Raid Set up # 000 RaidSet Degraded

2016-04-28 xv:00:23 ARC-1882-VOL#000 Volume Degraded

2016-04-28 xiv:24:48 Enc#two SLOT 03 Device Inserted

2016-04-28 fourteen:24:47 Enc#ii SLOT 03 Device Removed

2016-04-28 14:24:43 Raid Fix # 000 RaidSet Degraded

2016-04-28 xiv:24:43 ARC-1882-VOL#000 Volume Degraded

2016-04-28 fourteen:23:42 Proxy Or Inband HTTP Log In

2016-04-28 14:15:05 ARC-1882-VOL#000 Outset Initialize

2016-04-28 14:15:03 ARC-1882-VOL#000 Create Book

2016-04-28 fourteen:fifteen:03 Raid Ready # 000 Create RaidSet

2016-04-28 14:fourteen:41 Raid Set # 000 Delete RaidSet

2016-04-28 14:fourteen:36 Raid Prepare # 000 Delete RaidSet

2016-04-28 xiv:14:28 Raid Set # 000 Delete RaidSet

2016-04-28 14:13:43 Proxy Or Inband HTTP Log In

2016-04-28 x:03:21 Enc#ii 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#ii 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 Kickoff 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 Commencement Rebuilding

2016-04-27 17:41:55 ARC-1882-VOL#000 Failed Volume Revived

2016-04-27 17:41:55 Enc#ii 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 Prepare # 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 Kickoff Rebuilding

2016-04-27 17:twoscore:23 ARC-1882-VOL#000 Failed Volume Revived

2016-04-27 17:40:23 Enc#ii SLOT 08 Device Inserted

2016-04-27 17:40:21 Enc#2 SLOT 08 Device Removed

2016-04-27 17:40:05 Enc#two SLOT 08 Device Removed

2016-04-27 17:40:04 ARC-1882-VOL#000 Finish 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:xv: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:xv: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 Ready # 000 RaidSet Degraded

2016-04-27 xvi: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:xx Enc#2 SLOT 08 Device Inserted

2016-04-27 xvi:21:xix 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:xix Raid Set # 000 RaidSet Degraded

2016-04-27 xvi:21:19 ARC-1882-VOL#000 Volume Failed

2016-04-27 sixteen: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:nineteen:22 Enc#2 SLOT 08 Device Inserted

2016-04-27 sixteen:19:21 Enc#2 SLOT 08 Device Removed

2016-04-27 sixteen: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 xvi: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 sixteen:17:30 Enc#two SLOT 08 Device Removed

2016-04-27 16:17:30 ARC-1882-VOL#000 Cease 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 Book Failed

2016-04-27 sixteen:13:21 ARC-1882-VOL#000 Outset Rebuilding

2016-04-27 16:thirteen:19 ARC-1882-VOL#000 Failed Book Revived

2016-04-27 sixteen:13:19 Enc#2 SLOT 06 Device Inserted

2016-04-27 16:xiii:18 Enc#ii SLOT 06 Device Removed

2016-04-27 16:xiii:18 ARC-1882-VOL#000 Terminate Rebuilding 000:31:29

2016-04-27 16:13:xviii Raid Gear up # 000 RaidSet Degraded

2016-04-27 16:thirteen:18 ARC-1882-VOL#000 Volume Failed

2016-04-27 15:41:49 ARC-1882-VOL#000 Outset Rebuilding

2016-04-27 fifteen: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 ready to hot spare. And the another bulldoze will driblet. What’s odd is that you see removed and inserted when nosotros didn’t physically pull the bulldoze.

Practice they show equally failed or gratuitous when they drop?

They say failed, simply can be instantly gear up to hot spare.

Are the 8087/SATA cables y’all are using the ones shipped with the cards or did you lot buy third party cables?

3Ware from Newegg, Detail=9SIA24G28N2208, SFF-8087 to 4 Sata

Do you have ability management enabled on the menu?

Hither are the settings (Default?) from Hdd Power Management

Stagger Power On Command
0.7

Time To Hdd Low Power Idle
Disabled

Time To Hdd Low RPM Manner
Disabled

Fourth dimension To Spin Down Idle HDD
Disabled

SATA Power Up In Standby
Default

Delay For PHY To Stable
Disabled

Yous are aware that none of the Doctor series Toshiba drives are listed in their HCL, just some of the MG serial, right?

Yeah, I am, unfortunately I wasn’t in on that conclusion.

Thanks

#2,514

Please mail specifics about the enclosures you are running, the BIOS/Firmware revisions of both the cards and the drives. Delight post the full card log from i of the machines. What kind of ability supplies, motherboards and other installed devices are you running? Is it ever the same drives dropping out? Practise they evidence 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 political party cables? Do you lot have power management enabled on the carte? Yous are enlightened that none of the MD series Toshiba drives are listed in their HCL, only some of the MG series, correct?

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 Proper noun ARC-1882IX-12
Firmware Version V1.53 2016-02-16
Kicking ROM Version V1.53 2016-03-xvi
PL Firmware Version 19.0.0.0
Chief Processor Intel Cadre i7-4770
Memory 8GB

Windows Commuter is latest

Date: 11/15/2014, Version 6.20.0.31

Typical Drives in x Deejay Raid half-dozen
Device Blazon SATA(5001B4D51C7F101C)
Device Location Enclosure#2 SLOT 01
Model Name TOSHIBA MD04ACA400
Series Number 85R2KPIOFSAA
Firmware Rev. FP2A
Deejay Chapters 4000.8GB
Physical Block Size 4096
Logical Block Size 512
Current SATA Mode SATA600+NCQ(Depth32)
Supported SATA Mode SATA600+NCQ(Depth32)
Error Recovery Command (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 Yep
SMART Read Error Rate 100(fifty)
SMART Spinup Time 100(1)
SMART Reallocation Count 100(fifty)
SMART Seek Error Rate 100(fifty)
SMART Spinup Retries 101(30)
SMART Calibration Retries North.A.(North.A.)
SSD Reserved Infinite N.A.(Northward.A.)
SSD Wearing Indicator N.A.(Due north.A.)

. Please postal service the full card log from 1 of the machines.

2016-05-02 10:00:xviii E2 SLOT 03 HotSpare Deleted

2016-05-02 09:59:57 Proxy Or Inband HTTP Log In

2016-05-02 09:01:fifty H/Westward 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 Outset 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-thirty 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#two SLOT 05 Device Inserted

2016-04-thirty 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-xxx 06:04:55 Raid Set # 000 RaidSet Degraded

2016-04-xxx 06:04:55 ARC-1882-VOL#000 Volume Failed

2016-04-thirty 05:54:05 ARC-1882-VOL#000 Get-go Rebuilding

2016-04-30 05:54:03 ARC-1882-VOL#000 Failed Volume Revived

2016-04-xxx 05:54:03 Enc#2 SLOT 01 Device Inserted

2016-04-thirty 05:54:02 Enc#ii 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-thirty 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 Book Revived

2016-04-30 04:32:09 Enc#two SLOT 01 Device Inserted

2016-04-30 04:32:08 Enc#ii SLOT 01 Device Removed

2016-04-30 04:32:08 ARC-1882-VOL#000 Terminate Rebuilding 000:05:45

2016-04-thirty 04:32:08 Raid Set # 000 RaidSet Degraded

2016-04-thirty 04:32:08 ARC-1882-VOL#000 Book Failed

2016-04-xxx 04:26:22 ARC-1882-VOL#000 Commencement Rebuilding

2016-04-thirty 04:26:20 ARC-1882-VOL#000 Failed Volume Revived

2016-04-30 04:26:20 Enc#two SLOT 01 Device Inserted

2016-04-30 04:26:nineteen Enc#2 SLOT 01 Device Removed

2016-04-30 04:26:xix ARC-1882-VOL#000 Terminate Rebuilding 000:50:52

2016-04-30 04:26:19 Raid Prepare # 000 RaidSet Degraded

2016-04-30 04:26:19 ARC-1882-VOL#000 Book 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#ii 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-thirty 03:35:24 Raid Set # 000 RaidSet Degraded

2016-04-xxx 03:35:24 ARC-1882-VOL#000 Book Failed

2016-04-30 03:09:04 ARC-1882-VOL#000 Start Rebuilding

2016-04-30 03:09:02 ARC-1882-VOL#000 Failed Book Revived

2016-04-30 03:09:02 Enc#2 SLOT 01 Device Inserted

2016-04-30 03:09:01 Enc#ii 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-thirty 03:09:01 ARC-1882-VOL#000 Volume Failed

2016-04-30 02:13:x ARC-1882-VOL#000 Start Rebuilding

2016-04-30 02:xiii:08 ARC-1882-VOL#000 Failed Volume Revived

2016-04-thirty 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 End Rebuilding 000:31:51

2016-04-30 02:13:07 Raid Set # 000 RaidSet Degraded

2016-04-30 02:xiii:07 ARC-1882-VOL#000 Volume Failed

2016-04-thirty 01:41:16 ARC-1882-VOL#000 Start Rebuilding

2016-04-thirty 01:41:14 ARC-1882-VOL#000 Failed Volume Revived

2016-04-thirty 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:thirteen ARC-1882-VOL#000 Stop Rebuilding 000:12:45

2016-04-30 01:41:13 Raid Prepare # 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 Showtime 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-xxx 01:28:24 ARC-1882-VOL#000 Book Failed

2016-04-30 01:01:26 ARC-1882-VOL#000 Beginning Rebuilding

2016-04-xxx 01:01:24 ARC-1882-VOL#000 Failed Volume Revived

2016-04-thirty 01:01:24 Enc#two SLOT 01 Device Inserted

2016-04-xxx 01:01:23 Enc#ii SLOT 01 Device Removed

2016-04-30 01:01:23 ARC-1882-VOL#000 End Rebuilding 001:26:26

2016-04-30 01:01:23 Raid Prepare # 000 RaidSet Degraded

2016-04-thirty 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 Cease 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#ii SLOT 08 Device Inserted

2016-04-29 22:58:39 Enc#two SLOT 08 Device Removed

2016-04-29 22:58:38 ARC-1882-VOL#000 Cease Rebuilding 003:sixteen:47

2016-04-29 22:58:38 Raid Ready # 000 RaidSet Degraded

2016-04-29 22:58:38 ARC-1882-VOL#000 Book 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 nineteen: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 Terminate 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:xviii Enc#2 SLOT 01 Device Removed

2016-04-29 xix: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 eighteen:43:45 ARC-1882-VOL#000 Start Rebuilding

2016-04-29 xviii:43:43 ARC-1882-VOL#000 Failed Book 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 Terminate Rebuilding 001:18:35

2016-04-29 xviii: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 Kickoff 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:xviii

2016-04-29 17:25:04 Raid Set # 000 RaidSet Degraded

2016-04-29 17:25:04 ARC-1882-VOL#000 Book Failed

2016-04-29 16:fifteen:16 Enc#2 SLOT 09 Device Inserted

2016-04-29 16:15:16 Enc#2 SLOT 09 Device Removed

2016-04-29 sixteen:15:15 Raid Prepare # 000 RaidSet Degraded

2016-04-29 sixteen:15:15 ARC-1882-VOL#000 Book Degraded

2016-04-29 fifteen:52:45 ARC-1882-VOL#000 Beginning Rebuilding

2016-04-29 fifteen: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 Ready # 000 Delete RaidSet

2016-04-28 fifteen: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 Gear up # 000 RaidSet Degraded

2016-04-28 15:00:25 ARC-1882-VOL#000 Volume Failed

2016-04-28 xv: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 fifteen:00:24 Raid Gear up # 000 RaidSet Degraded

2016-04-28 fifteen:00:24 ARC-1882-VOL#000 Book Failed

2016-04-28 15:00:24 Raid Set # 000 RaidSet Degraded

2016-04-28 xv: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 xv:00:24 Raid Prepare # 000 RaidSet Degraded

2016-04-28 fifteen:00:24 ARC-1882-VOL#000 Volume Degraded

2016-04-28 15:00:23 Raid Set # 000 RaidSet Degraded

2016-04-28 fifteen:00:23 ARC-1882-VOL#000 Volume Degraded

2016-04-28 14:24:48 Enc#2 SLOT 03 Device Inserted

2016-04-28 xiv:24:47 Enc#2 SLOT 03 Device Removed

2016-04-28 14:24:43 Raid Ready # 000 RaidSet Degraded

2016-04-28 14:24:43 ARC-1882-VOL#000 Book Degraded

2016-04-28 14:23:42 Proxy Or Inband HTTP Log In

2016-04-28 14:fifteen:05 ARC-1882-VOL#000 Showtime Initialize

2016-04-28 xiv:fifteen:03 ARC-1882-VOL#000 Create Volume

2016-04-28 xiv:fifteen:03 Raid Gear up # 000 Create RaidSet

2016-04-28 14:14:41 Raid Set # 000 Delete RaidSet

2016-04-28 fourteen:fourteen:36 Raid Set # 000 Delete RaidSet

2016-04-28 fourteen:14:28 Raid Set # 000 Delete RaidSet

2016-04-28 xiv:13:43 Proxy Or Inband HTTP Log In

2016-04-28 x:03:21 Enc#2 SLOT 03 Device Inserted

2016-04-28 ten: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#ii SLOT 03 Device Removed

2016-04-28 09:47:57 ARC-1882-VOL#000 Arrest Rebuilding 000:44:eighteen

2016-04-28 09:47:57 Raid Ready # 000 RaidSet Degraded

2016-04-28 09:47:57 ARC-1882-VOL#000 Book Degraded

2016-04-28 09:34:06 Enc#2 SLOT 09 Device Inserted

2016-04-28 09:34:05 Enc#ii 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 Book Degraded

2016-04-28 09:03:39 ARC-1882-VOL#000 Start Rebuilding

2016-04-28 09:03:36 Raid Fix # 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#ii 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 Book 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 Book Failed

2016-04-27 17:41:57 ARC-1882-VOL#000 First Rebuilding

2016-04-27 17:41:55 ARC-1882-VOL#000 Failed Book 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:xl: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 Finish Rebuilding 000:24:26

2016-04-27 17:twoscore:04 Raid Gear up # 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 Get-go Rebuilding

2016-04-27 17:15:36 ARC-1882-VOL#000 Failed Volume Revived

2016-04-27 17:fifteen: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:xv: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 Showtime Rebuilding

2016-04-27 xvi:59:37 ARC-1882-VOL#000 Failed Volume Revived

2016-04-27 16:59:37 Enc#two SLOT 08 Device Inserted

2016-04-27 16:59:36 Enc#ii SLOT 08 Device Removed

2016-04-27 16:59:36 ARC-1882-VOL#000 Stop Rebuilding 000:38:xiv

2016-04-27 16:59:36 Raid Set # 000 RaidSet Degraded

2016-04-27 16:59:36 ARC-1882-VOL#000 Book Failed

2016-04-27 16:21:22 ARC-1882-VOL#000 Kickoff Rebuilding

2016-04-27 xvi:21:20 ARC-1882-VOL#000 Failed Volume Revived

2016-04-27 16:21:xx Enc#ii SLOT 08 Device Inserted

2016-04-27 16:21:19 Enc#two SLOT 08 Device Removed

2016-04-27 16:21:nineteen ARC-1882-VOL#000 Stop Rebuilding 000:01:54

2016-04-27 xvi:21:19 Raid Set # 000 RaidSet Degraded

2016-04-27 16:21:19 ARC-1882-VOL#000 Volume Failed

2016-04-27 sixteen: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#ii SLOT 08 Device Inserted

2016-04-27 16:19:21 Enc#two SLOT 08 Device Removed

2016-04-27 16:19:21 ARC-1882-VOL#000 Stop Rebuilding 000:01:47

2016-04-27 16:nineteen:21 Raid Set # 000 RaidSet Degraded

2016-04-27 16:nineteen:21 ARC-1882-VOL#000 Volume Failed

2016-04-27 16:17:33 ARC-1882-VOL#000 Offset Rebuilding

2016-04-27 sixteen: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 xvi:17:30 Raid Set # 000 RaidSet Degraded

2016-04-27 xvi:17:30 ARC-1882-VOL#000 Volume Failed

2016-04-27 16:13:21 ARC-1882-VOL#000 Start Rebuilding

2016-04-27 sixteen:13:19 ARC-1882-VOL#000 Failed Volume Revived

2016-04-27 xvi:13:19 Enc#2 SLOT 06 Device Inserted

2016-04-27 16:xiii:18 Enc#2 SLOT 06 Device Removed

2016-04-27 xvi:xiii:18 ARC-1882-VOL#000 End Rebuilding 000:31:29

2016-04-27 16:thirteen:18 Raid Ready # 000 RaidSet Degraded

2016-04-27 16:13:18 ARC-1882-VOL#000 Volume Failed

2016-04-27 fifteen:41:49 ARC-1882-VOL#000 Start Rebuilding

2016-04-27 15:41:47 ARC-1882-VOL#000 Failed Book Revived

2016-04-27 15:41:47 Enc#two SLOT 08 Device Inserted

2016-04-27 15:41:46 Enc#ii SLOT 08 Device Removed

2016-04-27 15:41:46 ARC-1882-VOL#000 Stop Rebuilding 003:48:09

Is it ever the same drives dropping out?

No, If I rebuild with 1 that dropped, it can exist gear up to hot spare. And the another drive will drop. What’southward odd is that you see removed and inserted when nosotros didn’t physically pull the drive.

Practice they show as failed or complimentary when they drop?

They say failed, simply can exist instantly ready to hot spare.

Are the 8087/SATA cables you are using the ones shipped with the cards or did you buy 3rd political party cables?

3Ware from Newegg, Particular=9SIA24G28N2208, SFF-8087 to 4 Sata

Do you have power direction enabled on the bill of fare?

Here are the settings (Default?) from Hdd Power Direction
Stagger Power On Control
0.seven

Fourth dimension To Hdd Low Power Idle
Disabled

Time To Hdd Depression RPM Mode
Disabled

Time To Spin Down Idle HDD
Disabled

SATA Power Upwardly In Standby
Default

Delay For PHY To Stable
Disabled

Yous are aware that none of the Physician serial Toshiba drives are listed in their HCL, only some of the MG series, right?

Yep, I am, unfortunately I wasn’t in on that determination.

Thanks[/QUOTE]

#2,515

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

In case anyone needs to know, the “background priority” is set to eighty% and has been since mean solar day 1.

Then.. new thought: My raid that’s currently expanding right at present was in ONLINE mode (although I’m only in the BIOS itself).
If I were to fix the RAID to an OFFLINE condition and so brainstorm expansion, will this expansion occur equally a FOREGROUND process/initialization or still count as background? I believe this might become me a bit of a meliorate result as I think if the raid is in online mode, it automatically processes things as a background chore?

Last edited:
Jun 17, 2016

#2,516

Hullo 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 eight Samsung Pro 850 SSDs in Raid 0 (256 Stripe Size, write through (also tried write back) formatted as 64k in Windows 10) currently for prototype 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’chiliad trying to figure out what might be the cause of such lob sided readings?

Any help would exist much appreciated!

#ii,517

NO!
Do not buy a “USB-to-RJ11”
modem, or worse, a impaired USB-iv-pin to RJ11-iv-pin adapter.

This is the pinout for the Areca RJ11 expander connector:

To make your own cablevision, you will need:

USB to RS232 serial male person adapter
(cheaper ones are available just the FTDI chipset only works)

Modular (i.eastward. configurable) DB9 female to RJ11 adapter

RJ11 cablevision

I’m deliberately not including the DB9 pinouts. If yous’re not confident about figuring those out, you shouldn’t exist making this cable. Contact Areca Support (or Tekram) and beg/buy a cable.

I don’t have an Areca -9 card any more than or I’d permit you borrow mine.

PS: A lot of motherboards will include a COM1 header on the board, fifty-fifty if there is no serial port connector on the I/O. Those are standardized and instead of the USB, you can go a simpler adapter similar
this. Information technology’s a native series port which is always preferable to a USB adapter.

I made a cablevision upwardly for my ARC-1680 using these instructions – I connected them like so:

RJ11_________DE9
Pin 1 ———– Pin 7 (RTS)
Pin 2 ————- Pivot 2 (RXD)
Pin 3 ————– Pivot 3 (TXD)
Pin 4 ————– Pin five (GND)
(Pivot 5 & six not connected)

I can become to a prompt when I plug it in to the expander that says “Password” withal information technology seems to transport likewise many characters at once and “*” when I press enter – not sure if I’thousand getting the password wrong or there is some other issue.

My concluding settings are VT102 (no vt100 in minicom, should be uniform anyway) 115200 eight North 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 printing enter until it actually sends the enter key:

                              
                                Password:**   Password:**   Password:****   Password:*******   Password:****   Password:*******   Password:**************   Password:**   Countersign:   Countersign:****

Concluding edited:
Jun 29, 2016

#2,518

I am planning a custom NAS case and I am trying to work out the individual (non global) LED Activity pin-outs on the ARC-1203-8i (eight-port) controller.

Looking at the manual it illustrates where the pin-outs are for the LED connectors (which I’1000 assuming are positive?).

The global LED pin-out is articulate as daylight yet it is a bit vague every bit to where the negative side for the individual LED’s connect back to?
The simply mention of negative (highlighted beneath) is referring to the “EPLD CTL output pin” which it doesn’t really say where information technology is on the raid controller, or if it ‘s referring to something else? Maybe it’s a typo for “LED CTL” instead?

I am assuming the correct 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”

I gauge I can say “yes indeed I have read the manual”, but now I’grand quite stuck.

#ii,519

I have an Areca 1882 with 4GB, I employ it in my abode network, with 4 deejay raid5-sets. It is mainly used for streaming so on, normally no more than 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 fifteen-thirty seconds (300-400 MBs per 2nd from the array), and then it grinds to a halt for a footling while, and the speed then picks upward. Is there any settings that sacrifices som top performance for more consistently good and snappy operation.

#2,520

Merely joined this forum, kickoff time OP hither…

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

one RaidSet 14 disks with ii hot spares

1 RAID5, xl TB VolumeSet on this RaidSet

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

Rebuild ran through the dark

seven/21: six: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 one free disk. See pics, please.

In improver, I had an 1883X configured as JBOD in the same R900. PCIe Fatal Error started flashing on the server. I shut it downwardly, and pulled the RAID controller – reboot – all the same PCIe fault. Put in 1882 every bit a replacement, pulled 1883 JBOD – no more than PCIe Fatal Error.

So the questions I take are:

1) Why didn’t the second hot spare pick up when the second drive failed?

ii) What is the existent status of the drives?
3) Am I shooting myself in the pes trying to run 2 PCIe controllers in this server?

Whatsoever advice/data is appreciated.

Firmware on This Sas1066e 05 Appears Broken Res2sv240

ARECA Possessor’southward Thread (SAS/SATA RAID Cards)

Firmware on This Sas1066e 05 Appears Broken Res2sv240

You May Also Like

Cara Menghubungkan Hp Ke Tv Biasa

Cara Sharing Printer Windows 10 Dengan Lan

Cara Mengetahui Password Wifi Yang Belum Pernah Terkoneksi

Cara Reset Printer Epson Plq 20

Cara Mematikan Lampu Black Ink Pada Printer Canon E400

Cara Ganti Password Wifi First Media Melalui Laptop