May 13, 201115 yr 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.
May 13, 201115 yr Have you run an overnight memory test? I think that's where I would start. BTW, just because the memory sticks have been corrupted does not mean they are bad. Could just be that you hve some bad memory and that data is being corrupted as it is written to the drives.
May 13, 201115 yr Author 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....
May 13, 201115 yr I agree with bjp999 - system memory is a likely suspect. Another possibility could be a dodgy power supply, but the RAM would be where I'd start looking.
May 13, 201115 yr I doubt it is a hardware or memory flaw. Where do you have the USB stick mounted? I was having a similar issue with my unraid usb stick for a while. It would be fine up until I tried to write something on it. Then the filesystem would go read only because of errors. Turned out to be the cable I was using. I had a weak or unshielded usb cable inside the machine going to the usb drive also inside. I never realized how much interference is floating around inside there. Once I swapped out the cable with a beefier one all the errors were gone. Also, once you get errors like this make sure you run a scan disk on it to correct them or it will keep going read only on you even once you have corrected the issue.
May 13, 201115 yr Use either of these to mount it inside your case: http://www.amazon.com/StarTech-Motherboard-4-Pin-Header-USBMBADAPT/dp/B000IV6S9S http://www.amazon.com/gp/product/B002GNU2V6/ref=pd_lpo_k2_dp_sr_3?pf_rd_p=486539851&pf_rd_s=lpo-top-stripe-1&pf_rd_t=201&pf_rd_i=B000IV6S9S&pf_rd_m=ATVPDKIKX0DER&pf_rd_r=0FSB4ENE4S9TZZ9ZSAJK
May 13, 201115 yr Author 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.
May 13, 201115 yr 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. What is your complete hardware breakdown? Can we get a full syslog? You should have probably cleared the drives and tested them before putting them into service. For all we know you could be running an NForce4 board (corrupts data), an Atheros NIC (unstable mostly and can cause problems), have marginal hardware/cables/power in the system, etc. It really is a guess check and revise. If you have more than one stick of RAM in the machine then please pull one and use the server for a while with only the one stick, see if the problem happens again. If it does, switch sticks around and test again.
May 13, 201115 yr 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. It will not take a week. You can pre-clear them all at the same time. Or if you have data on them buy another disk and pre-clear while the system is running and then replace one disk at a time, rebuild on the replacement disk, and pre-clear the replaced disk. This can all be done with the array operational. If you can't buy a disk, the procedure is similar but less safe. Stop the array, unassign a drive, start the array, pre-clear the drive and reassign it. Do this one drive at a time. The array will be operational for the entire time except when you briefly stop it.
May 13, 201115 yr I thought he was talking about his flash drive getting corrupted. How does pre-clearing the drives have anything to do with that?
May 13, 201115 yr Author 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...
Archived
This topic is now archived and is closed to further replies.