Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Installation - Getting started with Red Hat Linux
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
System keeps dropping into shell.

System keeps dropping into shell.

2005-06-27       - By Ong Ying Ying

 Back
Reply:     1     2     3     4     5  

It didn't say that. Anyway, I've tried fsck using different hda number
but it didn't work.

Instead, it said that fstab did not contain fsck passno field. (1st
warning shown). I guess it then tried to fsck for me, stating
fsck.ext2/ :
Then it said "The superblock could not be read or does not describe a
correct ext2 filesystem ... try running e2fsck with alternate superblock :
  e2fsck -b 8193 <device>
I've tried e2fsck like stated on screen with different hda. How many
superblocks are there? I'll check the different hda starting blocks
again but I doubt it will work. What if the filesystem is using ext3?

What error report? I know dmesg but it is in /var/log which is empty.

YYOng


Alfred Hovdestad wrote:

> It sounds like your system is detecting a file system error which the
> boot-up check cannot repair.  It should say something like:
>
> fsck /dev/hda1
>
> where /dev/hda1 is where your / or /boot partition is mounted.  If you
> type the command as shown when you drop down to the shell, you should
> be able to repair the filesystem.  If you can post the error reported
> from another computer, it should be easier to analyze your problem
> (unless your hard drive died).
>
>    Alfred Hovdestad
>


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Earn $52 per hosting referral at Lunarpages.