Member Avatar for kwsiu1982

I am using RedHat 9 , but it cannot boot .

Can anyone teach me how to solve it ? :cry:

It has not any respond at this moment each time. the message is as below:


EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel mamory: 132k freed
INIT: version 2.84 booting
Settomg defai;t fpmt (latarcyrheb-sun16): [ ok ]
Welcome to /etc/rc.d/rc.synsinit: line 70: 35 Segmentation fault LC_ALL=C grep
-q "Red Hat" /etc/redhat-release Red Hat Linux
Press 'I' to enter interactive startup.
Mounting proc filesystem: [failed]
/etc/rc.d/rc.sysinit: line 90: 42 Segmantation fault LC_ALL=C grep -q .initrd
/proc/mounts
Confuguring kernel parameters: Error: /proc must ve mounted
To mount /proc at boot you need an /etcfstab line like:
/proc /proc proc defaults
In the meantime, mount /proc /proc -t proc
[failed]
Setting clock (localtime): Fi Jan 23 09:06:35 MST 2004 [ ok ]
Loading default keymap (us): [ ok ]
Setting hosname mgserver.net: [ ok ]
/etc/rc,d/rc.sysinit: line 182: 65 Segmentation fault LC-ALL=C grep -iq"nousb"
/proc/cmdline 2>/dec/null
/etc/rc,d/rc.sysinit: line 182: 67 Segmentation fault LC-ALL=C grep -q"usb"
/proc/devices 2>/dev null

Thx all very muxh ~~~~~~~~
Ivan

  • 9 Contributors
  • 8 Replies
  • 375 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by John A

Dani AI

Generated

The pattern of early init-script segmentation faults reported by and echoed by others points away from the scripts themselves and toward either damaged userland binaries/shared libraries (glibc/coreutils), filesystem/RAID corruption, or bad memory. Following the rescue/live-boot path mentioned by and allows inspection without making risky live-system changes; the goal is to confirm which of those three classes of failure is happening and then repair or recover data.

A practical rescue checklist (from a live or install-rescue shell, with devices adjusted to the actual system):

# mount the installed root and change root
mkdir /mnt/sysimage
mount /dev/sda1 /mnt/sysimage     # adjust device
chroot /mnt/sysimage /bin/bash

# quick binary checks
file /bin/grep
ldd /bin/grep
rpm -qf /bin/grep
rpm -V coreutils glibc

Those checks reveal whether /bin/grep is a valid ELF, whether its shared libraries are present, and whether RPM sees altered files. If coreutils or glibc are shown as corrupted, reinstall those packages from the original media while chrooted rather than copying .so files in place.

Parallel hardware/filesystem checks are important because a failing disk or controller can silently corrupt files. From the rescue environment, unmount target partitions and run e2fsck on ext partitions and examine SMART/controller logs (smartctl or RAID utilities). If intermittent hangs or many failures are present, long memory tests (memtest) are also appropriate, as noted earlier by .

If repair looks risky, priority must be a full data snapshot (home, /etc, databases) before attempting in-place glibc/coreutils replacement; incorrect replacement can leave the system unbootable. When recovery is complete, rebuilding the system from known-good media and restoring data is often the safest final option.

Recommended Answers

All 8 Replies

Member Avatar for oberoc

Ok, first thing is:

-Try to boot up using single user mode. If you are using grub, I think the keystroke are e (for edit) and the append single onto the end.
-If that doesn't work, grab a copy of knoppix and mount the drive after knoppix boots up. If you need further need, give me a shout.

-Tino

I am using RedHat 9 , but it cannot boot .

Can anyone teach me how to solve it ? :cry:

It has not any respond at this moment each time. the message is as below:


EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel mamory: 132k freed
INIT: version 2.84 booting
Settomg defai;t fpmt (latarcyrheb-sun16): [ ok ]
Welcome to /etc/rc.d/rc.synsinit: line 70: 35 Segmentation fault LC_ALL=C grep
-q "Red Hat" /etc/redhat-release Red Hat Linux
Press 'I' to enter interactive startup.
Mounting proc filesystem: [failed]
/etc/rc.d/rc.sysinit: line 90: 42 Segmantation fault LC_ALL=C grep -q .initrd
/proc/mounts
Confuguring kernel parameters: Error: /proc must ve mounted
To mount /proc at boot you need an /etcfstab line like:
/proc /proc proc defaults
In the meantime, mount /proc /proc -t proc
[failed]
Setting clock (localtime): Fi Jan 23 09:06:35 MST 2004 [ ok ]
Loading default keymap (us): [ ok ]
Setting hosname mgserver.net: [ ok ]
/etc/rc,d/rc.sysinit: line 182: 65 Segmentation fault LC-ALL=C grep -iq"nousb"
/proc/cmdline 2>/dec/null
/etc/rc,d/rc.sysinit: line 182: 67 Segmentation fault LC-ALL=C grep -q"usb"
/proc/devices 2>/dev null

Thx all very muxh ~~~~~~~~
Ivan

Member Avatar for alc6379

Why did this happen? Did you rebuild your kernel or something?

It looks like what happened is that /proc didn't mount, which screwed up a lot of stuff. What changes have you made to the system recently?

Member Avatar for kc0arf

Hello,

Agree with Alex. The crux of the problem is that /proc did not mount properly. Or, if you re-compiled, did you not move the initrd (ram disk) file over too? Do you have multiple choices in grub / lilo that you can boot another kernel successfully?

You might need that floppy disk that you should have made during the RH install.

Christian

Member Avatar for brian89gp

Does anybody know the cause of this?

I have a friend that is having the exact same issue. He was using Webmin to modify Shorewall settings for about 2 hours. All of a sudded Webmin starts to flake out (disconnect, not respond, not save stuff, etc) and when he tries to restart it it refueses to stop. I go in and do a kill command on it and restart it, its still acting strange. Go down for a restart and it freezes on trying to stop webmin, when it tries to restart it gets the exact same messages as above on both kernal boot options. BTW, this is on a Dell Poweredge 2300 with RedHat 9, I ran a farily extensive test on the hard drives and raid card so I'm fairly certain that it isn't a hardware failure.

Member Avatar for eid

Hi,

I am facing the exact same problem.

Has anyone been able to fix it?

Appreciate your help.

Regards,

Ashraf

Member Avatar for fbifido

my system is:
Dell PowerEdge 6600 Bios Rev.A12

on the case display, it say "DRIVE FAIL

I am also using RedHat 9 , but it cannot boot .

Can anyone teach me also on how to solve it ?

-[message]------------------------------------------

EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel mamory: 244k freed

-----------------------------------------------------

and the system just hang.

after pressing alt+ctrl+del, i get this message:

md: stopping all md devices.

after that i have to press the power button.


can someone help me please.

Member Avatar for Khayrul

I am using RedHat 9 , but it cannot boot .

Can anyone teach me how to solve it ? :cry:

It has not any respond at this moment each time. the message is as below:


EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel mamory: 132k freed
INIT: version 2.84 booting
Settomg defai;t fpmt (latarcyrheb-sun16): [ ok ]
Welcome to /etc/rc.d/rc.synsinit: line 70: 35 Segmentation fault LC_ALL=C grep
-q "Red Hat" /etc/redhat-release Red Hat Linux
Press 'I' to enter interactive startup.
Mounting proc filesystem: [failed]
/etc/rc.d/rc.sysinit: line 90: 42 Segmantation fault LC_ALL=C grep -q .initrd
/proc/mounts
Confuguring kernel parameters: Error: /proc must ve mounted
To mount /proc at boot you need an /etcfstab line like:
/proc /proc proc defaults
In the meantime, mount /proc /proc -t proc
[failed]
Setting clock (localtime): Fi Jan 23 09:06:35 MST 2004 [ ok ]
Loading default keymap (us): [ ok ]
Setting hosname mgserver.net: [ ok ]
/etc/rc,d/rc.sysinit: line 182: 65 Segmentation fault LC-ALL=C grep -iq"nousb"
/proc/cmdline 2>/dec/null
/etc/rc,d/rc.sysinit: line 182: 67 Segmentation fault LC-ALL=C grep -q"usb"
/proc/devices 2>/dev null

Thanks to All

Khayrul

Member Avatar for John A

Several possible reasons:

  • Your RAM could be corrupted. Test it with memtest86.
  • The program 'grep' is damaged. You could reinstall it and most likely get rid of the problem (by booting off a rescue CD), but chances are that other files are also damaged. I would reinstall from scratch to make sure.
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.