Skip to contentSkip to conversation

bad blocks and rebooting

DISCUSSION Subba Rao 3 participants 3 messages Oct 3, 2001 – Oct 4, 2001

lore
Share & tools
lore

Subba Rao

author
#0 lore raw

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.

Signature · 6 lines
Subba Rao
[email protected]                     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
#1 lore raw
Quoted 5 lines · Subba Rao

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.

Signature · 1 line
Ignacio Vazquez-Abrams  <[email protected]>
#2 lore raw
In reply to Subba Rao
Quoted 5 lines · In article <[email protected]> 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