Can't SSH into Raspberry Pi after changing permissions [duplicate]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
This question already has an answer here:
Wrongly set chmod / 777. Problems?
4 answers
sudo chmod -R 777 / was entered in an attempt to regain access to directories that were previously accessible, but this caused the SSH connection to be closed and now can no longer be reconnected. A "Login failed." error is displayed. The Pi can still be accessed directly.
Any use of sudo returns sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
How can this be reversed? What did the permission changes do to cause this?
debian ssh raspberry-pi raspbian
asked Jul 19 at 19:57
Ctrl S
356
marked as duplicate by roaima, Jesse_b, slm♦ Jul 19 at 20:27
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |Â
up vote
0
down vote
favorite
This question already has an answer here:
Wrongly set chmod / 777. Problems?
4 answers
sudo chmod -R 777 / was entered in an attempt to regain access to directories that were previously accessible, but this caused the SSH connection to be closed and now can no longer be reconnected. A "Login failed." error is displayed. The Pi can still be accessed directly.
Any use of sudo returns sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
How can this be reversed? What did the permission changes do to cause this?
debian ssh raspberry-pi raspbian
asked Jul 19 at 19:57
Ctrl S
356
marked as duplicate by roaima, Jesse_b, slm♦ Jul 19 at 20:27
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
In practical terms you restore from your backup or reinstall from scratch. You have hosed your system. There are some answers here (I'll see if I can find a duplicate for you) that explain how you might be able to repair your Pi but basically you've broken it.
– roaima
Jul 19 at 20:12
Sounds broken, haha. Reinstall looks like the cleanest solution.
– Ctrl S
Jul 19 at 20:16
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This question already has an answer here:
Wrongly set chmod / 777. Problems?
4 answers
sudo chmod -R 777 / was entered in an attempt to regain access to directories that were previously accessible, but this caused the SSH connection to be closed and now can no longer be reconnected. A "Login failed." error is displayed. The Pi can still be accessed directly.
Any use of sudo returns sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
How can this be reversed? What did the permission changes do to cause this?
debian ssh raspberry-pi raspbian
asked Jul 19 at 19:57
Ctrl S
356
This question already has an answer here:
Wrongly set chmod / 777. Problems?
4 answers
sudo chmod -R 777 / was entered in an attempt to regain access to directories that were previously accessible, but this caused the SSH connection to be closed and now can no longer be reconnected. A "Login failed." error is displayed. The Pi can still be accessed directly.
Any use of sudo returns sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
How can this be reversed? What did the permission changes do to cause this?
This question already has an answer here:
Wrongly set chmod / 777. Problems?
4 answers
debian ssh raspberry-pi raspbian
asked Jul 19 at 19:57
Ctrl S
356
edited Jul 19 at 20:10
asked Jul 19 at 19:57
Ctrl S
356
asked Jul 19 at 19:57
Ctrl S
356
asked Jul 19 at 19:57
Ctrl S
356
356
marked as duplicate by roaima, Jesse_b, slm♦ Jul 19 at 20:27
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by roaima, Jesse_b, slm♦ Jul 19 at 20:27
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
In practical terms you restore from your backup or reinstall from scratch. You have hosed your system. There are some answers here (I'll see if I can find a duplicate for you) that explain how you might be able to repair your Pi but basically you've broken it.
– roaima
Jul 19 at 20:12
Sounds broken, haha. Reinstall looks like the cleanest solution.
– Ctrl S
Jul 19 at 20:16
add a comment |Â
In practical terms you restore from your backup or reinstall from scratch. You have hosed your system. There are some answers here (I'll see if I can find a duplicate for you) that explain how you might be able to repair your Pi but basically you've broken it.
– roaima
Jul 19 at 20:12
Sounds broken, haha. Reinstall looks like the cleanest solution.
– Ctrl S
Jul 19 at 20:16
In practical terms you restore from your backup or reinstall from scratch. You have hosed your system. There are some answers here (I'll see if I can find a duplicate for you) that explain how you might be able to repair your Pi but basically you've broken it.
– roaima
Jul 19 at 20:12
In practical terms you restore from your backup or reinstall from scratch. You have hosed your system. There are some answers here (I'll see if I can find a duplicate for you) that explain how you might be able to repair your Pi but basically you've broken it.
– roaima
Jul 19 at 20:12
Sounds broken, haha. Reinstall looks like the cleanest solution.
– Ctrl S
Jul 19 at 20:16
Sounds broken, haha. Reinstall looks like the cleanest solution.
– Ctrl S
Jul 19 at 20:16
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
-1
down vote
You can fix this by removing the SD card and mounting it in another device under /mnt and chmodding the files under /mnt.
Another option is if you can get it to boot by mounting a rescue image you can run aptitude reinstall "~i" which should fix file permissions.
That said unless there is data you can't lose you should reinstall.
answered Jul 19 at 20:26
Joe M
5964
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
-1
down vote
You can fix this by removing the SD card and mounting it in another device under /mnt and chmodding the files under /mnt.
Another option is if you can get it to boot by mounting a rescue image you can run aptitude reinstall "~i" which should fix file permissions.
That said unless there is data you can't lose you should reinstall.
answered Jul 19 at 20:26
Joe M
5964
add a comment |Â
up vote
-1
down vote
You can fix this by removing the SD card and mounting it in another device under /mnt and chmodding the files under /mnt.
Another option is if you can get it to boot by mounting a rescue image you can run aptitude reinstall "~i" which should fix file permissions.
That said unless there is data you can't lose you should reinstall.
answered Jul 19 at 20:26
Joe M
5964
add a comment |Â
up vote
-1
down vote
up vote
-1
down vote
You can fix this by removing the SD card and mounting it in another device under /mnt and chmodding the files under /mnt.
Another option is if you can get it to boot by mounting a rescue image you can run aptitude reinstall "~i" which should fix file permissions.
That said unless there is data you can't lose you should reinstall.
answered Jul 19 at 20:26
Joe M
5964
You can fix this by removing the SD card and mounting it in another device under /mnt and chmodding the files under /mnt.
Another option is if you can get it to boot by mounting a rescue image you can run aptitude reinstall "~i" which should fix file permissions.
That said unless there is data you can't lose you should reinstall.
answered Jul 19 at 20:26
Joe M
5964
answered Jul 19 at 20:26
Joe M
5964
answered Jul 19 at 20:26
Joe M
5964
answered Jul 19 at 20:26
Joe M
5964
5964
add a comment |Â
add a comment |Â
In practical terms you restore from your backup or reinstall from scratch. You have hosed your system. There are some answers here (I'll see if I can find a duplicate for you) that explain how you might be able to repair your Pi but basically you've broken it.
– roaima
Jul 19 at 20:12
Sounds broken, haha. Reinstall looks like the cleanest solution.
– Ctrl S
Jul 19 at 20:16