Filesystem could not be mounted

  • Magnar

    Magnar - 2010-10-11


    After a OS (Win XP) breakdown Portable Ubuntu won't start. The error message I get is as follows:

    mountall: mount   terminated with status 1
    mountall: Filesystem could not be mounted:
    ata_id: unable to open '/dev/.tmp-block-22:0'

    fsck from util-linux-ng 2.16
    WARNING: bad format on line 19 of /etc/fstab
    /dev/cobd0: clean, 153070/639584 files, 979323/2560000 blocks
    One or more of the mounts listed in /etc/fstab cannot yet be mounted:
    (ESC for recovery shell)
    /: waiting for /dev/cobd0
    /tmp: waiting for (null)
    : waiting for -e

    Anyone got a solution? That would be greatly appreciated!


  • Anonymous

    Anonymous - 2010-11-20

    This seems to happen to me in case of a bad (not-clean) shutdown.

    1. Press ESCAPE
    2. mount -o remount,rw /
    3. nano /etc/fstab
    And then delete the "-e" and the beginning of a line, just after cofsX… not sure how this "-e" came here…

    Hope this helped

  • Kitty Draper

    Kitty Draper - 2010-11-30

    This actually happens for me on EVERY shutdown.  I found the source of this random -e showing up, however - a shutdown script that's misbehaving.  Here are the full steps to solve this problem, starting from the very beginning:  (Steps 1-6 are a more detailed explanation of the above, so if you've done those already, just skip to step 7.)

    1. Look for the pubuntu icon in your task bar, right click it, and click restore
    2. In the terminal that pops up, press ESCAPE
    3. type: mount -o remount,rw /
    4. type: nano /etc/fstab
    5. delete the "-e" at the beginning of a line, just after cofsX.
    6. Press Ctrl+X, press Y, and press ENTER
    7. type: nano /etc/init.d/
    8. replace the first like (#! /bin/sh) with #! /bin/bash
    (/bin/sh doesn't handle echo -e properly)
    9. Repeat step 6
    10. type: reboot

  • Kitty Draper

    Kitty Draper - 2010-11-30

    Excuse my error - this is an init script, not a shutdown script.  As evidenced by it being in init.d.


Log in to post a comment.