how do i disable that annoying start up test??

[Guest william198312]

i know theres gotta be a way its driving me insane on my friends comp it takes his POS 10 minutes to load with mandrake...

 

it takes maybe about 30 seconds on my but it would be even faster if i could disable the test.

 

me and him would benefit from it..

[liquidzoo]

Which test are you referring to?

[Guest william198312]

when you first boot up mandrake.

 

you get these messages

 

checking file modules

checking dependices

checking file sysyem

checking....clean file system.

 

that's test i speak of

[liquidzoo]

Um, I don't believe you can disable it. You can turn off the verbose mode for the boot in MCC so that you don't see the messages. Someone will have to help me out on exactly which steps to take to do this. I'm not sure at all. I believe it's part of the lilo config, but I could be wrong.

[bvc]

If you use quota adjust accordingly and use at your own risk. It can't really hurt. There's always rescue mode commandline to undo :wink: This isn't really necessary anyway is it? Anyone? Isn't fsck JUST for ext2?....who uses that, except for the /boot partition, and I have yet to figure that one out either :roll: I use reiserfs so fsck is absolutely useless to me, and since this has always gotten on my nerves, I thought I'd poke around a bit. It's dirty, aru probably knows a much better way, but now all I get is the message

Checking filesystems

 

#comment out all fsck's

/etc/rc.d/rc.sysinit

#if [ "$FSCKOPTIONS" ]; then

#	fsckoptions="$FSCKOPTIONS"

#    else

#	fsckoptions=

#fi

#

#

#if [ -f /forcefsck ]; then

#	fsckoptions="-f $fsckoptions"

#elif [ -f /.autofsck ]; then

#        quiet off

#	gprintf "Your system appears to have shut down uncleanlyn"

#	AUTOFSCK_TIMEOUT=5

#	[ -f /etc/sysconfig/autofsck ] && . /etc/sysconfig/autofsck

#	if [ "$AUTOFSCK_DEF_CHECK" = "yes" ]; then

#  AUTOFSCK_OPT=-f

#	fi

#

#	if [ "$PROMPT" != "no" ]; then

#  if [ "$AUTOFSCK_DEF_CHECK" = "yes" ]; then

# 	 if /sbin/getkey -c $AUTOFSCK_TIMEOUT -m "Press N within %d seconds to not force file system integrity check..." n; then

#    quiet off

#    AUTOFSCK_OPT=

# 	 else

#           echo

#           quiet on

# 	 fi

#  else

# 	 if /sbin/getkey -c $AUTOFSCK_TIMEOUT -m "Press Y within %d seconds to force file system integrity check..." y; then

#           quiet off

#    AUTOFSCK_OPT=-f

# 	 else

#    echo

#           quiet on

# 	 fi

#

#  fi

#  echo

#	else

#  # PROMPT not allowed

#  if [ "$AUTOFSCK_DEF_CHECK" = "yes" ]; then

# 	 gprintf "Forcing file system integrity check due to default settingn"

#  else

#  fi

#	fi

#	fsckoptions="$AUTOFSCK_OPT $fsckoptions"

#fi

#

#if [ "$BOOTUP" = "color" ]; then

#	fsckoptions="-C $fsckoptions"

#else

#	fsckoptions="-V $fsckoptions"

#fi

#

#Fsck()

#{	initlog -c "/sbin/fsck $*"

#	rc=$?

#	if [ $rc -ne 0 -a $rc -ne 1 ]; then

#     quiet off

#     gprintf "Failed to check filesystem. Do you want to repair the errors? (Y/N)n"

#     gprintf "(beware, you can lose data)n"

#     read answer

#

#     if strstr "yY" "$answer"; then

#  initlog -c "/sbin/fsck $* -y"

#  rc=$?

#     fi

#	fi

#}

#

#_RUN_QUOTACHECK=0

#ROOTFSTYPE=`awk '/ / / && ($3 !~ /rootfs/) { print $3 }' /proc/mounts`

#if [ -z "$fastboot" -a "X$ROOTFSTYPE" != "Xnfs" ]; then

#

#

#	quiet off       gprintf "Checking root filesystemn"

#	Fsck -T -a $fsckoptions /

#

#	if [ "$rc" = "0" ]; then

#  echo_success

#  echo

