ok, changed all my bios settings. FREAKED out, for a second, as it wouldnt boot. AMD DTI error. Turns out I had to go tell it to boot usb. all good.

 

unRAID up but wants to do another freakin parity check! if i cancel, its "unprotected". No way around this? thats 24 hours, urgh.

 

new syslog attached. dont see the usb issue anymore.

 

oh, i didnt flash the bios, just changed it.

syslog_5-2010-09-09.txt

ok, changed all my bios settings. FREAKED out, for a second, as it wouldnt boot. AMD DTI error. Turns out I had to go tell it to boot usb. all good.

 

unRAID up but wants to do another freakin parity check! if i cancel, its "unprotected". No way around this? thats 24 hours, urgh.

 

new syslog attached. dont see the usb issue anymore.

 

oh, i didnt flash the bios, just changed it.

If you do not stop the array before rebooting it will always want to perform a full parity check.

 

A parity check can be anywhere from a few hours, to 8 or more.  It all depends on the size of your disks and the bus bandwidth available.    You cannot just cancel it.  Please let it finish...

 

Then, once it has finished, "Stop" the array before you power down (press the "Stop" button on the management interface).  It will then know it is a clean stop and will not need to do a full parity check when you next start the array.

 

Joe L.

Thanks Joe. Makes sense. Dont like it but I get it. So, everyday  I will have to wait a day for the parity check to finish only to have to wait another day for it to finish again as it crashes everyday, got it, lol.

Until you replace the hardware that is the cause of the crash... yes.

Joe, what hardware is causing my problem? Can you tell from the syslog? Thanks for your input.

onchip SATA Type - NATIVE IDE

onchip SATA Port 4/5 Type - IDE (it wont let me change this)

 

 

Not good with bios so sure could use some advice on what to change or change back.

I would not use NATIVE IDE mode for SATA drives.  I would change that to ACHI.  (And then it might let you change the port 4/5 too)

 

Joe L.

thanks Joe. I did change that last night per bcboys post. I ddint notice where that allowed me to change port 4/5, will look when my everlasting parity check is done AGAIN. which will be in the middle of the night.

 

Thanks!

Joe, what hardware is causing my problem? Can you tell from the syslog? Thanks for your input.

I wish I could.  Others have pointed out the LAN chipset has been an issue with others.  You said you would upgrade it to a 1000Mb/s network card.  Did you get the chance to do that yet?  (don't forget to disable the built-in one when you do)

 

Have you verified the file systems yet for errors?  I've seen an error in the file-system crash a server.  You probably need to have a monitor connected directly and not through a KVM when trying to determine the cause of a crash since many times the critical clues are on the system console.  You can even run a "tail -f /var/log/syslog"

 

Or, you can run these commands and mirror the syslog to a file on your flash drive and also to virtual console12.

mv -f /boot/syslog.current /boot/syslog.last 2>/dev/null

cat /var/log/syslog >/boot/syslog.current

echo -e '*.*\t/boot/syslog.current' >>/etc/syslog.conf

echo -e '*.*\t/dev/tty12' >>/etc/syslog.conf

/etc/rc.d/rc.syslog restart

setterm -term linux -powersave off -powerdown 0 -blank 0 </dev/tty12 >/dev/tty12

 

On the server press ALT-F12 to switch to the console with the log output.

Press ALT-F1 to get back to the normal system console where you normally log in. 

(Actually you can log in on ALT-F1 through ALT-F6 as there are 6 vurtual consoles defined for login use)

Ranger, how much and what type of data do you have on your system?  Reason I ask is if your system freezes every time you attempt to copy a file larger than 100 MB or so to it (like mine did), you 1) probably don't have too much on it and 2) are likely going to have to hard reboot several more times before the problem is resolved.

 

What I'm getting at is if you wait until the parity check finishes, then attempt to copy something to it which immediately causes it to freeze, the next time it reboots its going to want to run the parity check again.  You may want to consider copying off any critical data so that you can cancel the repeated parity checks until you get the problem fixed.  I know all too well its hard to troubleshoot if you have to wait hours in between each attempt.

Joe, what hardware is causing my problem? Can you tell from the syslog? Thanks for your input.

