Permission denied on /bin/bash when attempting login
by bougiemane from LinuxQuestions.org on (#6DPN4)
Oof, this is a doozie.
I inherited a server. This server is almost as old as I am and has no business in being alive, yet I work in government and my job is to keep dinosaurs like these alive.
Server is in RAID 5, one disk dies two weeks ago, government job says no disk replacement available, I go "your funeral" and go on summer break. Come back, me and senior admin find the filesystem has turned to read-only and has basically bit the bullet.
Today we did a machine restart prepared that it won't turn on and it didn't with a kernel panic for a bad superblock.
Code:JBD: Failed to read block at offset ...
EXT3-fs: error loading journal
mount: error 22 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed:2
Kernel panic - not syncing: Attempted to kill init!Booted from a live environment, did the following:
Code:sudo e2fsck -f deviceshowed bad superblock.
Went ahead and found superblock backups, then restored from backup with
Code:sudo e2fsck -f -b 32768 /dev/sdb1System check finished successfully, restarted the machine. And that's where it went wrong - all services seem to start succesfully. The system gets its hostname, recieves an IP from the DHCP server, responds to ping etc. Yet when someone tries logging in via ssh they get "/bin/bash - Permission Denied" error. When you try logging in from a local console, it spawns a shell for a milisecond and then just goes back to the login screen. From a rescue shell I can spawn a shell from /bin/bash or sh or ksh easily, yet they all yield Permission Denied when logging into the machine. Permissions on all of those under /bin are 755 and root:root for owner and group. Has anyone faced an issue like this? What can I do?
I inherited a server. This server is almost as old as I am and has no business in being alive, yet I work in government and my job is to keep dinosaurs like these alive.
Server is in RAID 5, one disk dies two weeks ago, government job says no disk replacement available, I go "your funeral" and go on summer break. Come back, me and senior admin find the filesystem has turned to read-only and has basically bit the bullet.
Today we did a machine restart prepared that it won't turn on and it didn't with a kernel panic for a bad superblock.
Code:JBD: Failed to read block at offset ...
EXT3-fs: error loading journal
mount: error 22 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed:2
Kernel panic - not syncing: Attempted to kill init!Booted from a live environment, did the following:
Code:sudo e2fsck -f deviceshowed bad superblock.
Went ahead and found superblock backups, then restored from backup with
Code:sudo e2fsck -f -b 32768 /dev/sdb1System check finished successfully, restarted the machine. And that's where it went wrong - all services seem to start succesfully. The system gets its hostname, recieves an IP from the DHCP server, responds to ping etc. Yet when someone tries logging in via ssh they get "/bin/bash - Permission Denied" error. When you try logging in from a local console, it spawns a shell for a milisecond and then just goes back to the login screen. From a rescue shell I can spawn a shell from /bin/bash or sh or ksh easily, yet they all yield Permission Denied when logging into the machine. Permissions on all of those under /bin are 755 and root:root for owner and group. Has anyone faced an issue like this? What can I do?