Thanks, Mark. I will try the fsck -c from the rescue disk. There is nothing wrong with the rescue disk. I hae two identical systems, side-by-side. I had to use the rescue disk on the second system to change the inittab entry to 1. I needed to update the NVIDIA driver on the second system. chroot appeared on that system. chroot did not appear on the first system because the system said something like it couldn't find all the system partitions. On Wed, Oct 16, 2013 at 12:47 PM, mark <m.roth@xxxxxxxxx> wrote: > On 10/16/13 12:36, Doll, Margaret Ann wrote: > >> This is a RedHat server 6.4 >> >> When I tried to reboot the system, it comes up as readonly. See the >> attached file with more details. >> >> I tried to use the installation disk to recover the system, but again the >> chroot command is not available and /mnt/sysimage comes up readonly. >> >> Is there a simple way to fix the problem? Luckly all the data in /home, >> /tycho-1 and /raid seem to be ok. >> >> > Hi, Margaret, > > First, the chroot command is always available in the rescue mode; if > it's not, then something's wrong with your media. > > Second, if it's coming up in readonly, then this *very* strongly > suggests you've got a drive error, and that would be on the root > filesystem. Boot off of rescue, and fsck -c (check for bad blocks) -y (yes > to all fixes) on /boot and / partitions. > > Then build a new /boot and /. > > mark > > > -- > "First they ignore you, then they laugh at you, then they fight you, then > you win." > "Strength does not come from physical capacity. It comes from an > indomitable will." -Gandhi- > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@**redhat.com<redhat-list-request@xxxxxxxxxx> > ?subject=unsubscribe > https://www.redhat.com/**mailman/listinfo/redhat-list<https://www.redhat.com/mailman/listinfo/redhat-list> > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
