Ext2Fsd 0.69 released !

WARNINGS:

    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.
Features implemented and bugfix:
    1, FIXME: superblock corruption of EXT4 volumes with 64BIT mode enabled 
    2, FIXME: possible corruption by race conditions in buffer-head reapering
    3, FIXME: possible deadlock issues (when flushing) caused by BCB locks
    4, FIXME: miscellaneous minor updates of Ext2Fsd code base
Supported Ext3/4 features:
    1, flexible inode size: > 128 bytes, up to block size
    2, dir_index:    htree directory index
    3, filetype:     extra file mode in dentry
    4, large_file:   > 4G files supported
    5, sparse_super: super block backup in group descriptor
    6, uninit_bg:    fast fsck and group checksum
    7, extent:       full support with extending and shrinking.
    8, journal:      only support replay for internal journal
    9, flex_bg:      first flexible metadata group
   10, symlink and hardlink
   11, Mount-as-user: specified uid/gid supported
Unsupported Ext3/4 features:
  1, 64BIT mode (to support 2^64 blocks)
  2, journal: log-based operations, external journal
  3, EA (extended attributes), ACL support

Features to be implemented in next release:
   1, Extents management improvement
   2, EA and ACL security checking
Files descriptions:
Ext2Fsd-0.69.exe:    Setup wizard for Windows systems (win2k, Winxp, 
                     Vista, Win7, Win8, Win10, Server 2003/2008/2012)
Ext2Fsd-0.69.7z:     Batch setup package in 7-zip
Ext2Fsd-0.69.zip:    Batch setup package in zip

Download link:
http://sourceforge.net/projects/ext2fsd/files/Ext2fsd/0.69/
Files checksum:
C:\Works\Ext2fsd\0.69>sha1sum Ext2Fsd-0.69*
00d1d616ee5365c6554043d2e2967a93c8f8722c *Ext2Fsd-0.69.7z
f6362b88470241c5bb209c10704bb5f46720a897 *Ext2Fsd-0.69.zip
5adaf3d830a904dc60adb1a6594f68cc0197f791 *Ext2Fsd-0.69.exe

WARNINGS:
    The driver may crash your system and ruin your data unexpectedly,
    since there might be software conflicts and I could only test it
    on some of the popular platforms. You should use it with care and
    use it at your own risk!
Matt <mattwu@163.com>
http://www.ext2fsd.com

Tags: ,