I wish I could.  Others have pointed out the LAN chipset has been an issue with others.  You said you would upgrade it to a 1000Mb/s network card.  Did you get the chance to do that yet?   (don't forget to disable the built-in one when you do)

 

No, I have not determined yet which one to buy. I did a search for compatible nics, etc. didnt find a list.

 

Have you verified the file systems yet for errors?   I've seen an error in the file-system crash a server.  You probably need to have a monitor connected directly and not through a KVM when trying to determine the cause of a crash since many times the critical clues are on the system console.   You can even run a "tail -f /var/log/syslog"

 

Im really confused why a KVM would affect anything, but I will try that. Thought a monitor was a monitor was a monitor.

 

Or, you can run these commands and mirror the syslog to a file on your flash drive and also to virtual console12.

mv -f /boot/syslog.current /boot/syslog.last 2>/dev/null

cat /var/log/syslog >/boot/syslog.current

echo -e '*.*\t/boot/syslog.current' >>/etc/syslog.conf

echo -e '*.*\t/dev/tty12' >>/etc/syslog.conf

/etc/rc.d/rc.syslog restart

setterm -term linux -powersave off -powerdown 0 -blank 0 </dev/tty12 >/dev/tty12

 

On the server press ALT-F12 to switch to the console with the log output.

Press ALT-F1 to get back to the normal system console where you normally log in.  

(Actually you can log in on ALT-F1 through ALT-F6 as there are 6 vurtual consoles defined for login use)

 

Woah, over my head. LOL Let me re-read it several times. You are a true gentleman for the help!

 

 

Ranger, how much and what type of data do you have on your system?  Reason I ask is if your system freezes every time you attempt to copy a file larger than 100 MB or so to it (like mine did), you 1) probably don't have too much on it and 2) are likely going to have to hard reboot several more times before the problem is resolved.

 

What I'm getting at is if you wait until the parity check finishes, then attempt to copy something to it which immediately causes it to freeze, the next time it reboots its going to want to run the parity check again.  You may want to consider copying off any critical data so that you can cancel the repeated parity checks until you get the problem fixed.  I know all too well its hard to troubleshoot if you have to wait hours in between each attempt.

 

I have only 39 movies so far. and all my cd collection which is a couple thousand songs. I have my music on another hard drive so thats not a big deal to lose. I can always re-copy the dvd's if needed but yes, certainly a pain. I guess the best route is to replace the nic. Funny thing is the whole system from the motherboard, power supply, sata cards, case and everything came recommended specifically for an unRAID server on avsforum. Thats makes it more frustrating. (not a knock against AVSforum!)

If one is having hardware problems they should start by listing their configuration first:

1. Motherboard - brand, model and if possible hardware and BIOS revision (if you have a brand new MB this is usually printed on white label somewhere on the box)

2. CPU

3. Memory - brand, model etc. if available

4. Power supply - brand and model - this is important

5. Any other cards that you have installed right now (even if unused at the moment)

6. Case and hot swappable units if any;

7. Hard drives and if some are Seagate the firmware for them

 

IMHO it is also advisable to use a dedicated monitor and keyboard during the troubleshooting stage.

 

This way we can have much more educated guess what is going on and propose solutions.

IMHO it is also advisable to use a dedicated monitor and keyboard during the troubleshooting stage.

 

This way we can have much more educated guess what is going on and propose solutions.

Some modern KVM have a tough time when the display is rapidly changing resolutions, as when booting up.  I just do not want any delay to get in your way of seeing the boot messages or being able to respond to them.  Later on, you can put the KVM back into place.

 

(If your KVM is an older mechanical switch this is not the case... but those are rare these days)

 

Joe L.

Ranger, how much and what type of data do you have on your system?  Reason I ask is if your system freezes every time you attempt to copy a file larger than 100 MB or so to it (like mine did), you 1) probably don't have too much on it and 2) are likely going to have to hard reboot several more times before the problem is resolved.

 

What I'm getting at is if you wait until the parity check finishes, then attempt to copy something to it which immediately causes it to freeze, the next time it reboots its going to want to run the parity check again.  You may want to consider copying off any critical data so that you can cancel the repeated parity checks until you get the problem fixed.  I know all too well its hard to troubleshoot if you have to wait hours in between each attempt.

 

I have only 39 movies so far. and all my cd collection which is a couple thousand songs. I have my music on another hard drive so thats not a big deal to lose. I can always re-copy the dvd's if needed but yes, certainly a pain. I guess the best route is to replace the nic. Funny thing is the whole system from the motherboard, power supply, sata cards, case and everything came recommended specifically for an unRAID server on avsforum. Thats makes it more frustrating. (not a knock against AVSforum!)

 

The problem is that many recommended systems are recommended because they are cheap and use budget hardware items.  QC is shoddy on budget items and you may get 10 that work perfectly, and then the next ten don't work half the time.  They are cheap, but they are hit and miss.

that makes sense, but I didnt realize anything I bought was cheap, lol. I will post a list soon of my components.

I have a GA-MA785GT-UD3H mother board.

 

That.

 

I had this same board, found this thread after I was having same issues.  System would essentially go dead with no input allowed via any network communication protocol (telnet, http, etc.) and the keyboard/monitor connected were dead as well (re-connecting did not help).  I tried everything, but was forced every time to simple power cycle the system and endure a parity check.

 

I disabled the onboard NIC and put in a PCI Intel Pro 1000/GT I had - issues appear to be gone.

 

Just wanted to confirm the corrective action for me so anyone finding this doesn't spend a ton of time on this issue.