Manjaro not detecting Windows HDD

Hello,
Sorry I’m sure this question was asked before but I couldn’t find the solution to fix it.
I’m new to manjaro. I have both M2 SSD & HDD. Comming from Windows I installed Manjaro on M2 but not I’m unable to access the files on my 1TB HDD.
I have disabled fast boot & secure boot
I ran

sudo parted -l

Model: ATA HGST HTS721010A9 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  538MB   537MB   fat32              msftdata
 2      538MB   1000GB  1000GB                     lvm


Model: Samsung SSD 960 EVO 500GB (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name  Flags
 1      2097kB  317MB  315MB   fat32                 boot, esp
 2      317MB   491GB  490GB   ext4            root
 3      491GB   500GB  9449MB  linux-swap(v1)        swap

And

efibootmgr

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0001
Boot0001* UEFI OS
Boot0002* UEFI OS

Appreciate the help.

A logical volume without anything in it? Seems weird…

lsblk -af
1 Like

Is your HDD set to AHCI in the UEFI firmware setting? If not, change it to AHCI.

NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
                                                                            
loop1
                                                                            
loop2
                                                                            
loop3
                                                                            
loop4
                                                                            
loop5
                                                                            
loop6
                                                                            
loop7
                                                                            
sda                                                                         
├─sda1
│    vfat   FAT32 SYSTEM
│                       FEC1-C808                                           
└─sda2
                                                                            
sr0                                                                         
nvme0n1
│                                                                           
├─nvme0n1p1
│    vfat   FAT32 NO_LABEL
│                       A650-0E9E                             299.1M     0% /boot/efi
├─nvme0n1p2
│    ext4   1.0         19c6e3a7-af76-4d62-899c-d35c78bac46b  377.5G    11% /
└─nvme0n1p3
     swap   1     swap  5006d6ca-30a7-42a1-908e-49d24a0ed1cc                [SWAP]

@Aragorn In the boot menu for SATA Select mode, it says AHCI. Should I check something else?

No, the setting is correct then. :man_shrugging:

Was the Windows partition encrypted?

@maycne.sonahoz Could be I’m not sure :sweat_smile:

The only thing we know about that partition is that is uses (almost) your full HDD, and that it has the “lvm” flag.
Digging a bit, it seems Windows cannot read LVM partitions, so it seems unlikely it’s the one that put it there.

LVM is commonly used on Linux for encrypting drives. Do you remember doing anything related to this?

Maybe you can try using lvm2 to check what is inside: LVM - ArchWiki
Otherwise, that partition is as good as empty…

I actually never heard of LVM used in encryptying drives.

AFAIK, LVM is the technology used in the old BIOS MBR to extend the maximum of 4 partitions, like when you use the old fdisk application to partition drive.

As the old MBR can only have up to 4 primary partitions, the only way to extend partitions is to have 3 primary partitions and 1 extended partition. And you set the extended partition to LVM, so you can create more virtual partitions, thus the naming “Logical Volume Management”. Virtual partitions also make it easier to expand and shrink partition size because then’re no such thing as neighbouring partition (neighbouring partitions only exist in physical partition).

In short, LVM is a virtual partitions technology, in the same sense as virtual machines. That’s why you don’t see mounted filesytem in LVM.

As I recall about LVM, your LVM in this HDD is empty. No virtual partitions has been made. Again, as I recall, you should see partitions listed below the LVM partition (known by the flags) had you made virtual partitions previously.

But your HDD partition table is already GPT, so you don’t actually need LVM and can just reformat that partition to physical partitions. Plus your LVM partition is empty (no virtual partitions).

FYI: The limitation of 4 primary partitions in MBR is one of 2 main reasons why GPT was conceived, as GPT can support many partitions (don’t remember how many, but too many for normal use). The other main reason is that MBR drive max size is ~2TB.

1 Like

Off-Topic:

https://wiki.archlinux.org/title/LVM

https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#LVM_on_LUKS

https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#LUKS_on_LVM

Perhaps this is/was a windows dynamic disk?

Try reading/mounting that hdd on a windows machine (could be a vm with direct access to the disk).

Also see Dynamic disks - ArchWiki

1 Like