
Formatting an EXT3 disk in Windows
#1
Posted 07 March 2011 - 10:03 AM
#2
Posted 07 March 2011 - 10:26 AM
I can only find a reader(LinuxReader),
Your ubuntu cd or PartedMagic on a stick, would be my way.
GNU/Linux is fast at formatting.
And it would only take a few minutes to delete the partition. The reboot back to windows to do the creating and formatting of the raw partition.
I'm interested on how you get this job/task done with out rebooting.
Regards Glenn
#3
Posted 18 March 2011 - 02:48 PM
Edited by lew~, 18 March 2011 - 03:20 PM.
#4
Posted 18 March 2011 - 02:54 PM
#5
Posted 18 March 2011 - 04:05 PM
#6
Posted 18 March 2011 - 08:19 PM
I think you're confusing the terms disk and partition. Unless of course, you did the extra-unusual step of abandoning the idea of a partition table and went and formatted the entire disk EXT3, which would be why Windows is so confused. (It'll be expecting a MS-DOS disklabel there.)
The thread title made me wonder if you weren't trying to format a disk partition as EXT3.
The EXT3 partition, when residing in a MS-DOS disklabel (typical of most IBM clone installations) typically will be marked as partition type 0x83 (Linux FS), 0x8e (Linux LVM) or 0xfd (Linux software RAID). Windows will not recognise this by default, and therefore will not attempt to mount the volume on a drive letter. If I recall correctly, in order to format it, it needs to be mounted in some way. (This is in stark contrast to Linux, where you need the device to be unmounted.)
Windows only recognises FAT volumes (0x04, 0x06, 0x0b, 0x0c, 0x0e or 0x0f), extended partitions (0x05), or NTFS/HPFS (yes, they use the same partition type; 0x07). You will need to change the partition to be one of these recognised types (except extended) before it will recognise it. Catch is, I do not believe Windows gives you that ability — end users aren't supposed to know about this sort of thing.
Therefore your easiest course of action will be to blow away the partition first and create afresh. You should be able to do this in Disk Management. Right-click on "My Computer" and select Manage. From there, locate the disk manager applet, it should load up and display your drives, each with the partitions contained within. Right-click on offending partition and select "Remove".
It should hopefully comply, and you'll be left with space to place the new partition by a similar method. Once created, you should then be able to mount the empty volume on a drive letter and format it in the usual manner.
Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind, it's backed up on a tape somewhere...
No longer active on these forums, see http://stuartl.longlandclan.yi.org/ for contact details.
#7
Posted 19 March 2011 - 10:34 PM
Therefore your easiest course of action will be to blow away the partition first and create afresh. You should be able to do this in Disk Management. Right-click on "My Computer" and select Manage. From there, locate the disk manager applet, it should load up and display your drives, each with the partitions contained within. Right-click on offending partition and select "Remove".
It should hopefully comply, and you'll be left with space to place the new partition by a similar method. Once created, you should then be able to mount the empty volume on a drive letter and format it in the usual manner.
This is what I was visualising, and wondering why it wasn't working. Teach me to assume too much.
#8
Posted 20 March 2011 - 01:56 PM
#9
Posted 22 March 2011 - 10:33 AM
Okay, I can mount the drive. I can view its file system in Windows. (Server 2008 R2, btw.)
It is when I go to delete the EXT3 volume and reformat it as NTFS when things go tits up.
If I open disk manager, I can delete the partition, then it shows it as unallocated. When I go to create a new one, the moment it attempts to format an error is thrown up.Two caps below, before and after.

