Mounting Windows partition

Support
1

There was a issue with Windows boot driver corruption, after fixing it manajro does not mount the Other windows partition and KDE Partition manager show those as LDM partition, how can i mount them…

its sda3 partition, the partition is still NTFS partition but kde partition report it as LDM

NAME          SIZE LABEL   FSTYPE UUID
sda         931.5G                
├─sda1          1M                
├─sda2        127M                
├─sda3      629.1G                
└─sda4      301.8G         btrfs  bc6344b2-5481-4008-a3de-03f6d61d1917
2

Please, post the output of sudo fdisk -l

3 

Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WDS500G2B0C-00PXH0                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 70767AAE-D682-4067-8891-5C866021DFA3

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      2048    534527    532480   260M EFI System
/dev/nvme0n1p2    534528    567295     32768    16M Microsoft reserved
/dev/nvme0n1p3    567296 770902062 770334767 367.3G Microsoft basic data
/dev/nvme0n1p4 975704064 976773134   1069071   522M Windows recovery environment
/dev/nvme0n1p5 770902063 975704062 204802000  97.7G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA MQ04ABF1
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: F32514FA-D930-4D65-A24C-C3233278BAA1

Device          Start        End    Sectors   Size Type
/dev/sda1          34       2081       2048     1M Microsoft LDM metadata
/dev/sda2        2082     262177     260096   127M Microsoft reserved
/dev/sda3      262178 1319630847 1319368670 629.1G Microsoft LDM data
/dev/sda4  1319630848 1952462847  632832000 301.8G Linux filesystem

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.
4

How was it fixed?

LDM (Logical Disk Manager) is the Microsoft equivalent to LVM (Logical Volume Manager) on Linux. Looks like it has been converted to some kind of Windows only Software Raid?

In any case, it would better for compatibility to convert it back to basic ntfs partition, but linux has also a ldm tool:

pamac install libldm

The partitions must be mounted to /dev/mapper with the ldmtool and then be mounted to a real folder.

Personally I never used LDM on linux, therefore here is a link: Dynamic disks - ArchWiki

1 Like
5

Thank you so much…

I formatted the disk then copied all the boot files and ran boorec /fixmbr which thrown an error Access Denined then out of despressison i ran automatic repair and it fixed the issue,

/dev/nvme0n1p2

On windows disk manager it still show as ntfs partition, is there a way to convert it back without loosting the data?

Will give it a shot

6

There are ways, but if you do a mistake, it can be easily result in data loses: https://www.get-itsolutions.com/how-to-convert-a-dynamic-disk-to-basic-disk/

However, this have to be done on windows and here is not the place for Windows Support :wink:

7

I think i know the issue, Actually there was a uallocated space in the drive so i extended the current drive and that could be the reason behind ldm…

although using ldmtool i get an issue it seems like converting is the only way to go forward

Unable to create volume Volume1 in disk group d916ae12-dcc2-11ec-a560-c03c5982c57f: ldm_vol_LAPTOP-1PHC70BI-Dg0_Volume1: Stacking NODE_DEL [verify_udev]