Ahh so you watched me suffer ;)
System is still running without problems, case closed.
Thanks for your input.
Type: Posts; User: eppo78
Ahh so you watched me suffer ;)
System is still running without problems, case closed.
Thanks for your input.
Thanks again, I should have tried this earlier :o
I've downgraded the firmware/bios to 1.46 and setup replication for 1024GB. The system past 2 initial replications, no crashes.
The release...
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....
...
500Gb replication was OK but when I setup the system for 1024GB replication the system crashed after 3.5 hours :mad:
....
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...
The system crashed again so I think I can savely say it is not a power problem.
No word from support yet..
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...
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...
I always send my logfiles with the mails I send to support. I'm still waiting for an anwser...
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.
The same issue occurs while replicating a 500GB volume...
I don't think it is ESX related as I have the same problem with a empty volume without a LUN assigned to it.
As far as I know you can only replicate through a nic ( Intel 82575EB internal)
Thanks...
Oh yeah... Because the server frooze up I had to do a hard powercycle.
The result was a corrupted systemvolume that I was not able to repair, all my data was lost :mad:
I don't think 8GB is supported yet
This is saying that the intitiator driver 'qla2xxx' isn't allowed to load, this is because you set it to target mode.
Regards,
Eddo
Hey all,
I'm having serious issues with replicating 1TB FC volumes to my destination DSS.
I'm running DSS6.0up10.8101.3719 64bit on the following hardware;
SuperMicro X7DWN+ Motherboard
64GB...