On Sat, 10 Aug 2002, Geetha Shamanna wrote: > I use Redhat 7.1, which did not come with a Linux rescue floppy. The Red Hat manuals, which are on the web for use in your browser (and also downloadable for off line use), tell how to use your install disk as a rescue disk. If you have a full set of install CD's, including the documentation CD, you probably can access the manuals from the doc CD. I think the speakup site tells you how to download a modest amount of stuff, and modify the the install floppy (or CD, if you have a CD writer), so as to speech enable them. Hopefully, the rescue mode would work with the speech modifications. Can someone that runs speakup (I don't) confirm this, or suggest an alternative? The reason you will need a speech enabled rescue disk or other boot scheme with speech through speakup from the start is this: The Red Hat boot procedure normally automatically repairs the filesystem when shut down improperly (the "fsck" check and repair command mentioned in other posts is built into the boot procedure, and the system knows when it needs to be done). What happened to you probably means that it was unable to make the necessary repairs, and needs more intelligent intervention. With new users, this usually means that the user has repeatedly cut power or reset the computer without a proper shutdown, so that extensive filesystem damage has accumulated. After you have fixed the filesystem problem, you will need to add some beeps to the halt script, /etc/rc.d/init.d/halt, at the end; a line like this should do it: echo -e "\a\c"; sleep 1; echo -e "\a\c"; sleep 1; echo -e "\a\c" which will give you 3 beeps, spaced one second apart (modify pattern to taste). That way you can just do a ctrl-alt-del from text mode, which runs the shutdown command for you, and wait till you hear the beeps before resetting or powering off (or just listen for sounds of the reboot, if your machine makes distictive enough noises). Now, concerning the repair problem: you will possibly need to look around for some instruction in the manuals, or a HOWTO on what to do in such a situation. I have run linux and Red Hat for years, with many power outages that forced an improper shutdown, but the damage has always been fixed with no problem, so I have no real experience with this situation: the linux filesystems and the fsck procedure are very robust, so that automatic repairs are virtually always successful. Most people here are likely in the same boat and can't give much specific help. If you don't have much data to lose (your linux system is a recent install, with little modification), you might find it easier to just re-install, or better yet, upgrade to Red Hat 7.3 (see the blinux FAQ for info on how to get very inexpensive upgrade/install CD-ROM disks). Alternatively, if no one here can tutor you through this, and you don't find some HOWTO or other instruction (search on, say, http://www.tldp.org/ -- the Linux Documentation Project web page, or http://www.google.com/linux ), try posting to one of the really high traffic linux news groups, like comp.os.linux.setup (be prepared to search for relevant answers among hundreds of other posts each day -- use a news reader that makes this kind of keyword searching easy). Hope this helps, LCR > At 06:41 PM 10/08/02 +1000, you wrote: > > > >This is caused normally by a fault while scanning the > >filesystem. > > > >If a ctrl-d or typing in your root pass doesn't get you to a > >prompt, you might like to boot from a linux rescue floppy, > >like the one that comes with debian and repair your filesystem > >manually. > > > >You do this by typing > > > >e2fsck /dev/hda2 > > > >replacing /dev/hda2 with the partition that your system is > >reporting faults with. > > > >You can find out which partition is damaged on the screen just > >before the message you described in your email. > > > >This is generally caused by a system not shutting down > >correctly or something else that causes the integrity of your > >file system to become unstable. > >>From Mitchell > > > >----- Original Message ----- > >From: "Geetha Shamanna" <s_geetha@vsnl.com> > >To: <blinux-list@redhat.com> > >Sent: Saturday, August 10, 2002 6:43 PM > >Subject: Problem with booting into Linux > > > > > >> Hello all: > >> > >> I am very new to Linux and have been using it on and off for about a > >couple > >> of weeks now. > >> When I boot into Linux, I normally hear a prompt which indicates that my > >> synthesizer (doubletalk) has been found. I then key in my user > >information, > >> and start Emacspeak. At this point DoubleTalk starts speaking. I have had > >> no problem with this setup so far. > >> > >> However, when I booted into Linux this morning, I did not here the > >> "DoubleTalk found" prompt. Instead, the following error message appeared > >on > >> the screen: > >> "An error has occurred during the file system check, dropping you to a > >> shell. The system will reboot. When you leave the shell, give root > >password > >> for maintenance, or type ctrl-d for normal startup." > >> It does not however accept my root password. If I hit ctrl-d as suggested, > >> the system reboots. However, the same message appears again. I am unable > >to > >> figure out why this happened, or what needs to be done to set it right. -- L. C. Robinson reply to no_spam+munged_lcr@onewest.net.invalid People buy MicroShaft for compatibility, but get incompatibility and instability instead. This is award winning "innovation". Find out how MS holds your data hostage with "The *Lens*"; see "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html