rockytt

thank you for sending these over - didn't really apply in my case as I went through them - no recent update, and the fact that DLNA is working but I can't access the shares through Windows Explorer has me stumped. If it were only the Webgui I would keep pounding away at those threads, although my situation seems a bit unique and specific - Also - the fact that those 2 items just quitting, while DLNA keeps humming along has me perplexed as well

Very strange - this just popped yesterday and now I can't: 1) Access WebGui using IP address (verified address using 'ifconfig eth0') 2) Can't browse to any of the disks/shares using windows explorer BUT I run a DLNA plugin to serve up movies to the various tvs in the house and it works fine. I can watch movies/listen to music all day long using DLNA - so the unraid server is up and running. I have rebooted a few times with no love. For a brief period of time last night I could see the WebGui on my Android phone browser using the IP Address - but that stopped working also. Does this make any sense at all to anyone? Seems like everytime I lose the WebGui it comes down to that darn CR2032 motherboard battery - but have replaced it and still no change. syslog.txt

Geez - that was a stupid fix - changed the cr2032 battery on the motherboard - fired right up! Thanks again for your help with this - appreciate the willingness to troubleshoot -

ahh - got it - actually not sure - been running this server for a long time, although haven't really touched it for years. (other than a MB replacement) Probably found it on the forum here and been using it ever since. Very much appreciate the help - was a tcl developer for a long time, but never got into Linux -

that's from the syslog

Anything to do with: Oct 8 12:05:33 Tower logger: installing plugin: webGui-latest Oct 8 12:05:33 Tower logger: Oct 8 12:05:33 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Document is empty in /usr/local/sbin/installplg on line 13 Oct 8 12:05:33 Tower logger: Oct 8 12:05:33 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Oct 8 12:05:33 Tower logger: Oct 8 12:05:33 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Oct 8 12:05:33 Tower logger: Oct 8 12:05:33 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Start tag expected, '<' not found in /usr/local/sbin/installplg on line 13 Oct 8 12:05:33 Tower logger: Oct 8 12:05:33 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Oct 8 12:05:33 Tower logger: Oct 8 12:05:33 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Oct 8 12:05:33 Tower logger: xml parse error

sorry not a Linux guy - but essentially, root root 0 2014-10-18 10:09 repeated in front of the commands below and the following ./ ../ .bash_profile mdcmd* pwerdown -> /usr/local/sbin/powerdown* samba -> /etc/rc.d/rc.samba*

Thanks for the help Frank - unfortunately I get a "command not found" when I type that in...

A little crazy - had to reboot today b/c of a case fan that was screaming to wake the dead- Watched everything boot up nice as could be, saw the login prompt and then tried to hit the webgui at Tower - but got the old "tower’s server IP address could not be found." -Ran ifconfig and got the IP address, tried to hit that directly - no love either, although I have a green light on the router. Next steps to try? syslog

