Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
When I installed winxp on a wester digital 500gb sata drive. I used 137gb for the windows partition and aprox. 363g for the second partition. When I check the drive contents in windows my computer the second partition only shows 70gb.
I've messing around with Linux distros and was wondering if something from the grub bootloader caused this change. This is odd though because I install the Linux on a separate physical drive. I've also installed the winxp service pack 3. Could either of the two events caused this change in the hard drive? Also when I boot into my bios, this drive doesn't show up.
I've listed below a description of my computer's hardware:
id:
paul-desktop
description: Desktop Computer
product: MS-7032
vendor: MSI
version: 1.0
serial: 00000000
width: 32 bits
capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
configuration:
chassis = desktop
cpus = 1
uuid = 00020003-0004-0005-0006-000700080009
id:
core
description: Motherboard
product: MS-7032
vendor: MSI
physical id:
0
version: 1.0
serial: 00000000
slot: To Be Filled By O.E.M.
id:
firmware
description: BIOS
vendor: American Megatrends Inc.
physical id:
0
version: 080011 (07/26/2005)
size: 64KiB
capacity: 448KiB
capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification
id:
cpu
description: CPU
product: AMD Sempron(tm) Processor 2800+
vendor: Advanced Micro Devices [AMD]
physical id:
4
bus info:
cpu@0
version: 15.12.2
serial: To Be Filled By O.E.M.
slot: CPU 1
size: 1600MHz
capacity: 1600MHz
width: 64 bits
clock: 200MHz
capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt x86-64 3dnowext 3dnow up pni lahf_lm
id:
cache:0
description: L1 cache
physical id:
5
slot: L1-Cache
size: 128KiB
capabilities: pipeline-burst internal varies data
id:
cache:1
description: L2 cache
physical id:
6
slot: L2-Cache
size: 256KiB
capacity: 256KiB
capabilities: pipeline-burst internal varies unified
id:
memory
description: System Memory
physical id:
28
slot: System board or motherboard
size: 640MiB
id:
bank:0
description: DIMM DDR Synchronous 266 MHz (3.8 ns)
product: PartNum0
vendor: Manufacturer0
physical id:
0
serial: SerNum0
slot: DIMM0
size: 512MiB
width: 64 bits
clock: 266MHz (3.8ns)
id:
bank:1
description: DIMM DDR Synchronous 266 MHz (3.8 ns)
product: PartNum1
vendor: Manufacturer1
physical id:
1
serial: SerNum1
slot: DIMM1
size: 128MiB
width: 64 bits
clock: 266MHz (3.8ns)
id:
pci:0
description: Host bridge
product: K8T800Pro Host Bridge
vendor: VIA Technologies, Inc.
physical id:
100
bus info:
pci@0000:00:00.0
version: 00
width: 32 bits
clock: 66MHz
configuration:
driver = agpgart-amd64
latency = 64
module = amd64_agp
id:
pci
description: PCI bridge
product: VT8237 PCI bridge [K8T800/K8T890 South]
vendor: VIA Technologies, Inc.
physical id:
1
bus info:
pci@0000:00:01.0
version: 00
width: 32 bits
clock: 66MHz
capabilities: pci pm bus_master cap_list
id:
display:0
description: VGA compatible controller
product: RV350 AS [Radeon 9550]
vendor: ATI Technologies Inc
physical id:
0
bus info:
pci@0000:01:00.0
version: 00
width: 32 bits
clock: 66MHz
capabilities: agp agp-3.0 pm bus_master cap_list
configuration:
latency = 64
mingnt = 8
id:
display:1
description: Display controller
product: RV350 AS [Radeon 9550] (Secondary)
vendor: ATI Technologies Inc
physical id:
0.1
bus info:
pci@0000:01:00.1
version: 00
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list
configuration:
latency = 64
mingnt = 8
id:
ide:0
description: IDE interface
product: VIA VT6420 SATA RAID Controller
vendor: VIA Technologies, Inc.
physical id:
f
bus info:
pci@0000:00:0f.0
logical name:
scsi0
logical name:
scsi1
version: 80
width: 32 bits
clock: 33MHz
capabilities: ide pm bus_master cap_list emulated
configuration:
driver = sata_via
latency = 64
module = sata_via
id:
disk:0
description: ATA Disk
product: WDC WD5000AAKS-0
vendor: Western Digital
physical id:
0
bus info:
scsi@0:0.0.0
logical name:
/dev/sda
version: 12.0
serial: WD-WCAPW3744003
size: 465GiB (500GB)
capabilities: partitioned partitioned:dos
configuration:
ansiversion = 5
signature = 22ba8210
id:
volume:0
description: Windows NTFS volume
physical id:
1
bus info:
scsi@0:0.0.0,1
logical name:
/dev/sda1
version: 3.1
serial: 68b963c3-bfd8-a541-9050-658e67a86c41
size: 127GiB
capacity: 127GiB
capabilities: primary bootable ntfs initialized
configuration:
clustersize = 4096
created = 2007-08-19 08:53:24
filesystem = ntfs
state = clean
id:
volume:1
description: Extended partition
physical id:
2
bus info:
scsi@0:0.0.0,2
logical name:
/dev/sda2
size: 337GiB
capacity: 337GiB
capabilities: primary extended partitioned partitioned:extended
id:
logicalvolume:0
description: HPFS/NTFS partition
physical id:
5
logical name:
/dev/sda5
logical name:
/media/NEW VOLUME
capacity: 70GiB
configuration:
mount.fstype = fuseblk
mount.options = rw,nosuid,nodev,user_id=0,group_id=0,allow_other,blksize=4096
state = mounted
id:
logicalvolume:1
description: Linux filesystem partition
physical id:
6
logical name:
/dev/sda6
capacity: 196MiB
id:
logicalvolume:2
description: Linux LVM Physical Volume partition
physical id:
7
logical name:
/dev/sda7
serial: pQ3uK1-FI3j-K8W5-8iTB-PeWg-WDz2-o12gSu
size: 267GiB
capacity: 267GiB
capabilities: multi lvm2
id:
disk:1
description: ATA Disk
product: WDC WD2500KS-00M
vendor: Western Digital
physical id:
1
bus info:
scsi@1:0.0.0
logical name:
/dev/sdb
version: 02.0
serial: WD-WCANK5214761
size: 232GiB (250GB)
capabilities: partitioned partitioned:dos
configuration:
ansiversion = 5
signature = 0a861d0d
id:
volume
description: Windows NTFS volume
physical id:
1
bus info:
scsi@1:0.0.0,1
logical name:
/dev/sdb1
version: 3.1
serial: 8c5137b9-08b1-5e46-af0c-28c731b2a05a
size: 232GiB
capacity: 232GiB
capabilities: primary bootable ntfs initialized
configuration:
clustersize = 4096
created = 2006-11-15 14:25:02
filesystem = ntfs
label = DRV4_VOL1
state = clean
id:
ide:1
description: IDE interface
product: VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE
vendor: VIA Technologies, Inc.
physical id:
f.1
bus info:
pci@0000:00:0f.1
logical name:
scsi3
version: 06
width: 32 bits
clock: 33MHz
capabilities: ide pm bus_master cap_list emulated
configuration:
driver = pata_via
latency = 32
module = pata_via
id:
cdrom
description: CD-R/CD-RW writer
product: CRD-BP1600P
vendor: QPS
physical id:
0.0.0
bus info:
scsi@3:0.0.0
logical name:
/dev/cdrom
logical name:
/dev/cdrw
logical name:
/dev/scd0
logical name:
/dev/sr0
version: 3.41
capabilities: removable audio cd-r cd-rw
configuration:
ansiversion = 5
status = nodisc
id:
disk
description: ATA Disk
product: WDC WD2500JB-00R
vendor: Western Digital
physical id:
0.1.0
bus info:
scsi@3:0.1.0
logical name:
/dev/sdc
version: 20.0
serial: WD-WMANK2646468
size: 232GiB (250GB)
capabilities: partitioned partitioned:dos
configuration:
ansiversion = 5
signature = 000a0f2f
id:
volume:0
description: EXT3 volume
vendor: Linux
physical id:
1
bus info:
scsi@3:0.1.0,1
logical name:
/dev/sdc1
logical name:
/
logical name:
/dev/.static/dev
version: 1.0
serial: fce780c7-9690-43f0-9e21-0c6e13b220c7
size: 231GiB
capacity: 231GiB
capabilities: primary journaled extended_attributes large_files huge_files recover ext3 ext2 initialized
configuration:
created = 2008-12-17 13:02:30
filesystem = ext3
modified = 2008-12-18 10:59:06
mount.fstype = ext3
mount.options = ro,errors=remount-ro,data=ordered
mounted = 2008-12-18 10:59:06
state = mounted
id:
volume:1
description: Extended partition
physical id:
2
bus info:
scsi@3:0.1.0,2
logical name:
/dev/sdc2
size: 1835MiB
capacity: 1835MiB
capabilities: primary extended partitioned partitioned:extended
id:
logicalvolume
description: Linux swap / Solaris partition
physical id:
5
logical name:
/dev/sdc5
capacity: 1835MiB
capabilities: nofs
id:
usb:0
description: USB Controller
product: VT82xxxxx UHCI USB 1.1 Controller
vendor: VIA Technologies, Inc.
physical id:
10
bus info:
pci@0000:00:10.0
version: 81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration:
driver = uhci_hcd
latency = 64
module = uhci_hcd
id:
usb:1
description: USB Controller
product: VT82xxxxx UHCI USB 1.1 Controller
vendor: VIA Technologies, Inc.
physical id:
10.1
bus info:
pci@0000:00:10.1
version: 81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration:
driver = uhci_hcd
latency = 64
module = uhci_hcd
id:
usb:2
description: USB Controller
product: VT82xxxxx UHCI USB 1.1 Controller
vendor: VIA Technologies, Inc.
physical id:
10.2
bus info:
pci@0000:00:10.2
version: 81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration:
driver = uhci_hcd
latency = 64
module = uhci_hcd
id:
usb:3
description: USB Controller
product: VT82xxxxx UHCI USB 1.1 Controller
vendor: VIA Technologies, Inc.
physical id:
10.3
bus info:
pci@0000:00:10.3
version: 81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration:
driver = uhci_hcd
latency = 64
module = uhci_hcd
id:
usb:4
description: USB Controller
product: USB 2.0
vendor: VIA Technologies, Inc.
physical id:
10.4
bus info:
pci@0000:00:10.4
version: 86
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration:
driver = ehci_hcd
latency = 64
module = ehci_hcd
id:
isa
description: ISA bridge
product: VT8237 ISA bridge [KT600/K8T800/K8T890 South]
vendor: VIA Technologies, Inc.
physical id:
11
bus info:
pci@0000:00:11.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: isa pm bus_master cap_list
configuration:
latency = 0
id:
multimedia
description: Multimedia audio controller
product: VT8233/A/8235/8237 AC97 Audio Controller
vendor: VIA Technologies, Inc.
physical id:
11.5
bus info:
pci@0000:00:11.5
version: 60
width: 32 bits
clock: 33MHz
capabilities: pm cap_list
configuration:
driver = VIA 82xx Audio
latency = 0
module = snd_via82xx
id:
network
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id:
12
bus info:
pci@0000:00:12.0
logical name:
eth0
version: 78
serial: 00:13:d3:ce:00:02
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration:
autonegotiation = on
broadcast = yes
driver = via-rhine
driverversion = 1.4.3
duplex = full
ip = 192.168.0.177
latency = 64
link = yes
maxlatency = 8
mingnt = 3
module = via_rhine
multicast = yes
port = MII
speed = 100MB/s
id:
pci:1
description: Host bridge
product: K8T800Pro Host Bridge
vendor: VIA Technologies, Inc.
physical id:
101
bus info:
pci@0000:00:00.1
version: 00
width: 32 bits
clock: 33MHz
id:
pci:2
description: Host bridge
product: K8T800Pro Host Bridge
vendor: VIA Technologies, Inc.
physical id:
102
bus info:
pci@0000:00:00.2
version: 00
width: 32 bits
clock: 33MHz
id:
pci:3
description: Host bridge
product: K8T800Pro Host Bridge
vendor: VIA Technologies, Inc.
physical id:
103
bus info:
pci@0000:00:00.3
version: 00
width: 32 bits
clock: 33MHz
id:
pci:4
description: Host bridge
product: K8T800Pro Host Bridge
vendor: VIA Technologies, Inc.
physical id:
104
bus info:
pci@0000:00:00.4
version: 00
width: 32 bits
clock: 33MHz
id:
pci:5
description: Host bridge
product: K8T800Pro Host Bridge
vendor: VIA Technologies, Inc.
physical id:
105
bus info:
pci@0000:00:00.7
version: 00
width: 32 bits
clock: 33MHz
id:
pci:6
description: Host bridge
product: K8 [Athlon64/Opteron] HyperTransport Technology Configuration
vendor: Advanced Micro Devices [AMD]
physical id:
106
bus info:
pci@0000:00:18.0
version: 00
width: 32 bits
clock: 33MHz
id:
pci:7
description: Host bridge
product: K8 [Athlon64/Opteron] Address Map
vendor: Advanced Micro Devices [AMD]
physical id:
107
bus info:
pci@0000:00:18.1
version: 00
width: 32 bits
clock: 33MHz
id:
pci:8
description: Host bridge
product: K8 [Athlon64/Opteron] DRAM Controller
vendor: Advanced Micro Devices [AMD]
physical id:
108
bus info:
pci@0000:00:18.2
version: 00
width: 32 bits
clock: 33MHz
id:
pci:9
description: Host bridge
product: K8 [Athlon64/Opteron] Miscellaneous Control
vendor: Advanced Micro Devices [AMD]
physical id:
109
bus info:
pci@0000:00:18.3
version: 00
width: 32 bits
clock: 33MHz
configuration:
driver = k8temp
module = k8temp
id:
network
description: Ethernet interface
physical id:
1
logical name:
pan0
serial: 12:4f:e0:a7:0b:fa
capabilities: ethernet physical
configuration:
broadcast = yes
driver = bridge
driverversion = 2.3
firmware = N/A
link = yes
multicast = yes

