Visit Open-E website
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: DSS6.0up10 Replication problem I/O errors

  1. #11

    Default

    Quote Originally Posted by JFleck
    You are not alone with this issue.
    Thanks for your reply! I'm sorry to hear you have the same problem..
    Are you using a supermicro chassis?
    Are you using a Areca Raid Controller
    What kind of disks are you using?

    I'm starting to think the problem could be power or disk related. On this areca faq there was someone with the same abort device commands and solved it by upgrading the power supply.

    I attached 8 of my 24 disk to a 500watt PS, Ik takes a lot longer for the system to crash
    I know the power supply is not broken because I swapped the entire chassis.
    Maybe the power output is not sufficient?

    Still no word from support, In really hope they can point me in the right direction. I'm wasting time chasing a ghost and my manager is not amused

  2. #12

    Default

    Did you have tested this problem with Areca 1680 and FW 1.46? Same error ?

  3. #13

    Default

    Quote Originally Posted by stardf
    Did you have tested this problem with Areca 1680 and FW 1.46? Same error ?

    No have not tried that yet. I will test this after my current test, I have left 8 HDD's in the system and created a raidset, if it is a power problem then chances are that the issue will no longer occur.

  4. #14

    Default

    Quote Originally Posted by eppo78
    I have left 8 HDD's in the system and created a raidset, if it is a power problem then chances are that the issue will no longer occur.

    The system crashed again so I think I can savely say it is not a power problem.
    No word from support yet..

  5. #15

    Default Updates

    I am using the Areca Controller Card (ARC-1680) in my system as well. I have recently upgraded the firmware to ver 1.47 and am still seeing the problems. Strange thing is that I have two devices that are identical other than the fact that one is failing with that error and the other does not.

    Drives are ST31500341AS 1.5TB drives. Have a total of 16 in the system. Support has asked me to open up remote support but can't seem to get that to work right now, I am waiting on a response from them still.

    Controller Name ARC-1680
    Firmware Version V1.47 2009-07-16
    BOOT ROM Version V1.47 2009-06-25
    SAS Firmware Version 4.7.3.0

    Main Processor 1.2GHz IOP348 C1
    CPU ICache Size 32KBytes
    CPU DCache Size 32KBytes/Write Back
    CPU SCache Size 512KBytes/Write Back
    System Memory 2048MB/533MHz/ECC
    Current IP Address 10.1.8.101

  6. #16

    Default Problem Solved! :d [

    I managed to solve the problem!

    There is a bios setting on my motherboard (X7DWN+) that sets the 'max payload size'
    for PCI-Express devices. This setting was default on 256, when I had set this to 128 the problem was gone.

    Areca support (as good as the cards are ) has confirmed that the Areca raidcontrollers use a default payload setting of 128.

    Replication works fine now!

  7. #17

    Default Recall Problem NOT solved!

    Quote Originally Posted by eppo78
    I managed to solve the problem!
    Replication works fine now!
    500Gb replication was OK but when I setup the system for 1024GB replication the system crashed after 3.5 hours

    ....

  8. #18

    Default

    I've swapped my motherboard for a new Supermicro X8DTN+ with 8GB DDR3 just in case.
    The system crashed again...

    I downgraded the Areca firmware/bios to 1.46 and setup replication for 1024GB....

    I could really use a break..

  9. #19

    Default Preliminary tests are successful

    Quote Originally Posted by stardf
    Did you have tested this problem with Areca 1680 and FW 1.46? Same error ?
    Thanks again, I should have tried this earlier

    I've downgraded the firmware/bios to 1.46 and setup replication for 1024GB. The system past 2 initial replications, no crashes.

    The release notes of Areca firmware/bios 1.47 state that there has been a modification to the SendAbortTask, maybe thats the issue?

    I'll keep on testing and keep you updated on my progress.
    If it is still working after a week I'll say the problem is fixed

  10. #20

    Default

    No problem

    I had this problem for a while

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •