bad blocks and rebooting

bad blocks and rebooting

[Subba Rao]

Hello

I have a system setup as a black box. If the system is powered
off accidentally, and upon powering on the system keeps rebooting 
after trying to do the file system consistency check. The file 
system message is to run "ef2fsck -v -y <partition>. Is there
anyway to force this check at lilo prompt? 

Thanks for any help.
-- 

Subba Rao
subba9@home.com                     http://members.home.net/subba9/
OpenPGP/GPG public key ID CCB7344E

 => Time is relative. Here is a new way to look at time. <=
http://www.smcinnovations.com

Re: bad blocks and rebooting

[Ignacio Vazquez-Abrams]

On Wed, 3 Oct 2001, Subba Rao wrote:

> I have a system setup as a black box. If the system is powered
> off accidentally, and upon powering on the system keeps rebooting
> after trying to do the file system consistency check. The file
> system message is to run "ef2fsck -v -y <partition>. Is there
> anyway to force this check at lilo prompt?

That's what journaled filesystems like ext3, ReiserFS, XFS, and JFS are for.

-- 
Ignacio Vazquez-Abrams  <ignacio@openservices.net>

Re: bad blocks and rebooting

[Bernd Eckenfels]

In article <20011003134423.A28512@home.com> you wrote:
> I have a system setup as a black box. If the system is powered
> off accidentally, and upon powering on the system keeps rebooting 
> after trying to do the file system consistency check. The file 
> system message is to run "ef2fsck -v -y <partition>. Is there
> anyway to force this check at lilo prompt? 

You can modify the init scripts to search for an init arg. Most init scripts
check for /forchecheck. For an embedded box it is MUCH better to have the
filesystem readonly or at least use a journaled FS.

Greetings
Bernd