Results 1 to 4 of 4

Thread: Getting error when attempting to mount external HD

  1. #1

    Default Getting error when attempting to mount external HD

    I'm not sure what the error means or how to fix it.

    Code:
    An error occurred while accessing 'Expansion Drive', the system responded: org.freedesktop.Hal.Device.Volume.UnknownFailure: $MFTMirr does not match $MFT (record 0). Failed to mount '/dev/sdg1': InputOutput error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware.
    It's a seagate HD.

    Any ideas what I can do?

  2. #2

    Default Re: Getting error when attempting to mount external HD

    I fixed it! I used the info here: [kubuntu] Help! New External Hard Drive Broke Mid-transfer [Archive] - Ubuntu Forums

    Basically, you need to install "ntfsprogs" (was already installed) and then run:

    Code:
    #Run this to find out the name of your external HD (mine's /dev/sdg1 in this example)
    sudo /sbin/fdisk -l
    
    #Run this to fix it
    sudo ntfsfix /dev/sdg1

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,853

    Default Re: Getting error when attempting to mount external HD

    Nice you found it.

    Did you notice that you did not mention the fact that the device had an NTFS file system on it? Didn't you know or did you try to make it more difficult to people to help you?

    Well it is somewhere in that long message, but how can one know that the error message did guess it right when something is wrong?
    Last edited by hcvv; 23-Sep-2011 at 03:49.
    Henk van Velden

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Getting error when attempting to mount external HD

    On 2011-09-23 12:56, hcvv wrote:
    > Well it is somewhere in that long message, but how can one know that
    > the error message did guess it right when something is wrong?


    A bit cryptic, but the info is there. Probably would have been better to
    check the partition in windows, perhaps it was removed un-safely.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

Posting Permissions

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