DrPrimo

I had the same thing the other day (http://lime-technology.com/forum/index.php?topic=40073.0). Do not and have not had any VMs on that server. Although I think the reason the console may have been "unresponsive" in my case was a faulty keyboard that was just purchased. It has been exchanged and I have had no further issues with unresponsiveness.

This morning I upgraded to v6 RC3, everything seemed to have gone smoothly. I then proceeded to upgrade parity. It seems to be proceeding fine, but the console gave the following error: Tower login: tar: domain.img: Cannot change ownership to uid 0, gid 999:Operation not permitted tar: Exiting with failure status due to previous errors Console is non-responsive, although according to the WebGUI parity rebuilding is still going, currently at 2.6%. Is this something to be worried about? Will the console become responsive again once the rebuild is finished? Should the rebuilding be stopped? Thanks! EDIT: Console now responsive, seems to be behaving normally. Any ideas on what caused above error? EDIT 2: Appended to end of previous syslog: May 21 09:05:45 Tower avahi-daemon[1440]: Service "Tower" (/services/smb.service) successfully established. May 21 09:39:33 Tower kernel: usb 7-4: new low-speed USB device number 2 using ohci-pci May 21 09:39:33 Tower kernel: input: HID 04d9:1203 as /devices/pci0000:00/0000:00:16.0/usb7/7-4/7-4:1.0/0003:04D9:1203.0001/input/input5 May 21 09:39:33 Tower kernel: hid-generic 0003:04D9:1203.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 04d9:1203] on usb-0000:00:16.0-4/input0 May 21 09:39:33 Tower kernel: input: HID 04d9:1203 as /devices/pci0000:00/0000:00:16.0/usb7/7-4/7-4:1.1/0003:04D9:1203.0002/input/input6 May 21 09:39:33 Tower kernel: hid-generic 0003:04D9:1203.0002: input,hidraw1: USB HID v1.11 Device [HID 04d9:1203] on usb-0000:00:16.0-4/input1 May 21 09:41:28 Tower login[1377]: invalid password for 'UNKNOWN' on '/dev/tty1' May 21 09:41:40 Tower login[1377]: ROOT LOGIN on '/dev/tty1' For some reason was not recognizing the keyboard? syslog.zip

OK, was able to copy off a 1.5GB, 1.8GB and 7.85GB file with no crashes.

Correct. I copied ~1.1TB to the server with parity unassigned. Write speeds without parity were ~35MB/s using Teracopy. Initially with parity assigned I was getting ~7-10MB/s using Teracopy. I have not tried copying files off the server, only watched video files that are stored on it which never caused a crash. I will try to copy a file off later tonight. Are the low write speeds significant? Is there anything specific that may indicate? The assigned data drive and the parity drive with both precleared with 3 cycles. They both were precleared at the same time. One averaged 25:45 per cycle, the other 28:30. No other changes have been made to the network since adding the server. I have changed the servers port on the switch (just did now). How many simultaneous preclears are an ideal test? ~95% of the data is still on other drives. I built the server to house rips of my DVDs/BRs, and I deleted the extra copies of some of those (about 50) to make room for more (I have about 800 out of 1200 done, then on to box sets....). I can always (hopefully) copy those off the server to re-preclear the drives, or worst case scenario I just re-rip.

Well, was able to copy two files from 2 seperate computers (the same win7 box and a MBP). Attempted to copy one of the files that had made it crash before - crashed again. So can I rule out RAM? The Kingston is on the QVL. The fact that both the Kingston and PNY ram show up the same under memtest is weird though. Can this mean some sort of MB issue? The BIOS does correctly recognize it though. I have a few 10/100 PCI nic's, so I can try one of those tonight. I have never tried StressLinux. Can it be run with the data drive unattached? Or would that give inaccurate results?

The foxconn nettop that I am using has the ION chipset. Only problem I have had was with a m2ts file in VLC, and once I unloaded the processing to the ION chipset it played it fine. It is the priciest one of the group, but I think still in line with similar solutions. It can also easily be repurposed easily - one is currently being used at my work as a VOIP server, and we just received one to be used to stream internet video to a TV display (they are both lower end ones)! It is also very quiet - I was worried when I bought it that it would be noisy as I had seen many complaints about that but it has not had a problem. Many people I read also resolved their noise issues when the added a SSD instead of a platter drive. I would prefer a small Zacate box, hopefully they come out with something soon or I will just have to roll my own.

