exfat-fs fails with a Windows-formatted drive about exfatprogs HOT 15 CLOSED

Can you show me the value after commanding the below ?

# cat /sys/block/sda/queue/hw_sector_size 

from exfatprogs.

cat /sys/block/sdb/queue/hw_sector_size
512

from exfatprogs.

Please do this also.

$ lsblk --topology /dev/vda
NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED       RQ-SIZE  RA WSAME
vda          0   4096      0    4096    4096    1 mq-deadline     256 128    0B

You can command "lsblk --topology /dev/sdb"

from exfatprogs.

# lsblk --topology /dev/sdb
NAME   ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED       RQ-SIZE  RA WSAME
sdb            0   4096      0    4096     512    1 mq-deadline       2 128    0B
├─sdb1      3072   4096      0    4096     512    1 mq-deadline       2 128    0B
└─sdb2         0   4096      0    4096     512    1 mq-deadline       2 128    0B

from exfatprogs.

okay. Could you please try to mount after formatting your usb drive using mkfs.exfat ?

from exfatprogs.

I can, but I need to back up the data first. It will take a few hours. I will report back!

from exfatprogs.

Ah..Okay, no need to do it if you need backup.

from exfatprogs.

@cvubrugier Could you please help me fix this issue ? I don't have this type of HDD.
His hard has 4K hw sector and 512B logical sector. I wonder if this difference is causing this issue.
Do you have this type of HDD drive ?

from exfatprogs.

@fijam if you try to mount /dev/sdb2 ?

from exfatprogs.

Mounting sdb2 in fact works! Although I don't understand why Windows creates two volumes (the drive only appears as one volume in Windows).

Apologies for the trouble.

from exfatprogs.

@namjaejeon wrote:

@cvubrugier Could you please help me fix this issue ? I don't have this type of HDD.
His hard has 4K hw sector and 512B logical sector. I wonder if this difference is causing this issue.
Do you have this type of HDD drive ?

I could arrange for that. Most modern HDDs have 4 KB sectors but emulate 512 bytes sectors (512e) so that even firmware or OSes that do not support 4 KB sectors can work with them.

I guess the problem reported by @fijam is not caused by the HDD sector size.

dump.exfat /dev/sdb1
exfatprogs version : 1.1.3
bogus sector size bits : 0

I think sector size bits should be 9 (1 << 9 == 512).

tune.exfat -v /dev/sdb1
exfatprogs version : 1.1.3
[exfat_get_blk_dev_info: 202] Block device name : /dev/sdb1
[exfat_get_blk_dev_info: 203] Block device offset : 17408
[exfat_get_blk_dev_info: 204] Block device size : 134217728

So the size of the first partition is 128 MiB whereas the HDD capacity is 3 TB. This looks like an EFI System Partition.

Mounting sdb2 in fact works! Although I don't understand why Windows creates two volumes (the drive only appears as one volume in Windows).

This is consistent with our guess that the first partition is an EFI System Partition.

@fijam, could you run the following command? With that, we can verify if the first partition is an EFI System Partition.

$ sudo blkid /dev/sdb1

from exfatprogs.

Looks like you got it right:

# blkid /dev/sdb1
/dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="69faad38-f483-4939-a7bf-c7d6cef4828b"

from exfatprogs.

Maybe the exfatprogs utilities do not display an error if the file system magic does not match the one for exFAT.

In your situation, I think fsck.exfat, dump.exfat, and tune.exfat should have warned you that it is not an exFAT file system. Instead of that, the commands reported that the file system was corrupted.

There is probably room for improvement here.

from exfatprogs.

@cvubrugier Fully agreed:)

from exfatprogs.

@cvubrugier
Thank you for comments. I will fix it.

from exfatprogs.