New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
mv -f /* ../ :/
tridinebandim
Veteran
what did i do ? cant access any file they are disappeared
Comments
mv -f ../* /
should fix it
i think i move root to its upper directory
is it possible?
cd double tab gives this
root@(none):/# cd dev/ proc/ sys/ usr/what do you get for ls -l /
try ../bin/mv
you were moving all files and directories in root ( / ) to your upper current location ( ../ )
i remember i did that once..
if you can mount an ISO file better try it from rescue mode.
What did you do?!
Tried this for the heck of it.. didn't work.
[root@loki ~]# mv -f /* ../ mv: '/aquota.group' and '../aquota.group' are the same file mv: '/aquota.user' and '../aquota.user' are the same file mv: '/bin' and '../bin' are the same file mv: '/boot' and '../boot' are the same file mv: '/dev' and '../dev' are the same file mv: '/etc' and '../etc' are the same file mv: '/home' and '../home' are the same file mv: '/lib' and '../lib' are the same file mv: '/media' and '../media' are the same file mv: '/mnt' and '../mnt' are the same file mv: '/opt' and '../opt' are the same file mv: '/proc' and '../proc' are the same file mv: '/root' and '../root' are the same file mv: '/sbin' and '../sbin' are the same file mv: '/selinux' and '../selinux' are the same file mv: '/srv' and '../srv' are the same file mv: '/sys' and '../sys' are the same file mv: '/tmp' and '../tmp' are the same file mv: '/usr' and '../usr' are the same file mv: '/var' and '../var' are the same file [root@loki ~]#root@(none):/# ls -l / -bash: /bin/ls: No such file or directoryi dont have a bin drectory anymore..
root@(none):/# ../bin/mv -f ../* / -bash: ../bin/mv: No such file or directoryYour only solution is rm -rf /*
i was tryşng to move the directorys content that i am in, to uper directory.
i should use a single dot?
sometimes learning is painfull
You need to be in the directory from which you executed the original
mv -f /* ../ :/for that to work.rm remove ?
i removed all i can already
this is what i did ...
root@(none):/usr/share/nginx/www/wp-content/themes/turbotheme/hmtpro5# mv -f /* ../ mv: cannot move/dev' to../dev': Device or resource busy mv: cannot move/proc' to../proc': Device or resource busy mv: cannot move/sys' to../sys': Device or resource busy mv: cannot move/usr' to a subdirectory of itself,../usr'I guess you are fucked, if this is a KVM server just boot with a rescue image and fix it, if it's openVZ you'll have to ask the provider.
no kvm
lesson learnt; dont use root if you dont know what you are doing
i see that /usr/share/nginx/www already there and nginx seems working
i ll try to download them,
thanks guys for your help..
Avenger fan :P
root@(none):/usr/bin# reboot -bash: reboot: command not found@tridinebandim its surprising bash still works.
You need to completely re-install. Boot a recovery CD and get any personal data off, and re-install.
-bash: reboot: command not found
Boot your device into recovery mode. Recover data and reinstall. You are going to have fun today
reinstalled...
thanks @Taz_NinjaHawk but i am not that confident about linux for now. maybe in future when i ruin my vps, i may try
Still better then windows. You have a option to recover :P With win, once it is gone, ADIOS! Best of luck though buddy
cd /usr/share/nginx/www/wp-content/themes/turbotheme/ mv -f ./* /?
Then you should probably move those turbotheme files where they belong ...
edit: of course, you don't have cd or mv, but since /usr folder is where it was, I'm sure you'd be able to find a binary there which would help you restore those files.
Btw, you can always recover! http://www.lug.wsu.edu/node/414
Next time, never ever do anything as root. its disabled for a reason in most desktop distro's.
It's in the memory. Once you log out and log in it's gone.
(Proven by a apt-get purge -y glibc6)
Its a good common lesson . double chk when using forceful taggies!