problem mounting drives after install -please help!

Bill Maltby LFS Related lfsbill at wlmcs.com
Sun Aug 18 15:33:14 PDT 2002


On Sun, 18 Aug 2002, Joe wrote:

> K let me expand on this: I used a redhat recovery disk and chrooted into my
> LFS. If i umount /var for instance then try to mount it again, i get "mount:
> block device /dev/hda8 is write-protected, mounting read-only \ mount:
> cannot mount block device /dev/hda8 read-only"
> 
> ARGH!!! I'm so close!!
> 
> 
> "Joe" <Joe at joe.joe> wrote in message
> news:ajos31$ln5$1 at shadowfax.linuxfromscratch.org...
> > I finished the whole LFS install finally, and i rebooted. The kernel loads
> > up, then the system tells me there are critical errors on my /boot
> > partition. I turned off filesystem checking and it now gets past that
> part,
> > but when it tries to load the other partitions i get something like:
> > "/dev/hda6 is write protected, trying to mount read-only" then "read-only
> > mount failed." it does this for all the other partitions. What the hell?
> Is
> > it obvious to one of you what I did? here is my /etc/fstab. I have tried
> > mounting as ext2 as well with the same results.
> >
> > /dev/hda1    /boot    ext3    noauto    1 1
> > /dev/hda2    none    swap    pri=1        0 0
> > proc            /proc    proc    defaults    0 0
> > devpts        /dev/pts    devpts    gid=4,mode=620 0 0
> > /dev/hda5    /        ext3        nodev    0 0
> > /dev/hda6    /usr    ext3        nodev    0 0
> > /dev/hda7    /var    ext3        nodev    0 0
> > /dev/hda8    /tmp    ext3        nodev,noexec,noatime    0 0
> > /dev/hda9    /home    ext3     nodev,nosuid    0 0
> >
> >

I haven't used etx3 yet, but an obvious question: is ext3 support
in that kernel that is running? /usr/src/linux/.config should have
CONFIG_EXT3_FS enabled.

Secondly, I don't see the word "defaults" in your options. I've never
bothered to see what happens if it's not there. Maybe...?


Bill Maltby
billm at wlmcs.com

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-support' in the subject header of the message



More information about the blfs-support mailing list