fs corrupted - permissions altered
Hi, My nightmare : one of our programmers accidently has "chown (as root) * -R". Hardware problems shuted down the box during the night and this morning the machine won't boot. I had tried several things : 1. normal reboot does an normal fs repair, then it hangs on "unable to mount /proc - only root can do that". The next reboot will eventually pass this phase but will stop on "init : runlevel 6 respawn too fast disabling for 5 minztes" and again and again. 2. boot in rescue mode - can't mount file system, anywhere (i figured now that HD devices are in RAID mode). What should i do. I am not that experienced with RAID and although i can handle an rescue environement this situation is above my skill i fear. Help will be much appreciated. Thanks. Miguel
/ 2004-07-28 10:48:32 +0200 \ Miguel Albuquerque:
Hi,
My nightmare : one of our programmers accidently has "chown (as root) * -R". Hardware problems shuted down the box during the night and this morning the machine won't boot. I had tried several things :
1. normal reboot does an normal fs repair, then it hangs on "unable to mount /proc - only root can do that". The next reboot will eventually pass this phase but will stop on "init : runlevel 6 respawn too fast disabling for 5 minztes" and again and again.
2. boot in rescue mode - can't mount file system, anywhere (i figured now that HD devices are in RAID mode).
What should i do. I am not that experienced with RAID and although i can handle an rescue environement this situation is above my skill i fear.
Help will be much appreciated.
try this: at the lilo/grub boot promt, say init=/bin/sash (which is the stand alone shell, much functionality statically linked in.) bash will do, too (maybe). then, mount -o remount,rw / mount the other parts of the system ... to get at least some of the permissions and ownders right again, try rpm -qa | xargs rpm --setperms --setugids now, at least what is listed in the rpm db should be "back to normal". for real users, you can only "guess" what belongs to them. chown them their home directories, and hope for the best. lge
Thanks everybody, i was able to restore permissions and have a normal reboot using rpm -qa | xargs rpm --setperms --setugids after remounting root rw. It returns an error but worked for me ! Best regards, Miguel On Wednesday 28 July 2004 11:26, Lars Ellenberg wrote:
/ 2004-07-28 10:48:32 +0200
\ Miguel Albuquerque:
Hi,
My nightmare : one of our programmers accidently has "chown (as root) * -R". Hardware problems shuted down the box during the night and this morning the machine won't boot. I had tried several things :
1. normal reboot does an normal fs repair, then it hangs on "unable to mount /proc - only root can do that". The next reboot will eventually pass this phase but will stop on "init : runlevel 6 respawn too fast disabling for 5 minztes" and again and again.
2. boot in rescue mode - can't mount file system, anywhere (i figured now that HD devices are in RAID mode).
What should i do. I am not that experienced with RAID and although i can handle an rescue environement this situation is above my skill i fear.
Help will be much appreciated.
try this: at the lilo/grub boot promt, say init=/bin/sash (which is the stand alone shell, much functionality statically linked in.) bash will do, too (maybe).
then, mount -o remount,rw / mount the other parts of the system ... to get at least some of the permissions and ownders right again, try rpm -qa | xargs rpm --setperms --setugids
now, at least what is listed in the rpm db should be "back to normal". for real users, you can only "guess" what belongs to them. chown them their home directories, and hope for the best.
lge
Hi Miguel, try following ... ... plug in a standard IDE hdd with LINUX on board .. start it .. mount the scsi hdd ( as root ;-) ) .. and change the permissions back again ... I'd give it a try .. -Alex "Miguel Albuquerque" <mfoacs@e-workshop.ch> schrieb am 28.07.2004 10:48:32:
Hi,
My nightmare : one of our programmers accidently has "chown (as root) * -R". Hardware problems shuted down the box during the night and this morning the machine won't boot. I had tried several things :
1. normal reboot does an normal fs repair, then it hangs on "unable to mount /proc - only root can do that". The next reboot will eventually pass this phase but will stop on "init : runlevel 6 respawn too fast disabling for 5 minztes" and again and again.
2. boot in rescue mode - can't mount file system, anywhere (i figured now that HD devices are in RAID mode).
What should i do. I am not that experienced with RAID and although i can handle an rescue environement this situation is above my skill i fear.
Help will be much appreciated.
Thanks.
Miguel
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
my suggestion would be to either install another linux hard drive and boot from it, then mount the other hard drive and change the permissions or to use any of the micro linux (floppy) or distros (bootable cd) to accomplish the same. I don't use suse on a regular basis past just installing and playing with an older version, but I do use redhat and gentoo every day for 5+ years. Speaking from RH experience, their installation disk has a way to boot for repair and chroot the hard drive. You can then mount it writable and make the repairs. I would assume almost all distro's have a similar feature. On Wed, 2004-07-28 at 04:48, Miguel Albuquerque wrote:
Hi,
My nightmare : one of our programmers accidently has "chown (as root) * -R". Hardware problems shuted down the box during the night and this morning the machine won't boot. I had tried several things :
1. normal reboot does an normal fs repair, then it hangs on "unable to mount /proc - only root can do that". The next reboot will eventually pass this phase but will stop on "init : runlevel 6 respawn too fast disabling for 5 minztes" and again and again.
2. boot in rescue mode - can't mount file system, anywhere (i figured now that HD devices are in RAID mode).
What should i do. I am not that experienced with RAID and although i can handle an rescue environement this situation is above my skill i fear.
Help will be much appreciated.
Thanks.
Miguel
participants (4)
-
bleonhardt＠analytek.de -
Lars Ellenberg -
Miguel Albuquerque -
Security - Ed Wiget