HDD not recognized by Mint

[BlackStork07]

I have successfully installed Linux Mint on my SSD along with Windows 10. All partitions of main SSD disc are visible by Linux and I can access files from C Windows 10 drive.
Unfortunately I can't read any data from my second 1TB HDD drive from Mint. This disc was divided into two partitions: D(500GB) and E(500GB), under Windows 10. Under Linux I can only see one small Windows partition (around 100MB) and "unknown" partition of size 1TB. Both partition are NTFS and disk is GPT.
Is it possible to make those Windows 10 made partitions readable for Mint without deleting data? If not, is it at least possible to make them readable for both systems?
Here is result of lsblk command:

Code: Select all

    NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda           8:0    0 931,5G  0 disk 
    ├─sda2        8:2    0 931,4G  0 part 
    └─sda1        8:1    0   128M  0 part 
    nvme0n1     259:0    0 238,5G  0 disk 
    ├─nvme0n1p5 259:5    0  15,9G  0 part [SWAP]
    ├─nvme0n1p3 259:3    0   495M  0 part       //Windows Recovery
    ├─nvme0n1p1 259:1    0    99M  0 part       /boot/efi
    ├─nvme0n1p4 259:4    0  81,8G  0 part /   // Linux Mint
    └─nvme0n1p2 259:2    0 140,2G  0 part    // Windows 10
    

I am using Linux Mint Cinammon 64bit on Lenovo Y700
SSD - intel 600p series 256 GB
HDD- WD 1TB blue
CPU- intel 6700hq
GPU - Nvidia Gforce 690M

[Mute Ant]

Windows does know what's happening there, Linux doesn't. So don't use any Linux tools until you know what's happening.

You might look at the drives with the gdisk command...
sudo gdisk -l
...and post the results.

The gparted application understands GPT... there's a gparted-live distribution ISO with their best offering in a minimalist debian shell.

If there's something more that Windows 10 does to drives, in addition to GPT and NTFS, it might be confusing to your written-to-specification Linux programs. Certainly they get horribly confused if you present them with a Live Session boot disk, or even a partitionless drive.

[BlackStork07]

Here is result of gdisk command:

Code: Select all

 sudo gdisk /dev/sda -l
[sudo] password for XXXXX: 
GPT fdisk (gdisk) version 1.0.1

The protective MBR's 0xEE partition is oversized! Auto-repairing.

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): F603A126-B1D3-11E6-A98D-E4B318C6E719
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              34          262177   128.0 MiB   0C01  Microsoft reserved ...
   2          264192      1953523711   931.4 GiB   4202  Pula magazynu 

I guess that I have to make a backup of that disc and then configure it in a way that would allow it to be readable by both systems. Does anyone know how to do it? Is there any chance of not wiping data?

[Mute Ant]

The GPT makes sense, code 4202 is 'Windows Storage Space'. Deeper than that is OS-specific. Only Windows can access the file systems in there because D: and E: are not really 'plain' or 'simple' but 'virtual' and 'proprietary'.

[BlackStork07]

OK
Thanks, at least I know its a win10 issue. After I make a copy of that disk, what do I have to do in order to make this HDD usable for both operating systems?

[Mute Ant]

Any GNU-Linux will recognise GPT. Windows 10 will recognise it and possibly leave it as it finds it.

An MBR partition table will work on a 1TiB drive.

A NTFS seems to be the obvious choice, but I don't use Windows.

[Laurent85]

Check your backup before proceeding, data on drive will be lost.

From Mint run gparted and select the 1 TB drive. Create a new gpt partition table:
Device > Create Partition Table > Select new partition table type gpt > Apply

Still from gparted create your partitions and select ntfs as file system type.

[Spearmint2]

This is caused by the Secure Boot capability of your UEFI-BIOS computer.