Accidently ran chmod 777 -R on / - what can I do now?

  • Hello all,


    due to...well let's just call it stupidity... I managed to run chmod 777 -R on /


    OMV runs on a headless HP server, which I usually ssh into.


    Now of course I cannot access the server at all anymore (neither via ssh nor the web-admin panel).


    Does anyone have any idea of how I can proceed?


    (Yes I feel bad and I should feel bad and damn...)

  • You gave read/write/execute to all files in your system.
    Can't see why this is something that prevents you to connect to the server anymore.
    Maybe I am missing something here?
    Anyhow I don't think there is any way to undo what you did.
    So next time have a look on the threads about backup !!!
    I use clonezilla from the backup plugin and it's straight forward.
    I learnt the hard way myself too (rm -r as root a system directory :( )
    and from then I do regular backups of the OS.

  • I feared as much. But since it's a headless system, I wouldn't know how to do so. Plugging in an OMV USB installation drive won't do any good as I can't access the setup routine.


    - Is there a headless OMV 2.0 usb installation method?
    - I would need to setup all plugins, settings, etc., again, I assume?

  • Well, time to take the baby to my workplace and grab an old monitor and have some new setup fun.


    Thanks all for the confirmation that there isn't a magical "OMV rescue USB drive" method ;)

  • Zitat

    you can but so many chmod values have been damaged it would take forever to fix. Also, someone would have to feed him the correct values. It would take far too much time.


    yes , i forgot completely in that perspective .

    • Offizieller Beitrag

    Install fresh. There are plenty of files on a Linux box that can't be 777 because the service won't allow it. You would have a very difficult time finding all the right permissions.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Install fresh. There are plenty of files on a Linux box that can't be 777 because the service won't allow it. You would have a very difficult time finding all the right permissions.


    Yes, I am planning on, am just happy that I was able to regain access. Is there a tutorial on how to backup all relevant server and plugin settings, etc., and do a fresh install?


    Thank you all for the help and input.

    • Offizieller Beitrag

    You can keep /etc/openmediavault/config.xml for reference but that is about it.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Yup, I know this thread is 4 months old, but just for reference:


    http://serverfault.com/questio…s-chmod-r-777-destructive


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • Reinstall is the easiest and safest option. However, you can try:
    https://matoski.com/article/de…ar-ownership-permissions/


    Slow way:
    Reinstall all Packages, will redo permissions:
    dpkg --get-selections \* | awk '{print $1}' | xargs -l1 aptitude reinstall


    Do the dpkg/apt way: Download all installed packages (you need space for that), read the permissions and apply that to your files. (called Method 2 in the link above)


    [edit]
    Having a backup is always the best way to restore from stupidity

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!