49 Responses to “Ext2Fsd 0.69 released !”

  1. Jeditobe Says:

    Please mention your Ext2Fsd driver as ReactOS-compatible. ReactOS operating system uses your filesystem driver on daily basis.

    [Reply]

  2. Oleksii Says:

    Thanks for Warning!

    I decided to reinstall my Debian to the last version. I read WARNING. And install new version of Ext2Fsd.
    But I have 2 Windows (for experiments), and I forgot that in the second it is old Ext2Fsd.
    So I was surprised when my fresh install had crashed.

    People, pay attention.
    :-)))

    [Reply]

  3. Shyam Says:

    Great Thanks for this software. Helped a lot in managing ext partitions. Ext2fsd seems to be the only perfect software of its kind. Please keep developing it.

    [Reply]

  4. Grant Atoyan Says:

    There is a bug in Ext2fsd 0.69 which is absent, say, in v. 0.52. It is not a bug, probably, it is “side effect” – to be fixed. If the driver is installed in Windows Server 2012 R2, when I use USB HDD (with 2 NTFS primary partitions, no EXT2), it cannot be parked! I.e. the drive is parked when you use “Safely remove” button in Windows notification area (the safely remove button shows that it is parked), but in fact it remains mounted in the system, and the OS hangs when I try to reboot the computer. If I uninstall the driver, everything gets ok again. I’ll check it in Windows 10 build 1709 and Windows 8.1 and report how the things are there. Of course, I’d like to use the latest version. Is there any workaround? Please, fix it!

    [Reply]

    vman Reply:

    How the heck did you manage to uninstall the driver, it’s conflicting with win32diskmanager i can’t make backups of my sd cards 🙁

    [Reply]

    vman Reply:

    I got it no worries, major conflict

    [Reply]

  5. Benjamin Says:

    I’m using this tool (v 0.51) on Windows 7 for many years in order to mount my ext3 formatted HDD which is installed in my Popcorn A400 media player.

    I recently bought a new, bigger SSD drive and decided to go for Windows 10. Since Ext2Fsd 0.51 doesn’t work with Win10, I downloaded and installed 0.69. Mounting my ext3 HDD was no problem, but my whole system now crashes every time while copying new data to the drive!
    Fortunately, I kept my Windows 7 partition on the old SSD. So, as far as there is no solution in sight, I have to switch back to my “old” Win7-SSD to be able to refill my ext3-HDD.

    Thanks though for this nice little tool. I’m gonna keep an eye on its future development hoping that some day it will work smoothely under Win10.

    [Reply]

    Grant Atoyan Reply:

    I think, you may use 0.52 version. It is possible to be installed on Win 10, but with a command file.
    Old versions do not have exaustive write support of ext partitions – you may write only new files, but neither delete, nor rewrite existing. Although old version will not crash Windows when unmounting mounted drives.

    [Reply]

    Benjamin Reply:

    Thanks for your advice! I’ll try to install the 0.52 version the next time using the described cmd line.
    But I’m not sure what you mean by “…but neither delete, nor rewrite existing”. When connected to my pc, I always DO delete some files that could not be deleted by the delete function of my media player.

    [Reply]

    Grant Atoyan Reply:

    I mean this happens with ext4 partition of 64-bit Linux – such partitiona are not fully supported with 0.52 version of Ext2fsd. Although you can create dirs and copy new files to such partitions. The correct write support is implemented in the later builds of Ext2fsd. But the critical thing is to make latest Ext2fsd not hang during unmount when rebooting Windows.

    [Reply]

  6. unknown Says:

    Ext2Mgr hangs at startup:

    Reverting parts of git commits d8632a1 and d570f95 fixes that issue.

    Patch: https://pastebin.com/hbytvTFS

    [Reply]

  7. Grant Atoyan Says:

    Dear Ext2fsd developers!

    I tested Ext2fsd 0.69 on Windows 10 x64 build 1709 (Creator’s Update), it works flawlessly, it is free of the bug I noticed in Windows Server 2012 R2. Please try to fix this annoying unmount bug under Windows Server 2012 R2 (see my earlier post). I guess you did not launch it in W2012R2!

    [Reply]

    Grant Atoyan Reply:

    Update:
    Unmount bug under Windows Server 2012 R2 mentioned in December 2017 remarkably dissapeared after the new Windows Server 2012 R2 update was issued – KB4103725, 05 2018. So, it is possible to use tha latest Ext2fsd 0.69 version – after the update is installed.

    [Reply]

    Grant Atoyan Reply:

    I found out that the unmount bug still persists (maybe after some of Windows updates). Under Windows Server 2012 R2, please, try the following command to unmount, for e.g. drive k:

    mountvol k: /p

    The unmount heppens when you run chkdsk with ‘/F’ parameter. So, I cannot check my USB drive if version 0.69 is installed. So, I have to use 0.52 by far. So, could you find out what is happening?

    [Reply]

  8. Anonymous Says:

    With 64-Bit mode now listed as an unsupported feature, I’m assuming 64-bit EXT4 drives/partitions can’t currently be mounted?

    [Reply]

  9. ALEX BALCANQUALL Says:

    .69 cannot be installed due to the driver not being signed, oh well.

    [Reply]

  10. Sergey Says:

    0.69 doesn’t seem to work on Windows 10 x64, after assigning a drive letter to ext4 disks they show as unformatted; I hope it will be fixed in the next version

    [Reply]

    ceres-c Reply:

    Same here.
    I tried to mount with mount.exe running from an admin prompt and, while it said “Succeed.” the drive is actually not mounted and I’m asked to format it. The dev might have simply disabled ext4 mount due to the 64bit mode issue…

    [Reply]

    Simon Reply:

    It seems all ext4 mounting was disabled, as I experienced similar occurrences on 32 bit machines, showing ext4 partitions as ext3.

    [Reply]

  11. Simon Says:

    I’m not sure if it is a bug, or if I’m just too stupid to use the program: the 0.69 version doesn’t recognize Ubuntu ext4 partitions as ext4 but as ext3 and consequently windows complains about the drives not being formatted.

    [Reply]

  12. Siddappa Says:

    It would be helpful to mention Ubuntu/Fedora/Mint versions rather than ext4 or 64 bit…

    Ubuntu16.04 LTS is ext4 64 bit….

    [Reply]

  13. Pat Says:

    I am trying to format an external hdd with ext4, for primary use in linux, and secondary use with windows/ext2fsd.

    My questions about this release, and how to format the partition for this purpose:

    1. Should I turn off extents?
    2. Should I turn off journaling
    3. Should I (and how can I) turn off 64-bit mode?
    4. Are there other considerations for creating the ext4 file system?

    [Reply]

  14. Sean Says:

    Well, I installed this on my system… I didn’t enable startup load, but I did enable write access.
    And it somehow corrupted my main Windows 10 x64 boot drive. The system gives me a boot error and Windows can’t repair it. 🙁 System restore also doesn’t work, so it must have somehow made a modification to my drives. I didn’t even get to use it… I simply rebooted after installing it.

    [Reply]

  15. Sergey Says:

    I’m using Ext2Fsd with an ext2 partition and some programs report that they fail to find a path located on this partition even though it’s mounted and I can access it on Git Bash / command prompt / Explorer.

    For example, if I execute “find . -name test” in Git Bash it outputs the following error:

    find: failed to read file names from file system at or below ‘.’: No such file or directory

    Android Studio also has problems with building an Android project located on the ext2 volume. I’m mounting it using the “Create a permanent MountPoint” option.

    [Reply]

    BugFinder Reply:

    It is (mostly) an MSYS2 problem. MSYS emulates inode number by hashing of the path. Their hashing algorithm is broken and produces different hashes for “C:\TMP” and “C:\TMP\” – it is easy to discover using
    find /c/tmp -printf “%p %i\n”
    find /c/tmp/ -printf “%p %i\n”

    find gets confused at a times and produces the error message.

    cygwin works fine. MSYS uses different algorithm since it is case insensitive.

    [Reply]

  16. keranique reviews by doctors Says:

    Wonderful goods from you, man. I have understand your stuff prior to and
    you’re just extremely fantastic. I actually like what
    you’ve got right here, certainly like what you are saying and the way in which by which you assert it.
    You make it enjoyable and you still take care of to keep it smart.
    I can’t wait to learn far more from you. That is actually
    a wonderful web site.

    [Reply]

  17. issuu.com Says:

    Howdy! Quick question that’s completely off topic. Do you know how to make your site mobile friendly?
    My weblog looks weird when browsing from
    my iphone. I’m trying to find a theme or plugin that might be able to resolve this issue.
    If you have any recommendations, please share. Thanks!

    [Reply]

  18. Menotu Says:

    Please fix ext4 access on Windows 10. Windows like to Format the drive and ext2fsd Shows it as ext3 and not ext4.

    [Reply]

  19. whatsapp dp Says:

    It’s an amazing paragraph in favor of all the online people; they will get benefit
    from it I am sure.

    [Reply]

  20. RusselF Says:

    Installed Ext2fsd 0.69 from sourceforge onto old Toshiba Windows Xp/SP3 laptop. I had built ext3 partitioned disk using Fedora (kernel 2.6.25-14 ) and my USB drive (a NexStar with an old 85GB disk inside) which runs fine from Linux. I found Ext2fsd and thought great, perfect solution – I can plug the USB disk into the Windows laptop, and migrate files. For a while it sort of worked, but after using it for a while, I find now, anything I write on the USB drive, does not persist. It is there when plugged into Windows, but it looks like everything is in a memory cache or something. If I try to “Safely remove Hardware” (to close the USB port), it hangs Windows (completely locks it up, have to hard-reset). And when I plug the disk into the Linux machine, *none* of the files copied onto the disk are present. Nothing. Access to an ext3 file system from a Windows platform is a great idea. Thanx for your efforts. But it is a non-starter for now. I’ve given up, and am using “scp” to transfer the files via wifi link, which is *slow* but works.

    There seems to be some serious issue where the files that appear to be copied onto the ext3 partition on the USB drive, are actually pendent in cache. I tried explicitly flush the cache out to disk, and about every possible way of mounting the USB drive from Windows. I can successfully mount the ext3 drive and see the LInux files, and I have all the write-enable boolean values set correctly, and the write appears to work. But there is a complete and brutal system-hang when one tries to unmount the ext3 disk. This WinXP/SP3 laptop is super reliable, and has run flawlessly for years. And Ext2fsd installed correctly, and appears to work ok,until one tries to close or unmount the USB port.

    It would be good if this software could be made to actually work, as it is a good idea, and a could be a useful tool, if it could be made to work.

    If I just want to write Windows files to an ext3 partition on a USB drive, might an earlier version exist that actually works? I think the difference is I initially had ext2fsd set up to mount “on demand”, but now have it set to automount. But now, nothing I do will let it write files that actually get retained (despite flushing cache, etc.)

    Any ideas? Oh, and both laptops are 32-bit devices. And the USB drive, with the ext3 filesystem, works flawlessly on the Linux machine. Is there some method that will allow this software to work so that a windows box can write files to a USB drive device with an ext3 filesystem? Thx for any info. – Rus.

    [Reply]

    Grant Atoyan Reply:

    This is not only the case of yours. The process hangs when trying to unmout the removable (USB) drive volume in Windows, not obligatory EXT partition, if the driver (0.69) is installed. See my comments, how to reproduce the bug.

    [Reply]

    Jorge Reply:

    Perdi uma semana de trabalho, gravei e editei vídeos e ao guardá-los no meu hd para transferencia descobri que os arquivos não haviam sido copiados, mas eu havia aberto os arquivos antes até olhei várias vezes.
    Se alguem por favor souber como recupero os arquivos

    I lost a week of work, recorded and edited videos and when saving them on my hd for transfer I found that the files had not been copied, but I had opened the files before and even looked at them several times.
    If someone please know how to recover files

    [Reply]

  21. Andrew Says:

    win10 x64 explorer stops responding when I try to share folder on disk.

    [Reply]

  22. DenisLp Says:

    I highly do not recommend using your app. I guess you should stop developing it.
    I installed it in Windows 7, ReadOnly mode. Manually assigned letters for EXT4 partitions. Everything is working. I delete the letters … I was wondering what would happen if I delete letter C from system NTFS partition. Removed letter C – Windows not responding and does not load anymore. Unfortunately, I have disabled system recovery. Luckily, Windows has been installed quite recently for the purpose of experimentation and it’s not a pity. But I delete your app and never again use it and do not advise anyone. And if user wanted to remove letter from EXT4 drive, confused and deleted from C? I believe Total Commander with EXT4 plugin will be much safer.

    [Reply]

  23. aaronfranke Says:

    It doesn’t open on Windows 8.1. I click on it, nothing happens.

    [Reply]

  24. wilson Says:

    When I install the Ubuntu 18.04, I can’t use ext2fsd to see the linux files in my windows 10.
    Previously, my ubuntu is 16.04 ,all is ok for ext2fsd.

    I can assign the drive letter to ubuntu file system, but in windwos explorer ,it always say “it need to format this drive’.
    What’s wrong with it.
    Thanks.

    [Reply]

  25. Simon Says:

    Hello, I want to run Ext2Fsd on WinPE 10 x64. Is is a x64 only system. No chance to run x86 executables.
    I downloaded v0.69. Running Setup.bat ends with success. But running mount.exe fails with hint, that this executable is not in right version for this system (error message if you want to run a x86 executable on a x64 only windows).
    I downloaded sources, but can’t build it without errors. Is there a possibility to get this to work?

    [Reply]

  26. Grant Atoyan Says:

    Dear developers and forumers!

    We still cannot use version 0.69, since the unmount bug persists! It reveals both under Windows 7 x64 and Windows Server 2012 R2. As there was no reaction to my previous messages, I should mention the details to make you understand the problem better. I think many of us use the external USB HDD drives, particularly with NTFS partitions (with write caching enabled). The bug can be reproduced the following way.

    1. Install Ext2fsd 0.69 driver under your Windows system with the command line:

    setup.bat wxp amd64

    (This syntax is also for Windows 7 )

    Reboot the computer.

    2. Mount the ext (ext2/ext3/ext4) partition on the _internal_ HDD, assign the letter, create directory or write some files to the partition (i.e. write something there)

    3. Plug in the _external_ USB drive (with NTFS partition). Make sure that the letter is assigned, for e.g. k: (You may do some operations on the volume – read/write files, so on).

    4. Make sure volume k: is unlocked, try to unmuont it. The easiest way to do it is to run

    mountvol k: /p

    The thread hangs on the unmounting!!!

    The unmount attempt is effected, for e.g., when you run chkdsk with ‘/F’ parameter and it finishes checking the volume, when you try to reboot the computer with plugged-in USB drive. The USB drive partition may remain dirty then. So, I can niether check my USB drive, nor unplug the drive with unmouting, nor reboot the machine, if version 0.69 is installed! What is more important – access to EXT partitions or USB storage? Therefore, I have to use 0.52 by far!

    So, who can tell me what is happening? I’m sure that many people have noticed the problem. With great pleasure I would assist in debugging the driver, in testing the attempts to correct the bug.

    [Reply]

  27. Geetsce Says:

    No success trying version 0.69 on a fresh install of Windows 10 Pro 19H2 on my second hard disk. Trying to access my EXT4-partitioned Ubuntu disk (in read-only) prompts an invitation to format that disk. I declined 😉

    F.Y.I., the EXT4 is formatted with these options (reported by tune2fs) :

    Filesystem revision #: 1 (dynamic)
    Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file dir_nlink extra_isize metadata_csum
    Filesystem flags: signed_directory_hash
    Default mount options: user_xattr acl
    Filesystem state: clean
    Errors behavior: Continue
    Filesystem OS type: Linux
    Inode count: 2796032
    Block count: 715759360
    Reserved block count: 121679
    Free blocks: 94814113
    Free inodes: 2056340
    First block: 0
    Block size: 4096
    Fragment size: 4096
    Group descriptor size: 64
    Reserved GDT blocks: 1024
    Blocks per group: 32768
    Fragments per group: 32768
    Inodes per group: 128
    Inode blocks per group: 4
    Flex block group size: 16
    Filesystem created: Fri Nov 23 12:44:51 2018
    Last mount time: Mon Dec 16 10:38:28 2019
    Last write time: Mon Dec 16 10:38:28 2019
    Mount count: 484
    Maximum mount count: -1
    Last checked: Fri Nov 23 12:44:51 2018
    Check interval: 0 ()
    Lifetime writes: 5347 GB
    Reserved blocks uid: 0 (user root)
    Reserved blocks gid: 0 (group root)
    First inode: 11
    Inode size: 128
    Journal inode: 8
    Default directory hash: half_md4
    Directory Hash Seed: e29ad6ac-a4b9-4430-8aa4-14db2aef4856
    Journal backup: inode blocks
    Checksum type: crc32c
    Checksum: 0xac56c6c1

    [Reply]

    Bo Brantén Reply:

    If you format without 64bit and metadata_csum or turn them of with tune2fs it will work.

    [Reply]

    Geetsce Reply:

    @Bo Brantén : Thanks, I wil try it after a full backup of that (2TB) disk to my USB equivalent. I found you can turn these options off on an existing file system :

    https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums#Detailed_Instructions :

    “ensure that the filesystem will pass fsck. Then turn off metadata_csum via tune2fs, e.g. tune2fs -O ^metadata_csum /dev/path/to/disk.”

    – man resize2fs :

    The -b and -s options enable and disable the 64bit feature, respectively. The resize2fs program will, of course, take care of resizing the block group descriptors and moving other data blocks out of the way, as needed. It is not possible to resize the filesystem concurrent with changing the 64bit status.

    -s : Turns off the 64bit feature and frees blocks that are no longer in use.

    [Reply]

  28. Bo Brantén Says:

    Hello, I am helping Matt to develop support for the new features metadata checksums and 64-bit blocknumbers and now it is ready to be tested by interested users. If you want to help me testing follow these steps: 1. Install the old version using the official installation program. 2. Copy my driver http://www.acc.umu.se/~bosse/ext2fsd/bin/ext2fsd.sys over the old in \windows\system32\drivers. 3. Reboot. Then you should be able to read and write the newest ext4 filesystems from Linux! (sorry, I can’t sign drivers so you must turn off Windows check for that during testing) I hope you all are well in different parts of the world these days! Bo.

    [Reply]

    Bo Brantén Reply:

    The driver is now test signed so you can load it if you turn on testsigning with the command “bcdedit.exe -set testsigning on”

    [Reply]

    Max Burns Reply:

    Hi, it works!
    Is there a way to make this work without being in test mode?

    [Reply]

    Bo Brantén Reply:

    Nice to here that it works. To sign the driver for real one needs somthing called EV certificate (Extended Validation) and I think only companies are allowed to buy one so wee need help to sign the driver.

    [Reply]

    Max Burns Reply:

    Ah right, I guess it doesn’t matter too much though because I’ve been using test mode since and I don’t see a difference between normal windows..
    Will this patch come into an upcoming update?

    [Reply]

  29. Dink Says:

    I have used Ext2Fsd for many years with no issues however after updating to the newest Ubuntu and needing a newer Ext2Fsd to deal with the Ext4 format, I now have Superblock issues on Ubuntu.

    I did have Win 7 pro 64bit and Ext2Fsd 0.51 with Ubuntu 13.1 and all worked fine on Ext3.

    I have done a fresh install of Ubuntu to 20.04 LTS and as I could not see files , even though it did see drive , I tried updating Ext2Fsd to 0.68 , this worked fine and I could view files but it caused Superblock issues when trying to boot into Ubuntu.

    ……………………………………………………………………………………………………………….

    0.68 loads fine assigns drive letter , sees drive as EXT4 and files can be viewed , but
    Superblock issue on Ubuntu Ext4 partition .

    0.69 loads fine assigns drive letter , files cannot be viewed via Explorer but drive shows as a
    drive with a letter , trying to view gets a response from Win 7 asking to format drive.

    …………………………………………………………………………………………………………………

    I have tried your new sys file on both 0.68 and 0.69 , both show a drive letter but neither allowing viewing files , and both see it as EXT3 .

    I notice that when assigning letter to drive the header “Codepage” has ” utf8 ” when it is going to allow viewing files and blank when not , also it will show as EXT3 and not EXT4 .

    I will be adding Win 10 pro as a Tri-Boot soon , so it would be nice to see this working even if it will only work properly on Win 7 due to the driver signing issues on Win 10.

    Anyone reading this and wondering how to fix the Superblock issues so you can get back into your Linux distro , do this :

    1/ Get ” boot-repair-disk-64bit.iso ” and ” RUFUS v3 ” both free online ,
    and a USB flash drive of at least 708MB .

    2/ Use RUFUS to make a bootable flash drive from the .iso above , as soon as you select the
    iso in RUFUS it auto fills boxes and you can just click start.

    3/ Boot from flash drive and choose auto repair , it will fix the Superblock issue in a couple of
    minutes and then you can reboot back into your Linux distro again.

    Please email me if I can help .

    [Reply]

    Bo Brantén Reply:

    As far as I know only 0.68 will corrupt the superblock while 0.69 should refuse to mount incompatible file systems. Anyway both should be possible to upgrade with my latest sys file (if you do it before corrupting the superblock)

    [Reply]

  30. Dink Says:

    Hi Bo,

    This is on Win 7 Pro 64bit , Ubuntu 20.04 64 bit LTS Dual boot ,

    After repairing superblock as above I tried searching for hours to find an answer to this , as it would either corrupt SuperBlock or simply refuse to allow viewing of files , tried 0.68/0.69 and tried the swap out of sys file in system32/drivers to no avail 🙁

    However , I found this on the Ubuntu forum ( so I can’t take credit )

    >>>>>>>THIS MUST BE RUN FROM THE UBUNTU 20.04 LIVE CD >>>>>>>>>>

    Boot from Live CD and choose ” Try It ” NOT ” Install It ” , once booted open Apps
    and look for ” Terminal ”

    Put this into the Terminal ( Its like Command Prompt for Windows )

    You need to know which partition your Ubuntu is on , mine is partition 3 on my disc, adjust to fit your setup on disc.

    sudo tune2fs -O ^metadata_csum,^64bit /dev/sda3 ( Yes that’s a capital O not zero )

    – system will ask you to run e2fsck -f first like this , to check file system is good :

    sudo e2fsck -f /dev/sda3

    Now you can run the sudo tune2fs command again …..

    sudo tune2fs -O ^metadata_csum,^64bit /dev/sda3

    Only took a couple of minutes for me , then it will ask you to run :

    sudo resize2fs -s /dev/sda3

    It should now confirm it has done it.

    Shut down PC , Remove Live CD or USB stick and Reboot PC.

    Now I can view the Ext4 partition from Windows 7 and I have no Superblock issues when I return to Ubuntu .

    Now I need to load Win 10 on my 2nd Partition and see what games I have ahead of me to make it work with Win 10 Pro , lol.

    Hope this helps any poor soul with a simple understanding of Linux like me to get this Ext2fs driver to work as its so useful to be able to view and change files on the Linux partition from Windows. From reading the Ubuntu forums many have had these issues since the newer installers load these 2 options as default now , this command simply turns both options OFF so
    it stops Superblock corruption.

    On Win 7, I used 0.69 without changing sys driver , I did try the sys change but had issues ,
    sometimes it would read files and on another boot it could see drive but gave the ” Do you want to format or incompatible files error ” ? Maybe it will be needed on Win 10 ?

    [Reply]

Leave a Reply