Subject says it all, really.  I was running rc8 without a hitch and am playing with the idea of setting up a Plex server. I installed Plex for unraid then rebooted. After I tried to start the array from the webUI, it refreshed to a 404 and the array never comes online. No disk activity, only the flash drive is visible on the network.

 

I can't telnet to the server, but I can log in from the server itself.

 

I then upgraded to rc11 to see if it would fix the problem. It didn't.

 

It looks like I'm getting an out of memory error from the emhttp process.

 

I've tried removing plex (txz file and plugins dir) , but the same error is happening.

 

Syslog is attached.

 

Thanks in advance!

syslog.txt

Posting in the User Customizations forum is more likely to get the attention of a qualified responder.

I may try that, except the problem is still happening even with everything disabled. I've followed the instructions to revert to stock in your signature. So this problem may actually be unrelated to Plex.

 

Syslog of that attached (looks like the same error to me).

syslog.txt

Did you change the tunable parameters for stripe size, etc...

This line seems to indicate your server is attempting to allocate a huge amount of memory

(it is probably using "low" memory)

Feb  3 09:16:00 Cooper kernel: 4164MB HIGHMEM available.

Feb  3 09:16:00 Cooper kernel: 891MB LOWMEM available.

 

Feb  3 09:16:39 Cooper kernel: unraid: allocating  1057000K for 12800 stripes (20 disks)

 

My server says

Jan 28 22:29:25 Tower kernel: unraid: allocating 39140K for 1280 stripes (7 disks)

 

What do you have in your /boot/config/disk.cfg file for those parameters... I suspect you changed them...  (and forgot to mention it when requesting assistance)

 

I have on my personal server:

md_num_stripes="1280"

md_write_limit="768"

md_sync_window="288"

 

Looking in your syslog I see:

Feb  3 09:16:39 Cooper kernel: mdcmd (25): set md_num_stripes 12800

Feb  3 09:16:39 Cooper kernel: mdcmd (26): set md_write_limit 7680

Feb  3 09:16:39 Cooper kernel: mdcmd (27): set md_sync_window 288

 

I think if you restore those to values that do not exceed your RAM you'll be fine.

 

Joe L.

Huh... I don't ever remember setting or changing those values, but I took off the extra 0's and it started up perfectly. Thanks Joe!