Hi,

 

The mover always did it's job, but it doesn't work anymore.

 

I believe the issue began because I had some drives without free space, but after creating some it still didn't work.

Can you guys help me out? Thx!

 

PS  I use unraid pro 5.0 final, have one share: high water, split level 2 (always worked like a charm)

syslog.zip

See here: http://lime-technology.com/forum/index.php?topic=28484.0

Followed instructions as described, but the problem still exists.

 

When I start the mover, the same errors appear and when I run Tom's script again the earlier removed "user.org.netatalk.supports-eas" messages are back.

 

Any futher suggestions?

I'd suspect file system corruption after the mover failed on the full disk error.

 

Reiserfsck check on your drives.

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

Just 'check' first, then be sure to follow the instructions before 'fixing' anything.

 

If nothing shows up in Reiserfsck, post a full syslog, not just the part with the mover failing.

http://lime-technology.com/forum/index.php?topic=9880.0

Checked all my data drives, no corruptions found. Didn't check my cache drive, should I?

 

I included the full syslog, but I believe my previous posted log is the full one too.

 

Another thing I see; the cache drive status is blinking green-white, which I believe is the signal that it's spun down? When spinning up all disks it shows normal green again.

So nothing special I think?

syslog.zip

The logs still claim there are problems with the file attributes.

Can you look at the DISK SHARES and see if the media have perhaps been successfully copied to the array, but were never deleted from the cache drive?

Pick a few sample files that are still on the cache drive and see if they're actually on one of the array disks.

 

 

It seems you are right DaleWilliams.

It looks like the files on the cache drive have already been copied to the array. All folders are still present on the cache drive, most files too, but some have been already deleted.

Could this cause my problem? And if so, how do I solve this?

 

Thanks for helping me out, I really appreciate it!

 

Enable the cache disk share and delete any files that have been moved.

This actually happened to me, once.

There's probably a smart way to tell which files were successfully copied from cache to the array, and which weren't.

I decided that inelegant but easy was the solution.

 

Luckily, I had space available on my Mac, so...

I copied everything back from cache disk share to Mac.

Deleted all those files on cache disk.

Then copied from Mac to the appropriate user shares.

 

When prompted about what to do with the duplicates, I used 'overwrite' when prompted by unRAID.

(on the assumption that the files originally on the cache disk were most likely to be correct, and that a file or two on the array might be bad.)

Followed instructions, but now running into the problem that some folders/files on the cache drive will not be deleted.

I don't get any message, but the folders are just staying on the drive.

 

Any suggestions how to remove them?

My plan is to take out my cache drive, format it as fat32 on a Windows machine, it put it back in my array.

 

Or is there an easier way to clear the cache drive?

 

Thanks!

My plan is to take out my cache drive, format it as fat32 on a Windows machine, it put it back in my array.

 

Or is there an easier way to clear the cache drive?

 

Thanks!

You said you checked the data drives for corruption but not the cache. You should probably do the check on the cache drive.

 

unRAID will reformat the cache drive as ReiserFS anyway if you format it fat32 so I guess it wouldn't hurt. An easier way to get it formatted might be to remove it and then add it back.