Jump to content

Upgraded to Pro and Hell got loose B14 Cache drive problem


Dawid

Recommended Posts

Posted

First of all I was a happy unraid user for over 3 months so I actusly thought one day im so happy that I will pay for the FW and get a cache drive also. That plan wasn't the best idea.

1) I stop the array.

2) Powered it down

3) Added the chache drive disk

4) Started the server

5) Added the cache drive to the config

6) enabled cache on shares

7) Copied some files to unraid and success! cache is working

 

and at this point the problems started. first I get the seg foult on the emhttpd but its not a big problem for me as long as the raid is accessable I dont have to look at it.

after a jumped to a linux server and did ls -la I got nfs stale file handle  o_O  now after some experiments I have found the couse of this problem it's the cache drive I and the Mover script

When the mover script finishes moving the files kaboom I have got the Stale Nfs problem on all ubutu clients running ubu 10.04 LTS and 11.10.  I have tried to disable the spin down on the cache drive but this didn't help @ all.

 

Specs:

GA-E350N-USB3 (FUSION)

2 GB of RAM

3x EARX sata 3

1x 120 gb 2,5" drive for cache

 

log: pastebin(dot)com/2wF9scrc

 

Regards

 

Posted

No 0 addons...

But i Know that this problem is not only on my unraid I made a setup with my friend and he added a cache drive also the mover script kills the shares. The funny thing is that you can access it via direct links but you cant browse ls -la will not work. but if a do i.e. cp /media/Tower/Movies/Avatar/movie.avi /foo/b it will work fine.

 

Posted

Me too.  No add ons except unmenu.  I shut down the array manually because of an ice storm we were having, and now I can't start the array because unmenu doesn't know how to do that and I don't know the command.  Dead in the water. 

 

Already posted in the announcement thread and another thread on this topic but no support seems to be forthcoming except for idiotic, snide comments about what I named my server.

 

Lately emhttp is not segfaulting but there is some kind of binding problem:

Jan 15 16:01:33 freenas emhttp: main: can't bind listener socket: Address already in use

root@freenas:/usr/local/sbin# ps -efl | grep emhttp
4 S root      1107     1  0  80   0 -  2974 sk_wai 11:55 ?        00:00:01 /usr/local/sbin/emhttp
0 S root      1488  1205  0  80   0 -   613 pipe_w 16:23 pts/0    00:00:00 grep emhttp

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...