4.7 Issue - Server Randomly UnPingable and Unresponsive

terminaldawn · February 1, 2015

Hello,

I have been using my unraid server ver 4.7 since early 2011 without issue. Recently (1/28/2015) my server was not pingable, couldn’t bring up the web-console, and couldn’t connect to it in any way. I hooked up a monitor to it and all I seen was a black screen. So I rebooted it and it came back up. So I thought... one hang in the 4 years I have been using this thing no big deal, right…? But ever since the initial incident, the hang is happening about every 24 hours.

I apparently set up some auto-logging to my flash drive back in the day, or maybe the server is set up that way by default? So I believe the attached are the current log files. Its all the log files located in the logs directory anyways. Since the server is unresponsive, after the issue, I am not able to get logs better than this; that I am aware of.

I can’t really decipher much from the logs, but to me it looks like the box is restarting when I am not intending it to, I am not sure what is causing this. Can anyone discern anything from the logs as to what may be happening? Or anything I can do to help troubleshoot this issue?

Thanks in advance for any help that can be provided!

(NOTE will have to post logs seperately. Will not attach to this post for whatever reason, yes they are below 192 KB).

terminaldawn · February 1, 2015

Log file 1 of 3.

sglogs1.zip

terminaldawn · February 1, 2015

log file 2 of 3.

sglogs2.zip

terminaldawn · February 1, 2015

log files 3 of 3.

sglogs3.zip

terminaldawn · February 5, 2015

UPDATE

Issues are still continuing. I had a keyboard and monitor hooked up to my server to hopefully be able to log in locally post freeze, however I just see a black screen and the server is unresponsive to keyboard entry, and server is unpingable. I thought my server was writing logs automatically however its not, so I don't think the logs I posted are helpful at all. I am out of ideas here. Can anyone please throw me a bone and brainstorm what I can try to try to solve this issue please?

JonathanM · February 5, 2015

Typically hard freezes are hardware related. Check for cooling issues with the cpu. Dust, heatsink grease breakdown, fan failure, etc. Also, try running the memtest from the unraid boot menu at the local console for 24 hours or more to see if it locks up or throws memory errors. The PSU can also cause lockups if it's failing.

terminaldawn · February 7, 2015

Thanks for the reply.

I ran memtest for about 40 hours through about 80 passes without a single error. So memory is not the issue here. My server typically will freeze within 24 hours, therefore since memtest ran for 40, I am hypothesizing that whatever is triggering the hardware issue has something to to do with unRaid. Does this also eliminate any other hardware issues?

From another thread it was recommended to trail the logs. Below is the output from that. Not sure when the server froze. Last entry in log is at 3 Am and I didn't go to use the server until like 5PM later that day. Anything look sketchy in the logs? Any other tests I can do to stress the CPU or anything else to diagnose what may be going on?

Thanks

^{stargate login: root}

^Password:

^{Linux 2.6.32.9-unRAID.}

