Okay so, where to start, I've been trying to set up a centralised database for xbmc using unraid but been failing miserably, this led to me re-booting a lot of times today and got to this current stage where i cannot access my server at all on boot, I've hooked it up to my TV and can get into the command line on the server but only whilst booting can I access it via http://tower/main.htm but after a minute (when the command line becomes available on the server) I am unable to access this, unmenu or anything else. I'll admit I'm a noob and don't really have a clue what I'm doing, which is why I'm here, I've attached the latest log I can find and I'm certain the same problem existed on that time. Can I get this back to booting so I can access it again from my media pc browser or am I best starting from scratch again and if i were to start from scratch (which i feel would be the easiest option by far) would i lose the data on the drives currently in my array (there is no parity disk yet) anyway we'll try start with a fix and move onto that as a worst case scenario I'm using version 4.7 (I think)

 

Thanks in advance

syslog-20110706-230004.zip

okay before giving up for the night I powered on for what must have been the 20th time since 10pm when it began to fail, and its working!!! don't know how or why but hell... anyway I'm going to have to powerdown to move it across the room to its normal home rather then infront of the TV, Standby

I regret turning it off, back to not working again.

I see two obvious issues in the syslog.  The first may not be too serious, but it is still something to consider.  There appears to be something screwy going on with your router.  Take a look at this:

 

Jul  6 22:51:42 Tower dhcpcd[1361]: broadcasting DHCP_DISCOVER 
Jul  6 22:51:42 Tower dhcpcd[1361]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.0.255 
Jul  6 22:51:42 Tower dhcpcd[1361]: dhcpIPaddrLeaseTime=3600 in DHCP server response. 
Jul  6 22:51:42 Tower dhcpcd[1361]: dhcpT1value is missing in DHCP server response. Assuming 1800 sec 
Jul  6 22:51:42 Tower dhcpcd[1361]: dhcpT2value is missing in DHCP server response. Assuming 3150 sec 
Jul  6 22:51:42 Tower dhcpcd[1361]: DHCP_OFFER received from  (192.168.0.1) 
Jul  6 22:51:42 Tower dhcpcd[1361]: broadcasting DHCP_REQUEST for 192.168.0.16 
Jul  6 22:51:43 Tower dhcpcd[1361]: dhcpIPaddrLeaseTime=3600 in DHCP server response. 
Jul  6 22:51:43 Tower dhcpcd[1361]: dhcpT1value is missing in DHCP server response. Assuming 1800 sec 
Jul  6 22:51:43 Tower dhcpcd[1361]: dhcpT2value is missing in DHCP server response. Assuming 3150 sec 
Jul  6 22:51:43 Tower dhcpcd[1361]: DHCP_ACK received from  (192.168.0.1) 
Jul  6 22:51:43 Tower ifplugd(eth0)[1333]: client: dhcpcd: MAC address = 00:01:2e:35:d8:75
Jul  6 22:51:43 Tower ifplugd(eth0)[1333]: client: dhcpcd: your IP address = 192.168.0.16
Jul  6 22:51:43 Tower ifplugd(eth0)[1333]: client: dhcpcd: MAC address = 00:01:2e:35:d8:75
Jul  6 22:51:43 Tower ifplugd(eth0)[1333]: client: dhcpcd: your IP address = 192.168.0.16

 

Normally a router in DHCP mode will offer up an IP address to the server right away, not take a while like yours is doing.  You might want to try running your server on a static IP for a while, at least until we resolve your second issue.  You can make this change directly on your flash drive, even with the server powered off.  If you need help setting a static IP, just let me know and I'll be happy to walk you through it.  There's really no downside to running your server on a static IP - I use a static IP on my server all the time, and I've found it to be a bit more reliable because of it.

 

Your second and far more grievous issue a whole bunch of OOM (out of memory) errors that are crashing your server.  Presumably these are the result of the XBMC database software you've been attempting to run.  I would suggest that you start by editing your 'go' file on your flash drive and commenting out all add-ons (including unMenu) for now.  Again, if you need more guidance, just let me know.

 

Let's first ensure that the server will boot reliably with a static IP and no add-ons running.  Once we've established that, then we can start adding the add-ons back on and working out any new issues that crop up.

Hey, thanks for the advice, i've set up a static IP but as for the other problem I decided to take the easy way out and go for a clean install of unraid again and start afresh

Everythings up and running now, albeit 11 hours after I started.

 

Thanks