I'm trying to find out the "default" schedule for the mover script.  I ran a crontabs -l and it just lists the run_parts script and the only thing in the /etc/* directories is the logrotate script.

 

Is there no default set when you enable the cache drive?  I just noticed this issue because I've re-ripped a lot of movies and the cache drive filled up and never moved anything over.  I've not manually ran the script and it is working, just trying to understand how it should work.

 

thanks

dave

I'm trying to find out the "default" schedule for the mover script.  I ran a crontabs -l and it just lists the run_parts script and the only thing in the /etc/* directories is the logrotate script.

 

Is there no default set when you enable the cache drive?  I just noticed this issue because I've re-ripped a lot of movies and the cache drive filled up and never moved anything over.  I've not manually ran the script and it is working, just trying to understand how it should work.

 

thanks

dave

A. what version of unRAID are you running?

B. It is set in the unRAID settings...  If you've not enabled a cache drive, it might not be there in cron.

C. It is usually set to 3:40 AM daily, but you can set it as desired on the unRAID settings page.

 

I'm trying to find out the "default" schedule for the mover script.  I ran a crontabs -l and it just lists the run_parts script and the only thing in the /etc/* directories is the logrotate script.

 

Is there no default set when you enable the cache drive?  I just noticed this issue because I've re-ripped a lot of movies and the cache drive filled up and never moved anything over.  I've not manually ran the script and it is working, just trying to understand how it should work.

 

thanks

dave

A. what version of unRAID are you running?

B. It is set in the unRAID settings...  If you've not enabled a cache drive, it might not be there in cron.

C. It is usually set to 3:40 AM daily, but you can set it as desired on the unRAID settings page.

 

 

OK I see it in the settings page and it is set for 3:40AM daily.  Wonder why it didn't run last night.  I also don't see it in the crontab settings at least not when I run crontab -l

 

I'm running 5.0-Beta6a.  I've had the cache drive running for a year or so and never seen any issues, but to be honest I've never really looked at it either.  I just noticed because my cache drive filled up yesterday and I had to stop copying over movies as I had no idea what would have happened if it filled up completely.

 

thanks

dave

I've looked at my syslog from the reboot I did yesterday and don't see any crontab entry being created for the mover script.  I also looked at one from April 27th and do see this:

Apr 27 16:57:54 Tower emhttp: shcmd (4): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root

Apr 27 16:57:54 Tower emhttp: shcmd (5): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root

 

Which makes sense.

 

I don't see that at all in my current syslog file.  Could it be that this did not run because I had to replace a drive on this last reboot and rebuild the array?  So when this happens somehow the crontab doesn't get setup?

 

I went to the webpage and hit apply on the mover script settings and now see this in syslog:

Jun 19 13:10:26 Tower emhttp: shcmd (90): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 40 3 * * * /usr/local/sbin/mover 2>&1 |logger"

 

Which was created by my hitting the apply key on the webpage and I do see it in the /etc/cron.d/root file now.

 

This is why I was/am confused on how this "should" all work.

 

sorry for the ramble,

 

dave

I'm trying to find out the "default" schedule for the mover script.  I ran a crontabs -l and it just lists the run_parts script and the only thing in the /etc/* directories is the logrotate script.

 

Is there no default set when you enable the cache drive?  I just noticed this issue because I've re-ripped a lot of movies and the cache drive filled up and never moved anything over.  I've not manually ran the script and it is working, just trying to understand how it should work.

 

thanks

dave

A. what version of unRAID are you running?

B. It is set in the unRAID settings...  If you've not enabled a cache drive, it might not be there in cron.

C. It is usually set to 3:40 AM daily, but you can set it as desired on the unRAID settings page.

 

 

OK I see it in the settings page and it is set for 3:40AM daily.  Wonder why it didn't run last night.  I also don't see it in the crontab settings at least not when I run crontab -l

 

I'm running 5.0-Beta6a.  I've had the cache drive running for a year or so and never seen any issues, but to be honest I've never really looked at it either.  I just noticed because my cache drive filled up yesterday and I had to stop copying over movies as I had no idea what would have happened if it filled up completely.

 

thanks

dave

Yes, looks like you have to hit "apply" for it to put the entry in place.

 

I would think you should not have to press "apply" every time you reboot, but, I don't usually have any cache drive configured.

The moved schedule should survive reboots. Are you sure the destination is not blocked, e.g., disk full, share allocation issue, etc.?

The moved schedule should survive reboots. Are you sure the destination is not blocked, e.g., disk full, share allocation issue, etc.?

 

it ran fine when I kicked it off manually.

 

dave