fuzzewuzze

You know Jazzy, I think you may be onto something that i had been thinking about myself. I havent copied very large amounts of data between, maybe a gig or two but they all went fine. This hard reboot is always related to when i am using both Sickbeard and Sabnzbd and are downloading at full speed. Im assuming the constant read/writing/downloading/extracting may be at play. Ill see if i can throw an adapter in and if it makes it go away... Last night i tried plugging in just one drive at a time into different SATA ports to see if maybe it was just one of the SATA ports going out..but it still happened although less frequently...which maybe another good sign you are right...

Lol i just get some error when it starts about swapon: .unraid_swapfile: Invalid argument or something like that

Interesting.... When both are running my free mem drops from like 1500 to 40 and hovers in that range....cached shows 1590ish... I wonder if this is related to my issue...how do i go about creating a swap, or fixing this issue without getting more RAM?

I dont see why 2 Gig wouldnt be enough, thats a lot of space for an app that barely takes any. Two gig can run all of Windows, a ton of apps and sabnzbd/sickbeard. So i dont think thats the issue Im trying each of my drives one at a time, and stumbled upon a new error. While running sabnzbd + sickbeard all of a sudden both reported Killed and when i try to restart them i get SABnzbd.py: Transport endpoint is not connected Not only that but the main unRaid web service is down and i cant connect, the system is still up and running fine and can be pinged...its like everything came crashing to a halt....

Swap file? Not sure what you even mean, I havent heard of needing to setup a swap file?

Sadly thats true, im going to try a few more things tonight before i give up and RMA..hate to do it because NewEgg's RMA process sucks and im not gonna get a new board for over a week.

I did buy a UPS as ive needed one, but it didnt make a difference. So far ive replaced everything except the motherboard and drives, the drives check out according to their SMART reports and Preclear...with that information is that enough to say with certainty its not my drives and has to be the Motherboard?

Ok thanks, i do need some further clarification though. I have 3 drives sda(parity) sdb(data) sdc(data) Looking in /dev i only have /dev/md1 and /dev/md2...i assume that those are my two data drives and it just doesnt make a /dev/md0 because thats my parity drive with no filesystem on it? Just want to make sure i dont run it on my parity drive and that im not missing a /dev/md3 for example.

Hmmm when i try to run reiserfsck on any of these drives it says reiserfs_open: the resiserfs superblock can not be found on /dev/sda failed to open the filesystem If the partition table has not been changed, and the partition is valid, and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb I started running it with rebuild-sb, but it asks a bunch of questions i dont know the answers too about which reiserfs and block size, etc...

More info, tried swapping the DDR 3 from my HTPC out into the unRaid box, still hard rebooting... Kinda disheartened by this board honestly, any suggestions for a replacement for AM3 DDR3? I got this because it comes with 6 SATA ports onboard and seemed to get good reviews on this site, maybe just bad luck and try a new one?

Well im running out of ideas here...swapped PSU with the 430W and it still happens. Since i have tested all RAM, HD's, and now PSU the only logical thing left is that the Motherboard is faulty... Im gonna try and flash it to the latest FW and double check all my BIOS settings and try one more time then RMA it i guess unless anybody has any other ideas...

Well thankfully i ordered a Corsair Builder 430 for my HTPC as well, so ill pull that out of that box and put it into my unRaid box and see what happens.

Yea Sab and Sickbeard work pretty effortlessly...i will just say from that tutorial to not use port 8080 for Sabnzbd which is its default. Because unMenu also uses 8080 and you will likely want to use that sometimes.

Already way ahead of you Already ran Memtest overnight and it worked fine for 14x passes Its only 1 stick of RAM, so theres nothing to remove ... I dont have the output for the log, but rest assured it had nothing to do with this rebooting. It was just info from updating sickbeard and a few rmdir commands failing because the folder didnt exist. I wish there was an easy way to test Power supplies and motherboards I could just return both i suppose and hope that fixes the issue... Although i would hate to get new PS and Mobo and still have this issue lol...

So it finally rebooted, nothing showing in the console ..the last thing in it was from like 30 minutes earlier from sickbeard...

No right now its literally just plugged straight into the wall as i have it in my office from setting it up. Go figure though after connecting with putty its been an hour and no reboot...

Duh, man im an idiot of course ...ill do that now.

Oh and im 99.9% sure its not heat, the system is actually quite cold. HD's are actually cold to the touch and show around 29C in unRaid. Is there anything i can do to test my power supply as the fault?