I did run DISKPART to clean the disk, this left the disk in an 'unallocated' state, then I was back to square one when it reverts back to an EXT3 partition, couldn't format it. As is depicted above.
I can use a *nix boot disk, or UBCD...but that detracts from my original statement whereby I would like a solution that doesn't involve me bringing down the Windows server. Which is a Hyper-V box hosting many other servers.
It is not that critical, but rather than just say "Fuck it, you win, I will shut you down and insert you into a Linux environment so as I can delete your bastard of a partition" I would like to find a way...it is the Atomic way, not to give in.
Oh and don't get me started on shouldn't Windows just work.
It was Linux that got me into this mess in the first place.
The reason it is now in a Windows box is because I got sick and tired of having to execute a mountain of code just to execute basic tasks...you know, like installing drivers and or applications :p
Edited by twinair, 22 March 2011 - 10:34 AM.
#10
Posted 22 March 2011 - 10:46 AM
I did run DISKPART to clean the disk, this left the disk in an 'unallocated' state, then I was back to square one when it reverts back to an EXT3 partition, couldn't format it. As is depicted above.
This bit is confusing, I wonder how the disk keeps "reverting" to having an ext3 partition?
The CLEAN command should leave the disk, as you say, unallocated. You then use Disk Manager to create a partition (or Simple Volume) and format it.
Are your new, unformatted partitions coming in as being identified as ext3?
#11
Posted 22 March 2011 - 10:52 AM
Only on that particular disk.Are your new, unformatted partitions coming in as being identified as ext3?
Yes, it is weird, isn't it?
#12
Posted 22 March 2011 - 11:01 AM
Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind, it's backed up on a tape somewhere...
No longer active on these forums, see http://stuartl.longlandclan.yi.org/ for contact details.
#13
Posted 22 March 2011 - 11:04 AM
#14
Posted 22 March 2011 - 08:12 PM
#15
Posted 24 March 2011 - 07:52 PM
#16
Posted 24 March 2011 - 10:31 PM
Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind, it's backed up on a tape somewhere...
No longer active on these forums, see http://stuartl.longlandclan.yi.org/ for contact details.
#17
Posted 17 May 2011 - 04:16 PM
GlennsPref: Don't see why you'd have to reboot after formatting...
I thought you had to to rewrite the changed specs to the disk record (partition table).
Most disk/partition managers I use(, not M$) require rebooting after changes to the partition table.
;-) Glenn
#18
Posted 09 March 2012 - 08:26 PM
#19
Posted 09 March 2012 - 10:18 PM
I am having this exact same problem. A disk was initially set up with two EXT3 partitions and a linux swap space partition and works fine as such. I can delete the partitions in windows 7 disk management (yielding unallocated space) but as soon as I reformat to NTFS it will chug away for about 20mins, then fail. The disk then reverts back to EXT3 even if it was recognised as unallocated space before the format was attempted! I am sure there is more to this problem than the disk simply being f*cked.
At this stage I suspect the ext2fs driver I have installed in win7 is causing the problem (even if the drive is not mounted by the ext2fs explorer software).
-zoldrin
Uninstall driver, reboot, format now successful. Cannot say for sure if it was the driver or simply reboot. To original poster - did you have such a driver installed also?
#20
Posted 25 July 2013 - 03:16 PM
I am having this exact same problem. A disk was initially set up with two EXT3 partitions and a linux swap space partition and works fine as such. I can delete the partitions in windows 7 disk management (yielding unallocated space) but as soon as I reformat to NTFS it will chug away for about 20mins, then fail. The disk then reverts back to EXT3 even if it was recognised as unallocated space before the format was attempted! I am sure there is more to this problem than the disk simply being f*cked.
At this stage I suspect the ext2fs driver I have installed in win7 is causing the problem (even if the drive is not mounted by the ext2fs explorer software).
-zoldrin
Uninstall driver, reboot, format now successful. Cannot say for sure if it was the driver or simply reboot. To original poster - did you have such a driver installed also?
I know it's a long time since anyone wrote anything on this thread, but I can confirm this. I had the same problem as the postee of this thread. I also had the ext2fsd-drivers installed. I uninstalled it and then tried formatting it again. Successfull!
My initial problem was that my Linux distro(OpenSuSE 12.3), did not want to partition/delete one of two discs containing an older SuSE distro(SuSE 11.3). I was logged in as $USER, opened YAST as usual by giving root-password. I could delete and repartition on one disc, but not the other. But I have a feeling that one has to be logged in as root to do some jobs in SuSE, and not just do a sudo or su.
Edited by oopsypoo, 25 July 2013 - 03:18 PM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users