{"id":275,"date":"2005-12-05T18:25:00","date_gmt":"2005-12-06T02:25:00","guid":{"rendered":"https:\/\/kb.terabyteunlimited.com\/kb-articles\/unable-to-mount-linux-partition-in-bootit-bm-image-for-dos-or-image-for-windows\/"},"modified":"2021-09-03T15:16:21","modified_gmt":"2021-09-03T22:16:21","slug":"unable-to-mount-linux-partition-in-bootit-bm-image-for-dos-or-image-for-windows","status":"publish","type":"lsvr_kba","link":"https:\/\/www.terabyteunlimited.com\/kb\/kb-articles\/unable-to-mount-linux-partition-in-bootit-bm-image-for-dos-or-image-for-windows\/","title":{"rendered":"Unable To Mount Linux Partition In BootIt BM, Image for DOS, or Image for Windows"},"content":{"rendered":"

When working with a Linux partition in BootIt BM, Image For Windows, Image For DOS, or Image for Linux, you may get one of the following error messages when attempting to perform an operation -- such as imaging, copying, sliding, or accessing Properties\/Details:<\/p>\r\n

\r\n

The 'data only' request failed because the file system could not be mounted<\/strong> <\/font><\/p>\r\n

Unable to mount the file system<\/font><\/strong><\/p>\r\n

Drive not ready<\/font><\/strong><\/p>\r\n <\/blockquote>\r\n

These error messages can occur for essentially two reasons:<\/p>\r\n

    \r\n
  1. The partition is not yet formatted <\/strong>(meaning there is no file system to mount). When a Linux partition is created in BootIt BM, it will not be formatted until that is later done from within Linux, or while installing Linux. BootIt BM does not format Linux partitions.

    <\/li>\r\n
  2. There was a problem found with the file system <\/strong>which prevented it from being safely mounted and accessed for the requested operation. One common reason for this is that the partition was not unmounted after it was last used (due to power failure, forced reset etc.). That will leave the clean\/not clean flag in the superblock set to 'not clean', which in turn will result in one of the above error messages. However, the error messages above can also be the result of other problems detected in the file system's superblock.
    <\/li>\r\n <\/ol>\r\n

    In the vast majority of cases,  the problems described in (2) above will be corrected by running the appropriate file system checker for the file system involved - which for Linux will typically be either Ext2\/Ext3\/Ext4 or ReiserFS. There are a couple of ways to go about doing that, depending on circumstances and preference:
    <\/p>\r\n

      \r\n
    1. Boot from an alternate Linux system and run the file system checker manually. <\/strong>This will work in all cases and is generally the safest way to proceed because you are assured of working under more controlled circumstances (because there will be no automatic file system checks on boot). Typically this means booting from a Live CD or DVD (such as Knoppix) or a floppy disk that contains the Linux file system utilities. Booting from a second Linux installation on the hard drive is another option, if available.

      <\/li>\r\n
    2. Boot Linux normally and let it run the file system checker automatically.<\/strong> This will work for any partition that is automatically mounted on boot and whose current status is 'not clean'. In that case, the Linux boot scripts (init scripts) will detect that status and automatically launch the appropriate file system checker to correct any problems found and restore the status to 'clean' (assuming all problems found can be fixed). The automatic check will not<\/strong> occur for any partition that is marked as 'clean' (even though it could still have problems) or any partition that is not automatically mounted on boot. Of course, in those cases you still have the option of running the file system checker manually after booting, assuming that the partition is one that is not required to be mounted. The root partition, for example, always needs to be mounted.


      <\/li>\r\n <\/ol>\r\n

      How To Run The File System Checkers Manually (requires root privileges)<\/font><\/strong><\/p>\r\n

        \r\n
      1. Make sure the partition is NOT mounted by running either the df<\/font><\/strong> command, or the mount<\/font><\/strong> command. Both commands will show you which partitions are currently mounted.

        <\/li>\r\n
      2. If the partition is mounted, you can attempt to unmount it with the umount  \/dev\/hdxx<\/font> <\/strong>command, where hdxx is the partition in question (such as hda1, hda2, etc.). Note that the spelling of this command is umount<\/em>, not unmount<\/em>. If the partition can not be unmounted, you will get a 'device is busy' error message -- in that case, it will be necessary to boot from an alternate Linux system, such as a Knoppix Live CD.

        Note:<\/strong> Depending on the version of Linux and the type of drive, sdxx<\/font><\/strong> may be used instead of hdxx<\/font><\/strong>. For example: \/dev\/sda1
        <\/font><\/strong>
        <\/li>\r\n
      3. Run the appropriate file system checker.

        For Ext2\/Ext3\/Ext4:   e2fsck  -f  \/dev\/hdxx<\/font>          <\/strong>(see additional notes below)
                                        e2fsck  -f  \/dev\/sdxx<\/font><\/strong>

        For ReiserFS:            reiserfsck  \/dev\/hdxx<\/font>         <\/strong>(see additional notes below)


        <\/li>\r\n <\/ol>\r\n

        Additional Notes For Working With Ext2\/Ext3\/Ext4 Partitions:<\/font><\/strong><\/p>\r\n

        e2fsck  \/dev\/hdxx<\/font><\/strong>  --  the basic command that will check the file system only if the clean\/not clean flag in the superblock indicates 'not clean'. Adding the -f<\/font><\/strong> option (as shown above) forces a check, even if the superblock status is 'clean'.<\/p>\r\n

        e2fsck -fn  \/dev\/hdxx<\/strong>  <\/font>--  the 'n<\/font><\/strong>' will cause the file system to be opened read-only and it will automatically answer no<\/em> to all prompts to fix problems. This can be used to determine the extent of the problems, without actually making any changes to the file system.<\/p>\r\n

        e2fsck -fy  \/dev\/hdxx<\/strong>  <\/font>--  the 'y<\/font><\/strong>' will cause an automatic answer of  yes<\/em> to all prompts to fix problems, instead of having to answer each prompt manually.

        tune2fs -l | less<\/strong>  <\/font>--  will display the superblock data, including the current clean\/not clean status. No changes to the file system will be made (the l<\/font><\/strong> is a lower-case L<\/font><\/strong>).


        <\/p>\r\n

        Additional Notes For Working With ReiserFS Partitions:<\/font><\/strong><\/p>\r\n

        reiserfsck  -y  \/dev\/hdxx<\/strong>  <\/font>--  the 'y<\/font><\/strong>' eliminates the need to type "Yes" to perform the check.<\/p>\r\n

        debugreiserfs  \/dev\/hdxx<\/strong>  <\/font>--  will display the superblock data, including the current clean\/not clean status. No changes to the file system will be made.
        <\/p>\r\n


        Additional Notes For Knoppix:<\/font><\/strong><\/p>\r\n

        When booting the Knoppix CD\/DVD, typing knoppix 2<\/font><\/strong> at the boot prompt will take you directly to a root console, without loading X Window desktop.<\/p>\r\n

        If you need (or want) to mount a partition from the root console, it is suggested that you first create a new directory and then mount the partition there as shown below. This ensures that you get the partition mounted with the mount options you want, without interference from the contents of \/etc\/fstab.<\/p>\r\n

        mkdir  \/mydirectory<\/strong> <\/font>                                   (creates directory)
        mount  \/dev\/hdxx  \/mydirectory<\/strong>                 <\/font>(mounts partition read-write)
        mount  -o ro \/dev\/hdxx  \/mydirectory<\/strong>         <\/font>(mounts partition read-only)
        umount  \/dev\/hdxx<\/strong>                                     <\/font>(unmounts partition)<\/p>","protected":false},"excerpt":{"rendered":"

        When working with a Linux partition in BootIt BM, Image For Windows, Image For DOS, or Image for Linux, you may get one of the following error messages when attempting to perform an operation — such as imaging, copying, sliding, or accessing Properties\/Details: The ‘data only’ request failed because the file system could not be […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"lsvr_kba_cat":[1805],"lsvr_kba_tag":[],"class_list":["post-275","lsvr_kba","type-lsvr_kba","status-publish","hentry","lsvr_kba_cat-shared-issues"],"_links":{"self":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba\/275","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/comments?post=275"}],"version-history":[{"count":0,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba\/275\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/media?parent=275"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba_cat?post=275"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba_tag?post=275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}