But the system is hard rebooting, unless i sit there and stare at it for two hours at the last line hoping to catch one thing being written before the machine reboots the next millisecond how does tail help me? Or am i missing something about how the command works? Its not gracefully shutting down, one second my monitor is on..the next its off and my BIOS is booting. Thanks in advance for all the help, im leaning towards a Power supply issue, but i dont know how i can verify that...

Ill give that a try, but its so random if i have to be here to catch it i dont think i can. Two drives were Precleared at the same time, one after. Also LOL it just rebooted again but i couldnt see anything happen in the tail of the log... Right now data is only being written to one of the drives, i will try changing my user share to write to the other drive and see if it still happens.

So i had a thread last week about my usb stick becoming corrupt, sadly i am still having system reboots so im here to try and get some help and figure out whats causing it. Basically the system will run forever if i just leave it and do nothing and had no issues during preclear with it rebooting, but as soon as i start an application like Sabnzbd+Sickbeard that is writing to the drives through a user share within an hour or two the system just hard reboots with no errors. So without further ado here is everything i know Unraid 4.7 2GB Sandisk Cruzer ASRock 880GM-LE AM3 AMD 880G Micro ATX AMD Motherboard AMD Sempron 140 2GBx1 Kingston ValuRam 1333Mhz Corsair Builder 500W PSU 3x2TB WD Caviar Green EARS drives in AHCI Things I Know PreCleared all 3 Drives with no issues Ran Memtest overnight, ran 14 passes with no errors. Only happens when things are actively being written... Attached is my Syslog, although im not sure how much it will help. It wont have captured the crash itself but here it is... Running Sabnzbd+Sickbeard off a user share on my drives to keep it from read/writing to my USB stick all the time. Changed all paths within sabnzbd/sickbeard to run off the drive not USB Any help on where to go from here would be GREATLY appreciated, if im going to have to return something its in the next week or two... syslog.txt

I think my USB disk getting corrupted is likely a side effect of hard reboots the system is experiencing is why Xamindar, its not getting unmounted properly. As for my system it is actually based on one of the popular builds here ASRock 880GM-LE AM3 AMD 880G Micro ATX AMD Motherboard AMD Sempron 140 2GBx1 DDR3 1333 Kingston ValueRam 2TBx3 WD Green EAR's drives Corsair Builder 500 Power Supply Thats pretty much everything in the system, no SATA cards, no special cable setups. 3 drives plugged into the first 3 SATA ports on the motherboard. They are all 3 brand new drives, theres been SOME data put on them but honestly i dont care about it i can copy it on there again i can just wipe them all clean. I just wanna figure out whats causing these resets ASAP so i can Return/RMA if i need too ... Ill post my Syslog when i get home...

Yea ran Memtest last night....20 passes 0 errors. I just have my USB stick in one of the slots on the motherboard. Im out of ideas what could be causing it, the system does still reboot sometimes out of the blue...i think that could be corrupting things. But it only seems to happen when im actively using the system, since its not memory i wonder if the drives themselves could be causing it? I never did do a complete PreClear on these drives because it would take me like a week to clear all 3 drives and i'd like to use the system before that How can i go about setting up the system to record the system log forever somewhere until it reboots? Looking at the syslog tells me nothing because it gets cleared when it reboots.

I ran 3 passes of Memtest and there was no issues, i will try running it overnight. I formatted one of the drives and then copied over the contents of the other and all booted up well, but theres still issues with the system rebooting and i think that could be whats causing it like you said....

So this morning i wake up to find my system had rebooted itself again(was having an issue with this while setting it up), so i went to mess with Sickbeard/Sabnzbd and i cant do anything, the entire boot drive is set to read only as are all of my SATA drives. After much searching i figured out how to read the Syslog, of course i cant get it off the system because i cant copy it to my read only boot stick but found these errors FAT: Filesystem error (dev sdd1) Clusters badly computed (200 != 186) File System has been set read-only! It spams about 4 of these at the very end of my syslog before i can see ROOT logging in. That was with a brand new SuperMicro Cruzer 2gb from Best Buy...so i said whatever ill return it and i threw in an old 1Gb stick i had laying around. And what do you know here 8 hours later it is doing the exact same thing, only with different clusters computing badly. What in the hell is going on? As i understood it the Sandisk Cruzer drives were supposed to be an good stick to use for unRaid... Is there something i can do to fix these drives short of plugging them into my Windows box and reformatting them? I should mention this is a brand new system, i just set it up yesterday and havent even got to put anything on it yet because flash drives keep dying.