Ok, first off thanks everyone. I took a 4gb stick of ram out of my desktop and put it into the unraid box. For s***s and giggles, I decided to see what it showed up as in memtest. The "settings: ram:" showed the same. Mapping correctly showed it as 1333MHz DDR3, the same speed/type as the Knigston stick (the board can only run it at 1066MHz though). Could this be some sort of MB issue? An issue with memtest itself? When I got home from work this afternoon, it had successfully completed its parity check - no errors reported. I then tried to copy a file from the same box but different drive. Same result. unraid is currently running another parity check. I will see if it continues to reboot itself with the new stick. Should I bother to run memtest on this stick? What other hardware tests are recommended (other than swapping out hardware - which I will do after we see how the new RAM runs)?

What about something like this: http://www.newegg.com/Product/Product.aspx?Item=N82E16856119044. They have them in various configurations: http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=100008345%2050002136&IsNodeId=1&name=Foxconn. I have the NT330 model serving as my HTPC for now. Runs torrents fine, has ripped (I have not tried encoding) DVDs/BRs. And its hardly any bigger then my wireless router! They do go on sale regularly at newegg, either cheaper or combo'd with RAM/DVD drive. I made a deal alert at slickdeals and picked mine up for $145 w/ matching external DVD drive on black friday.

Unraid now keeps rebooting itself during parity check. Any thoughts? Latest syslog attached. syslog.txt

unraid rebooted on its own while checking parity, again nothing presented in syslog w/ tail in putty. It is checking parity again, will see if it keeps happening.

So far it has only happened with this file. It is located on a external USB hard drive connected to a Windows 7 box. I have transferred successfully from this drive/box before, however parity was not assigned during previous transfers. Unraid is checking parity now, about 7.5 hours to go. I will then attempt to copy another file from a different drive/computer (will probably tomorrow early morning or early afternoon). After the latest crash I reseated RAM/sata/power cables/usb before booting. Thanks for the response!

OK, so parity check completed with the 512 sync errors it had found previously. Attempted to copy the file that had crashed unraid before. After ~47 seconds, teracopy fails - states "Error: The network path was not found". Unraid becomes unreachable from the network, console becomes unresponsive (see photo below). Attempt to copy syslog (w/ tail) from putty, it disappears - however had copied all but last line previously: putty had no other lines than that that were not in last posted syslog. Console: Any theories? Should I attempt to write without parity as I did before? Attempt to write with parity and a different file? EDIT: Attached syslog from after latest reboot. syslog.txt

UPDATE: Parity check is now at 46% - 512 sync errors found. Updated syslog attached. syslog.txt

Thank you, attached find my current syslog. I have tail running in a telnet window to capture the syslog in the event it crashes again. I restarted unraid and it is currently checking parity (currently at 43% - 0 errors found so far - ~271 minutes to complete). Once it finishes, I will attempt to recreate the crash. Thank you for your help. SYSTEM UnRaid Version: 4.7 Motherboard/Processor: ASUS E35M1-M PRO AMD Zacate E350 AMD Hudson M1 Micro ATX Motherboard/CPU Combo RAM: 1x Kingston KVR1333D3N9/2G (2GB) Hard Drives (assigned): HITACHI Deskstar 5K3000 (Parity); 1x Samsung F4 - firmware updated (Data) Power Supply: Antec EarthWatts Green EA-380D USB: Verbatim TUFF-'N'-TINY 4GB Flash Drive (using StarTech USBMBADAPT2 2 Port USB Motherboard Header Adapter) Case: Antec 300 Cables: using the SATA cables that came with the MB. Hard drives currently report at 26° and 28°. All hardware was bought new, and not used before building the server. Hard drives ran 3 preclear cycles before being assigned. The only add-on I have installed or used is the preclear script. unMenu will be installed in the near future. syslog.txt

OK, so more than 10 hours of Memtest results in 9 passes and 0 errors. However, the line "Settings: RAM: 320 MHz (DDR640) / CAS : 4-3-3-3 / DDR2 (64 bits)" is interesting. I have never used memtest before, rebooting and checking the bios shows it correctly reported as 1066MHz DDR3 with voltage and CAS timings on auto (1.5v[correct] and CAS timings not displayed). Does that line mean anything significant? Should I manually set the CAS timings instead of leaving on auto? Where do I go from here? Start the array and let it check parity?