#	elif [ "$rc" = "1" ]; then

#         echo_passed

#  echo

#       fi

#

#       # A return of 2 or higher means there were serious problems.

#	if [ $rc -gt 1 ]; then

#     echo_failure

#     echo

#     echo

#     gprintf "*** An error occurred during the file system check.n"

#     gprintf "*** Dropping you to a shell; the system will rebootn"

#     gprintf "*** when you leave the shell.n"

#

#     PS1="(Repair filesystem) # # "; export PS1

#     sulogin

#

#           gprintf "Unmounting file systemsn"

#     umount -a

#     mount -n -o remount,ro /

#           gprintf "Automatic reboot in progress.n"

#     reboot -f

#	elif [ "$rc" = "1" ]; then

#  _RUN_QUOTACHECK=1

#	fi

#fi

#

#quiet on

#

#progress 4

#

## Possibly update quotas if fsck was run on /.









#Fsck -T -R -A -a -t noopts=loop $fsckoptions











#Fsck -T -R -A -a -t opts=loop $fsckoptions

 

change line 899 (or about) from

#rm -f /fastboot /fsckoptions /forcefsck /.autofsck /halt /poweroff /etc/killpower

to

rm -f /fastboot /halt /poweroff /etc/killpower

 

 

#comment it all out.

/etc/sysconfig/autofsck

# -*- Mode: sh -*-

# $Id:$



# Specify here how many seconds we wait for timeout

#AUTOFSCK_TIMEOUT=5



# Specify if we do automatic fsck.

#AUTOFSCK_DEF_CHECK=no



# Specify how many seconds we wait for mounting crypto.

#AUTOFSCK_CRYPTO_TIMEOUT=5

 

 

As for as the other checks?.....you need them....your sys wouldn't run very good without them, or at all. Of course it won't run at all if you never repair a damaged filesys after a bad shutdown either :wink: You can edit the scrips to get rid of the messeges though. But don't you want to know if all your modules load?

[theYinYeti]

Just a little check... What filesystem did you use at install-time? Ext2, Ext3, ReiserFS, XFS, JFS...

 

Yves.

[dalek]

I bet if he knew what went on behind the scenes with windoze it would understand that all OS's have to check and start services. Even windoze does that. You just don't get to see it.

 

Well, with windoze it actually has to do it more often, because of the crashes and frequent reboots, ya know. :lol: :lol:

 

You may be able to cut off services that you don't need and speed up the boot process. That's the best way to handle the problem. Making the screen not show it will not make it boot faster.

 

My crappie ol two cents worth.

 

:D :D :D

[Gowator]

William

Like others have said, mainly you need those checks. Windows does them but hides them, linux prefers to inform you.

 

One way to speed up a boot is to remove unneccassry services. I know this wasn't what you asked but it will have the same effect... booting faster.

 

If you aren't using a web-server, mysql etc you can cut down on boot time and free memory by using drakxservices (in the MCC) to disable them at boot.

Others can be started on demand so they only start when needed.

 

Personally I prefer using linuxconf (but MCC works too or the good ole CLI)

 

As mentioned you can also put a splash screen over them and not see it like Windows does!

 

maybe post your ruinning services and let us have a look what you can disable.

[Cannonfodder]

What are the specs for the POS computer in terms of speed/memory. Some other ideas... do you have dma enabled for your hard drive? Could there be some service that is not setup correctly and is thrashing or timing out? 10 min's seems extreme in any case..

[bvc]

The only thing I've ever know to take an extremely long time at boot is a misconfigured ethernet card/dhcp network. Improperly configure, my network can hang me for 2 or 3 minutes at boot. Things like dma/mem etc....are not going to cause this long of a delay. Even -no dma + I/O errors and init repawning too fast disabled for 5 minutes is just 5 minutes, and I've never seen the kernel recover from this not to mention you get a message saying this is what's happening.

 

Yes, specs would be nice :)

[Guest william198312]

his pc specs

 

amd k6 500 mhz

192 mb pc 66 ram

5.0 gig hd

 

BTW i forgot to mention his motherboard is a Comcrap..

 

i think thats whats causing the problems... :D

 

i am glad mine aint like that

[Gowator]

unless its the network / dhcp like bvc said something is seriously wrong with the config.