Find the answer to your Linux question:
Results 1 to 5 of 5
Hi all. I am running DSL in a VM using VirtualBox that has some custom software loaded in it so we can send it out to customers on a CD. ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2009
    Posts
    2

    Automatically run FSCK at boot?


    Hi all. I am running DSL in a VM using VirtualBox that has some custom software loaded in it so we can send it out to customers on a CD.

    My problem is that when I close the VM the way a novice computer user will, which is basically pulling the plug on the VM and then restart the VM, I get a message that FSCK has failed and I need to repair it manually and reboot. Once I manually mount the drive and then run fsck and reboot, it works fine.

    I am trying to find a way to have linux run mount the drive and run fsck at boot every time whether or not it is needed, in order to fix this issue so it never happens again.

    Is that possible?

    Thanks,
    REM2500

  2. #2
    Linux Guru Jonathan183's Avatar
    Join Date
    Oct 2007
    Posts
    3,043
    Welcome to the forums REM2500

    I don't think fsck should be run on a mounted partition ... maybe better to get the end user to shutdown the VM correctly

  3. #3
    Just Joined!
    Join Date
    Mar 2009
    Posts
    2
    I wish I could have them shut down the VM properly, but that's just not an option. They are not even logging into Linux on the VM...

    What I am doing is setting up a custom web app to run inside the VM that they can hit the app with their web browser on their PC. Once they are done, all they do is hit the X on the VM window and it closes. Then when the VM is restarted, I get the error described above...

    Thanks

  4. #4
    Linux Guru bigtomrodney's Avatar
    Join Date
    Nov 2004
    Location
    Ireland
    Posts
    6,133
    How about a workaround? If it's only running in a VM, maybe include a shutdown button within the webapp?

  5. #5
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,756
    The best protection against corruption from a hard poweroff is a natively-journaled filesystem. With that in place, the log is replayed automatically after a power loss.

    My own preference is reiserfs (for / or small files) and XFS (for filesystems with large files.)

    * EXT3 is not a natively-journaled filesystem.

Posting Permissions

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