Re: System only boots to read-only

Abhishek Tyagi <[email protected]>
Newsgroups gmane.linux.redhat.general
Message-ID <CAPtzR8FZVEOp-b=tyxv1sVzn5+VWG4fP7yXm72xoF65PxhLh-w@mail.gmail.com>
mount -n -o remount,rw /

This will remount root as read-write and you should be able to edit the
fstab. After you finish, do a control-d to reboot.


On Thu, Oct 17, 2013 at 12:53 AM, Doll, Margaret Ann <
[email protected]> wrote:

> I can
>
> fsck.ext4 /dev/sdan  while the compute is up readonly where "n" is a
> variety of partitions.
> Except for /dev/sda6.  I am assuming that this partition contains the
> Volume group of / and swap.
>
> lvdisplay, vgdisplay and pvdisplay  give me the error message
>
> files base locking initialization failed.
>
> If I come up with the repair cd, fsck -c on any of the devices fails.
>
>
> On Wed, Oct 16, 2013 at 2:16 PM, mark <[email protected]> wrote:
>
> > On 10/16/13 14:10, Doll, Margaret Ann wrote:
> >
> >> Sorry.   I moving between buildings.  Below is the data.
> >>
> >> df
> >> /dev/mapper/VolGroup00-**LogVol00        34%    /
> >> tmpfs                     0%    /dev.shm
> >> /dev/sda3                45%    /boot
> >> /dev/sda5                92%    /home
> >> /dev/sdb1                 1%    /tycho-1
> >> /dev/sde1                37%    /raid
> >>
> >> I had to mount everything except / by hand
> >>
> >> service network start
> >> Bringing up loopback interface:
> >> Bringing up interface eth0:
> >> Determining IP information for eth0...Can't create
> >> /var/run/chclient-eth0.pid:
> >>              Read-only file system.
> >> ...
> >>
> >> fdisk /dev/sda
> >> p
> >> /dev/sda1    1    5    40131    de    Dell Utility
> >> /dev/sda2    6    789    6290480  c    W95 FAT32 (LBA)
> >> /dev/sda3    790    815     204800    83    Linux
> >> Parition 3 does not end on cylinder boundary.
> >> /dev/sda4    815    121602    970218496 5    Extended
> >> /dev/sda5    815      1337      4194304 83    Linux
> >> /dev/sda6    1338    121602    966022144 8e    Linux LVM
> >>
> >> mount /dev/sda6  /tmp
> >> mount:  unknown filessystem type 'LVM2_member'
> >>
> >
> > Ok, the rescue doesn't seem to understand LVM2.
> >
> >
> >> fstab
> >> /dev/mapper/VolGroup-LogVol100  /        ext4
> >> UUID=f1fa....466        /boot    ext4
> >> UUID=13a6e...eb5        /home    ext4
> >> /dev/mapper/VolGroup00-**LogVol101 swap    swap
> >> tmpfs
> >> devpts
> >> sysfs
> >> proc
> >>
> >> /dev/sdb1            /tycho-1 ext4
> >> /dev/sdd1            /raid    ext4
> >>
> >>  Ahhhh.... when you boot via rescue, or if you've brought it up
> manually,
> > check the UUID of the drives. If they've changed, both /etc/fstab *AND*
> > /boot/grub/grub.conf need to be changed.
> >
> > Or you can use e2label to label the filesystem, and then change
> /etc/fstab
> > to
> > LABEL=/boot     /boot...
> > etc.
> >
> >
> >         mark
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request@**redhat.com<
> [email protected]>
> > ?subject=unsubscribe
> > https://www.redhat.com/**mailman/listinfo/redhat-list<
> https://www.redhat.com/mailman/listinfo/redhat-list>
> >
> --
> redhat-list mailing list
> unsubscribe mailto:[email protected]?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>



-- 
Abhishek tyagi
[email protected]
09873924446
-- 
redhat-list mailing list
unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.