Results 1 to 3 of 3

Thread: Unable to access 1.0 TB WesternDigital Hard Disk Drive

  1. #1
    Join Date
    Aug 2019
    Beans
    1

    Exclamation Unable to access 1.0 TB WesternDigital Hard Disk Drive

    Well, here is the problem:

    Few days ago I decided to use Ubuntu 18.04.03 LTS, intead of my classic Windows 7.
    My PC is an intel i5 3rd. gen on a H81M-S2PH Gigabyte board with 8GiB RAM, I use 3 Hard Disks of 1.0 TB each one without any OS, and a 500GiB disk for Windows. When I decided to use Ubuntu, I just repartitioned and formatted the 500GiB totally to use with Ubuntu, it means I don't have a Windows OS to make some practices.

    The case explicit is:
    My WDC disk appears on DISKS Utility, but it shows two partitions, at the start of HardDrive appears 134Mb of free space and at the next 931.4GiB is allocated a "Microsoft LDM data (System, Legacy BIOS Bootable)", in the DISKS utility, I can see a button to mount the partition in my other two 1.0 TB disks, but in this partition just the "-" and the config button appears.

    In my windows environment, that disk contains my personal documents, I don't tried to reformat or repartition it, 'cause I don't have any backup of that data.

    Some pages in internet gives tools and methodes to correct possibly corruption on the hard disk drive, I tried to list partitions from the fdisk utility

    Code:
    $ fdisk -l /dev/sdd
    Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 877FE66D-12CB-4438-B4C1-3AED17B13E93
    
    Device      Start        End    Sectors   Size Type
    /dev/sdd3  262178 1953523711 1953261534 931.4G Microsoft LDM data
    
    Partition 3 does not start on physical sector boundary.
    Code:
    $ fdisk -l /dev/sdd3
    Disk /dev/sdd3: 931.4 GiB, 1000069905408 bytes, 1953261534 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Alignment offset: 3072 bytes
    Disklabel type: dos
    Disk identifier: 0x73736572
    
    Device      Boot      Start        End    Sectors   Size Id Type
    /dev/sdd3p1      1920221984 3736432267 1816210284   866G unknown
    /dev/sdd3p2      1936028192 3889681299 1953653108 931.6G unknown
    /dev/sdd3p3               0          0          0     0B  0 Empty
    /dev/sdd3p4        27722122   27722568        447 223.5K  0 Empty
    
    Partition 1 does not start on physical sector boundary.
    Partition 2 does not start on physical sector boundary.
    Partition 3 does not start on physical sector boundary.
    Partition 4 does not start on physical sector boundary.
    Partition table entries are not in disk order.
    And previously I used parted to get some info of my disk:

    Code:
    $ parted -l /dev/sdd
    
    Model: ATA WDC WD10EARX-00N (scsi)
    Disk /dev/sdd: 1000GB
    Sector size (logical/physical): 512B/4096B
    Partition Table: gpt
    Disk Flags: 
    
    Number  Start  End     Size    File system  Name  Flags
     3      134MB  1000GB  1000GB  ntfs         tb01  hidden, legacy_boot
    If someone has any idea of how can I solve this, please let me know.
    I really need to access my data

  2. #2
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Unable to access 1.0 TB WesternDigital Hard Disk Drive

    Here's my research, in order, after reading the post ...

    Well, if the other disks weren't properly closed by Windows, then it is likely Windows left them open, so Linux won't touch them.
    Win7 did NOT have that enabled by default like Win8 and later all do. I don't know if Win7 supported Fast Start or not.

    If Windows wasn't using a "BASIC Partition", Linux won't have an easy time reading it.
    /dev/sdd3 doesn't seem like any device name I've ever seen, so I'm guessing there is some funky Windows non-standard file system happening. It would be best if you could find a Windows machine and convert to basic partitions and normal NTFS. Then Linux shouldn't have issues accessing the data.

    Google says these are "Microsoft Windows dynamic disks". Ouch. https://askubuntu.com/questions/1056...osoft-ldm-data didn't seem like they had much luck.
    https://ubuntuforums.org/showthread.php?t=2325331 is from 2016, which seems like it magically started working after loading and running 1 package.
    Last edited by TheFu; September 6th, 2019 at 12:58 PM. Reason: clarified a bit.

  3. #3
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to access 1.0 TB WesternDigital Hard Disk Drive

    I have seen a user use testdisk to convert MBR dynamic partitions back to basic, if only 4 partitions. With gpt that may not be an absolute requirement.

    Only if you have good backups of all the NTFS data inside the dynamic partitions, you can try testdisk.

    Other options also Aomei or even testdisk if only 4 dynamic partitions:
    http://askubuntu.com/questions/48276...-the-full-driv

    It used to be that Linux would not see dynamic partitions at all. But now you maybe can, but grub will not install with other partitions as dynamic.

    From Linux view LDM
    http://mika.soup.io/post/304505086/l...mic-disks-from
    https://askubuntu.com/questions/4827...-the-full-driv

    Post 96 using sfdisk - must have only 4 partitions
    http://www.sevenforums.com/tutorials...c-disk-10.html
    http://support.microsoft.com/kb/309044
    Also used testdisk if less than 4 dynamic partitions
    http://ubuntuforums.org/showthread.php?t=1675420
    Used testdisk but see caveats in Post#7:
    http://ubuntuforums.org/showthread.php?t=1669418
    Used testdisk but see caveats in Post#7:
    http://ubuntuforums.org/showthread.php?t=1669418
    Also used testdisk
    http://ubuntuforums.org/showthread.php?t=1675420

    General rule is to use Windows tools for Windows.
    Most of the Windows third party tools, may only run conversion if you upgrade to a paid version.
    If you have good backups you can experiment with Linux tools to try conversion.

    Also best not to have NTFS if not using Windows. NTFS need chkdsk & defrag periodically and you cannot do those from Linux. If you have NTFS at least keep a Windows repair flash drive.
    Last edited by oldfred; September 6th, 2019 at 05:01 AM.
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

Tags for this Thread

Bookmarks

Posting Permissions

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