Ext2Fsd ProjectExt2Fsd 0.48 was released !
Modifications from V0.46:
- Acronis TrueImage compatible issue solved: Verified with Acronis True Image Home 2009. Also verified with FreeOFTE 3.0, TrueCrypt 6.2a.
- Driver code-signed for Vista and Server 2008
- Bo Branten’s 5+ patches merged, lots ifstest failures resolved
- Code improvements for FastIo routines and drive letter & mount points management
- Mount point automatic assignment for USB key and other removable
disks or removable media devices
You can download Ext2Fsd at: http://sourceforge.net/projects/ext2fsd/files/
MD5:
——————————————————————————-
Ext2Fsd-0.48.exe 9565ffa63cdb22cac81853aec64eed77
Ext2Fsd-0.48.src.zip c454f32da6eb7f4c2dcb48cd7788c80b
Ext2Fsd-0.48.zip efc34c86e772cd135633f64bee8679d7
Have fun with Ext2Fsd !
August 5th, 2009 at 10:29 am
So far so good, everything works perfectly! The only issue I’ve had is that if I set Ext2Fsd to start when I log in, a UAC prompt will pop up as soon as I sign on. I’ve tried adding it to the Task Scheduler to “Run with highest privileges” but the prompt still pops up.
I’m on Vista Business 64-bit, do you have any suggestions?
August 6th, 2009 at 10:47 am
Option 1, Try Norton UAC tool.
Norton UAC tool supports white/black list. UAC won’t bother once you put Ext2Mgr into the whitelist.
X86: ftp://ftp.symantec.com/misc/sabu/norton_labs/NUACx86.exe
X64: ftp://ftp.symantec.com/misc/sabu/norton_labs/NUACx64.exe
Option 2: Disable UAC
August 12th, 2009 at 9:25 pm
It’s really perfect !! You are wonderful !
August 13th, 2009 at 4:16 am
Great stuff !
But…I got random crashes (bsod) while opening directories with lots of smaller files in them…
thanks
August 15th, 2009 at 10:10 am
Thanks so much for the new version
August 16th, 2009 at 1:02 am
Big, big thanks for your work!
August 20th, 2009 at 12:04 pm
I have a 2 primary partitions on a 16GB USB drive. #1 is FAT32, #2 is ext2. In volume manager properties, partition #2 has status ’stopped’ and i cannot add a mount point.
How can I get this partition ‘online’?
August 25th, 2009 at 10:29 am
When I mount I get Windows 7 telling me that the drive needs to be formatted because it can’t recognize the filesystem. I tried working with the TESTSIGNING option in bcdedit.exe and adding the ext2fsd.sys file to the drivers in the OS using “Driver Signature Enforcer Overrider”, which I saw worked for someone in an Ubuntu forum. Nothing is working! Why me?? Either way I’ve used Ext2Fsd in the past and it is wonderful software.
August 28th, 2009 at 5:47 pm
it works, but in windows 7 not very well, very often BSOD
August 29th, 2009 at 2:16 am
xp64, intel matrix raid 0+1 setup. Linux formatted to EXT4 on the RAID0 partition.
It installs correctly, recognizes the Linux partition and shows the files in the root directory but the directories are empty. Some files in the root directory can be read, other cannot, and they have a wrong size.
0.46 worked correctly with xp64 on an nvidia raid 0 config. Probably the linux partition was formatted to EXT3 on that config.
Maybe EXT4 is the problem here. Is it supported? Wiki says it is backward compatible with EXT3.
September 5th, 2009 at 11:00 pm
Been getting a lot of BSOD in Windows 7 RC x86 using 0.46, will upgrade to 0.48 but seems other users are having problems too. Normally my message at the top is BAD_POOL_HEADER.
Do you know if ext2fsd will be fully compatible with Windows 7, if so any date?
September 5th, 2009 at 11:01 pm
Sorry, correction, I was using 0.46 and getting BSOD, been using 0.48 for some time with the same issue.
September 8th, 2009 at 3:49 pm
my only problem however is that I’m unable to run the game grand theft auto IV – but it works with ext2ifs which is strange. have not been able to try other exe files… using Windows XP.
Other than that, this is working well, Thanks. you’ve given users who have low space on their hard disk like me the ability to use the space freely, as well as external drives.
September 13th, 2009 at 8:22 pm
First of all, thanks a lot for ext2fsd! But the new version didn’t worked for me, had to downgrade to 0.46a.
My case is fully documented here: (first and last post)
http://ubuntuforums.org/showthread.php?t=1090472
Basically, I had it working with 0.46 reading a 560mb ext3 (with 256b inodes) /home partition in the middle of a 1tb disk. Reinstalled WinXP, installed 0.48, and when I try to access the ext3 WinXP asks to format the disk.
Uninstalled 0.48, installed 0.46a and it now works as before.
September 15th, 2009 at 12:57 am
eks: I see you too have a large EXT-partition that you’re accessing in Windows, could you check and see if you get the same issues as I do?
http://sourceforge.net/tracker/?func=detail&aid=2857629&group_id=43775&atid=437368
Would love to have profiled it myself but I’m a web developer, even asked my father if he could look at it (C/C++ programmer), but he couldn’t make heads or tails of it; Never played around with drivers before, it seems. :-\
September 21st, 2009 at 3:47 am
eks, re: I have encountered the same problem in xp… May be there is a bug in exe installer?
Try to install the driver via inf file in ext2fsd-0.48.zip, it works well for me (note, however, the wrong version, in the inf file). Then ext2mgr and other included tools may be installed manually, if necessary.
September 22nd, 2009 at 1:25 pm
Really, the BSOD are really annoying, I’m getting them so often to the point that I dread using my ext2 partitions. My biggest wish right now is for a new release that will solve them. I get the same error “bad pool header”, especially when navigating with Explorer in big folders. I’m using Total Commander and it’s a bit better, but I’ve got those BSODs too, with TC.
September 25th, 2009 at 5:48 pm
Hello.. googling I got that (at now, end of sept 2009) no win drivers exist for ext4 partitions.
Can you give us some comments on the development status (if any) of an ext4 option to be included in ext2fsd ??
ciao e grazie…
September 27th, 2009 at 11:24 pm
Antonello: EXT4 is backwards compatible, so you can use this driver with it. Won’t get the new features of EXT4 though, but that shouldn’t be a necessity when running in Windows anyway.
September 29th, 2009 at 12:38 am
I had exactly the same problem as eks above. Ext2fsd.46a working fine mounting a truecrypt ext3 volume under winXP. Reinstalled winXP, upgraded to .48, whenever I mounted the volume it came up as unformatted. Found Eks note above, downgraded back to .46a, works perfectly again. I think there is a problem with .48 . . .
PS great software!
October 1st, 2009 at 4:09 am
Just installed on my laptop with a 320 gig drive partitioned with ~130 Gig for Linux root, ~15 Meg for /boot, ~150 Gig for WinXP, and ~40 Gig for FAT32. v.48 doesn’t seem to mount the / partition correctly…WinXP complains that it needs to be formatted. But, v.46 works just fine.
Otherwise, awesome job!
October 1st, 2009 at 9:26 pm
Noted above v.048 WinXP problem seems may be solved manually, by deleting after installation related registry parameter `Automount’ (=0) in [HKLM]/…/Ext2fsd/parameter/ at all, or setting Automount=1 (see, also, corresponding option in Ext2Mgr).
October 8th, 2009 at 3:43 pm
Whenever I change my eSATA Drives formated in ext3 on a WinXP pro SP3 the hole system hangs and Ext2Fsd will not close anymore, so I have to switch the power of.
October 11th, 2009 at 5:31 am
I’ve noticed the same issue as Thomas, after I had upgraded to 0.48 from 0.46. However, after I uninstalled 0.48 and did a manual cleanup of the Registry and the inf-folder (were one file and a couple of reg entries left), I reinstalled 0.48. Now it seems to be working just as nicely as 0.46 was.
Speed is still a HUGE issue on my 750 GB EXT3 partition though.
October 11th, 2009 at 9:58 pm
The previous statements about ext4 compatibility are of course wrong. While partially compatible, once you use extents (and why would you not?), compatibility is lost. Hence, no ext2fsd for you.
I too would very much appreciate support for ext4 in ext2fsd. (any plans, Matt?)
October 14th, 2009 at 1:57 am
Ah, I stand corrected then. Thanks for letting me know about that caveat, bot.
October 15th, 2009 at 7:25 am
Did not mount my ext3 usb drive. I installed it, choose not to run it as a service. Started the manager after install. Saw the disk and choose to assign it a drive letter. However it never gave me a mount point. Could not mount the disk in WinXP professional.
October 16th, 2009 at 3:31 am
All you that are getting BSOD:s should help debug the driver by sending in a memory dump to one of us that knows how to analyze it, Matt is busy but I could try to help: bosse at acc.umu.se
Regarding ext4: Files stored using extents (default on) can’t be read with the Windows driver but ext4 with mount option noextent or old files on an upgraded ext3 partition can be read.
October 18th, 2009 at 8:43 pm
Excuse me for my precedent comment. ext2fsd seem to work on Windows Seven 64bits but I have to reboot to verify. Thanks
October 21st, 2009 at 6:49 am
Why do hard links not work?
When executing under Cygwin something like:
ln x.txt y.txt
on an ext2 file system, and then check with
ls -i
or with stat I get different inode numbers.
They should be the same for hard links,
but instead, I just get a copy of the same file.
October 21st, 2009 at 6:18 pm
I have some problem with Ext2Fsd-0.48 on Win XP Prof. After 2 days using this one the system send message “Insufficient system resources exist to complete the request”.
I’m coping many files with size about 30GB and more. After getting the message system was freezing and I need to reboot system by power button.
Can you advise, what I need to do for solving the problem?
Thanks!
October 22nd, 2009 at 10:50 pm
first: thanks! great driver works very well!
second: I have a problem… I lateley upgraded to win7 and upgraded my fs to ext4! first everything worked as normal, but since mondey (hell-of-patch-atuo-install) the drive is only in read only mode… tried multiple times to fix this with no success! anyone with a similar prob?
October 23rd, 2009 at 2:51 am
>second: I have a problem… I lateley upgraded to win7 and upgraded my fs to ext4!
The driver does not realy support ext4 but you can read old files and files created with mount option “noextent”
October 27th, 2009 at 6:37 pm
Reading through these comments, I think it would be great if you could clarify the situation for users with ext4 partitions. Specifically which options (when creating and mounting) are supported, and which are not!
Thanks!
November 1st, 2009 at 1:35 am
Hi:
Thanks a lot for your work, used this driver in Vista succesfully.
Now on Windows 7 I see in the FAQ page that its NOT officially supported, but I see people here using it though some having BSODs.
I would like to know if its safe to use on Windows 7? Are there any know problems with the driver (like it would cause data loss) in 7 that would stop anyone from using and just wait for it the be updated?
November 1st, 2009 at 1:59 am
Hello, some people have reported BSOD on Windows 7 and after analyzing there memory dumps I found an error where the driver referenced memory after it was freed. I have produced a new version of the driver with a fixed for this, you can get it here: http://www.acc.umu.se/~bosse/ext2fsd-new.zip At least one user have reported that the problem is solved in this version. (Note that Matt is the main developer for the driver I only help debug it)
November 1st, 2009 at 2:13 am
One more thing: Use the driver in the “fre” directory, “i386″ for 32-bit Windows and “amd64″ for 64-bit Windows, just copy the .sys file to \windows\system32\drivers\ Also note that the test release is not signed so on 64-bit Windows you must press F8 at boot and select “disable enforce driver signing”.
November 1st, 2009 at 2:19 am
Yet another thing: The new test release I mention above also sets the hidden attribute on files stored using ext4 extents, since the driver cant read the content of those files I thought it could avoid confusion if they are not visible.
November 1st, 2009 at 7:34 am
Thank you Matt & Bo Brantén !
I’ve successfully used Ext2fsd on Windows 7 to read my ext4 filesystem.
For those interested, the how-to is here: Read ext3/ext4 Partition from Windows 7
November 5th, 2009 at 3:46 pm
I’ve got another odd problem with these drives on Windows XP sp3, wondering if anyone else is having the same issue or if they can reproduce it.
I’ve got a 1tb drive formatted to ext3, and a FAT32 truecrypt volume. If I so much as try to mount or even go near the file to move it or highlight it, windows explorer just crashes and my drive gets unmounted.
The volume is 30GB in size.
November 6th, 2009 at 5:49 pm
Hi,
Just downloaded and followed the instructions of the “beta” for Win7. Until now, no BSOD
I’ll be back to report if & how the new version works.
But .. the ext2 disk not appear with the driveletter in the overview of diskmanagment. And – i think its related – the ext2 disk does not show up in Picasa
However, Picasa reads & write in a folder that’ s drag&dropped.
November 6th, 2009 at 5:51 pm
o wait. Picasa sees the Z:\ (= ext2) as a removable drive.
November 7th, 2009 at 7:26 am
I am running Vista Home Premium on a HP laptop; I have a Ubuntu 9.04 Ext3 installed on a PHDD and I have installed both Ext2IFS_1_11a & Ext2Fsd-0.48 and they are able to read the drive and mount it to any drive letter I want, but whenever I attempt to access them, it tells me I have to formate the drive with no other option. I have been attempting to access this drive for 2 months now with no success; if anyone can provide some feedback on how to resolve this, I would greatly appreciate it.
November 8th, 2009 at 2:13 am
Using 7-zip in Win 7 as the file manager works with 0.48 and ext3 (tested 29GB partition) – no BSOD. Explorer gave BSOD every time. Haven’t tried the debug zip above.
November 10th, 2009 at 10:29 pm
Still no BSOD here with the unofficial beta. So, for me its working good!
November 11th, 2009 at 10:17 pm
The new beta driver works! Thanks!!
November 13th, 2009 at 4:29 pm
Ext2Fsd works fine but when will it be possible to use EXT4-Partitions ?
November 15th, 2009 at 2:46 am
Just wanted to note that using both 0.48 and 0.46a, I can see directories in my root folder, but they’re all empty. This is mounting an ext3 partition with 256 size inodes (the default for my ubuntu 9.10 install). I’m not sure why others could access similar partitions with 0.46a, but neither work for me. Maybe ubuntu 9.10 does something else new and exciting, in addition to changing the inode size?
November 15th, 2009 at 2:50 am
Doh. Looks like ubuntu now installs itself with ext4. So naturally neither work!
November 17th, 2009 at 1:59 am
What to do if Picasa can’t see your ext partition
the answers here
http://byisk.info/?p=468
November 21st, 2009 at 2:10 am
got one BSOD on win7 with the unofficial beta. Been running it for more than 2 weeks 24/7 and got just the one (used to be once every ~2-3 days).
Another issue with 0.48+ is that Properties on reports all selected ext3 files/dirs as 0 bytes in size, whereas 0.46 used to take forever to open but reported correct sizes (again the delay occurred only on ext3 partitions)
November 21st, 2009 at 4:12 am
cygnus – please mail me the minidump from c:\windows\minidump\
Properties reports correct size for me.
November 24th, 2009 at 9:14 pm
I think I’ve found that “the blue screen crash” in Windows 7 comes from the presence in the file system, ext2 / 3 of some links” in the loop “(link that points to a path that contains itself). In this situation the number of files goes to be counted to infinity.
November 25th, 2009 at 5:34 am
This is about ext2fs version 0.48, Ext2Mgr 2.47. It sees the insertion of a USB memory stick which was partitioned on a linux machine, and a drive letter is assigned to the partition of interest, and all the files are visible. I am using FreeOTFE
version 5.10.00.4058 and FreeOTFE driver version 5.00.0000 to get access to a Luks volume on a file. If the Luks volume was formatted as a dos file system (back on the linux machine where it was created) then OTFE asks for the passphrase and unlocks it and a new drive letter becomes available via Windows Explorer, for instance. All the files inside the encrypted Luks files become visible. HOWEVER, if the Luks volume on a file is formatted as an ext2 ( back on the linux machine when it was created), then, after the Luks is unlocked, a new drive letter is available, but when I try to access it Windows Explorer says it is not formatted.
I think this is what is happening … OTFE unlocks it and says to the system that there is a new device; BUT, Ext2fsd does not pick up on it; OR, OTFE doesn’t do the notification completely.
If someone else could try the EXPERIMENT, I would appreciate it:
On a linux machine,
mount # this shows the mounted file systems before the USB
cat /pro/mounts
# Insert the usb memory stick
# cd to the memory stick.
# The object is to create a file sytem on top of Luks on top of a file on the USB memory stick.
dd if=/dev/urandom of=./some-file bs=1M count=1 # make a file with
# random numbers in it
losetup /dev/loop0 ./some-file # provides access to ./some-file
# as though it were a device
cryptsetup luksFormat /dev/loop0
cryptsetup luksOpen /dev/loop0 Luks-01 # creates /dev/mapper/Luks-01
losetup /dev/loop1 /dev/mapper/Luks-01 # provides access to the ‘device’
mkfs.ext2 /dev/loop1
mkdir ./test-mount-point
mount /dev/loop1 ./test-mount-point
cp ./some-file ./test-mount-point
umount /dev/loop1
rm -rf ./test-mount-point
losetup -d /dev/loop1
cryptsetup luksClose Luks-01 # takes down /dev/mapper/Luks-01
losetup -d /dev/loop0
cd
sync;
# remove the memory stick
The test is to see if the file that you copied into the Luks file system appears in a Windows XP system when the memory stick is inserted into the system.
November 26th, 2009 at 5:48 am
I installed Ext2IFS and the ext2 file system encrypted per Luks on Debian etch (4.0)
works as expected: When it is ‘mounted’ per freeOTFE, then a new volume appears
in Windows Explorer and I have access to all the files.
So, I am convinced there is something wrong going on between freeOTFE and ext2fsd.
Hope someone discovers what it is, because I want to use Ext2fsd.
Thanks.
November 27th, 2009 at 12:59 am
Pierpaolo Cellini – I did some tests with recursive links on XP without problem, can you say how to create one that triggers the error.
November 27th, 2009 at 2:06 pm
Yes. And thank you for your interest. It will be morning before I can post
exactly what I did. I wrote scripts so that I could be sure that it was repeatable.
And for me, it is repeatable.
But I am in the middle of some assigned things right now. So, in the morning.
November 29th, 2009 at 3:19 pm
Nice to see there is other with the BSOD problem, i thought i had a hardware problem and couldn’t find what it was before pinning it down.
I’m using Windows xp 32 bit, and right now i’m in the middle of moving a very large number and volume of files from an ext2 drive to an ext3 drive (both external disk in usb).
I’m using v0.48 (mainly since the ext3 one use large inodes), and i’ve been having BSOD since i started to transfer the files.
All goes well as long as i move around directories with not too much files in it and not too voluminous (i’m sure for things under 30Go, for things above 30Go i didn’t find where is the limit yet, through trial and error/BSOD, sometimes 60Go is good, sometimes not, i think it depends on the number of files in the subtree), but as long as i get to one thing too big, it ends up with the “inssufficent ressources to complete” error, and then when i try to access any of the two drives after that (origin or destination), i get a BSOD.
I can’t give you any dump because i had no swap on the system drive so it was not saved, i’ve changed the configuration so it now have one, i’ll see what it gives.
I just put in the new driver linked in the comments to see if it’s working, i’ll let you know.
The BSOD in itself just
November 30th, 2009 at 5:10 pm
I just installed Windows 7 Ultimate (build 7600) and was able to access my 1TB EXT3 partition. Back in XP I used the “Creat a permanent MountPoint via Session Manager” but now in Windows 7 it always states needing format (*even after restarts, disabling UAC w/e) but works flawlessly under the “Automatic mount via MountManager” so far at least ;-D (Crosses fingers for no BSOD)
^Hardcore Linux user, just trying out Win7 for the hell of it now that it’s not beta (i tried that
)
December 2nd, 2009 at 1:45 pm
Ok, I’ve since upgraded my setup to dual boot Windows 7 retail and Ubuntu 9.10 (with ext3 as the file system). I haven’t had a single blue screen problem after applying Bo Brantén’s patch. Much appreciated! All is well, getting speeds over USB at around ~20MB/sec on my 1TB and 500GB drives.
The only major issue I have now is the problem with TrueCrypt I mentioned back in September still exists. I can’t mount any of my FAT TrueCrypt volumes, when I attempt to, explorer just crashes and then I can’t even mount the drive itself anymore without a reboot. I would love to post detailed error messages or logs but I don’t know where to start. Nothing really happens except a total freeze up. Does anyone have any suggestions on what to do since I’m still having this problem, and I’d like to be able to get to my truecrypt drives every now and then?
December 7th, 2009 at 10:21 pm
Bo Brantén: Thanks a lot for trying to fix the BSOD errors for us. Unfortunately mine are still there. I tried with your version, without your version (0.48) and with version 0.46. The problem is with a 160GD IDE HDD with EXT3.
I also have another drive, an external usb drive which works fine (I think).
I have tried with “Automatic mount via MountMgr” or “Create a permanent MountPoint”. With “Create a permanent MountPoint” I can’t access my drives at all. It just says I need to format the drives.
On my Karmic I have no problem with either of the drives. I’ll try a fsck on the drive.
Should I send you my c:\windows\minidump\ ? The one I get with your version?
December 10th, 2009 at 7:27 am
Does ext2fsd support 16KB block sizes as well as 4KB? I have a problem with an EXT3 drive formatted with 16KB block sizes from a SPARC-based Linux box that I can’t access from Ubuntu and wondered if your utility will enable me to get to it from Windows? I have checked the FAQ but there is nothing in there (or anywhere else I can see) about block sizes. Sorry if this is a stupid question!
December 11th, 2009 at 9:27 pm
Further question – after connecting the drive I can see three partitions:
1 – EXT3 – 2GB – “Linux”
2 – RAW – 250MB – “Linux swap”
3 – RAW – 463GB – “Linux LVM”
I have tried mounting partition 3, the one which contains my data, but without any success. It may be because this partition was created using LVM rather than as a simple EXT3 partition, but I just don’t know enough about Linux to know whether this is the problem or not. I can’t see any mention of LVM and whether ext2fsd is compatible with LVM partitions or not on this website.
December 12th, 2009 at 11:49 am
Windows does not support LVM, which lies between the physical HDD and the file system. Thus ext2fsd does not even get to see the logical EXT-3 partition.
December 18th, 2009 at 10:45 pm
Cheers!
I’ve DL the file but how does one install the beta?
December 21st, 2009 at 7:05 pm
Use the driver in the “fre” directory, “i386″ for 32-bit Windows and “amd64″ for 64-bit Windows, just copy the .sys file to \windows\system32\drivers\ Also note that the test release is not signed so on 64-bit Windows you must press F8 at boot and select “disable enforce driver signing”.
December 23rd, 2009 at 5:03 am
working great! been transferring big files and using it with heavy I/O for torrents. had to use this instead of other IFS because my ext3 fs has inode size 256. this is working great even with the larger inode size! on other IFS it would not work with inode size 256.
December 25th, 2009 at 10:49 am
“Also note that the test release is not signed so on 64-bit Windows you must press F8 at boot and select “disable enforce driver signing”.”
You can use test signing for things like this.
January 7th, 2010 at 1:04 am
it seems to me that ext2mgr simply refuses to show the “unlocked” freeotfe devices “\Device\FreeOTFE\Disks\Disk*”. therefore i’m unable to assign drive letters and windows isn’t using the ext2fsd driver for this partitions which results in “drive is not properly formatted” messages by the windows explorer. what can i do?
January 7th, 2010 at 5:25 am
pls help me…. while running this ext2fsd the ext2fsd.sys file will not be created. This is my problem…
January 20th, 2010 at 11:00 pm
thanks a lot … using 0.48 under XP Home:
Quite often, when I delete a directory=folder I get the error, that the directory is used and cannot be deleted. But all the files in the folder are deleted. Only the empty dir is left. One can delete the empty dir afterwards. … how come ?
January 21st, 2010 at 10:50 pm
thank you!
reading is completely working, that’s all i need.
first one working after 3 others…
January 25th, 2010 at 3:21 pm
I have the same problem as noted above with all my Linux partitions
(both ext2 and ext3), namely the drive letters can be assigned, but WinXP
claims the drives are not formatted. I am using Ext2fsd v.0.48.
The Ext2fsd data is given below. I have mounted the 4 Linux partitions
from Disk 0 on drive letters G,H,I,J but none of them can be read
(they are all seen as unformatted partitions).
I run WinXP Pro SP2. I use the Linux boot manager (lilo) which is installed
in the MBR, and WinXP is a menu item.
I am able to view the contents of all but one of the Linux partitions with Paragon Partition Manager, but when mounted they are again regarded as unformatted.
Thanks for any suggestions? Some registry tweak?
…………………………………………………………………………………………………….
Disk devices:
Disk 0: \Device\Harddisk0\DR0
ProductId: ST3320620AS
SerialNumber:
BusType: ATA
Media Type: Basic
DiskGeometry Layout:
BytesPerSector = 512
SectorsPerTrack = 63
TracksPerCylinder = 255
Cylinderst = 38913
MediaType: Fixed
Partition Numbers: 7
Partition Type: Hidden FAT16
StartingOffset: 32256
PartitionLength: 2146765824
MountPoints:
Filesystem: FAT
Filesystem: FAT
Size: 2146467840
Free: 2146172928
Partition Type: HPFS/NTFS
StartingOffset: 2146830336
PartitionLength: 62915134464
MountPoints: (C:)
Filesystem: NTFS
Filesystem: NTFS
Size: 62915133440
Free: 49463250944
Partition Type: Linux
StartingOffset: 65061964800
PartitionLength: 92007982080
MountPoints: (G:)
Partition Type: Linux
StartingOffset: 188400070656
PartitionLength: 45181430784
MountPoints: (H:)
Partition Type: Linux swap
StartingOffset: 233581533696
PartitionLength: 2154991104
MountPoints:
Partition Type: Linux
StartingOffset: 258890720256
PartitionLength: 6851625984
MountPoints: (I:)
Partition Type: Linux
StartingOffset: 265742378496
PartitionLength: 54303266304
MountPoints: (J:)
Disk 1: \Device\Harddisk1\DR8
VendorId: WDC WD12
ProductId: 00JB-00DUA3
BusType: USB
Media Type: Basic
DiskGeometry Layout:
BytesPerSector = 512
SectorsPerTrack = 63
TracksPerCylinder = 255
Cylinderst = 14593
MediaType: Fixed
Partition Numbers: 5
Partition Type: FAT32X
StartingOffset: 32256
PartitionLength: 58366554624
MountPoints: (D:)
Filesystem: FAT32
Filesystem: FAT32
Size: 58352271360
Free: 30379343872
Partition Type: Linux
StartingOffset: 58366586880
PartitionLength: 27373731840
MountPoints:
Partition Type: Linux
StartingOffset: 85740350976
PartitionLength: 12782052864
MountPoints:
Partition Type: Linux swap
StartingOffset: 98522436096
PartitionLength: 542836224
MountPoints:
Partition Type: Linux
StartingOffset: 99065304576
PartitionLength: 20966206464
MountPoints:
Cdrom/DVD devices:
Cdrom 0: \Device\Cdrom0
ProductId: TSSTcorp CD/DVDW SH-S182D
SerialNumber:
BusType: ATAPI
Media Type: DVD
DiskGeometry Layout:
BytesPerSector = 2048
SectorsPerTrack = 32
TracksPerCylinder = 64
Cylinderst = 150
File system: CDFS
Online,Media Removable
Mountpoints: (E:)
Cdrom 1: \Device\Cdrom1
ProductId: Imation IMW16DL84I
SerialNumber:
BusType: ATAPI
Media Type: DVD
DiskGeometry Layout:
BytesPerSector = 0
SectorsPerTrack = 0
TracksPerCylinder = 0
Cylinderst = 0
Media ejected
Mountpoints: (F:)
Volume: \Device\HarddiskVolume1:
Filesystem: FAT
Mountpoints:
Volume status: Online
size: 2146467840
free space: 2146172928
Extent: 0
DiskNumber: 0
StartingOffset: 32256
ExtentLength: 2146765824
Volume: \Device\HarddiskVolume2:
Filesystem: NTFS
Mountpoints: (C:)
Volume status: Online
size: 62915133440
free space: 49463250944
Extent: 0
DiskNumber: 0
StartingOffset: 2146830336
ExtentLength: 62915134464
Volume: \Device\HarddiskVolume3:
Filesystem: EXT2
Mountpoints: (G:)
Volume status: Online
size: 92007982080
free space: 92007982080
Extent: 0
DiskNumber: 0
StartingOffset: 65061964800
ExtentLength: 92007982080
Volume: \Device\HarddiskVolume4:
Filesystem: EXT2
Mountpoints: (H:)
Volume status: Online
size: 45181430784
free space: 45181430784
Extent: 0
DiskNumber: 0
StartingOffset: 188400070656
ExtentLength: 45181430784
Volume: \Device\HarddiskVolume5:
Filesystem: SWAP
Mountpoints:
Volume status: Online
size: 2154991104
free space: 2154991104
Extent: 0
DiskNumber: 0
StartingOffset: 233581533696
ExtentLength: 2154991104
Volume: \Device\HarddiskVolume6:
Filesystem: EXT2
Mountpoints: (I:)
Volume status: Online
size: 6851625984
free space: 6851625984
Extent: 0
DiskNumber: 0
StartingOffset: 258890720256
ExtentLength: 6851625984
Volume: \Device\HarddiskVolume7:
Filesystem: EXT2
Mountpoints: (J:)
Volume status: Online
size: 54303266304
free space: 54303266304
Extent: 0
DiskNumber: 0
StartingOffset: 265742378496
ExtentLength: 54303266304
Volume: \Device\HarddiskVolume8:
Filesystem: FAT32
Mountpoints: (D:)
Volume status: Online
size: 58352271360
free space: 30379343872
Extent: 0
DiskNumber: 1
StartingOffset: 32256
ExtentLength: 58366554624
Volume: \Device\HarddiskVolume9:
Filesystem: EXT2
Mountpoints:
Volume status: Online
size: 27373731840
free space: 27373731840
Extent: 0
DiskNumber: 1
StartingOffset: 58366586880
ExtentLength: 27373731840
Volume: \Device\HarddiskVolume10:
Filesystem: EXT3
Mountpoints:
Volume status: Online
size: 12782052864
free space: 12782052864
Extent: 0
DiskNumber: 1
StartingOffset: 85740350976
ExtentLength: 12782052864
Volume: \Device\HarddiskVolume11:
Filesystem: SWAP
Mountpoints:
Volume status: Online
size: 542836224
free space: 542836224
Extent: 0
DiskNumber: 1
StartingOffset: 98522436096
ExtentLength: 542836224
Volume: \Device\HarddiskVolume12:
Filesystem: EXT3
Mountpoints:
Volume status: Online
size: 20966206464
free space: 20966206464
Extent: 0
DiskNumber: 1
StartingOffset: 99065304576
ExtentLength: 20966206464
January 26th, 2010 at 4:42 am
On the issue of after mounting the partition with a drive letter and windows saying format required – I also had this issue, and I just started the service by going to tools, Service Management and start the service. Once I did that, I had no problems with seeing the base directory of my ext3 partition. Granted, I still have hidden files as I can’t see my home folders at all, But I’m assuming its part of the ext4 thing that ubuntu 9.10 does, even though the partition shows as ext3.
February 2nd, 2010 at 2:42 pm
4k sector support.
Since windows doesn’t support 4k sector drives such as WD 1 – 2 TB drives, any problems mounting one formatted ext3 ?
February 8th, 2010 at 5:46 pm
Thank you for that driver so much. There are two issues which i want to solve.
1.) i run in the same promlem as eks, i upgraded from 0.46 to 0.48 on a Win-XP SP2 machine and my ext3 partition came as unformated, also Ext2Mgr could not be started. Downgraded to 0.46a and it runs.
2.) with 0.46 and 0.46a accessing an ext3 partition with utf8 encoding brings up quirky Letters for german umlaut (vowel). Changing “Global Codepage” in “Service Management” in “Volume Manager” from default to utf8 dose not change anything, even other settings do not show any effect.
Any comment?
February 9th, 2010 at 3:27 am
Tried Ext2IFS and had problems.
Loaded Ext2Fsd-0.48 and is working fine so far. XP-Pro-SP2-x86.
Good work !
Feature Request:
Support for GPT partitioned drives greater than 2TB.
With Ext2 formatted 4k/8k blocks, this would provide support
for 16TB/32TB drives, giving XP-32bit hudge R/W data disks
that M$ seems to be closing the door on.
February 26th, 2010 at 2:10 am
ext2fsd saved my life. It’s simple and does what you need. Thank you for your work!
February 26th, 2010 at 5:08 pm
For me it is working ok, but using the patch provided by Bo Brantén. Otherwise I was getting several BSOD errors each day. The only problem I have is that this patch is not digitally signed and I have to disable the digital signature check each time the windows is booting. Does anybody know a solution to this without having to disable the signature check?
February 28th, 2010 at 2:56 am
Indeed, it seems that Bo’s patch is working for everyone who has bsod problems. Any chance of a proper signed release?!
March 3rd, 2010 at 8:31 pm
I recently rebuilt my htpc and decided to you use Win7 x64. On my previous htpc I installed Win XP and used ext2fsd with an ext2 partition. It worked pretty good to prevent fragmentation for all my downloaded files. After the upgrade I was concerned after reading about all the BSODs on win7. Then I saw the beta driver but couldn’t use it because my htpc turns itself on automatically and no one around to push f8 during the boot process. So I was about to put ext2fsd on hold until I found something called ReadyDriverPlus. Supposedly, it that pushes f8 and disables driver signing for you. I have tried it yet but now I am hopeful again. For all those interested until a signed driver is released, here ya go and good luck! http://www.citadelindustries.net/readydriverplus/
March 13th, 2010 at 6:35 pm
It would be good to have the signed driver or a method to disable the enforcement only for this driver. Otherwise you are compromising the whole security of the system.
March 15th, 2010 at 9:55 pm
I installed win7 and ubuntu9.10 on my laptop, and I installed ext2fsd, want to copy files from ubuntu. But in win7, I can only see directories on my ubuntu, all the directories are empty. Can someone help me to solve it? Thanks.
March 16th, 2010 at 4:22 am
I have exactly the same problem, alex. I hope someone helps us finding a solution soon.
March 19th, 2010 at 3:33 am
Regarding the patchfile supplied by Bo from last November,
1). what do I do with the .pdb file
2). what do I do with the “chk” directory files?
Tnx
March 20th, 2010 at 1:00 pm
I have an Ext3 formatted external drive with 450 Gigs of data accumulated with various Linux distros. Running Win 7 Pro on new laptop.
What a headache. This is summary I made for myself ’cause I assume this driver will fail again for no apparent reason. So far has been steady since finally got working.
Win 7 has lots of trouble with file tags set by Linux but I’m gradually getting it worked out. Next time I’m going to set up a separate NTFS partition and write all the stuff I want to share to it so can always be read by Linux or Windows without going through this BS again.
Putzing around with sucky GUIs…….
1. Re-install with write and force write.
2. Change folder permissions to full control then change owner to user(self) in advanced tab.
3. Change to run only as administrator.
4. Next time fails log GUI steps — first 2 attempts didn’t work. Also try flushing dead drive letters first before deleting and reinstalling ExtFsd.
5. There are several slightly different GUI step options and one finally worked so next time just play around with it – log steps and save the one that worked.
6. 3/16/2010 at 2PM after nearly giving up and just doggedly sticking with it —
I FINALLY HAVE FULL WRITE ACCESS TO THE CIRAGO WITH WINDOWS 7!!!
7. Don’t forget this may have been enabled by the partdisk tip from technet forum
for changing disk read only flag even when it says read only etc.
http://tinyurl.com/yfnej9q
8. If Windows Explorer fails to list drive go to ExtFsd, right click volume with missing drive letter, hit reload and refresh. Worked.
9. Never close GUI. Only ever minimize. When reboot or wakeup from sleep drive auto-initiates. Service startup mode = SERVICE_SYSTEM_START
March 20th, 2010 at 1:36 pm
By the way – many distros are releasing now with Ext4 as default. If you format with Ext4 you’re out of luck. There is nothing available to read with Windows and no projects even started that I could find. You’ll need a shared NTFS partition from now on.
April 4th, 2010 at 5:34 pm
To Roger Young (and maybe others who are reporting problems like “Windows complains that disc needs to be formatted”):
This can occur if you have a hard disk larger than 128 Gbytes. The problem can appear either if you used a Windows installation CD prior to Windows 2000 SP 3 or prior to Windows XP SP 1 while installing Windows, or if you installed Windows using an installation CD with Windows 2000 SP 3 (or higher) or Windows XP SP 1 (or higher), but you had no hard disk in your computer larger than 128 GBytes (137 Gbytes, if incorrectly taken 1GB as 1000 MB) at this time. In such a case you either do not have any support for 48-Bit LBA, or you have support for 48-Bit LBA, but it is disabled.
It seems, that performing the procedure which is described in Microsoft’s Knowledge Base, KB305098 (for Windows 2000) and KB303013 (for Windows XP) can help. (Please pay attention to the warnings that you find in these articles.)
Shortly, begin by updating to Windows 2000 Service Pack 3 (or higher) or Windows XP Service Pack 1 (or higher), if necessary.
Start regedit.exe. Go to the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters
and add (or modify if it is already present) a registry value
EnableBigLba
type: DWORD
value: 0×1
Reboot your computer.
You can see http://www.fs-driver.org/troubleshoot.html addressing this problem.
April 8th, 2010 at 7:37 pm
1). what do I do with the .pdb file
It is read by the debugger if you debug the driver or analyze a crash dump.
2). what do I do with the “chk” directory files?
It is the debug version of the driver, it contains more information and some extra checks but has lower performance.
April 8th, 2010 at 7:43 pm
> I installed win7 and ubuntu9.10 on my laptop, and I installed ext2fsd, want to copy files from ubuntu. But in win7, I can only see directories on my ubuntu, all the directories are empty. Can someone help me to solve it? Thanks.
The driver does not support files stored using ext4 extents witch is default on many new distros, however you can write files from Windows anyway to the directories you se and you can also read files written while using the mount option noextent in Linux.
April 11th, 2010 at 4:17 pm
Is the driver mentioned at the top the same with the bugfixes from Bo Branten (like the one from 30/10). Because the date is september 2009 and suggests that the bugfixes of Bo Branten are not included
April 12th, 2010 at 5:54 am
Hello together
I’m running Windows Vista Business 32 bit and installed Ext2fsd to have access to my Ext3 Debian Sqeeze home Partition on the same drive. I could assign a drive letter and the partition is visible as Drive F: in the Explorer.
The problem is i can’t access it because Windows want to format it first.
Before trying Ext2fsd I also tried Ext2IFS with the same result There is a commandline diagnostic tool availible on the homepage from Ext2IFS and it told me that I have to change the Inode size from 256 to 128 KB first before I could use the driver.
Why does the Ext2FSD driver leads to the same result in spite of its capability to handle 256 KB Inodes and is there a solution of this problem yet?
April 12th, 2010 at 7:33 pm
The latest version is here: http://www.acc.umu.se/~bosse/ext2fsd-new.zip
To use it you first install the distribution and then copy the new .sys file to \windows\system32\drivers.
April 13th, 2010 at 5:28 am
I did as you advised and copied the driver from =>fre0=>x860=>ext2fsd.sys into the System32 directory but it didn’t help. This new driver should be a fix for BSOD in Win7? Maybe that’s because it doesn’t work?
It’s the same result as before: Windows just wants to format the drive.
Dirk
April 13th, 2010 at 5:32 am
..maybe the reason that it doesn’t work is because may Partition to mount is NOT a primary partition but a logical partition in a Extended Partition?
April 24th, 2010 at 10:55 am
http://ext2read.blogspot.com/ -> According to the home page, it can read ext4 file systems with extents.
However, this is not a file system driver (think explore2fs and not ext2fsd/ext2ifs).
May 2nd, 2010 at 5:02 pm
Whoever has been bitten by “Empty directories” bug might want to subscribe to the following bug to be notified when it gets fixed:
https://sourceforge.net/tracker/?func=detail&aid=2995425&group_id=43775&atid=437368
May 3rd, 2010 at 4:29 pm
As regard the “WIndows complains that the disc needs to be formatted” problem detailed by Roger Nagy in his Apr 4 2010 note and my note of Sept 29 above -
I have a 500 gig USB disc partitioned into two 224 gig areas, one of which is NTFS and the other ext3. My system is dual boot winXP SP3 and suse 11.2 and the ext3 partition which is used by both OS is encrypted as a device using Truecrypt.
I have been using Ext2Fsd for some time to mount the ext3 part then remount it using Truecrypt, most recently using the .046a release. I had found that if I mounted the USB disc using the “usb mount” option it came up with the “windows needs formatting” error, but if I mounted it as a fixed disc it worked fine after a reboot.
For other reasons I had to reinstall winXP, so in order to upgrade (and reading the note from Matt on the .048 release notes that said USB was improved) I installed .048 and found the same “windows needs reformatting” error, whether I mounted as USB or as fixed disc. I spent some hours trying various combinations but the error stayed. Interestingly, I tried Matt’s “mountdiag” tool and it told me that the problem was that the ext3 was 128 bit i-nodes and that I should back up the data, reformat to the larger i-node size, and try again. I haven’t really the time to do this at the moment, and given that I knew 0.46a had mounted the part fine I was a bit skeptical of this solution.
So I again uninstalled .048, rebooted, cleaned the registry, installed .046a and mounted the ext3 encrypted part as a fixed disc. Once again everything works fine, and I don’t seem to see any problems even when I unplug and replug the USB disc.
Again, thanks to Matt for a great utility. I’m passing on my results above as a help to others with the problem and possibly as some clues to Matt in terms of tracking down the issue.
May 4th, 2010 at 12:42 pm
I have problem with “unformated partition” on Windows 7 64-bit. For me: changing Tools -> Service Management -> Service Startup Mode from SERVICE_SYSTEM_START to SERVICE_BOOT_START solved problem.
May 20th, 2010 at 7:53 am
Great blog, I wanted to comment that i tried and i can’t connect to the rss reader, you should install certain wordpress plugin for that to workthat.
May 21st, 2010 at 9:48 am
I totally agree with ABEgorov statement; If you have problems getting with “unformated partition” on Windows 7 64-bit, open up Ext2Fsd program and go to Tools -> Service Management -> and change Service Startup Mode from SERVICE_SYSTEM_START to SERVICE_BOOT_START. And last reboot computer.
May 26th, 2010 at 8:39 am
it’s really nice software. I want to make a review about this one on my blog, http://otak-komputer.blogspot.com
I hope you didn’t mine if I do that. Thanks
June 4th, 2010 at 5:58 pm
In case anyone gets confused, like me, about what drivers to install, as they are all the same version:
In the Ext2Fsd-0.48.zip you can download from sourceforge you will find 2 versions, one signed and one unsigned for each different OS (2K, XP and 64 bits), both of them are 0.48.7.26, and in case of the XP versions (valid for Vista & 7) checksums are:
ext2fsd.sys (signed):
CRC32: 12A396CB
MD5: 0F8F910C369D8B45FACFDA04CBB8008E
ext2fsd.sys (unsigned):
CRC32: 32F75689
MD5: 9F8D1120E72C627BB2549B0424D2BD9A
These ones do not contain any of the mentioned patches.
On the other hand the fixed driver you can download from:
http://www.acc.umu.se/~bosse/ext2fsd-new.zip
its v0.48.7.26 too but unsigned only and the Ext2fsd.sys has this checksums:
CRC32: BC685D60
MD5: 58A481B3C79B9B3A1AEC669CFD691E17
June 5th, 2010 at 7:23 pm
Works perfectly under Windows 7 64 !
Thanks a lot for your great work
June 11th, 2010 at 6:53 pm
It works great, thanks alot !
June 17th, 2010 at 3:51 am
sometime blue screen crash windows seven 64bit edition on my ext3 mandriva partitions
July 4th, 2010 at 7:07 pm
Hey guys,
I myself find it super but while trying to read an ext4 under w7 64bit i get my folders visible but no files inside!
What could be the cause of that?
Thanks!
July 12th, 2010 at 12:37 am
Anyone know if there’s any chance of having UNICODE support anytime soon?
July 13th, 2010 at 1:43 am
Hi Guys
Wanted to leave a short guide for all having problems with ext2fsd+freeotfe on windows 7 x64:
1) Enable testsigning as explained in the FAQs
2) Download Ext2Fsd-0.48.zip from sourceforge
NOTE: the installer version didnt work for me – always got the “disk is not formarted error” dont know what causes this and didnt investigate further.
3) Extracted and rename Ext2Fsd-0.48\Ext2Fsd\Setup\w64\ext2fsd.sys to ext2fsd.unsigned or delete the file
4) rename Ext2Fsd-0.48\Ext2Fsd\Setup\w64\ext2fsd.signed.sys to ext2fsd.sys
5) edit Ext2Fsd-0.48\Ext2Fsd\Setup\ext2fsd.inf
search for the following lines:
HKR,”Parameters”,”Ext3ForceWriting”,%REG_DWORD%,0×00000000
HKR,”Parameters”,”WritingSupport”,%REG_DWORD%,0×00000000
and change them to:
HKR,”Parameters”,”Ext3ForceWriting”,%REG_DWORD%,0×00000001
HKR,”Parameters”,”WritingSupport”,%REG_DWORD%,0×00000001
6) run “setup.bat w64″
Note: I have UAC diabled, dont know if it works with UAC on
July 26th, 2010 at 3:02 am
the link for the driver fix (ext2fsd.new.zip) unfortunately is down. could someone reupload it or tell me another download location that works?
July 27th, 2010 at 11:56 pm
New release with full support for big files and directorys on ext4 http://www.acc.umu.se/~bosse/ext2fsd-0.48-bb5.zip