January 18, 201313 yr While I am not new to Linux or Unix, it has been a while since I was using them a lot day to day, until I created my unRaid server. I am running all 3TB drives and started the sever up back in Nov. Since day 1, the initial parity calc completed withn no issues (changed the parity drive once to check if that was my problem). Also, the parity calc while adding files is not problematic. But, whenever I run a parity check, the system completely locks up at some point (usually in the first 20% of the check) and the only way to restart or shutdown is a hard shutdown with the power button. I have attached the syslog from the last try for a look (which crapped out at 0.3%)... Syslog_1-18-13_1000.txt
January 18, 201313 yr Almost everything looks good in your syslog, but there is one thing that may or may not be a problem. The syslog shows ACPI parsing errors that are related to the onboard SATA support. Usually ACPI parsing errors are not important, but these seem directly related to the onboard SATA support, so I strongly recommend checking for a BIOS update for that motherboard, and installing it if there is one.
January 18, 201313 yr Author I updated the Bios, restarted, and got more of the ACPI errors. I currently have the parity check running...
January 19, 201313 yr Author So, it ran for the longest time yet, making it to 60%, but it crashed again. And on restart, it crashed VERY quickly when it restarted the parity check. Moreover, this new BIOS does not seem as stable as the last. Any more thoughts? I have attached the new syslog... Ted Syslog_1-18-13_1300.txt
January 19, 201313 yr So, it ran for the longest time yet, making it to 60%, but it crashed again. And on restart, it crashed VERY quickly when it restarted the parity check. Moreover, this new BIOS does not seem as stable as the last. Any more thoughts? I have attached the new syslog... Ted The new BIOS has removed S1 standby support. The only reason I can think of for doing that, is that it did not work before, and they either could not fix it, or decided they did not have time to fix it. Not a confidence building move either way. They also removed the pm flag from the onboard SATA support, I believe that means they dropped Port Multiplier support, again for probably the same reasons as dropping S1 support. They did not fix the ACPI parsing errors. I do have to confess one thing though, I obviously examined it too quickly and thought I saw SATA, but it was actually SAT0, a bit inexcusable of me. That may or not be SATA related, and I haven't taken time to research it. In any event, this BIOS does not seemed to have improved things for you. I don't see any evidence of it being less stable though, do you have other reasons why you feel that it is? One other possible cause is heat, and your symptoms are somewhat consistent with a critical component overheating. Does it appear to run longer when ambient temps are cooler, such as at night or in the morning, and crash sooner and more often in the afternoon or when it's warmer? CPU temp looks very good when you boot, but perhaps the northbridge/southbridge chipsets are overheating (they control all I/O including disk controlling). If it crashed at 60% because of overheating, it would crash again very quickly if you tried a disk-intensive operation very soon afterward.
Archived
This topic is now archived and is closed to further replies.