^{root@stargate:~# tail -f /var/log/syslog}

^{Feb 4 18:34:16 stargate emhttp: shcmd (21): mkdir /mnt/user}

^{Feb 4 18:34:16 stargate emhttp: shcmd (22): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions}

^{Feb 4 18:34:17 stargate emhttp: shcmd (23): killall -HUP smbd}

^{Feb 4 18:34:17 stargate emhttp: shcmd (24): /etc/rc.d/rc.nfsd restart | logger}

^{Feb 4 18:36:11 stargate ntpd[1294]: synchronized to 198.100.156.225, stratum 2}

^{Feb 4 18:36:11 stargate ntpd[1294]: time reset -0.313926 s}

^{Feb 4 18:36:36 stargate ntpd[1294]: synchronized to 198.100.156.225, stratum 2}

^{Feb 4 18:50:57 stargate login[2280]: invalid password for `UNKNOWN' on `tty1'}

^{Feb 4 19:24:00 stargate in.telnetd[2341]: connect from 192.168.0.196 (192.168.0 .196)}

^{Feb 4 19:24:06 stargate login[2342]: ROOT LOGIN on `pts/0' from `ENTERPRISE'}

^{Feb 4 19:26:05 stargate shfs: shfs_rmdir: rmdir: /mnt/disk2/Media/TV/Portlandia.S03.Kumail.Tours.Portlandia.720p.BluRay.x264-iNGOT (39) Directory not empty}

^{Feb 4 19:26:05 stargate shfs: shfs_rmdir: rmdir: /mnt/disk2/Media/TV/Portlandia (39) Directory not empty}

^{Feb 4 19:26:05 stargate shfs: shfs_rmdir: rmdir: /mnt/disk2/Media/TV/Portlandia/Season 1 (39) Directory not empty}

^{Feb 4 19:26:18 stargate shfs: shfs_rmdir: rmdir: /mnt/disk2/Media/TV/Portlandia/Season 2 (39) Directory not empty}

^{Feb 4 19:27:23 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/Dominion (39) Directory not empty}

^{Feb 4 19:27:33 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/Dominion/Season 1 (39) Directory not empty}

^{Feb 4 19:28:26 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/The Bridge Us/Season 1 (39) Directory not empty}

^{Feb 4 19:28:43 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/The Flash 2014 (39) Directory not empty}

^{Feb 4 19:28:43 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/The Flash 2014/Season 1 (39) Directory not empty}

^{Feb 4 19:29:01 stargate shfs: shfs_rmdir: rmdir: /mnt/disk2/Media/TV/The Leftovers/Season 1 (39) Directory not empty}

^{Feb 4 19:30:07 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/The Strain (39) Directory not empty}

^{Feb 4 19:30:07 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/The Strain/Season 1 (39) Directory not empty}

^{Feb 4 19:31:05 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/The Bridge Us/Season 2 (39) Directory not empty}

^{Feb 4 19:32:15 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/Movies/Scrooged.1988.720p.BRRip.x264-x0r (39) Directory not empty}

^{Feb 4 20:03:25 stargate ntpd[1294]: no servers reachable}

^{Feb 4 20:16:10 stargate ntpd[1294]: synchronized to 198.100.156.225, stratum 2}

^{Feb 5 02:11:32 stargate kernel: md: sync done. time=27577sec rate=70838K/sec}

^{Feb 5 02:11:32 stargate kernel: md: recovery thread sync completion status: 0}

^{Feb 5 03:11:41 stargate kernel: mdcmd (14): spindown 0}

^{Feb 5 03:11:41 stargate kernel: mdcmd (15): spindown 1}

^{Feb 5 03:11:41 stargate kernel: mdcmd (16): spindown 2}

^{Feb 5 03:11:42 stargate kernel: mdcmd (17): spindown 3}

Squid · February 7, 2015

Did you run that tail via telnet or putty?

You really should run it locally on the server via

tail -f /var/log/syslog >/boot/syslogtail.txt

(it will save the file onto your flashdrive)

running it locally will allow it to capture stuff after the network connection goes down.

I would still lean towards hardware rather than software.

terminaldawn · February 7, 2015

Thanks for the prompt reply.

I ran the tail log i posted below via a telnet session in putty per another thread I found.

I will log in locally and run the command you have recommended.

Since my server is randomly freezing, will I have to pull the flash drive after freeze to get the syslog? Or will I just be able to go to the flash share to pull the data?

Squid · February 8, 2015

Thanks for the prompt reply.

I ran the tail log i posted below via a telnet session in putty per another thread I found.

I will log in locally and run the command you have recommended.

Since my server is randomly freezing, will I have to pull the flash drive after freeze to get the syslog? Or will I just be able to go to the flash share to pull the data?

You can do either. It won't matter the file will still be on the flash drive. Usually you can do it in a putty session, but in the case of a hard crash / lockup, the relevant information may not have been transmitted, depending upon how long the network connection stayed active.

There's no guarantees that anything will show in the syslog, but at least there's a chance, because without any indication we're at a guessing game - just start trying stuff to see what makes it go away.

terminaldawn · February 8, 2015

Thanks again. I expect to be reporting my findings within 24 hours.

terminaldawn · February 8, 2015

Crash happened sooner than I expected. Crash happened at about 01:30 AM (was streaming a movie when the crash occurred, this was the first time it crashed when I was using the server), logs below.

Perhaps the more interesting part of this story is what happened after the crash.

I powered down the server. Pulled the flash drive and copied the log file as pasted below. Put the flash drive back in and booted up and attempted to start the logging again, however I got the error in the screenshot below. Additionally it looks like there was some booting errors. The server came up but it was in an odd state. It was pingable, however shares weren't working. Connected to the web UI and it looked like a generic server. Screenshots again below.

I had to reboot the server again obviously since it wasn't working as I expected. I issued a powerdown command. I attempted to power the server back on but it didnt boot. I rebooted again into bios and MOBO to check boot order etc.. and the MOBO wasnt recognizing my flash drive. So I rebooted again a third time into the bios and this time mobo recognized the flash drive. So I rebooted, and it appeared to boot normally. I started logging again, and my shares are working.

So based on this I am thinking this is perhaps a flash drive issue or maybe MOBO issue...? Thoughts?

_{Feb 7 16:40:30 stargate emhttp: shcmd (20): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root}

_{Feb 7 16:40:30 stargate emhttp: shcmd (21): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root}

_{Feb 7 16:40:30 stargate emhttp: shcmd (22): crontab /var/spool/cron/crontabs/root}

_{Feb 7 16:40:31 stargate emhttp: shcmd (23): killall -HUP smbd}

_{Feb 7 16:40:31 stargate emhttp: shcmd (24): /etc/rc.d/rc.nfsd restart | logger}

_{Feb 7 16:40:34 stargate ntpd[1293]: synchronized to 192.155.90.13, stratum 2}

_{Feb 7 16:40:34 stargate ntpd[1293]: time reset -1.505771 s}

_{Feb 7 16:40:38 stargate apcupsd[1588]: apcupsd FATAL ERROR in linux-usb.c at line 609 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see <}_{http://www.apcupsd.com/support.html>.}

_{Feb 7 16:40:38 stargate apcupsd[1588]: apcupsd error shutdown completed}

_{Feb 7 16:40:52 stargate login[2275]: ROOT LOGIN on `tty1'}

_{Feb 7 16:44:53 stargate ntpd[1293]: synchronized to 192.155.90.13, stratum 2}

_{Feb 7 22:07:36 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/Black Sails/Season 2/_UNPACK_Black.Sails.S02E03.720p.HDTV.x264-KILLERS (39) Directory not empty}

_{Feb 7 22:07:36 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/Black Sails/Season 2/Black.Sails.S02E03.720p.HDTV.x264-KILLERS (39) Directory not empty}

_{Feb 7 22:07:36 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/Black Sails/Season 2/Black.Sails.S02E02.720p.HDTV.x264-IMMERSE (39) Directory not empty}

_{Feb 7 22:07:36 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/Black Sails/Season 2 (39) Directory not empty}

_{Feb 7 23:58:48 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/Justified/Season 6/_UNPACK_Justified.S06E03.720p.WEB-DL.DD5.1.H.264 (39) Directory not empty}

_{Feb 7 23:58:48 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/Justified/Season 6/Justified.S06E03.720p.WEB-DL.DD5.1.H.264 (39) Directory not empty}

_{Feb 7 23:58:48 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/Justified/Season 6 (39) Directory not empty}

_{Feb 8 00:00:40 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/New Girl/Season 4/_UNPACK_New.Girl.S04E14.Swuit.1080p.WEB-DL.DD5.1.H.264-SA89 (39) Directory not empty}

_{Feb 8 00:00:40 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/New Girl/Season 4/New.Girl.S04E14.Swuit.1080p.WEB-DL.DD5.1.H.264-SA89 (39) Directory not empty}

_{Feb 8 00:00:41 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/New Girl/Season 4 (39) Directory not empty}

_{Feb 8 00:04:23 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/Suits/Season 4/_UNPACK_Suits.S04E12.720p.WEB-DL.DD5.1.H.264-NTb (39) Directory not empty}

_{Feb 8 00:04:23 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/Suits/Season 4/Suits.S04E12.720p.WEB-DL.DD5.1.H.264-NTb (39) Directory not empty}

_{Feb 8 00:04:23 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/Suits/Season 4 (39) Directory not empty}

_{Feb 8 00:07:01 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/American Idol/Season 14/_UNPACK_American.Idol.S14E10.720p.HDTV.x264-2HD (39) Directory not empty}

_{Feb 8 00:07:01 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/American Idol/Season 14/American.Idol.S14E10.720p.HDTV.x264-2HD (39) Directory not empty}

_{Feb 8 00:07:01 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/American Idol/Season 14 (39) Directory not empty}

_{Feb 8 00:10:04 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/How to Get Away With Murder/Season 1/_UNPACK_How.to.Get.Away.With.Murder.S01E11.720p.WEB-DL.DD5.1.H.264-BS (39) Directory not empty}

_{Feb 8 00:10:04 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/How to Get Away With Murder/Season 1/How.to.Get.Away.With.Murder.S01E11.720p.WEB-DL.DD5.1.H.264-BS (39) Directory not empty}

_{Feb 8 00:10:04 stargate shfs: shfs_rmdir: rmdir: /mnt/disk3/Media/TV/How to Get Away With Murder/Season 1 (39) Directory not empty}

_{Feb 8 00:12:33 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/American Idol/Season 14/_UNPACK_American.Idol.S14E09.720p.HDTV.x264-2HD (39) Directory not empty}

_{Feb 8 00:12:34 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/American Idol/Season 14/American.Idol.S14E09.720p.HDTV.x264-2HD (39) Directory not empty}

_{Feb 8 00:12:34 stargate shfs: shfs_rmdir: rmdir: /mnt/disk1/Media/TV/American Idol/Season 14 (39) Directory not empty}

_{Feb 8 00:16:16 stargate kernel: md: sync done. time=27348sec rate=71431K/sec}

_{Feb 8 00:16:16 stargate kernel: md: recovery thread sync completion status: 0}

dgaschk · February 8, 2015

Run checkdisk on the Flash in a PC or Mac.

terminaldawn · February 8, 2015

Run checkdisk on the Flash in a PC or Mac.

I should have mentioned that I have done that already. No errors found.

Squid · February 8, 2015

Well if that log was the one that was being saved continually to the flash drive, then there is nothing in it suggesting the reasons for the crash.

But, it looks like just prior to the crash, it finished the parity check (from the unclean shutdown).

Try cancelling the parity check (you can always run it later) and see what happens. The crash could be power supply related (too weak) - although I would think that it would have happened during the check, not after.

The crashes won't be caused by a bad flash drive. Its going to be either p/s or mobo - but, you've already run memtest for 40 hours, so the implication is that the mobo/cpu *should* be good

terminaldawn · February 8, 2015

Could a bad psu cause the flash drive to not be recognizable by the motherboard? Just want to make sure the point of the flash drive not being seen by motherboard is not missed. It seems as though something is flaky there. Also the boot up errors that have occurred in my photo I took, what could that indicate?

Squid · February 8, 2015

Bad supplies can cause just about anything. My initial guess was that the flash drive was corrupted, but 3 reboots and the problem disappeared, which implies no corruption.

It could be a bad stick, but that wouldn't explain the random crashing (after booting, the stick isn't really accessed at all - you can pull the thing and unraid will still chug along - will throw alot of "Bread" errors into the log, but nothing else will happen) (After you posted that picture, I originally thought that my command to write the syslog corrupted the stick by being in the middle of a write when it shut down)

The supply right now is the easiest thing to diagnose (by simply lowering the draw on the supply by cancelling the parity check) - Its not going to be a given, but its the first thing to check with issues like this.

After that, I would go with a completely stock unRaid.

The next item on my list would be a popped capacitor on the mobo. Hard to check if you don't know what you're looking for, and easiest to fix by replacing the mobo.

terminaldawn · February 8, 2015

If you are confident that pulling the flash after boot should not cause the server to lock, then for sure it has to be PSU or MOBO at fault here. And most likely the PSU based on some new findings I have. Something I didn't notice before; the PSU is making a high pitched noise when the server is turned off. When the PC starts the PSU no longer makes that noise. I didn't notice it until just now since its sitting next to a couple of other servers and the fan noise from the other servers masks the noise, and like I said, its only present when the system is powered off. I am going to replace the PSU and go from there.

Squid · February 8, 2015

If you are confident that pulling the flash after boot should not cause the server to lock, then for sure it has to be PSU or MOBO at fault here. And most likely the PSU based on some new findings I have. Something I didn't notice before; the PSU is making a high pitched noise when the server is turned off. When the PC starts the PSU no longer makes that noise. I didn't notice it until just now since its sitting next to a couple of other servers and the fan noise from the other servers masks the noise, and like I said, its only present when the system is powered off. I am going to replace the PSU and go from there.

I would leave it unplugged until the supply is replaced. While it may be just a transformer squeal, there may be other components that could be at risk of going down at any moment, and the last thing you need is high voltages to be going to the drives or mobo.

terminaldawn · February 9, 2015

Noted.

After issuing the powerdown command I am getting no such file or directory errors in the log. Not sure if this is relevant or not to my issue, so I posted to be safe.

Thanks again for all your help!

_{Linux 2.6.32.9-unRAID.}

_{root@stargate:~# powerdown}

_{Capturing information to syslog. Please wait...}

_{version[2370]: Linux version 2.6.32.9-unRAID (root@Develop) (gcc version 4.2.3) #8 SMP Wed Nov 24 01:15:59 MST 2010}

_{ls: cannot access /dev/hd[a-z]: No such file or directory}

_{status[2427]: State: STARTED}

_{status[2427]: Parity CHECK in progress, 93.0% complete, est. finish in 38.5 minu tes.}

_{status[2427]: D# Model / Serial Status Device}

_{status[2427]: 0 WDC WD20EARS-00 / WD-WMAZA3309401 DISK_OK sda}

_{status[2427]: 1 WDC WD20EARS-00 / WD-WMAZA2723821 DISK_OK sdb}

_{status[2427]: 2 WDC WD20EARS-00 / WD-WCAZA0826832 DISK_OK sdd}

_{status[2427]: 3 WDC WD20EARS-22 / WD-WCAZA3895793 DISK_OK sdc}

_{status[2427]: SMART overall health assessment}

_{ls: cannot access /dev/hd[a-z]: No such file or directory}

_{status[2427]: /dev/sda: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-g nu] (local build)}

_{status[2427]: SMART overall-health self-assessment test result: PASSED}

_{status[2427]: /dev/sdb: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-g nu] (local build)}

_{status[2427]: SMART overall-health self-assessment test result: PASSED}

_{status[2427]: /dev/sdc: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-g nu] (local build)}

_{status[2427]: SMART overall-health self-assessment test result: PASSED}

_{status[2427]: /dev/sdd: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-g nu] (local build)}

_{status[2427]: SMART overall-health self-assessment test result: PASSED}

_{status[2427]: /dev/sde: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-g nu] (local build)}

_{status[2427]: /dev/sde: Unknown USB bridge [0x13fe:0x3d23 (0x100)]}

_{status[2427]: Smartctl: please specify device type with the -d option.}

_{status[2427]: Use smartctl -h to get a usage summary}

_{status[2427]: No active PIDS on the array}

_{Removing old syslog: /boot/logs/syslog-20150128-200711.txt}

_{Saving current syslog: /boot/logs/syslog-20150209-004349.txt}

_{-rwxrwxrwx 1 root root 174831 Feb 9 00:43 /boot/logs/syslog-20150209-004349.txt}

_{zip not installed. Consider installing to automatically zip current syslog}

_{Broadcast message from root (pts/0) (Mon Feb 9 00:43:49 2015):}

_{The system is going down for system halt NOW!}

_{root@stargate:~#}

Squid · February 9, 2015

Noted.

After issuing the powerdown command I am getting no such file or directory errors in the log. Not sure if this is relevant or not to my issue, so I posted to be safe.

Thanks again for all your help!

ls: cannot access /dev/hd[a-z]: No such file or directory
ls: cannot access /dev/hd[a-z]: No such file or directory

Those happen on my machine. I think it tries to see if hda through hdz still exists. You don't have any drives labelled hda etc. I wouldn't worry about it. Normal

terminaldawn · February 12, 2015

ahhhhhhhhhhhhhhh.. ok.. i am ready to toss this thing. patience running out.

I replaced the psu today.

Tried booting up but wouldn't recognize my flash drive at all. So restored reccomended defaults on Mobo.

Flash Drive was then recognized.

Booted and Unraid freezes during boot - see first pic.

Booted again. Unraid freezes during boot - see second pic (notice the pixelation on screen?)

Booted third time and Unraid Freezes on Boot.

Somewhere in thee I had a CMOS error and had to restore default settings.

Sooo..... Bad Mobo? Bad Flash Drive? Obviously replacing the mobo is like the worst. and i have no freaking clue where to begin to make sure unraid will work with new mobo, etc.... I mean it almost makes sense to try a different flash drive right? Or another thought, is there another version of linux that i can try to run from a different usb stick to see if that crashes?

Squid · February 12, 2015

Bank interleave error could either be memory or the cmos needs to be cleared. (usually via a jumper - instructions in your manual)

Pixelization on screen is almost always memory.

Did you leave the old p/s unplugged until the replacement was installed?

If it was left unplugged, then try reseating the dimms. Maybe you knocked them installing the new p/s. Run memtest for a day.

After that, replace the sticks followed by the mobo.

(With pixelization appearing on a text only screen, there's zero point in testing with another version of linux. 100% guarantee that its a hardware issue - whether simple like dimm loose, or bad ram or mobo.)

Is it a correct assumption that your cpu has integrated graphics?

BTW, what P/S did you buy?

terminaldawn · February 12, 2015

Thanks again for your help.

Cleared CMOS

Re-seated DIMMS

running memtest.

side note.. think this mobo is toast. After cmos clear, it took several reboots for it to post... but finally got memtest running... really.. i wish it was more binary with this mobo, or whatever the problem. There is no consistency to this issue.

Yes, integrated graphics.

here are my full specs.

CASE: COOLER MASTER RC-692-KKN2 CM690 II Advanced Black Steel ATX Mid Tower Computer Case

MB: BIOSTAR A760G M2+ AM2+/AM2 AMD 760G Micro ATX AMD Motherboard

CPU: AMD Sempron 140 Sargas 2.7GHz Socket AM3 45W Single-Core Processor SDX140HBGQBOX

RAM: Kingston 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model KVR800D2N6K2/2G

PSU: Corsair CX Series 430 Watt ATX/EPS Modular 80 PLUS Bronze ATX12V/EPS12V 384 Power Supply CX430M

Pairity HDD: Western Digital Caviar Green WD20EARS 2TB SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

Flash: Verbatim TUFF-'N'-TINY 4GB Flash Drive (USB2.0 Portable) Model 96815

terminaldawn · February 12, 2015

it seems like replacing mobo is pretty painless according to this link: http://lime-technology.com/wiki/index.php/Replacing_the_Motherboard_in_Your_unRAID_Server

http://www.lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Motherboard

However the hardware compatibility page is filled with older motherboards. Considering I have an AM3 CPU what are my options besides buying some old stock on ebay?

Also I am assuming 4.7 will be less compatible than a new version.

4.7 Issue - Server Randomly UnPingable and Unresponsive

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation