I have a an external USB HDD with an EXT4 filesystem. When attached to Linux systems it works as expected. When attached to my windows 11 machine which is running LFS for Windows 6.5.1 with a home use license nothing happens.

  • I have tried other EXT4 USB drives on the same system and they work fine.
  • When plugging in the EXT4 drive on Windows 11 it shows in the Windows Device Manager as "ST1600N M001G-2KK103 SCSI Disk Device" which is correct.
  • The device shows up under the Windows Disk Manager as "Disk 1: Unknown, 14902.00 GB, Not Initialized". The capacity is correct but it says the space is 'Unallocated'. I have not attempted to initialize the disk in Windows.
  • The Paragon GUI for LFS for Windows displays "No supported Volumes to display"


The entire LFS log file is too long to paste here. Here are the parts of it that stood out to me:

Code:
 FDisk version 3.2 + Base + LDM + SCO + GPT + APT + LVM2 (Nov  3 2023, 14:23:16)
[1708628304][0x3608] FDISK: ============== PhysicalDrive 1 ,14902.00 Gb ==============
[1708628304][0x3608] FDISK:   Media type        : Unknown
[1708628304][0x3608] FDISK:   Cylinders         :    1937733, 0x1d9145
[1708628304][0x3608] FDISK:   TracksPerCylinder :        256, 0x100
[1708628304][0x3608] FDISK:   SectorsPerTrack   :         63, 0x3f
[1708628304][0x3608] FDISK:   BytesPerSector    :        512, 0x200
[1708628304][0x3608] FDISK:   Total sectors     : 31251759104, 0x746c00000
[1708628304][0x3608] FDISK:   C*H*S             : 31251757824, 0x746bffb00
[1708628304][0x3608] FDISK:   delta             :       1280, 0x500, 0.62 MB
[1708628304][0x3608] FDISK: ==========================================================
[1708628304][0x3608] FDISK: ============== Layout of PhysicalDrive 1 (Mbr partition style) ===========
[1708628304][0x3608] FDISK: Signature       0x0
[1708628304][0x3608] FDISK: PartitionCount  0
[1708628304][0x3608] Begin population fdisk tree
[1708628304][0x3608] Population fdisk tree
[1708628304][0x3608] Population fdisk tree: FDISK_ITEM_COMP
[1708628304][0x3608] Population fdisk tree
[1708628304][0x3608] Population fdisk tree: FDISK_ITEM_MBR_DISK
 [1708628304][0x3608] +CDiskManager::attachGroup()()
 [1708628304][0x3608] -CDiskManager::attachGroup()()
[1708628304][0x3608] Population fdisk tree
[1708628304][0x3608] Population fdisk tree: FDISK_ITEM_MBR_PRIMARY
 [1708628304][0x3608] +recognizeFileSystem()
 [1708628304][0x3608] #####ERROR( f:\buildagent\work\eeb25c741a672e2a\fs_for_win\extfs4win\ext4dokanservice\src\mounter\volumemanager\filesystems\core\FileSystem_impl.hpp line 1530 ):  [1708628304][0x3608] #####ERROR( src\mounter\volumeManager\FileSystems\UfsdVolume.cpp line 317 ): Can not mount volume. Error code is 0xC000014F
 [1708628304][0x3608] #####ERROR( src\mounter\ufsd_thread.cpp line 631 ): Recognition failed
Looking up error code 0xC000014F online returned results relating to BSOD but didn't seem to provide much in specific information on how to fix. Just people trying to profit off of 'windows boot fix' tools.

Mounting the drive to a Linux system i used fsck in hopes it might fix somthing but it dint seem to make any difference.

Code:
sudo fsck -p /dev/sdc1