For some reason after a while, I cannot access the web interface, even though everything else (samba, etc) is still up and running. I thought it was an issue with memory, so I upgraded from 2GB of memory to 4GB, it didn't seem to help, though. Rebooting seems to temporarily fix the issue.

 

I'm running unRAID Server 5.0-beta14, attached is my syslog. Thanks guys!

 

root@nas:~# free
            total       used       free     shared    buffers     cached
Mem:       3888536    3211896     676640          0     125884    2918892
-/+ buffers/cache:     167120    3721416
Swap:            0          0          0

syslog.txt

How are you rebooting?

telnetting in, shutting down the raid, then rebooting.

What do you do exactly?

 

Three safe ways to power down:

The unRAID webGUI

The powerdown script (available via unMenu). Use powerdown -r to restart.

http://lime-technology.com/wiki/index.php?title=Console#To_cleanly_Stop_the_array_from_the_command_line

 

There are no other safe ways to power down!

The command line method, since I don't have access to the web interface.

These lines suggest an unclean shutdown:

Nov 28 20:26:27 nas kernel: REISERFS (device md2): replayed 8 transactions in 1 seconds
Nov 28 20:26:27 nas kernel: REISERFS (device md2): Using r5 hash to sort names
Nov 28 20:26:28 nas kernel: REISERFS (device md1): replayed 7 transactions in 2 seconds
Nov 28 20:26:28 nas kernel: REISERFS (device md3): replayed 8 transactions in 2 seconds
Nov 28 20:26:28 nas kernel: REISERFS (device md1): Using r5 hash to sort names
Nov 28 20:26:29 nas kernel: REISERFS (device md3): Using r5 hash to sort names

Nov 28 20:26:30 nas kernel: REISERFS (device md4): replayed 10 transactions in 4 seconds
Nov 28 20:26:30 nas kernel: REISERFS (device md4): Using r5 hash to sort names

Nov 28 20:29:03 nas kernel: REISERFS (device md5): replayed 170 transactions in 157 seconds

 

This should restart the GUI:

killall emhttp
nohup /usr/local/sbin/emhttp &

 

Oh, thanks. That may have been from a power outage the other day, but I assure you when I can, I do shut everything down safely. 

And thank you, that does bring the GUI back online. I wonder why it's crashing, though.

It appears to have gotten worse, now I can never access the web interface, so my unraid machine is useless right now, as I cannot start the array.

Attaching most recent syslog (after a reboot)

 

EDIT: even if I could just get the array started for 5 minutes to retrieve a much needed backup, that would be great.

syslog.txt

I've tried starting the array manually with: /root/mdcmd start

 

However, the shares still do not show up, even if I restart samba.

 

The only functional web UI is unmenu: http://i.imgur.com/rJkCR.png

 

Any suggestions? I'm very close to tearing the server apart and mounting the disks on another machine to salvage my files.

At this point I've uninstalled all add-ons (unmenu and custom scripts), downgraded to beta13, and I'm at the end of my rope. I'll try live booting ubuntu to get my files.

I've managed to restore the file I've been trying to get for the last 12 hours.. finally I can sleep!

 

But it would be nice to know why unraid just decides to crap out like this. Any ideas?

 

EDIT: I'm running into the same issues as this guy http://lime-technology.com/forum/index.php?topic=16302.0

 

There is no solution, so I guess that's it for unraid for me, which is a shame. It's just far too unreliable in my experience. Thanks to those who tried to help me, though.

To put it bluntly, this is either a beta unRAID problem or you have a hardware issue. Either way, it's has nothing to do with unRAID being unstable.

 

Did you try 4.7 or an earlier beta like 5.0b6?

 

Did you test your memory?

 

Do you have a quality power supply?

 

Did you check that your hardware was compatible? Certain Atheros and Realtek LAN chipsets can cause lots of connection issues.

 

Peter

 

I think honestly without getting excited we should slow down just a bit.

We don't know your hardware configuration like lionelhutz mentioned.

It could be a controller, it could be a network device it could be anything at this point until we know what you have.

 

I have my complete build in my signature simply so if I ask for help and be a bit lazier than the average person.

Hey guys, I'd just to to apologize for being impatient. I'm a little embarrassed by what I wrote in my last couple of posts.. but in my defense I was sleep deprived and I just couldn't get things to work. I shouldn't have called unraid unreliable when it worked flawlessly for over a year.

 

I checked my memory and couldn't find any issues with it. My hardware hasn't changed at all. The most recent change was doubling the memory from 2gb to 4gb, but things seemed to work fine after that upgrade.

 

This is my hardware:

 

Corsair Professional HX650W 650W power supply

Sandisk 2GB Cruzer Micro U3 Smart USB 2.0 Flash Drive

Supermicro Black 3X5.25 to 5X3.5IN SATA Drive Bay  x3

AMD Sempron 140 Processor 2.7GHZ Socket AM3 1MB L2 Cache 45W

ASUS M4A78L-M mATX motherboard

 

All drives are WD 2TB EARS

 

I've actually figured out the problem and it's really my fault. I updated the motherboard BIOS to correct an issue with the flash drive losing precedence as the boot drive. It corrected the issue but must have changes some identifiers or something, which likely made unraid confused. So I installed unraid from scratch, re-assigned the drives in the same order as before from my screenshot, and now all is well again!

 

So yeah, sorry for being an impatient ass.