DSS6.0up10 Replication problem I/O errors

[eppo78]

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.

[eppo78]

I always send my logfiles with the mails I send to support. I'm still waiting for an anwser...

[symm]

keep us updated with your progress

[JFleck]

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.

[eppo78]

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

[stardf]

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

[eppo78]

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.

[eppo78]

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