-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work after windows 10 creators update #14
Comments
Downgrade to 0.68 will works. but 0.68 could corrupt your data, so I switch to Paragon ExtFS. |
@dd-han Ext2Fsd 0.69 was released 3 days after the issue was opened. What problem did you encounter with 0.69? |
@ngkaho1234 When I install ext2fsd without reboot, Ext2 Volume Manager unable to regcognized my ext4 partitison as following screenshot. After reboot, Ext2 Volume Manager can regcognized my ext4 partition and Ext2Fsd start success (It fail when Win 10 16299.64 still for Windows Insider only. Maybe reinstall fix that problem). Then I add driver letter for my ext4 partition. But it unable to show capacity or any infomation in explorer. If i double click on my ext4 volume (F:), just format dialog. That's problem I encounter with 0.69, and 0.68 fine. |
I have the same issue,firstly I thought something going wrong during the installation. |
Same here, ext4 is broken on 0.69. Couldn't even get it to work by reinstalling 0.68, strangely enough. |
It works perfectly for me, and I am using the latest insider preview for Windows 10 and the latest Ext2Fsd. No write privileges, but I can read... Target partition is a 64-bit EXT4 partition. |
@DaJakerBoss which win version? Now I am using win 10.0.17074 and ext3fsd 0.69. The issue is still not fixed. |
@kid1412621 The latest Insider Preview (Fast) |
@DaJakerBoss weird, insider slow here. My Linux portion is ext4. But it shows ext3 in ext3fsd. 😢 |
I am using build 17063 (updating to 17083 as we speak), and I think it
identifies it as EXT4, what did you use to make the partition?
|
@DaJakerBoss I don't make the partition. I just formatted the partition during installing the linux system. |
What Linux operating system did you install?
|
@DaJakerBoss Ubuntu 17.10 |
Hmmm... I am using 18.04 dev so that might be it?
|
@DaJakerBoss 😂 u suggest to update Ubuntu?U think thia bug is duo to Linux? |
Umm no I was just saying I had a different version of Ubuntu. Do you have a
GPT or MBR partition table.
|
I have an MBR system. If it has to do with the partition table than we have
issues.
|
@kid1412621 It shows the filesystem as EXT3 in Ext2Mgr also if the driver refuses to mount it. It can be related to incompatible features, such as 64bit. See e7c1142 . If you want to know more about your EXT4 filesystem, you might use debugfs like this: debugfs -R stats PATH_TO_VOLUME . Feel free to mail to me if you have any inquiries. |
Same here, WINDOWS 10 170928, Ubuntu 17.04. Only format dialog? |
just to be clear we have tried unsigned drivers boot in Windows, correct
…On Mar 17, 2018 at 9:18 PM, おとめ座 ひなたぼっこ ***@***.***> wrote:
Same here, WINDOWS 10 170928, Ubuntu 17.04. Only format dialog?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Afs4zynf4GZTirNbn7iUv2lVNzb4OyPDks5tfcQMgaJpZM4QJfUa>
.
|
@ngkaho1234 Thanks for reply.But I have no idea how to use this tool. Hey @DaJakerBoss , I just changed my laptop's motherboard,and reinstalled dual systems(Win 10 and Ubuntu 17.10),still cannot mount ext4 partition properly. |
Hey @kid1412621
You didn't really have to do all that (and hope you didn't) just so you
could mount your ext4.
IIRC an update had some issues with 64-bit EXT4 mounting, and had potential
to mess up your partition data.
The latest update (0.69) should fix that, so make sure you update.
Don't use Ext2Fsd 0.68 or earlier versions with latest Ubuntu or Debian systems. Ext2Fsd 0.68 cannot process EXT4 with 64-BIT mode enabled, then it could corrupt your data. Very sorry for this disaster issue, I'm working on an improvement.
Also, one quick question, are you using an MBR or GPT partition table? I don't know if this would be any cause but I'm collecting info.
I will look for more info regarding your situation.
|
@dd-han going back to your comment from earlier, USB and SSD/HDD are handled differently by the system as far as I know. Different drivers and such. I will try to recreate this with my computer at home. Does anyone have a system that uses different inputs for USB (2.0, 3.0, 3.1/Thunderbolt)? It would be interesting to see if interfacing has any effect on this. I'm going to try SATA and SATA->USB-3 connectors to see myself. |
@DaJakerBoss I done that because of fixing hardware issue. I didn't do that for mount ext4 on purpose. |
Using Ext2fsD 0.69 on Windows 10 build 1803, my system stop booting after installing it. Solved by killing ext2fsd.sys on system32/drivers... |
As a workaround for the now dropped 64-bit volume support, it might be worth a try to simply convert the file system to 32-bit using |
Should not be easier and better compat to ignore 64-bit enabled partitions?
Anyways, I'll check if it is the cause, because I have the same HD config
on my desktop (Win10 + Deb8 Ext4) and it worked fine.
…On Fri, Jul 27, 2018 at 1:49 PM Nmlgc ***@***.***> wrote:
As a workaround for the now dropped 64-bit volume support, it might be
worth a try to simply disable the 64-bit flag using resize2fs with the -s
option from a Linux system. Worked fine for my 2 TB drive; with the default
block size of 4 KiB, 64-bit blocks would only really be necessary for ≥16
TB drives.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAFCFhvptLF_fW52-MptKg3cCTozYKZtks5uK0SEgaJpZM4QJfUa>
.
--
Marcos Silva Cunha
Celular: +55 71 91348243 (TIM)
|
Does this mean windows have native support for ext4? |
Seems no. As they clearly mentioned that the functionality was implemented
with 9p protocol.
…On Sat, Feb 16, 2019, 12:50 PM kid1412621 ***@***.*** wrote:
https://blogs.msdn.microsoft.com/commandline/2019/02/15/whats-new-for-wsl-in-windows-10-version-1903/
Does this mean windows have native support for ext4?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALUjKDGDUUx3QusEKlhqFEVFR5JEh0rxks5vN44cgaJpZM4QJfUa>
.
|
What is 9p protocol?
…On Sat, Feb 16, 2019, 12:55 Ka Ho Ng ***@***.*** wrote:
Seems no. As they clearly mentioned that the functionality was implemented
with 9p protocol.
On Sat, Feb 16, 2019, 12:50 PM kid1412621 ***@***.*** wrote:
>
>
https://blogs.msdn.microsoft.com/commandline/2019/02/15/whats-new-for-wsl-in-windows-10-version-1903/
>
> Does this mean windows have native support for ext4?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#14 (comment)>,
or mute
> the thread
> <
https://github.com/notifications/unsubscribe-auth/ALUjKDGDUUx3QusEKlhqFEVFR5JEh0rxks5vN44cgaJpZM4QJfUa
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AZD4pifjH-H2FG3M46V_ty_5sGIFujbUks5vN49UgaJpZM4QJfUa>
.
|
I'm seeing exactly this behaviour as well, @achan-pancan. Windows 10, trying to mount an EXT3 (Linux Mint) partition on an external M.2 NVMe drive. |
I have the same issue as @achan-pancan and @isolationism - Windows 10 Pro v1803, I just get a format disk message when I try to access a drive, windows shows the service as running, but Ext2 shows it as not running and says it can't be started. |
For what it's worth @AdamSFX, my explorations online uncovered that an older release of ext2fsd, |
Thank you! Yes this works for me also. |
I have the same issues on Windows 10 Pro as pointed out by others, solved using |
Same problem. Reverted to ext2fsd-0.68 which works. |
I have the same issues on Windows 10 Pro build Version 1909 when used the newest version 0.69. The issue was solved by switched back to version 0.68 |
DON'T use the version 0.68 with Ubuntu on ext4. It will corrupt Ubuntu file system. |
In my case it was all due to Secure Boot. I had to disable it, enter Windows and modify a policy: |
Reverting to 0.68 worked for me too. I'm on Version 10.0.18363.778. |
I am using 0.68 as my data (external drive) and OS are on different partitions. Running on Version 10.0.18363.836. This thread was helpful. |
Cannot get ext2fsd service to start at all even without any other drive only Win 10 C:\ |
I had this exact problem and it turned out that Windows 10 Home does not work with v0.69; I had other PCs running Windows 10 Pro and they work well with v0..69. |
still same issue 69 not work |
The service refuses to start. This is all I know.
The text was updated successfully, but these errors were encountered: