bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Oddity with DOS Partitions/Swapping


From: Mark Bober
Subject: Oddity with DOS Partitions/Swapping
Date: Thu, 23 Nov 2000 23:20:10 +0000

I've searched through the archives and google, couldn't find anything 
relevant, so here goes:

Using GRUB 0.5.96.1

I've listed 'fdisk -l' output at the end of the message. I've got a 10gig 
drive, mostly linux with one FAT32 partition, on the primary master. On the 
secondary master, I have a 4 gig, with a 700meg FAT32 partition as primary, 
and the rest being a logical DOS FAT32 partition.

My boot sequence to get to windows is like this:
title WinME
root (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
makeactive
chainloader +1
boot              

As you can see I'm using Windows ME. Now, what I'd expect to see is:

C:      (hdc1, or the primary partition on the 4 gig)
D:      (hda2, or the primary FAT32 partition on the 10 gig)
E:      

What I get under Windows Explorer is this

C:      (hdc1, or the primary partition on the 4 gig)
D:      (hda2, or the primary FAT32 partition on the 10 gig)
E:      
F:      (hdc5, or the logical partition on the 4 gig)

Drive E: is the problem - it seems to be the "extended partition marker" on 
the 4 gig drive. For grins, I formatted it, and I had E: and F:, they were 
the *exact* same drive, just different data. I marked the new 'E:' drive with 
a text file, rebooted, that text file (and partition) moved to 'F:', and E: 
was once again this blank, unformatted, fake partition.

DOS's FDISK shows this:

Drive   Partition               Type            Label           Size
C:      1               PRI-DOS REAL-ME 700
            2           EXT-DOS -               3404

Logical Drive Screen:

E:                      Unknown                 3404

FDISK doesn't see F:, and shows E: as unformatted. but Windows Explorer does 
see F:, as formatted. The partitioning of the 4 gigabyte was done with 
WinME's FDISK, so was the formatting. If I unplug my 10 gig, and boot 
'native' to Windows, it doesn't see this blank partition. Is there something 
more I need to do in grub to get that extended partition to not show up to 
Windows?

Thanks!

Mark

(yes, I realize that making one partition is easier, but my plan was to have 
a 700 meg partition under VMWare, that I could doubly install apps to without 
screwing up the hardware configuration of the original Windows install (I 
still like my Windows games)

** fdisk -l output **

Disk /dev/hda: 255 heads, 63 sectors, 1232 cylinders
Units = cylinders of 16065 * 512 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       732   5879758+  85  Linux extended
/dev/hda2           733      1232   4016250    c  Win95 FAT32 (LBA)
/dev/hda5             1        31    248944+  83  Linux
/dev/hda6            32        94    506016   82  Linux swap
/dev/hda7            95       603   4088511   83  Linux
/dev/hda8           604       732   1036161   83  Linux      

Disk /dev/hdc: 255 heads, 63 sectors, 524 cylinders
Units = cylinders of 16065 * 512 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1   *         1        90    722893+   b  Win95 FAT32
/dev/hdc2            91       524   3486105    5  Extended
/dev/hdc5            91       524   3486073+   b  Win95 FAT32      



reply via email to

[Prev in Thread] Current Thread [Next in Thread]