Find the answer to your Linux question:
Results 1 to 5 of 5
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    Boot problem with LVM

    About a week and a half ago, I installed FC4 on a new hard drive. Actually, I'm now dual booting Linux & WinXP (using GRUB.) - and I've booted both, successfully, since installing, but today I got a new error message booting Linux:

    Checking filesystems
    fsck.ext3: permission denied while trying to open /dev/VolGroup00/LogVol00

    I have no idea what I could have done since my last successful Linux boot that could be causing problems. Any suggestions?


  2. #2

    I'm having the exact same problem

    I'm having the exact same problem: "fsck.ext3: Permission Denied while trying to open /dev/VolGroup00/LogVol00"

    If you search for "fsck.ext3: Permission Denied while trying to open /dev/VolGroup00/LogVol00", in quotes, on google, and then limit your results to only -english- results, there is only one result. On the whole Internet, apparently. Someone please help us.

    Note: I later found this German Page:

    Anyway, try this:
    From your recovery shell, type:
    mount -o remount,rw /dev/VolGroup00/LogVol00
    The run
    vi /etc/fstab

    Change your fstab entry that looks like
    /dev/VolGroup00/LogVol00 / ext3 defaults 1 1
    /dev/VolGroup00/LogVol00 / ext3 defaults 0 0

    Save the file, exit vi, and type "exit" in your rescue shell.

    It fixed my computer. Apparently, it just stops fsck from running.

    - Thanks, German Guys!

  3. #3
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    - Thanks, German Guys!
    HA! thats funny.
    And just FYI, changing the fstab didn't stop fsck from running, it just doesn't care about that drive anymore.
    Next time you have this problem, try using
    fsck -f /dev/hda or /dev/sda, whatever your disk is.
    I don't use VolumeGroups so I'm not sure if this will work right. And another thing, you need to unmount the disk before you attempt to repair it.
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  4. $spacer_open
  5. #4


    Oh, I did try "fsck -f" first, but, it didn't stop the error from occurring on boot-up. It found no errors on my drives, but, when the system tried to fsck the disk during boot-up, for some reason, fsck doesn't have read/write permissions on the LVM Volumes.

  6. #5
    Linux User
    Join Date
    Aug 2006
    Croydon, PA
    Try going into the system as "single user mode" init 1.
    Then try fsck -f -y /dev/VolGroup00/LogVol00
    Good Luck,

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts