diskpart

[SIW2]

And yet, we have two apparently conflicting screenshots:

That is precisely why I mentioned one of the Partition Wizard bugs.

Are we to believe nothing took place in between.

Yes

 

[dsperber]

And yet, we have two apparently conflicting screenshots:

That is precisely why I mentioned one of the Partition Wizard bugs.

I'm still trying to understand...

Are you saying that THIS presentation from PW, purportedly showing "100% unallocated", is actually a bug in PW?

I really do find that hard to believe.

Let's review what he's shown us.

(1) DISKPART LIST DISK shows two hard drives, the second with 232GB and 0GB free is the one in question, Iomega Prestige--250gb--54AJ34J763.

(2) DISKPART LIST VOLUME shows 11 volumes, of which VOLUME 10 is this 232GB disk partition with "RAW", i.e. factory unformatted with no file system on it.

(3) DISKMGMT showing the two hard drives, the second of which is "healthy, active + primary" of 232GB but no file system on it.

(4) DISKMGMT showing two hard drives, the second of which has now been partitioned (with PW presumably, following my suggested recipe steps) into two partitions: G - 184GB primary but with no NTFS file system, and M - 48GB logical with NTFS file system.

Personally, I believe this problem with G (showing no file system) can easily be fixed by PW, simply by selecting the 184GB space and then selecting the "Format partition" item from the left side available operations list. The partition that currently has no file system should be properly formatted as NTFS, if the setup here is followed correctly.

I've never seen "no file system" in a partition created by PW, so either (a) he failed to have NTFS in the file system box when he created the partition, or (b) there's something about the RAW Iomega drive which also requires a separate second "FORMAT" step after creating the partition... which I hadn't thought of before now.

Alternatively, even within DISKMGMT, if you select that 184GB space, and then right-click, there is also a "FORMAT..." option presented. Again, a properly formatted NTFS partition should result.

(5) Partition Wizard showing once again NO PARTITIONS, but instead showing 100% unallocated 232GB space.

