Re: [ntfs-3g-devel] NTFS signature is missing

[Jean-Pierre A. <jea...@wa...>]

Flaviu2 via ntfs-3g-devel wrote:
> Hello Pierre.
> 
> I am afraid I cannot run "blkid path-to-partition" command because I 
> don't have a Linux OS, just Win10.

Then, can you at least post an hexadecimal dump of the beginning
of the boot sector you read in the buffer pointed at by "b"
(64 bytes should be enough).

> Yes, I am trying to read a USB stick formatted as NTFS. That is for sure.
> 
> Inline image
> I am just suspecting that library doesn't read Win10 ntfs drives due to 
> this issue (from my post) and because I read this limitation in 
> documentation. I am in the lack of ideas ...

How did you guard against Win10 having opened the partition
exclusively in read-write mode ?

It might also be useful you tell how you open the partition,
and how you make sure you read actual data.

Jean-Pierre

> 
> Regards,
> Flaviu.
> On Thursday, February 27, 2020, 05:10:48 PM GMT+2, Jean-Pierre André 
> <jea...@wa...> wrote:
> 
> 
> Flaviu2 via ntfs-3g-devel wrote:
>  > Hello. I have loaded NTFS-3G from here:
>  > https://github.com/vitalif/ntfs-3g into 
> <https://github.com/vitalif/ntfs-3g%C2%A0into%20>a VS2017 project, 
> wanting to
>  > read NTFS USB stick drive. And when I debugging reading process, I saw
>  > that is not reading USB drive due to:
>  >
>  > *// bootsect.c*
>  >
>  > BOOL ntfs_boot_sector_is_ntfs(NTFS_BOOT_SECTOR* b)
>  > {
>  > u32 i;
>  > BOOL ret = FALSE;
>  > ntfs_log_debug("Beginning bootsector check.\n");
>  >
>  > ntfs_log_debug("Checking OEMid, NTFS signature.\n");
>  > if (b->oem_id != const_cpu_to_le64(0x202020205346544eULL))// "NTFS    "
>  > {
>  > ntfs_log_error("NTFS signature is missing.\n");        // *<-- my code
>  > is running from here ...*
>  > goto not_ntfs;
>  > }
>  > ...
>  > ...
>  >
>  >
>  > I run it this code on *Win10 64bit/VS2017*. And my USB stick are valid,
>  > I have tried several USB stick (all of them NTFS).
>  >
>  > I read that *vitalif/ntfs-3g* has a OS limitation: Windows XP, ... and
>  > Windows 7 file systems ... that is why I suspect the cause of my failing
>  > reading process ...
> 
> The mentionned check is valid, if it fails then you are
> not reading an ntfs partition. Maybe you are reading the
> full device instead of a partition, or reading a partition
> formatted as fat or exfat.
> 
> What is the output of "blkid path-to-partition" ?
> 
>  >
>  > I have seek it on github for another *NTFS-3G* /project that support
>  > Win10/, I didn't found it ... is there anywhere another version of
>  > *NTFS-3G library that work on Win10* ? Or, could another cause for my
>  > failing ?
> 
> Several limitations were lifted or pushed back on Win10,
> and AFAIK the latest ntfs-3g can access a partition updated
> by Win10.
> 
> Jean-Pierre
> 
> 
>  >
>  > Any support will be wellcome, I am struggle for this issue for days and
>  > days ...
>  >
>  > Regards,
>  > Flaviu.