Jump to content

<SOLVED> Mover error compounded into a total system error...


Recommended Posts

Ok damnit.  I messed this up bad.  Let me start by saying my Cache drive was getting full because mover was not writing to the array (I'm not sure what I had wrong but the syslog from unmenu says that I didn't have enough space when that was wrong.  

 

So now I wanted to at least get those movies off of the cache drive so I figured if I put it in a regular data slot I could get it out.  Not so much.  Now the stupid array won't start until I put that disk back and I can't replace it with another HD (that's just been sitting in the case and not assigned anywhere for no reason).  

 

WTF?  

 

First how do I fix this problem

Second How do I fix the mover

 

Link to comment

Ok damnit.  I messed this up bad.  Let me start by saying my Cache drive was getting full because mover was not writing to the array (I'm not sure what I had wrong but the syslog from unmenu says that I didn't have enough space when that was wrong. 

 

So now I wanted to at least get those movies off of the cache drive so I figured if I put it in a regular data slot I could get it out.  Not so much.  Now the stupid array won't start until I put that disk back and I can't replace it with another HD (that's just been sitting in the case and not assigned anywhere for no reason). 

 

WTF? 

 

First how do I fix this problem

Second How do I fix the mover

 

you start the same as anyone else.

 

Attach a syslog to your next post, and a screen-shot too.

 

also, once you can get the array started, the output of a

df

command will help to know what space is currently in use.

Link to comment

Let's try this -

 

<a href="http://twitpic.com/67zhuf" title="df command on Twitpic"><img src="http://twitpic.com/show/thumb/67zhuf.jpg" width="150" height="150" alt="df command on Twitpic"></a>

 

<a href="http://twitpic.com/67zh9m" title="Share photos on twitter with Twitpic"><img src="http://twitpic.com/show/thumb/67zh9m.png" width="150" height="150" alt="Share photos on twitter with Twitpic"></a>

Link to comment

You're running unRAID v5.0beta10.  There's a fault in that version relating to the scheduling of mover.

 

 

Put all your drives back in their correct configurations - if what you write is correct, it is only the cache drive assignment which needs correcting.  Now start the array.

If you go to the 'Settings' tab in the standard unRAID web interface, and select 'Share Settings', you will see 'Mover Settings' at the bottom section.

 

If you click on 'Move Now' then mover will run once - if your cache disk is really full, then it may take quite a long time to complete.

 

Once that is completed, you can prompt mover to run according to schedule by clicking the 'Apply' button, just above 'Move Now'.  You will need to do this every time your unRAID server is rebooted.

 

This problem has been fixed in v5.0beta11.

Link to comment

Archived

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

×
×
  • Create New...