April 14, 201115 yr Finished setting up my 4.7 unraid server with msi motherboard, realtek 10/100/1000 nic card and two 2tb WD Ears drives. Running 4k aligned after preclearing both drives. Don't have the parity drive setup yet as I'm waiting to get all my data copied over before setting that up. I have about 950gb to copy over from an external drive hooked up to my mac. Did a drag and drop right before I went to bed and wake up in the morning to a can't copy error 51? Not sure exactly when it stopped copying over? Tried to access the share via my mac and it crashed out finder trying to access it. I could still login and view the array via the browser but can't access the share over the network. Turned the power off and on on the server and all is accessible again. I was unable to grab a log before I rebooted the server. Can anyone shed some light on why it won't let me copy large amounts of data over to the server? I can copy single individual smaller files over no problem.
April 14, 201115 yr 1.Check your memory 2. Flash your motherboard BIOS to the latest version available.
April 15, 201115 yr Author latest updated system log attached here. Have some errors in there and not sure what they mean? Can anyone enlighten me? Tried copying data over to the server in smaller pieces and it still locks up while copying. Tried 147gb and it locked up once it reached around 9gb. Doing a memtest as I type this. Looks ok so far. Should ACPI in the bios be turned on or off? syslog.txt
April 15, 201115 yr Author ok did a memtest for 9 hours and came up with no errors. I did change one thing in the bios. For the sata mode it was set to ide and I changed it to AHCI. Would this make a difference?
April 15, 201115 yr It would get rid of these errors: ACPI Error: No handler for Region [sACS] http://lime-technology.com/forum/index.php?topic=6803.0
April 15, 201115 yr Author Ok tried to start copying data over again and it stopped. Logged into the unraid server via telnet and this is the error I get Tower login: root Linux 2.6.32.9-unRAID. root@Tower:~# Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: Oops: 0010 [#1] SMP Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: Stack: Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host1/target1:0:0/1:0:0:0/block/sdb/stat Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: Process unraidd (pid: 1383, ti=c38d4000 task=f7660dc0 task.ti=c38d4000) Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: Code: Bad EIP value. Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: Call Trace: Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: EIP: [<00000000>] 0x0 SS:ESP 0068:c38d5f08 Message from syslogd@Tower at Fri Apr 15 10:37:23 2011 ... Tower kernel: CR2: 0000000000000000 Anyone?
April 16, 201115 yr Author Well I swapped out the nic to an intel PCI x gigabit card and looks like I still have a problem. What could this be a bad drive? Here's my syslog error. I'm at my Wits end!! Message from syslogd@Tower at Fri Apr 15 17:35:14 2011 ... Tower kernel: Process unraidd (pid: 1341, ti=c38c2000 task=f6dae260 task.ti=c38c2000) Message from syslogd@Tower at Fri Apr 15 17:35:14 2011 ... Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host2/target2:0:0/2:0:0:0/block/sdb/stat Message from syslogd@Tower at Fri Apr 15 17:35:14 2011 ... Tower kernel: Stack: Message from syslogd@Tower at Fri Apr 15 17:35:14 2011 ... Tower kernel: Call Trace: Message from syslogd@Tower at Fri Apr 15 17:35:14 2011 ... Tower kernel: EIP: [<00000000>] 0x0 SS:ESP 0068:c38c3f08 Message from syslogd@Tower at Fri Apr 15 17:35:14 2011 ... Tower kernel: CR2: 0000000000000000 Message from syslogd@Tower at Fri Apr 15 17:35:14 2011 ... Tower kernel: Code: Bad EIP value. Here's some more in the latest syslog syslog.txt
Archived
This topic is now archived and is closed to further replies.