February 16, 201115 yr My parity drive died on me a few days ago, and I just received and installed the new one from WD, did the whole process of formatting and parity synching... I also noticed awhile ago there have been some updates to Unraid and my Unraid OS was a few versions old so I updated the memtest,bzroot, and bzimage files on the my flash key to v4.7. I began transferring files over to the server and about half way through the copying process on my win7 machine it stopped and gave me an error that it couldn't connect with the server. Tryed accessing it through the web interface couldn't connect, nothing was showing up on the monitor that i had plugged into the system to test the new drive installed. I did a system restart and this is what it looks like on the user screen(check image posted) https://picasaweb.google.com/lh/photo/7Xn_g0G1HlKwWhJm51nGsQ?feat=directlink Don't understand why it would do that. I have since down graded back to version 4.5.3 and everything is fine so far. ***UPDATE*** Never mind tried copying a few files over and it did it again half way trough a transfer the network loses the connection to the server, can't access webUI and I have to restart. Is this a hardware issue or software issue? Thanks
February 17, 201115 yr Author Syslog.txt This is the systemlog after a reboot when the server is working correctly. The problem with the drive size has since gone away, but whenever i try to copy files over from my win7 machine to the server about half way through the whole system crashes, the tower login screen on the server monitor goes blank, and WebUI is unaccessible. This happens every time there is a large file load being copied over, but as soon as I hit the reset button unraid loads and my files are accessible again. I wish I could get the syslog when the problem occurs but the OS doesn't work, and I am forced to reboot.
February 17, 201115 yr See this post: http://lime-technology.com/forum/index.php?topic=9880.msg94514#msg94514 Use the tail command to capture your syslog in a telnet window.
February 17, 201115 yr A system log may provide clues while your system is crashing, but to answer your question in my experience almost always problems such as yours are caused by faulty hardware. Sometimes it can be very difficult to troubleshoot. Since I have a pretty good spare parts bin, I prefer the "swap parts" approach. Swap your power supply, memory, processor, cables, motherboard etc. Since the problem can be almost anything, the preferred approach is to try the things first that are easy. The easiest thing to do is to run a memtest (option at boot). Let it run over night.
February 17, 201115 yr Once you get your system stable, you will have to investigate HPA: http://lime-technology.com/forum/index.php?topic=10866.0. This is the likely cause of the issue you had trying to run version 4.7
February 17, 201115 yr Author Thanks for the help guys. I have a feeling its the motherboard. Because I tried installing Ubuntu and Win7 on an extra HD that i plugged into the system and during both install the the monitor goes dark and the system is unresponsive just like when I am running the Unraid OS. I already did a memtest awhile ago but I will try it again.
February 17, 201115 yr Author Ran memtest for about 6 hrs passed 20 consecutive times. So i think it has something to do with the motherboard because i can't even get through a windows/Ubuntu install without the whole system becoming unresponsive. I have an extra system that I built from spare parts I had lying around (I upgrade my desktop a lot) how is UnRaid with AMD/Nvidia systems? Specs: CPU: AMD Athlon X2 dual Core 5600 Motherboard: ASUS M3N78 PRO Nvidia 720a chipset 8300 geforce IGPU RAM: 4x1GB OCZ Reaper DDR2 800 NIC: Intel pro 1000 pcie1x PSU: Antec TruePower Gold 500 watt
February 17, 201115 yr How many drives do you have? Try disconnecting most of the drives. Or disconnect all and add a new one then try the Ubuntu install. You should try to capture the log tail. It may be a drive or controller card and not the MB. You may replace the MB and find the problem does not go away.
February 17, 201115 yr Author I did disconnect all my 1.5 Green drives and I used another spare drive i had lying around does the same thing, and I'm not using a controller card just the MB. Check my signature below for further system specs.
Archived
This topic is now archived and is closed to further replies.