Visit Open-E website
Results 1 to 10 of 21

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

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. 10-30-2009, 01:30 AM #1
    symm
    symm is offline Master
    Join Date
    Jun 2008
    Posts
    255

    Default

    Did you try sending the logs to support?

    did the initilization finish before you started the replication ?


    BTW it does not seem like a vmware issue, but here is a link to the post concerning LUN 0

    http://kb.vmware.com/selfservice/mic...8601&stateId=0 0 44972208
    Reply With Quote Reply With Quote
  2. 10-30-2009, 07:50 AM #2
    eppo78
    eppo78 is offline Member
    Join Date
    Oct 2009
    Posts
    15

    Default

    I did wait until initilization finished, I even waited to put data on it until the initial replication would finish, but it never does.

    Thanks for the LUN 0 info.
    Reply With Quote Reply With Quote
  3. 10-30-2009, 07:52 AM #3
    eppo78
    eppo78 is offline Member
    Join Date
    Oct 2009
    Posts
    15

    Default

    I always send my logfiles with the mails I send to support. I'm still waiting for an anwser...
    Reply With Quote Reply With Quote
  4. 10-30-2009, 12:48 PM #4
    symm
    symm is offline Master
    Join Date
    Jun 2008
    Posts
    255

    Default

    keep us updated with your progress
    Reply With Quote Reply With Quote
  5. 10-30-2009, 06:54 PM #5
    JFleck
    JFleck is offline Newbie
    Join Date
    Oct 2009
    Posts
    2

    Default Sounds the same as my issue.

    You are not alone with this issue. I've also submitted a ticket and am awaiting a reply. I have two devices that I believe are identical in hardware and software. Replication from device A to Device B seems to be working without a problem. However, Replication from Device B to Device A seems to fail and cause both units to hang and reports a Journal committ error. fortunately I haven't lost any data, but it does require a hard power cycle (reboot command from console doesn't seem to do it) and it trashes any of the replications that I did have. I am using the default 40mb for my replication tasks.
    Reply With Quote Reply With Quote
  6. 11-02-2009, 08:24 AM #6
    eppo78
    eppo78 is offline Member
    Join Date
    Oct 2009
    Posts
    15

    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
    Reply With Quote Reply With Quote
  7. 11-02-2009, 09:34 AM #7
    stardf
    stardf is offline Member
    Join Date
    Mar 2009
    Posts
    11

    Default

    Did you have tested this problem with Areca 1680 and FW 1.46? Same error ?
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

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

Forum Rules