Hi, I'am the author of Buddy Linux (https://github.com/antonio-petricca/buddy-linux) which I uses everyday. The issue scenario boot sequence is: 1) The PC is a Windows 10 laptop on a NTFS partition. 2) The above partition hosts the LVM loopback files where Buddy Linux root partition has been installed. 3) An external USB pendrive, set a default boot device, hosts GRUB. 4) The initrd process mounts the NTFS volume by NTFS3 driver, setup the loopback files, mount EXT4 file system on them, and finally starts a native image of my Buddy Linux system. Today, a system freeze caused by the bug https://bugzilla.kernel.org/show_bug.cgi?id=215007 which I already submitted, made my system no more startable by NTFS3 driver. I started the PC by a live linux distro, I checked that the NTFS volume was dirty, so I fixed it by the ntfsfix tool, but it could not starts again. So, I tried by the old NTFS-3G, and it boots and uns without any problem. Please, could you tell how to recover from this situation and use again the NTFS3? Thank you in advance. Antonio Petricca
Hi, I installed a full distro onto a pendrive, added the kernel 5.15.2 and tryed mounting the NTFS partition. It says that cannot mount it because the volume is dirty and force flag is not set, or there is a bad superblock, or happened an unknown error. Thank you.
I did another attempt. I used the 'force' option and it worked, so I discovered that 'ntfsfix -d /dev/sda3' did not clear the dirty bit as expected. Is it safe to boot with `force` option? Should I do a CHKDSK by Windows 10? Thank you so much!
NTFS3 is not supposed to be used with potentially damaged partitions. Using the force flag is not recommended, this can lead to errors and data loss. And the driver has no any error checking/fixing capabilities. You should always run chkdsk in Windows first if there are any doubts about the partition integrity, the dirty flag is not made just for fun.
I will try with CHKDSK and then I will give a feedback. Tahnk you so much!
Issue fixed by CHKDSK. Thank you!