http://support.microsoft.com/kb/303013
ASUS A8N32-SLI Deluxe
AMD Athlon X2 4800+
2GB RAM, X1900GT
2x37GB WD Raptors, RAID 1
1x250GB WD Storage

It looks like it's seeing 337 gig of that drive as an extended partition. But within that extended partition is a logical drive of 70 gig. The rest of the partition isn't being used. 'My computer' is only seeing the 137 gig and 70 gig because it doesn't show unallocated space.
You can either create another logical drive using the remaining space or delete the 70 gig drive and create a single drive using all of the 337 gig.
(edit)Or you installed the linux on the remaining space--267 gig--and the second physical drive has nothing on it. I can't be sure because of the way your diagnostic software is presenting the information.

(I'm on the XP machine now) Just right click on 'my computer' and choose 'manage' and then 'disk management' under 'storage'. That'll show how the partitions are arranged and if you've got any unused space.

In response to: You can either create another logical drive using the remaining space or delete the 70 gig drive and create a single drive using all of the 337 gig.
I checked the contents of the drive in Mandriva 2009 and it shows the same as it does in windows xp. Don't know if that bit of info is of any use, but I was wondering if there is any app in Mandriva that I could use to create another logical drive using the remaining space. If it something that would require the terminal, I don't have much experience with that.As for the drive I installed Mandriva on, I took great caution to make sure I selected the drive that did not have windows.

I don't know anything about Mandriva but it should be easy to create a logical drive using 'disk management', assuming it shows some unallocated space in the extended partition.

Back to the suggestion: "You can either create another logical drive using the remaining space or delete the 70 gig drive and create a single drive using all of the 337 gig"
Of the 70g that is showing for the second partition of my boot drive only about 1g is available. I've noticed in windows that this second partition has the option of "deleting logical partition". If I deleted this logical partition would it still just show 70g available or would it show the correct available space which should be 363g (500g -137g
If it still just shows 70g could I use something like partition magic to get it to see the correct space(363g)? Bear in mind, I'm trying to correct this without reinstalling windows. Thanks.

The extended partition should show the 70 gig logical drive and about 267 gig of unallocated space. If so, then removing the 70 gig partition should show about 363. If it doesn't now show 267 gig of unused space then I'm not sure what's going on with it. (And of course, deleting the 70 gig partition will cause you to lose whatever is in it so you'd need to copy whatever you wanted to save to another drive.)
I'm not sure about partition magic. If XP is only showing the 70 gig and nothing more in that partition then that might be all that PM will see.
This appears to be the download page for your MB:
http://global.msi.com.tw/index.php?...
If you haven't already done so you should probably download and install the SATA and chipset drivers.

