ntfs3 and ntfs-3g

hevin · 2025-09-23 08:38:42

Hello. I have a strange problem. I have VirtualBox and libvirt installed on my Arch Linux. I created a WinXP virtual machine in VirtualBox and a Win11 virtual machine in virt-manager. The virtual disks of both virtual machines are located on sdb1. sdb1 is an NTFS partition. So, if I mount sdb1 with mount /sdb1 /mnt, WinXP works, but Win11 does not start. If I mount sdb1 as mount -t ntfs3 /dev/sdb1 /mnt, Win11 works, but WinXP does not start. Can you tell me what the problem is?

Last edited by hevin (2025-09-23 08:38:50)

seth · 2025-09-23 13:09:05

Not w/o error messages, please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

ntfs-3g is more lenient wrt dirty/open partitions (what's not necessarily a good thing and prone to cause data loss)
https://wiki.archlinux.org/title/NTFS#U … rked_dirty

Generally speaking and from what you describe you seem to be trying to mount the ntfs partition from the linux host as well as the windows VM at the same time.
DON'T! This will cause data corruption for almost sure.

hevin · 2025-09-23 13:58:00

No! How could you even think that? This NTFS partition contains images of virtual machine hard drives. winxp.raw and win11.raw are just files.

In addition, it is entirely possible to mount a single NTFS file system on multiple hosts. However, this must be done in read-only mode. Alternatively, read/write access can be granted to only one host, with the others having read-only access.In any case, I am not doing this in this particular scenario.
errors

ep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=810
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=201c val=1 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=201e val=0 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=2020 val=0 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=2022 val=0 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=401e val=61017eb err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=201a val=17142c05e err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=6802 val=0 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=681c val=0 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=681e val=fff0 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: vmwrite failed: field=6c02 val=1046db002 err=0
Sep 23 12:06:54 archlinux kernel: kvm_intel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.

I would prefer to use only ntfs3. With it, the disk works much faster than ntfs-3g.

Last edited by hevin (2025-09-23 14:16:38)

hevin · 2025-09-23 14:02:57

ok. seth
If you're so eager to see my journal, where should I send it?

[white_ghost@archlinux ~]$ journalctl --no-pager > journal.log
[white_ghost@archlinux ~]$ ls -la journal.log
-rw-r--r-- 1 white_ghost white_ghost 25931535 Sep 23 17:01 journal.log
[white_ghost@archlinux ~]$ ls -lah journal.log
-rw-r--r-- 1 white_ghost white_ghost 25M Sep 23 17:01 journal.log
[white_ghost@archlinux ~]$

seth · 2025-09-23 14:25:29

1st link below.

So for clarification: the setup are some windows VM images randomly reside on an NFTS partition and depending on how you mount that partition on the host you can start either one VM or the other???
Also please post the output of "mount | grep sdb1" for either mount.

frostschutz · 2025-09-23 14:32:10

hevin wrote:

This NTFS partition contains images of virtual machine hard drives. winxp.raw and win11.raw are just files.

Better to use native filesystems for that too.

ntfs-3g and ntfs3 have different interpretations regarding file properties and permissions (and symlinks, ...), not sure how that would cause issues with one VM but not the other though.

Can you md5sum those files, and do the checksums match when switching ntfs implementation?

hevin wrote:

Alternatively, read/write access can be granted to only one host, with the others having read-only access.

The writer would still corrupt the readers that are caching data in ram and do not expect there to be on-disk changes while in read-only mode.

Outside of cluster filesystems, it's expected for there to be a single authority.

But that's not your problem anyhow, so it's fine.

seth · 2025-09-23 14:38:14

The key difference will likely be virtualbox and libvirt, though if the VM is a single image file I'm not really sure how this would cause trouble, though the ntfs drivers might not properly handle nested FS headers.

hevin · 2025-09-23 14:55:02

[white_ghost@archlinux ~]$ mount |grep sdb1
/dev/sdb1 on /mnt type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
[white_ghost@archlinux ~]$ sudo umount /dev/sdb1
[white_ghost@archlinux ~]$ sudo mount -t ntfs3 /dev/sdb1
mount: /dev/sdb1: can't find in /etc/fstab.
[white_ghost@archlinux ~]$ sudo mount -t ntfs3 /dev/sdb1 /mnt
[white_ghost@archlinux ~]$ mount |grep sdb1
/dev/sdb1 on /mnt type ntfs3 (rw,relatime,uid=0,gid=0,iocharset=utf8)
[white_ghost@archlinux ~]$ md5sum /mnt
mnt/  mnt2/ mnt3/
[white_ghost@archlinux ~]$ md5sum /mnt/win1
win10tt.qcow2*    win111908.raw*    win111908.raw.gz*
[white_ghost@archlinux ~]$ md5sum /mnt/wxp/winxp/
Logs/                                                           winxp.vbox*                                                     winxp.vdi
Unattended-1e8a5e2e-c79a-4d99-bd6c-9b7dc98e6913-aux-floppy.img  winxp.vbox-prev*
[white_ghost@archlinux ~]$ md5sum /mnt/wxp/winxp/winxp.vdi
d9771cac93686eb0016c11175261cc55  /mnt/wxp/winxp/winxp.vdi
[white_ghost@archlinux ~]$ md5sum /mnt/win1
win10tt.qcow2*    win111908.raw*    win111908.raw.gz*
[white_ghost@archlinux ~]$ sudo virsh
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
       'quit' to quit

virsh # domblk
domblkerror      domblkinfo       domblklist       domblkstat       domblkthreshold
virsh # domblklist --
--details   --domain    --inactive
virsh # domblklist --domain win11
 Target   Source
------------------------------
 sda      /mnt/win111908.raw

virsh # exit

[white_ghost@archlinux ~]$ md5sum /mnt/w
win10tt.qcow2*    win111908.raw*    win111908.raw.gz* wxp/
[white_ghost@archlinux ~]$ md5sum /mnt/win111908.raw
afb42883ca02203bb490675b83569871  /mnt/win111908.raw
[white_ghost@archlinux ~]$ sudo umount /dev/sdb1
[white_ghost@archlinux ~]$ sudo mount /dev/sdb1 /mnt
[white_ghost@archlinux ~]$ md5sum /mnt/win111908.raw
afb42883ca02203bb490675b83569871  /mnt/win111908.raw
[white_ghost@archlinux ~]$ md5sum /mnt/wxp/winxp/winxp.vdi
d9771cac93686eb0016c11175261cc55  /mnt/wxp/winxp/winxp.vdi

Last edited by hevin (2025-09-23 15:20:56)

seth · 2025-09-23 20:43:22

Can you run the win10tt.qcow2 no matter what?
Do you get any errors from VB or WinXP when trying to start the latter form ntfs3?
Can you start XP eg. in failsafe mode (tap F8 while/before it's starting)?

hevin · 2025-09-24 03:19:55

No. The virtual machine simply won't start. VirtualBox says "starting the virtual machine...", and that's it. Nothing else happens. After about 3 minutes, it crashes with the following error:
Result Code:
NS_ERROR_FAILURE (0x80004005)

seth · 2025-09-24 11:37:23

Nothing at all?
Do you get some output if you enable debugging?
https://stackoverflow.com/questions/493 … x-gui-tool

I guess w/ WinXP you could also just copy the image into a tmpfs and start it from there…

Edit:

seth wrote:

Can you run the win10tt.qcow2 no matter what?

And on top of that, does it help to copy the XP vm somehwhere else on the ntfs partition?

Last edited by seth (2025-09-24 11:38:35)

hevin · 2025-09-24 14:15:10

I am very scared of this effect. That's why I'm afraid to write anything on this disk. If the driver is really crooked, it will write something there that I won't be able to find a single live file.
If you copy it to the system drive, for example, then of course everything starts up and works without any problems.

hevin · 2025-09-24 14:31:11

A long time ago, I used this NTFS partition in Arch Linux with the ntfs-3g driver and all kinds of performance optimization options. I don't remember what they were, but they all had a note saying that in case of something happening, the files would be corrupted. And indeed, I began to notice that files from the disk were actually disappearing somewhere. Then I reverted all the options to default, but the files continued to disappear. I thought the problem was with the disk, the cable, the USB port... and then it turned out that this computer didn't pass memtest. The RAM was corrupted. Then I took another computer, and it passed memtest. Yes, now that's the first thing I check :-). I installed Windows, and the files stopped disappearing. Everything was fine. Now I've uninstalled Windows and installed Arch Linux. And now something is happening again with one driver, one file is read with another... Maybe this is important, but I installed vbox when the disk was mounted as ntfs3, and win11 was written to the disk with the ntfs-3g driver.

seth · 2025-09-24 14:40:53

Do it from the windows system.
If there's no windows system, why is there an NTFS partition?

Files "disappearing" sounds a hell lot like the drive was mounted unclean (what ntfs-3g would happily do), possibly due to a hibernating system.

Maybe this is important, but I installed vbox when the disk was mounted as ntfs3, and win11 was written to the disk with the ntfs-3g driver.

But that would suggest that each file was written by the driver that now fails to run it, no?

seth, multiple times wrote:

Can you run the win10tt.qcow2 no matter what?

hevin · 2025-09-24 17:32:41

win111908.raw is connected to the win11 virtual machine.
win10tt.qcow2 is the system disk from another virtual machine. And yes, I can run win10.

What does “no matter what?” mean? The whole phrase just doesn't make sense in the translator. I only got the first part. But that's just another virtual machine. No problems with that one.

seth · 2025-09-25 13:45:07

"No matter what" meaning regardless of whether you mount the partition w/ ntfs3 or ntfs3g
Have you tried to make a copy of the XP image to a different location (in doubt from a windows system)?

dimich · 2025-09-25 16:16:33

Speculation: the issue may be related to sparse file gaps, how different FS drivers handle them and how raw and gcow2 adaptors use them.

hevin · 2025-09-25 17:24:26

Yes. I copied it to the system drive with f2fs. And everything runs smoothly from it, whether it's ntfs3 or ntfs-3g.

seth · 2025-09-25 17:35:26

If that's supposed to be an answer to #16, i meant whether you can run the W10 qcow2 from an ntfs3 and an ntfs-3g mount, but we already know that copying the images works.
dimich might have the right idea here.

Pending question is why you're using an ntfs partition tbw.

hevin · 2025-09-25 23:07:06

I didn't do it on purpose. It just happened that way. At first, I had Windows. Then it stopped loading. Just like that, for no reason. I reinstalled it. And after a while, it stopped booting again. The win111908.raw image is not quite what you think. It was created as a result of executing the command dd if=/dev/sda of=/mnt/win111908.raw. It's a sector-by-sector copy of the physical disk. Which is now connected as a virtual disk of a virtual machine .

seth · 2025-09-26 07:08:46

If you're not using any windows hosts, try to turn it into an ext4 partition or so.
All ntfs drivers are reverse engineered, there're no proper filesystem management tools (fsck) and NTFS isn't even POSIX compliant, ie. you don't get proper access rights control.
It's certainly not a filesystem you'd *want* to use on non-windows systems.

hevin · 2025-09-26 07:44:13

To create something, you first need to delete something How can I reduce the size of an NTFS partition in Linux?

cryptearth · 2025-09-26 08:16:53

hevin wrote:

To create something, you first need to delete something How can I reduce the size of an NTFS partition in Linux?

you DON'T!
and you do neither with any other tool but windows itself and windows only!
ntfs is microsofts abomination and as they never published full papers the community wasn't able to write fully compliant drivers, yet
so if you have to deal with ntfs - only do so from windows
otherwise you risk data corruption and loss

hevin · 2025-09-26 09:16:02

Damn! The bugs continue. It suddenly turned out that even though WinXP was copied to the system drive, it now runs alongside Win11, and there is no need to remount the drive every time. At the same time, they still don't want to work. The Win11 virtual machine hang.
here is such an error in the log

Sep 26 11:56:00 archlinux sudo[21703]: pam_unix(sudo:session): session closed for user root
Sep 26 11:56:10 archlinux kernel: SUPR0GipMap: fGetGipCpu=0x11
Sep 26 11:56:11 archlinux kernel: vboxdrv: 00000000d7effc79 VMMR0.r0
Sep 26 11:56:11 archlinux kernel: vboxdrv: 000000007e7d7de2 VBoxDDR0.r0
Sep 26 11:56:17 archlinux kernel: ------------[ cut here ]------------
Sep 26 11:56:17 archlinux kernel: vmread failed: field=4824
Sep 26 11:56:17 archlinux kernel: WARNING: CPU: 6 PID: 21737 at arch/x86/kvm/vmx/vmx.c:451 vmread_error+0x4d/0x60 [kvm_intel]
Sep 26 11:56:17 archlinux kernel: Modules linked in: cdc_acm vhost_net vhost vhost_iotlb tap ntfs3 tun nft_masq nft_ct nft_reject_ipv4 nf_reject_ipv4 nft_reject act_csum cls_u32 sch_htb nft_chain_nat nf_tables b>
Sep 26 11:56:17 archlinux kernel:  intel_uncore_frequency_common intel_tcc_cooling joydev mousedev snd_intel_dspcfg x86_pkg_temp_thermal snd_intel_sdw_acpi intel_powerclamp snd_hda_codec coretemp snd_hda_core sn>
Sep 26 11:56:17 archlinux kernel:  drm_display_helper spi_intel_pci spi_intel wmi cec intel_vsec
Sep 26 11:56:17 archlinux kernel: CPU: 6 UID: 962 PID: 21737 Comm: CPU 2/KVM Tainted: G     U  W  OE       6.16.8-arch3-1 #1 PREEMPT(full)  c3805c1210d56bc7a68d560dd9e968bb1cc9c38e
Sep 26 11:56:17 archlinux kernel: Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Sep 26 11:56:17 archlinux kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D90/B760M BOMBER (MS-7D90), BIOS A.E0 07/30/2025
Sep 26 11:56:17 archlinux kernel: RIP: 0010:vmread_error+0x4d/0x60 [kvm_intel]
Sep 26 11:56:17 archlinux kernel: Code: c1 e8 c7 ea 2d ec 85 c0 0f 85 01 57 03 00 5b c3 cc cc cc cc 48 89 fe 48 c7 c7 16 d5 5e c1 c6 05 94 f0 f7 ff 01 e8 f3 c4 2f eb <0f> 0b eb c5 0f 1f 40 00 66 66 2e 0f 1f 84 0>
Sep 26 11:56:17 archlinux kernel: RSP: 0018:ffffd4558aea38f0 EFLAGS: 00010246
Sep 26 11:56:17 archlinux kernel: RAX: 0000000000000000 RBX: 0000000000004824 RCX: 0000000000000027
Sep 26 11:56:17 archlinux kernel: RDX: ffff8f2eef59cfc8 RSI: 0000000000000001 RDI: ffff8f2eef59cfc0
Sep 26 11:56:17 archlinux kernel: RBP: ffff8f2be843c780 R08: 0000000000000000 R09: 00000000ffffefff
Sep 26 11:56:17 archlinux kernel: R10: ffffffffaec60e00 R11: ffffd4558aea3788 R12: 0000000000000000
Sep 26 11:56:17 archlinux kernel: R13: ffff8f2bfc10b000 R14: 0000000000000000 R15: 0000000000000002
Sep 26 11:56:17 archlinux kernel: FS:  00007f29f57ff6c0(0000) GS:ffff8f2f3fc9a000(0000) knlGS:0000000000000000
Sep 26 11:56:17 archlinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 26 11:56:17 archlinux kernel: CR2: 00000000e15ba000 CR3: 0000000205c7c001 CR4: 0000000000f72ef0
Sep 26 11:56:17 archlinux kernel: PKRU: 55555554
Sep 26 11:56:17 archlinux kernel: Call Trace:
Sep 26 11:56:17 archlinux kernel:  <TASK>
Sep 26 11:56:17 archlinux kernel:  __vmx_interrupt_blocked+0x71/0xa0 [kvm_intel a6d03c32468c208b1a5b522d91538613f0b4f08b]
Sep 26 11:56:17 archlinux kernel:  vmx_interrupt_allowed+0x36/0x70 [kvm_intel a6d03c32468c208b1a5b522d91538613f0b4f08b]
Sep 26 11:56:17 archlinux kernel:  kvm_vcpu_has_events+0x11e/0x1c0 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  kvm_arch_vcpu_runnable+0x39/0x50 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  kvm_vcpu_check_block+0x26/0xb0 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  kvm_vcpu_block+0x60/0xc0 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  kvm_vcpu_halt+0x182/0x430 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  kvm_arch_vcpu_ioctl_run+0xbb8/0x1830 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  ? vmx_set_cr0+0xc4/0x1500 [kvm_intel a6d03c32468c208b1a5b522d91538613f0b4f08b]
Sep 26 11:56:17 archlinux kernel:  kvm_vcpu_ioctl+0x11b/0x9f0 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  ? select_task_rq_fair+0x8b9/0x2190
Sep 26 11:56:17 archlinux kernel:  ? __seccomp_filter+0x41/0x4e0
Sep 26 11:56:17 archlinux kernel:  __x64_sys_ioctl+0x94/0xe0
Sep 26 11:56:17 archlinux kernel:  do_syscall_64+0x81/0x970
Sep 26 11:56:17 archlinux kernel:  ? ttwu_queue_wakelist+0xfe/0x120
Sep 26 11:56:17 archlinux kernel:  ? try_to_wake_up+0x309/0x740
Sep 26 11:56:17 archlinux kernel:  ? pollwake+0x77/0xa0
Sep 26 11:56:17 archlinux kernel:  ? __pfx_default_wake_function+0x10/0x10
Sep 26 11:56:17 archlinux kernel:  ? __wake_up_common+0x6f/0xa0
Sep 26 11:56:17 archlinux kernel:  ? __wake_up_sync_key+0x43/0x60
Sep 26 11:56:17 archlinux kernel:  ? sock_def_readable+0x42/0xc0
Sep 26 11:56:17 archlinux kernel:  ? unix_stream_sendmsg+0x630/0x6a0
Sep 26 11:56:17 archlinux kernel:  ? sock_write_iter+0x18e/0x1a0
Sep 26 11:56:17 archlinux kernel:  ? vfs_write+0x3c1/0x480
Sep 26 11:56:17 archlinux kernel:  ? ksys_write+0xcd/0xf0
Sep 26 11:56:17 archlinux kernel:  ? do_syscall_64+0x81/0x970
Sep 26 11:56:17 archlinux kernel:  ? __x64_sys_ioctl+0xb1/0xe0
Sep 26 11:56:17 archlinux kernel:  ? kvm_on_user_return+0x5e/0x90 [kvm 0ac1b7776fe9fccba0610db1d4377e6602f14195]
Sep 26 11:56:17 archlinux kernel:  ? fire_user_return_notifiers+0x34/0x60
Sep 26 11:56:17 archlinux kernel:  ? do_syscall_64+0x286/0x970
Sep 26 11:56:17 archlinux kernel:  ? do_syscall_64+0x286/0x970
Sep 26 11:56:17 archlinux kernel:  ? __irq_exit_rcu+0x4c/0xf0
Sep 26 11:56:17 archlinux kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Sep 26 11:56:17 archlinux kernel: RIP: 0033:0x7f2af9f0374d
Sep 26 11:56:17 archlinux kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 4>
Sep 26 11:56:17 archlinux kernel: RSP: 002b:00007f29f57fe4b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Sep 26 11:56:17 archlinux kernel: RAX: ffffffffffffffda RBX: 000055a74b915e80 RCX: 00007f2af9f0374d
Sep 26 11:56:17 archlinux kernel: RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000001c
Sep 26 11:56:17 archlinux kernel: RBP: 00007f29f57fe500 R08: 000055a72ba98810 R09: 000055a72ba98810
Sep 26 11:56:17 archlinux kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000ae80
Sep 26 11:56:17 archlinux kernel: R13: 0000000000000000 R14: 00007f2af7a14000 R15: 0000000000000000
Sep 26 11:56:17 archlinux kernel:  </TASK>
Sep 26 11:56:17 archlinux kernel: ---[ end trace 0000000000000000 ]---
Sep 26 11:56:17 archlinux kernel: kvm_intel: vmread failed: field=4824
Sep 26 11:56:17 archlinux kernel: kvm_intel: vmread failed: field=810
Sep 26 11:56:17 archlinux kernel: kvm_intel: vmread failed: field=4824
Sep 26 11:56:17 archlinux kernel: kvm_intel: vmread failed: field=810
Sep 26 11:56:17 archlinux kernel: kvm_intel: vmread failed: field=4824
Sep 26 11:56:17 archlinux kernel: kvm_intel: vmread failed: field=810
Sep 26 11:56:17 archlinux kernel: kvm_intel: vmread failed: field=4400
Sep 26 11:56:17 archlinux kernel: ------------[ cut here ]------------
Sep 26 11:56:17 archlinux kernel: vmwrite failed: field=810 val=ef err=0
Sep 26 11:56:17 archlinux kernel: WARNING: CPU: 6 PID: 21737 at arch/x86/kvm/vmx/vmx.c:469 vmwrite_error+0x63/0x140 [kvm_intel]
Sep 26 11:56:17 archlinux kernel: Modules linked in: cdc_acm vhost_net vhost vhost_iotlb tap ntfs3 tun nft_masq nft_ct nft_reject_ipv4 nf_reject_ipv4 nft_reject act_csum cls_u32 sch_htb nft_chain_nat nf_tables b>
Sep 26 11:56:17 archlinux kernel:  intel_uncore_frequency_common intel_tcc_cooling joydev mousedev snd_intel_dspcfg x86_pkg_temp_thermal snd_intel_sdw_acpi intel_powerclamp snd_hda_codec coretemp snd_hda_core sn>
Sep 26 11:56:17 archlinux kernel:  drm_display_helper spi_intel_pci spi_intel wmi cec intel_vsec
Sep 26 11:56:17 archlinux kernel: CPU: 6 UID: 962 PID: 21737 Comm: CPU 2/KVM Tainted: G     U  W  OE       6.16.8-arch3-1 #1 PREEMPT(full)  c3805c1210d56bc7a68d560dd9e968bb1cc9c38e
Sep 26 11:56:17 archlinux kernel: Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Sep 26 11:56:17 archlinux kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D90/B760M BOMBER (MS-7D90), BIOS A.E0 07/30/2025
Sep 26 11:56:17 archlinux kernel: RIP: 0010:vmwrite_error+0x63/0x140 [kvm_intel]
Sep 26 11:56:17 archlinux kernel: Code: c3 cc cc cc cc c6 05 26 e2 f7 ff 01 66 90 b9 00 44 00 00 0f 78 c9 76 41 4c 89 f2 48 89 de 48 c7 c7 e0 a0 5e c1 e8 6d b6 2f eb <0f> 0b eb b4 83 3d f2 48 f9 ff 11 76 30 0f b>
Sep 26 11:56:17 archlinux kernel: RSP: 0018:ffffd4558aea3940 EFLAGS: 00010246
Sep 26 11:56:17 archlinux kernel: RAX: 0000000000000000 RBX: 0000000000000810 RCX: 0000000000000027
Sep 26 11:56:17 archlinux kernel: RDX: ffff8f2eef59cfc8 RSI: 0000000000000001 RDI: ffff8f2eef59cfc0
Sep 26 11:56:17 archlinux kernel: RBP: ffffd4558aea3a20 R08: 0000000000000000 R09: 00000000ffffefff
Sep 26 11:56:17 archlinux kernel: R10: ffffffffaec60e00 R11: ffffd4558aea37d8 R12: 0000000000000000
Sep 26 11:56:17 archlinux kernel: R13: ffff8f2bfc10b000 R14: 00000000000000ef R15: 0000000000000002
Sep 26 11:56:17 archlinux kernel: FS:  00007f29f57ff6c0(0000) GS:ffff8f2f3fc9a000(0000) knlGS:0000000000000000
Sep 26 11:56:17 archlinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 26 11:56:17 archlinux kernel: CR2: 00000000e15ba000 CR3: 0000000205c7c001 CR4: 0000000000f72ef0

hevin · 2025-09-26 09:20:35

How can I do anything through Windows if I no longer have Windows? If I install Windows, how can I then read ext4 through Windows? Damn it! It's as if all this was invented in hell.

Arch Linux

#1 2025-09-23 08:38:42

ntfs3 and ntfs-3g

#2 2025-09-23 13:09:05

Re: ntfs3 and ntfs-3g

#3 2025-09-23 13:58:00

Re: ntfs3 and ntfs-3g

#4 2025-09-23 14:02:57

Re: ntfs3 and ntfs-3g

#5 2025-09-23 14:25:29

Re: ntfs3 and ntfs-3g

#6 2025-09-23 14:32:10

Re: ntfs3 and ntfs-3g

#7 2025-09-23 14:38:14

Re: ntfs3 and ntfs-3g

#8 2025-09-23 14:55:02

Re: ntfs3 and ntfs-3g

#9 2025-09-23 20:43:22

Re: ntfs3 and ntfs-3g

#10 2025-09-24 03:19:55

Re: ntfs3 and ntfs-3g

#11 2025-09-24 11:37:23

Re: ntfs3 and ntfs-3g

#12 2025-09-24 14:15:10

Re: ntfs3 and ntfs-3g

#13 2025-09-24 14:31:11

Re: ntfs3 and ntfs-3g

#14 2025-09-24 14:40:53

Re: ntfs3 and ntfs-3g

#15 2025-09-24 17:32:41

Re: ntfs3 and ntfs-3g

#16 2025-09-25 13:45:07

Re: ntfs3 and ntfs-3g

#17 2025-09-25 16:16:33

Re: ntfs3 and ntfs-3g

#18 2025-09-25 17:24:26

Re: ntfs3 and ntfs-3g

#19 2025-09-25 17:35:26

Re: ntfs3 and ntfs-3g

#20 2025-09-25 23:07:06

Re: ntfs3 and ntfs-3g

#21 2025-09-26 07:08:46

Re: ntfs3 and ntfs-3g

#22 2025-09-26 07:44:13

Re: ntfs3 and ntfs-3g

#23 2025-09-26 08:16:53

Re: ntfs3 and ntfs-3g

#24 2025-09-26 09:16:02

Re: ntfs3 and ntfs-3g

#25 2025-09-26 09:20:35

Re: ntfs3 and ntfs-3g

Board footer