Results 1 to 5 of 5
I am having a problem managing partitions on my WD 320GB drive, which is connected as the 2nd SATA drive. This all started when I decided to install Ubuntu Linux ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 05-09-2006 #1
- Join Date
- May 2006
Partition problems after setting up my drives for Windows/Linux dual boot. Help!
I am having a problem managing partitions on my WD 320GB drive, which is connected as the 2nd SATA drive. This all started when I decided to install Ubuntu Linux on the drive for a dual boot option (WinXP resides on my 74GB Raptor which is connected to SATA 1). Originally, my WD320 drive had 3 primary partitions, formatted as NTFS for data storage: 200GB, 65GB, and 50GB. When I decided to install Linux, I took the following steps after backing up my data on the 200GB partition.
Creating Partitions Using a Linux LiveCD
- I booted with the Ubuntu Linux LiveCD and opened the GParted partitioning program
- I deleted the 200GB primary partition on the WD320 drive.
- In its place I created a 10 GB primary partition and a 190GB extended partition
- The 10 GB primary partition was formatted as ext3 for the Linux root
- Within the 190 GB extended partition, I created 4 logical partitions: 15 GB formatted as ext3 for the Linux home directories, 1.5 GB for the Linux swap, 30 GB formatted as FAT32 for data storage/transfer, and the remainder (~140 GB) formatted as NTFS for data storage accessible from Windows
Windows Disk Management Sees All Partitions as "Unknown"
When I exited and booted back into Windows, I was surprised to find that the Windows Disk Management saw all the newly created partitions as "unknown". The format of the NTFS and FAT32 partitions was recognized, but Disk Management would not allow me to assign these drives as volumes to be accessed by Windows. So, to make my NTFS partition accessible, I deleted it and recreated it using Disk Management. This seemed to work, as I was able to assign a drive letter to this partition and transfer data to it.
Ubuntu Linux Installs Successfully
Next, I installed Ubuntu Linux using the partitions I created using the GParted program. This went smoothly, and the Grub boot loader was working fine allowing me to boot to Windows on the Raptor, or Linux on the WD320.
Problems Start when I try to get Windows to Mount the FAT32 Partition
Everything seemed to be going as planned *except* for the fact that Windows couldn't mount the FAT32 logical partition that I created using GParted. So, I decided to employ the same process I used to mount the NTFS partition: delete the partition and recreate it using Disk Management. Here is where things went terribly wrong. When I selected the FAT32 partition and told Disk Management to delete it, multiple logical partitions disappeared!!! The resulting partitions on the disk are shown in the image below.
As you can see, this operation deleted 3 logical partitions within the extended partition: the 140GB NTFS partition, the 30GB FAT32 partition, and the 1.5GB Linux swap partition! The 15GB partition for the Linux home directories was spared by this operation, for some odd reason (however, now Ubuntu fails to mount this when I boot).
At this point, Disk Management does not let me create any logical partitions within the free space of the extended partition! I can go through the steps to create a partition, but when I click "Proceed", I get the following error:
What is going on?! (Unfortunately I was in a hurry to get to work and I didn't check the Event Log for details)
Based on this experience, I now have many questions:
1) Why can't Windows mount NTFS or FAT32 partitions that I create using GParted from the Linux LiveCD?
2) Why did Disk Management delete 3 of my logical partitions when I only requested that it delete one?
3) Why won't Disk Management allow me to create any logical partitions in the free space within the extended partition?
4) If these problems can be blamed on the pathetic excuse for a partitioning tool called Disk Management, what are my options for resolving this problem in terms of software (preferably free).
5) Assuming I can recreate the lost partitions, how can I remount the swap space and home directories within my Linux installation?
Any help you could provide would be greatly appreciated!
- 05-09-2006 #2
I always put the FAT/ntfs partitions first on a drive to minimize the chances of confusing Windows. Also, I stick to the basic partition strategy you're using (one primary partition; everything else is logical partitions within one extended partition).
I've never had to go through any hoops to get Windows to recognize/mount any of the FAT/ntfs partitions. They just plain appear as the appropriate drive letters (D:, E:, etc).Isaac Kuo, ICQ 29055726 or Yahoo mechdan
- 05-09-2006 #3
Originally Posted by IsaacKuo
- Join Date
- May 2006
As it stands now, I'm thinking of deleting the entire extended partition and starting over. However, what will happen with GRUB if I do this? Will it render my Windows installation unbootable? If so, how can I fix it? Thanks for your help.
- 05-09-2006 #4
Sorry, I didn't use clear language. I never use any Windows tools for partitioning. I always use either QTParted (included on Knoppix, Mepis liveCDs) or Debian's partitioner (included on Debian install CDs).
By "first", I meant that the first partitions are FAT32/ntfs. For example, my usual dual boot system is partitioned this way:
hda1 - primary partition - FAT32 (Windows 98 OS; it's C: in Windows)
hda5 - logical partition - FAT32 (large data partition; it's D: in Windows)
hda6 - logical partition - ext3 (linux OS partition; invisible in Windows)
hda7 - logical partition - linux-swap (swap partition; invisible in Windows)Isaac Kuo, ICQ 29055726 or Yahoo mechdan
- 05-12-2006 #5
There are at least three types of extended partitions, 05, 0F, and 85
Which type you use may affect whether windows can see the logical
partitions within them. Mixing Microsoft and non-Microsoft logical partitions
within one extended partition may also cause unpredictable results.
When in doubt, simplify.