hey guys,

today i tried to move my plexmediafolders from hdds to my cache drive.

 

root@UNRAID:/# mv /mnt/disk4/appdata/ /mnt/cache/appdata/ *

mv: inter-device move failed: '/mnt/cache/appdata/' to 'var/appdata'; unable to remove target: Directory not empty
mv: cannot move 'boot' to 'var/boot': Device or resource busy
mv: cannot move 'dev' to 'var/dev': Device or resource busy
mv: cannot move 'lib' to 'var/lib': Directory not empty
mv: cannot move 'mnt' to 'var/mnt': Device or resource busy
mv: cannot move 'proc' to 'var/proc': Device or resource busy
mv: cannot move 'run' to 'var/run': Device or resource busy
mv: cannot move 'sys' to 'var/sys': Device or resource busy
mv: cannot move 'tmp' to 'var/tmp': Directory not empty

 

Yeah, now the system is broken. I'm still logged into the system with ssh/root, but every command is dead, reporting (example ls):

 

root@UNRAID:/mnt/cache/appdata# ls
-bash: /bin/ls: No such file or directory

 

I do think i moved folders named above to /var/, even tho i don't understand why the system acted like this.

Any chance that i can revert this move-command? Or what would be the easiest way to correct this?

Please help

It's unraid 6.2

I do think i moved folders named above to /var/, even tho i don't understand why the system acted like this.

 

It acted like that because you told it to.

 

Obviously not your intention, so why would the system do something like that?

 

Have a look at your command, it ends with a *. That character in that situation will expand and be replaced by something else. Since you were issuing the mv command from the root directory /, the character expanded to the names of files and folders available there and your command line actually turned into something like this:

 

root@UNRAID:/# mv /mnt/disk4/appdata/ /mnt/cache/appdata/ boot dev lib mnt proc run sys tmp var

 

The syntax for mv expects the last parameter to be the destination, and everything else specified should be moved there.

Thanks for this explanation! Dangerous Stuff

And what do i do now?

Dangerous indeed. The console is incredibly powerful - With great power comes great responsibility.

 

The system folders such as /bin and others won't be a problem, they exist only in RAM and will be created on boot. The contents of your unRAID USB drive, the cache drive and other disks on the other hand... Do you have decent backups?

I have no backup of USB Drive and Cache Drive.

I have backups of the important Data on the Datadrives. But there is still some data i have not backuped that i wouldn't like to loose. Tho, it would be not that tragic ..

Restarted the System, and everything seems ok? But have no idea, how this works.

I have no backup of USB Drive and Cache Drive.

CA will automatically create backups on a schedule of your appdata and flashdrive

 

(And as an aside could have also handled the move of the appdata by modifying the source and destination)

Just curious, why would you try to move system folders?  They are already all in RAM!

I don't think it was intentional Rob...

 

Sent from my LG-H815 using Tapatalk

 

 

Sorry!  I should have read it more carefully.