Re: fusefs & ntfs-3g

From: Michael Butler <imb_at_protected-networks.net>
Date: Sun, 8 Sep 2019 19:36:05 -0400
On 9/8/19 7:09 PM, Alan Somers wrote:
> On Sun, Sep 8, 2019 at 5:00 PM Clay Daniels Jr. <clay.daniels.jr_at_gmail.com>
> wrote:
> 
>> I want to view my Windows C: drive on ata0p4.
>> This is what I have:
>> FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT r351901 GENERIC  amd64
>> clay_at_bsd13:~ % pkg info -r fusefs-libs
>> fusefs-libs-2.9.9:
>> clay_at_bsd13:~ % pkg info -r fusefs-libs3
>> fusefs-libs3-3.6.2:
>> clay_at_bsd13:~ % cat /boot/loader.conf
>> hw.syscons.disable=1
>> fusefs_load="YES"
>> clay_at_bsd13:~ % kldstat
>> Id Refs Address                Size Name
>>  1   72 0xffffffff80200000  2336f80 kernel
>>  2    1 0xffffffff82538000    27990 fusefs.ko
>>  3    1 0xffffffff82720000   2519c4 amdgpu.ko
>>  4    2 0xffffffff82972000    77bd0 drm.ko
>>  5    5 0xffffffff829ea000    12470 linuxkpi.ko
>>  6    3 0xffffffff829fd000    12f30 linuxkpi_gplv2.ko
>>  7    2 0xffffffff82a10000      8e0 lindebugfs.ko
>>  8    1 0xffffffff82a11000     f281 ttm.ko
>>  9    1 0xffffffff82a21000     23f7 radeon_kabini_pfp_bin.ko
>> 10    1 0xffffffff82a24000     23f5 radeon_kabini_me_bin.ko
>> 11    1 0xffffffff82a27000     23f5 radeon_kabini_ce_bin.ko
>> 12    1 0xffffffff82a2a000     43f7 radeon_kabini_mec_bin.ko
>> 13    1 0xffffffff82a2f000     2a77 radeon_kabini_rlc_bin.ko
>> 14    1 0xffffffff82a32000     12e9 radeon_kabini_sdma_bin.ko
>> 15    1 0xffffffff82a34000     12eb radeon_kabini_sdma1_bin.ko
>> 16    1 0xffffffff82a36000    38ea7 radeon_kabini_uvd_bin.ko
>> 17    1 0xffffffff82a6f000    18c47 radeon_kabini_vce_bin.ko
>> 18    1 0xffffffff82a88000     2538 intpm.ko
>> 19    1 0xffffffff82a8b000      a50 smbus.ko
>> 20    1 0xffffffff82a8c000     1820 uhid.ko
>> 21    1 0xffffffff82a8e000     2928 ums.ko
>> 22    1 0xffffffff82a91000     1b00 wmt.ko
>> 23    1 0xffffffff82a93000      acf mac_ntpd.ko
>> 24    1 0xffffffff82a94000     a9f8 tmpfs.ko
>>
>> clay_at_bsd13:~ % pkg info fusefs-ntfs-2017.3.23
>> fusefs-ntfs-2017.3.23
>> Name           : fusefs-ntfs
>> Version        : 2017.3.23
>> Installed on   : Sun Sep  8 17:24:36 2019 CDT
>> Origin         : sysutils/fusefs-ntfs
>> Architecture   : FreeBSD:13:amd64
>> Prefix         : /usr/local
>> Categories     : sysutils
>> Licenses       : GPLv2+
>> Maintainer     : freebsd_at_dussan.org
>> WWW            : https://www.tuxera.com/community/open-source-ntfs-3g/
>> Comment        : Mount NTFS partitions (read/write) and disk images
>> Options        :
>> DOCS           : on
>> LOCK           : on
>> UBLIO          : on
>> Shared Libs required:
>> libfuse.so.2
>> libuuid.so.1
>> libublio.so.1
>> Shared Libs provided:
>> libntfs-3g.so.88
>> Annotations    :
>> FreeBSD_version: 1300044
>> repo_type      : binary
>> repository     : FreeBSD
>> Flat size      : 1.93MiB
>> Description    :
>> The ntfs-3g driver is an open source, freely available read/write NTFS
>> driver, which provides safe and fast handling of the Windows XP, Windows
>> Server 2003, Windows 2000, Windows Vista, Windows Server 2008, Windows 7
>> and Windows 8 NTFS file systems. Almost the full POSIX filesystem
>> functionality is supported, the major exceptions are changing the file
>> ownerships and the access rights.
>>
>> root_at_bsd13:/home/clay # ntfs-3g -o default_permissons /dev/ada0p4 /mnt
>> * Windows is hibernated, refused to mount.
>> The disk contains an unclean file system (0, 0).
>> Metadata kept in Windows cache, refused to mount.
>> Falling back to read-only mount because the NTFS partition is in an unsafe
>> state. Please resume and shutdown Windows fully (no hibernation
>> or fast restarting.
>>
>> I'm having a roadblock here. Maybe someone knows the answer.
>>
> 
> I'm assuming that you already ascertained that the Windows file system was
> in fact clean?  If so, then this sounds like a problem with fusefs-ntfs,
> not with fuse in general.  I've CC'd its maintainer.  He may be able to
> help you.
> -Alan

Windows-10 has a changed default; it does the equivalent of hibernation
to facilitate "fast start". ntfs-3g won't touch a partition for writing
in that mode :-(

If I recall correctly, there is a setting you must change from in
Windows under control panel -> system -> power and sleep. From there you
should be able to disable the "fast start" option and, after shutting
down, ntfs-3g will allow a read/write mount,

	imb
Received on Sun Sep 08 2019 - 21:46:29 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC