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

    Exclamation Weird Issue with mounting disks


    I've got 2 identical HDDs, each with single NTFS partition on it. When they're both online, I can't mount any of them in Mint 17.2. Gparted shows two disks with NTFS partitions that can't be mounted (standard information that lack of ntfs-3g might be a problem). Additionaly gparted shows some mapper drive with the size of both HDDs combined and no partitions.
    Firstly, I have got SSD drive for Windows and that one is mounted without problems, despite it being NTFS.
    Secondly, when I disable one of those HDDs in BIOS, the other one is mounted without problems. Tried both drives this way, same effect.

    Windows has no issues with both HDDs online. I also have Mac OS X installed. No problems there also.

    Gdisk sees the partitions when both HDDs are online and reports no issues on partition tables.

    Apparently the issue lies with both disks being identical in make, model and partition size. Formerly I've used them as RAID 0. Then I've changed my hardware (motherboard, CPU). After I've set it all up I've found that one disk has bad sectors and that is why I use them separately now, storing relevant and irrelevant data on different disks.

    Has anyone got any ideas?

  2. #2
    Linux User IsaacKuo's Avatar
    Join Date
    Feb 2005
    Location
    Baton Rouge, LA, USA
    Posts
    448
    It sounds like the UUID on both partitions are identical. This pretty much couldn't happen by random chance, it was most likely because one drive was cloned to the other (cloning UUIDs).

    To confirm this, run this command to see the UUIDs of every detected partition:

    Code:
    sudo blkid
    Then change one of them with a command like this:

    Code:
    sudo tune2fs /dev/sde5 -U f0acce91-a416-474c-8a8c-43f3ed3768f9
    Replace some of the numerical digits with some other digits. It doesn't matter what this UUID is, just that it's different from the UUIDs of any other partitions you have.
    Isaac Kuo, ICQ 29055726 or Yahoo mechdan

  3. #3
    -->
    Thanks for the reply.

    Here's the output for sudo blkid:
    Code:
    $ sudo blkid
    /dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" 
    /dev/sda2: UUID="4b51d3dd-72c5-3332-89db-65be82802a11" LABEL="Yosemite" TYPE="hfsplus" 
    /dev/sda3: UUID="d7cdcb39-288b-3905-9dc8-c33a567c9c62" LABEL="Recovery HD" TYPE="hfsplus" 
    /dev/sda4: UUID="88db46a6-850c-448c-aa5b-13b7be3c6b06" TYPE="swap" 
    /dev/sda5: UUID="20372be2-fc51-4c3c-885d-323058286df8" TYPE="ext4" 
    /dev/sdb: TYPE="promise_fasttrack_raid_member" 
    /dev/sdc1: LABEL="Odzyskiwanie" UUID="E4F08425F083FFD2" TYPE="ntfs" 
    /dev/sdc2: UUID="8E92-4563" TYPE="vfat" 
    /dev/sdc4: LABEL="Windows 10" UUID="EE34A73A34A70525" TYPE="ntfs" 
    /dev/sdd: TYPE="promise_fasttrack_raid_member"
    The disks in question are sdb and sdd. They seem to be in RAID for some weird reason. Actually, when I've changed my Motherboard and CPU, I have never dismantled the RAID 0. It was set up in BIOS. When I changed the hardware, it seemed to be gone obviously. Apparently Mint sees it and that is causing problems, but how is it even possible?

    This is the output of gdisk:
    Code:
    $ sudo gdisk -l /dev/sdb
    GPT fdisk (gdisk) version 0.8.8
    
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: present
    
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sdb: 976773168 sectors, 465.8 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 2A1D2A1C-2A1E-2A1F-202A-212A222A232A
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 976773134
    Partitions will be aligned on 8-sector boundaries
    Total free space is 1 sectors (512 bytes)
    
    Number  Start (sector)    End (sector)  Size       Code  Name
       1              34       976773133   465.8 GiB   0700  
    
    $ sudo gdisk -l /dev/sdd
    GPT fdisk (gdisk) version 0.8.8
    
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: present
    
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sdd: 976773168 sectors, 465.8 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): E27EEB28-7B4C-6819-F41C-AD893992BB53
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 976773134
    Partitions will be aligned on 8-sector boundaries
    Total free space is 1 sectors (512 bytes)
    
    Number  Start (sector)    End (sector)  Size       Code  Name
       1              34       976773133   465.8 GiB   0700
    EDIT

    I have disabled one disk in BIOS, then another. Here's what I got from blkid:
    Code:
    /dev/sdb1: LABEL="Good Storage" UUID="01D0E5B83096D980" TYPE="ntfs" 
    
    /dev/sdc1: LABEL="Bad Storage" UUID="01D0E5B85F866210" TYPE="ntfs"
    Seems that UUIDs are different though similar to some extent.

    EDIT2

    Apparently previous RAID 0 setup has left some metadata on the disks and that caused those issues. Simple command sudo dmraid -rE erased the metadata and fixed the problem with no data loss.

    PROBLEM SOLVED.
    Last edited by matmh1; 09-24-2016 at 02:47 PM.

$spacer_open
$spacer_close

Posting Permissions

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