[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [suse-security] fs corrupted - permissions altered



On Wednesday 28 July 2004 11:20, José Luis Ledesma wrote:
> First of all... you shouldn't give root permissions to programmers!
>
> I'm not a guru, but:
>
> How are you trying to mount the filesystem?

i've tried mount -o remount,rw /

> is a hardware raid or a software one?
> ide or scsi drives?

Two IDE, software RAID

>
> I supose you have solved the hardware problems, right?
>
> as much info you give, more help you will receive.
>
>
> José Luis Ledesma
> _______________
> Competitiveness
> Telephone: +34 93 582 02 90
> Email: jledesma@xxxxxxxxxxxxxxxxxxx
> Website: http://www.competitiveness.com
>
>
> -----Original Message-----
> From: Miguel Albuquerque [mailto:mfoacs@xxxxxxxxxxxxx]
> Sent: miércoles, 28 de julio de 2004 10:49
> To: suse-security@xxxxxxxx
> Subject: [suse-security] 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
>
> --
> Check the headers for your unsubscription address
> For additional commands, e-mail: suse-security-help@xxxxxxxx
> Security-related bug reports go to security@xxxxxxx, not here

--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here