No user0 directory [SOLVED]

Just noticed that I no longer seem to have a user0 directory... I have cache drive and there is data on it ..

I checked the contents of the cache drive and it looks like the mover has not run in a while.. What should I do ?

Attached syslog

I have a couple of weird things:

The directories left in the cache drive are mostly empty (I use my unraid system for movie storage), with empth I mean they do not contain the movie BUT they contain fanart, backgrounds, and other stuff that gets generated after downloading...

This gets created by the tool MyMovies that is running from my windows box (nothing on unraid itself doing anything about it). It looks like stuff that is created from windows gets a wrong userid / groupid ?

root@Tower:/mnt/cache/Movies/Avatar# ls -alg

total 384

drwxrwx---  2 users    80 2012-05-12 19:46 ./

drwxrwx--- 129 users  4448 2012-05-14 20:43 ../

-rw-rw----  1 root  385255 2012-05-12 19:46 fanart.jpg

In SYSLOG I found that my crontab does not appear to be running, herewith the results of a CRONTAB -L

root@Tower:/mnt/cache/Series# crontab -l

# If you don't want the output of a cron job mailed to you, you have to direct

# any output to /dev/null.  We'll do this here since these jobs should run

# properly on a newly installed system, but if they don't the average newbie

# might get quite perplexed about getting strange mail every 5 minutes. :^)

#

# Run the hourly, daily, weekly, and monthly cron jobs.

# Jobs that need different timing may be entered into the crontab as before,

# but most really don't need greater granularity than this.  If the exact

# times of the hourly, daily, weekly, and monthly cron jobs do not suit your

# needs, feel free to adjust them.

#

# Run hourly cron jobs at 47 minutes after the hour:

47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null

#

# Run daily cron jobs at 4:40 every day:

40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null

#

# Run weekly cron jobs at 4:30 on the first day of the week:

30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null

#

# Run monthly cron jobs at 4:20 on the first day of the month:

20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null

#Add sa1 data collection - 1 data point per 2 min

*/2 * * * * /usr/lib/sa/sa1 1 1

# Scheduled Parity Check

30 23 1 * * /root/mdcmd check  1>/dev/null 2>&1

02 00 * * * rsync -avz /mnt/user/users /mnt/user/Users_Yesterday >/dev/null 2>&1

Pressing "move now" gets me the following response:

May 14 20:56:01 Tower crond[1176]: exit status 1 from user root /usr/lib/sa/sa1 1 1

syslog.zip

Just noticed that I no longer seem to have a user0 directory... I have cache drive and there is data on it ..

 

I checked the contents of the cache drive and it looks like the mover has not run in a while.. What should I do ?

 

Attached syslog

since it moves file to /mnt/user0/whatever...

Something must have happened to the /mnt/user0 device.  (it is a view of the user-shares without the "cache" drive contents)

Stopping and re-starting the server should restore the /mnt/user0 device if you have a cache drive defined.

Just noticed that I no longer seem to have a user0 directory... I have cache drive and there is data on it ..

 

I checked the contents of the cache drive and it looks like the mover has not run in a while.. What should I do ?

 

Attached syslog

All you can do is stop and re-start unRAID.  The mover cannot move anything right now,

since it moves file to /mnt/user0/whatever...

 

Something must have happened to the /mnt/user0 device.  (it is a view of the user-shares without the "cache" drive contents)

 

Stopping and re-starting the server should restore the /mnt/user0 device if you have a cache drive defined.

I will do that tomorrowmorning (have some large file transfers running at the moment), hope it helps though, the files I see in the cache drive are pretty old any my server was restarted two days ago as a result of the RC3 install..

At least it will give us a clean syslog to look at ;-)

I restarted and when the system was back the user0 directory was there again, mover also worked and has emptied the cache drive, all is well in the world :-)