Sold! (And thanks for the recommendation Here's to another 10 happy years of storage!

Thanks for the responses - much appreciated! Hah! You got me! Cost reasons mostly - Funds are a little too tight to justify the extra $$ right now. (Although if someone has a recommendation for a sub $150 mb with 8 ports, I'm all ears. Everything I see in the thread is in the $250-$400 range)

Been running my system for almost 10 years now and my (old at the time) mb needs to be replaced. Not looking to spend a ton, but would love to have something with 8+ SATA connectors so I can ditch one of my controller cards. Currently running 12 drives (11+parity) and really won't be moving beyond that. Been looking at the ASUS A8N-SLI Premium which is listed on the compatible hardware page, and shows 8 sata ports. My (probably basic) questions is - since 4 (of the are showing as "SATA Raid", does this mean I can use all 8 w/o issue or only 4? Update: Been reading the manual and it talks about disabling RAID on those 4 SATA connectors via the BIOS setup. If I do so, do they then default to "regular" SATA connections? (Which means I can use all 8 for my unRaid box)

Yeah - I figured as much - I think the core of this system is over 8 years old now (and some if it was certainly not cutting edge when I put it together!) so I guess it should be expected. Probably be a couple of weeks before I can rebuild it - but one last favor would be for someone to take a look at the last bit of this latest syslog I just uploaded. This time I started the array w/o mounting the disks and the parity check hasn't yet frozen (knock on wood!) - anyone see anything suspicious in there? Thanks again for all the help, and I'll probably be posting again (new thread) when I get some new bits. syslog.txt

Yup - I've moved the usb stick around and swapped memory sticks (actual sticks as well as slots) to try and get rid of this "hanging" problem that has really been going on for a few months now. (The errors during boot are new) The problem seems to resolve itself and I think "aha!" and then it crops up again. In an attempt to trace the problem recently, it appeared that there were problems writing to one of the drives. I was able to replace it and successfully restore the data. ("Aha!") Unfortunately, when I went to check parity the array froze again (which brings us to today)

nope - running one now though (and I did replace the memory a couple months ago on the off-chance it was causing issues) Still really strange about those errors during booting though I'll report back tonight/tomorrow after the memtest - can't hurt to run it...

much craziness- different usb stick and still the same errors...(even formatted on a different pc to make sure my laptop wasn't acting up) unraid still boots btw, and if I cancel the parity check immediately after starting the array it works "fine" (can read all files/no red balls/etc) - although it crashes when I try and check parity later- Demon-possession perhaps? (I have attached the latest syslog - this after starting the array, but cancelling the parity check. Couldn't grab a later one after attempting a parity check - so this is as much as we're going to get) syslog.txt

yup - did google my error message and it didn't return much AFAIK it was a full scan - no option for anything (full or quick) - although I did a full format (not the quick one)

OK - two issues now... 1) Uploaded a new syslog - this was the very latest one I could grab which was about a second before the box froze. Currently it's freezing up within a second or two of a parity check. 2) In the off-chance that perhaps an update to the version might help, I attempted a (most likely ill-advised) change from 5.05 to 5.06. Did it as a fresh install - reformatted the flash drive/copied the files/brought over my saved "config" folder/made the drive bootable. During the boot process I get a whole string of "edd: error 0100 reading sector xxxxxxxxx" lines before the machine boots. (I have run the "scan/fix" on the drive and it always returns 0 errors - in spite of this, does it sound like the flash drive has died?) All the help is much appreciated- syslog.txt

Thanks for the reply - that's the log file (#2) that I mentioned in my previous post though

Hi -thanks for the reply, but I actually can't do that - once it crashes all contact is lost with the server- The two log files I attached are the only ones I can get - one from the flash drive (after a crash) and one from the unRaid main while it's still up

Running 5.0.5 with 10+1(parity) disks - Have had the beast for quite awhile now, and periodically it would lock up - no response to anything/no access from the network. The only way forward has been an unclean shutdown (no other option) - The last time I had to restart (a week ago), it wouldn't get through the parity check (sometimes 5%, sometimes 75%) before freezing again. Currently, I can't even start it in maintenance mode w/o it locking up. I'm hopeful that something in the last log file I could grab will be helpful and someone could point to something I might be able to check. syslog.txt is the last one I was able to grab from the web interface, while syslog2.txt was pulled from the flash drive after the last unsuccessful attempt at starting the array. Thanks!! syslog.txt syslog2.txt

Cautiously optimistic update- ran memtest last night for a few hours - didn't return any errors, but really slowed down to a crawl on a few of the tests. Since I had a couple of spare sticks lying around in a dead machine, I swapped them in and am now up to 35% on the parity check. (Before, the machine would lock up before even hitting 1%) I'm almost ready to call this one solved - thanks again for your help!

Strange - that's what it says in the upper right corner of my console when it's running- No issues with chkdsk on flash drive that windows could find running memtest as we speak

I do appreciate the help Here's one I was able to grab from earlier in the day - hope something stands out! towerLog.txt

sorry - 5.0.5 system is locked up - can't get a syslog