You say this is due to a "bug" in PW? I'm not convinced. I think he must have taken the first action in my "start over" method, and once again performed "delete all partitions". What's called for right now is simply a restart from my original step (7), namely "create partition" from the 100% unallocated free space, performed twice to create two partitions (but hopefully both logical this time, although it's not critical) and specifying NTFS as the file system for both new partitions.

It still may be necessary to also use the FORMAT function (something I hadn't thought to suggest but which now appears that it may well be needed), to properly place a correctly formatted NTFS file system onto the new partitions of this Iomega drive which appears to have arrived "RAW".


So, I would like to see a new and current pair of screenshots from both DISKMGMT and PW. I'm guessing they will both show 100% unallocated space. He must have repeated the first "delete all partitions" step as I asked him to, to "start over".

Then, select the 100% unallocated space in PW, select "create partition" on the left (or, the same operation can be selected from the popup menu if you right-click on the space), define 184GB logical NTFS partition, and OK. The graphic image will now change to show a 184GB partition and 48GB of unallocated space.

Next, select the 48GB unallocated space, select "create partition" on the left (or from the popup menu from right-click), define 48GB logical NTFS partition, and OK. the graphic image will now change to show both a 184GB partition as well as a 48GB partition.

There are now two queued operations in the list shown in the lower-left corner.

Just to be absolutely sure we get NTFS on both partitions, select the 184GB partition in the graphic, and select "format partition" on the left (or right-click and select "format" from the popup menu), and OK.

Repeat for the 48GB partition the same, again adding "format partition" for the 48GB partition to the queued operation list in the lower-left corner.

There are now four queued operations in the list shown in the lower-left corner.

Now push the APPLY button, and it should all work. He should end up with two new partitions on the Iomega drive, freshly created and formatted as NTFS and with two default drive letters assigned.


That's my recommendation.

 

[SIW2]

Did you not read my previous post?

MT have acknowledged to me personally that there is indeed a bug.

They are trying to fix it.

 

[dsperber]

Did you not read my previous post?

I did. But I asked you for a description of exactly what this bug was, that you reported.

Is it this precise issue... that there are two partitions allocated, but PW shows "unallocated" for the drive? Or is it something else?

I have requested OP to provide two fresh brand new current screenshots of the drive, from both PW and DISKMGMT. If they are now both "100% unallocated" then it would not seem to be a PW bug which is in any way entering this story. If DISKMGMT is still the earlier two partitions we saw, and PW is still the 100% unallocated, then I will agree that this is a PW issue which I, personally, have never ever seen myself before.

In that case, sticking with DISKMGMT to "FORMAT" that G-partition (if it is still shown) should install NTFS file system onto that partition which currently shows no file system present.

But my own guess, as to what we will see in the two new screenshots... is that they will BOTH show "100% unallocated". I think he just forgot to tell us that he HAD gotten started with my "start over" procedure, and had already repeated the "delete all partitions" step... and then just forgot where he was, or how to create the new partitions, or where he was in my "recipe".

I'm trying to be patient and helpful.

MT have acknowledged to me personally that there is indeed a bug.

They are trying to fix it.

I saw that too.

But I'm still asking your for WHAT WAS THAT BUG WHICH YOU REPORTED, and that they acknowledged?


In any case, I'm still trying to help the OP with his issue. There really aren't a lot of steps involved here... to delete everything, create two partitions, and FORMAT both partitions to NTFS just to be safe.

These few steps can be performed using either PW or DISKMGMT, if only I could get my fingers on OP's machine... or if OP would follow the directions I've provided several times now.

That's really the issue right now, to get his problem resolved and get the second drive partitioned and usable as he desires.

 

[SIW2]

To explain it simply, PW has an issue reading extended partition information correctly.

Manifested by PW reporting the extended partition ( and occasionally ) the entire disk as unallocated - when in fact, it isn't.

Will PW be able to create and format the disk it reports as unallocated ? Probably.

Does it cause an issue in this case? No, because there is no data on the disk the OP wants to keep.

However, in different circumstances, it may well be a problem.



Of course, if the OP has indeed deleted the partitions - then that would not apply in this case.

However, since he stated he had not done so , and since there is precisely that bug in PW - there is no reason to disbelieve him.

 

[SIW2]

Here is an example:

PW5.2



Windows Disk Management



Paragon Virtual Server



The pics are small.

 

[dsperber]

To explain it simply, PW has an issue reading extended partition information correctly.

Manifested by PW reporting the extended partition ( and occasionally ) the entire disk as unallocated - when in fact, it isn't.

I see. Personally I've never seen this myself, but if you have and if MT acknowledges it as a known problem, then I'm certainly willing to believe it.

Perhaps the circumstances involve something like the current situation... where somehow the original creation of that G partition which shows no file system (on the earlier screenshot) is the "giant clue", to why the later screenshot from PW shows 100% unallocated for the drive. Assuming the OP really did NOT perform "delete all partitions" between screenshots 1 and 2, I suppose that the PW bug you describe is the only other reasonable explanation for this seeming contradiction.

Again, I personally have never seen this. In fact, I can't even imagine how PW could have created G with 148GB allocation and not force NTFS (or at least some) file system on it as well. I've created partitions on brand new drives out of the box, and NEVER had to also "FORMAT" after "CREATE"... in order to plant NTFS on that partition. But then again, I've never had an Iomega USB drive, so who knows how this might differ? It's interesting that the second partition created on the drive, which was logical (M) instead of primary (G) apparently got created understandably and correctly by PW (in the extended partition), though the first partition created was messed up.

Will PW be able to create and format the disk it reports as unallocated ? Probably.

Unknown, I suppose, unless it's actually tried. OP seems to have taken a break.

But for sure, I would think even just going back to DISKMGMT and right-clicking on that problematic "no file system" 148GB G partition, and then selecting "FORMAT" from the popup menu and specifying NTFS there... that should get this mystery partition squared away, I would think. And if my hunch is correct, perhaps PW will now correctly show the entire drive and its two now properly formatted partitions.

Does it cause an issue in this case? No, because there is no data on the disk the OP wants to keep.

Yes, we can really experiment all we want here.

However, in different circumstances, it may well be a problem.

Understood.

But I'd still like to see the requested pair of new current screenshots, just so that we can all get on the same page as to where we currently stand for real... and decide what to do next depending on that.

Of course, if the OP has indeed deleted the partitions - then that would not apply in this case.

However, since he stated he had not done so , and since there is precisely that bug in PW - there is no reason to disbelieve him.

Again... he seems on a break.

First course of action when he returns: two fresh screenshots from DISKMGMT and PW. Then we'll decide what to do next, depending on what we see.

 

[essenbe]

Has anyone considered the possibility of the drive being DOA? There should not be this much of an issue partitioning and formatting any drive. It should be a simple procedure and should be easily done in PW, Diskpart or Disk management. Most external HDs come pre formatted yet his showed raw and cannot be formatted. Iomnega should have a diagnostic program to determine the status of the drive.

 

[dsperber]

Has anyone considered the possibility of the drive being DOA? Iomega should have a diagnostic program to determine the status of the drive.

Very interesting thought...

Doing a bit of research, it almost looks like Iomega USB drives ship formatted for Mac's, not for Windows:

"Some Iomega Hard Drives ship formatted Mac OS Extended (HFS+) for use with Mac OS and will not be recognized by Windows until they are reformatted NTFS or FAT32/exFAT. This includes most Iomega FireWire®/USB 2.0 Desktop Hard Drives, the MiniMax Hard Drive, the Iomega UltraMax Hard Drive, and some models of the Portable Hard Drive. If you are connecting one of these drives to a Windows PC, and you do not see the drive in 'My Computer' or Windows Explorer, follow the instructions below to format the drive to NTFS or FAT32. This will allow your computer to recognize the drive."

The procedure described on this Iomega support page describes the usual standard initialization for an MBR disk (under 2TB), as to how to re-prepare the drive for use with Windows. In particular this is the recommended solution if Windows does not assign a drive letter (sound familiar guys?).

NOTE: the DISKMGMT screenshots on that Iomega page look EXACTLY like the one we're puzzled about here, where there is a partition but no file system on it.

Again, strong evidence for why it looks like FORMAT to NTFS could solve the problem... if this is what's been the root problem all along.

I would think Partition Wizard's "initialize to MBR disk" function might accomplish the same result, although FORMAT to NTFS may also be needed afterwards.

Anyway, this is certainly an interesting new piece of information to consider.


OP?? Are you there???

 

[SIW2]

It may have escaped attention in this long thread - the OP has only made a few very short posts.

Reproduced here:

Deanie
Hi everyone. I have an external harddrive that is unreadable, so I used DBAN to clean it. I think it fixed the disk. Unfortunately, I cannot open it or assign a drive letter. I was trying to use diskpart, but it doesn't work. I am uploading a screenshot of the problem. Any assistance will be appreciated.

http://www.sevenforums.com/attachments/hardware-devices/152336d1304292227-diskpart-dispart.png

Deanie
The external hd was showing up in the disk management console, but it disappeared. It was shown as "healthy" and "raw". I tried to format it, but it was no go. Here is a picture of what I try to do next. Maybe the external hd is toast. Thanks.

http://www.sevenforums.com/attachments/hardware-devices/152342d1304295983-diskpart-dispart-2.png

Deanie
Hi. Here is a picture of the disk management console and the external harddrive is an Iomega Prestige--250gb--54AJ34J763

http://www.sevenforums.com/attachme...52364d1304305173-diskpart-disk-management.png


Unfortunately when I plug the external harddrive into the PC, I receive a message stating check the local disk for consistency. It takes forever to scan the disk. I had a power surge, so I had to start over. Why is it asking to check the disk? It is showing in disk management as healthy. I am a little scared to place files on this external hd, because they might disappear. What do you think? deanie

http://www.sevenforums.com/attachme...1304474177-diskpart-disk-management.png-2.png

SIW2

G appears not to have been formatted - at least not with a filesystem windows understands.

Try rt click G and do a quick format.

Next run windows checkdisk on G and then M