I used the partitioning tool in Mandriva Control Center to examine the partitions. I see that I have a 267GB partition that has: Type: Linux Logical Volume Manager (0x8e) I also have windows 70GB partition
What I don't understand is that I have Mandriva installed on a separate physical drive. I have been experimenting with different Linux distros. All of them have been installed on a seperate physical drive. I was wondering how this 267GB partition got on my windows drive. I copied all the info about the 3 partitions that are showing on this windows drive below:
hard drive description from partition tool in Mandriva:sdb
1st partition (of windows drive)
/media/hd2
Details
Mount point: media/hd2
Device: sdb
UUID .127EF0678EE785
DOS drive letter: c(just a guess)
Type: NTFS-3G(0X7)
Start: sector 63
Size 127 GB(27%), 268430022 sectors
Cylinder 0 to 16708
Mounted
Partition booted by default
(for MS-DOS boot, not for lilo)/
Details 2nd partition(of windows drive)
Device: sdb
Volume Label NEW VOLUME
UUID .6424A5D124A5A710
DOS drive letter: D(just a guess)
Type: NTFS-3G(0X7)
Start: sector 268430148
Size 70 GB(15%), 147781872 sectors
Cylinder 16709 to 25907
MountedDetails 3rd partition(of windows drive)
Device: sdb7
UUID: pQ3uK1-FI3j-K8W5-8iTB-PeWg-WDz2-o12gSU
Type: Linux Logical Volume Manager (0x8e)
Start Sector 416613708
Size: 267GB(57%), 560154357 sectors
Cylinder 25933 to 60800
If I do something to this partition in the partitioning app of Mandriva Control Center will it disturb my Mandriva install? disturb my windows install? Can I just simply delete this partition? What size a partition does the Linux Logical Volume Manager need? Could I safely resize the LInux Volume Manager? Would this free up space on the windows drive?

I don't know for sure what linux has done. It looks like it appropriated the blank space on the first drive. Maybe it's related to the boot loader.
If you're worried about what might happen to the linux on the second drive if you alter the partition on the first, just open the case and disconnect the linux drive so nothing on it can change. Or you can probably set it's drive type in cmos/bios setup to NONE.
Then using only the XP drive you can partition it as you please without worring about the linux drive.

I'm not as worried about the linux drive. (the second drive) Reinstalling Linux Mandriva is not as time consuming as reinstalling windows xp. I'm therefore more concerned with what will happen to windows. I mean, will removing or resizing the Linux partition affect windows? I'm talking about the Linux partition that somehow got onto the windows drive.

The windows partition shouldn't be affected as long as you only work with the extended partition.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |