Unix Technical Forum

Partitioning problems on Maxtor 80Gb drive

This is a discussion on Partitioning problems on Maxtor 80Gb drive within the Linux Operating System forums, part of the Unix Operating Systems category; --> I have tried to partition my Maxtor 80Gb drive as follows, using cfdisk: hda1 Primary Linux ext2 [/boot] 32.00 ...


Go Back   Unix Technical Forum > Unix Operating Systems > Linux Operating System

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-18-2008, 06:34 AM
Mark Hobley
 
Posts: n/a
Default Partitioning problems on Maxtor 80Gb drive

I have tried to partition my Maxtor 80Gb drive as follows, using cfdisk:

hda1 Primary Linux ext2 [/boot] 32.00
hda2 Primary Linux ext2 [/] 120.26
hda3 Boot Primary W95 FAT32 (LBA) 32767.97
hda5 Logical Linux ext2 [/usr] 120.26
hda6 Logical Linux ext2 [/var] 649.77
hda7 Logical Linux ext2 47506.13
hda8 Logical Linux swap 767.96

If I run fdisk, and print the partition table, I get the following information:

Device Boot Start End Blocks Id System
/dev/hda1 1 62 31216+ 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hda2 63 295 117432 83 Linux
Partition 2 does not end on cylinder boundary.
/dev/hda3 * 296 63787 31999968 c W95 FAT32 (LBA)
Partition 3 does not end on cylinder boundary.
/dev/hda4 63788 158816 47894616 5 Extended
Partition 4 does not end on cylinder boundary.
/dev/hda5 63788 64020 117400+ 83 Linux
/dev/hda6 64021 65279 634504+ 83 Linux
/dev/hda7 65280 157328 46392664+ 83 Linux
/dev/hda8 157329 158816 749920+ 82 Linux swap

If I use the v command in fdisk to check the partition table, I get the
following errors:

Partition 1 does not end on cylinder boundary.
Partition 1: head 227 greater than maximum 16
Partition 2 does not end on cylinder boundary.
Partition 2: head 130 greater than maximum 16
Partition 3 does not end on cylinder boundary.
Partition 3: head 82 greater than maximum 16
Partition 5: head 240 greater than maximum 16
Partition 6: head 239 greater than maximum 16
Partition 7: head 143 greater than maximum 16
Partition 8: head 236 greater than maximum 16
310 unallocated sectors

What is going on? Is this some kind of Geometry issue?

I have an Asrock K7S8XE motherboard.

The BIOS reveals:

Maxtor 6Y080P0 Type: Auto Cylinders: 39237 Heads: 16 Sectors: 255
Maximum Capacity: 82Gb

LBA Mode: On
Block Mode: On
32 Bit Transfer Mode: On
Fast Programmed I/O Modes: 4
Ultra DMA Mode: Auto

The settings for LBA and Block mode are greyed out as with the Type: Auto set
in the BIOS.

If I change the drive type to Type: User,

I get the facility to enter the number of cylinders, heads and sectors, and
the option to switch off LBA mode.

I don't know what values to key in for non-LBA mode, if I can use this.

In all of my other computers, I use Normal mode and have no problems
partitioning the disks. (All other machines run Linux only, and LBA mode is
not required). The BIOS on all other machines allows me to autodetect
the hard drive and automatically fills in the values for cylinders, heads and
sectors.

This computer is going to dual boot into Windows 2003. I presume that I need
LBA mode for Windows to work. (Does anyone know whether this is still a
requirement for Windows?)

The computer will boot both systems as it stands, but I want to correct the
partitioning errors.

I am also having problems with putting LILO on this computer, since it crashes
out with a segmentation fault during the debian install. This has resulted in
the grub boot loader being installed on the hard drive. LILO gives a
segmentation fault from the command prompt. I presume this is due to the dodgy
partitioning scheme that is being created on my drive.

I want to repartition the drive, make the partitions end on a cylinder
boundary, allocate all space on the hard drive, and dual boot into Windows 2003
using LILO.

How can I achieve this ?

Thanks in advance to anyone who can help.

Regards,

Mark.

--

Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Reply to: markhobley at hotpop dot do_not_type_this_bit com

http://markhobley.yi.org/
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 01-18-2008, 06:34 AM
mjt
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

Mark Hobley wrote:

> This computer is going to dual boot into Windows 2003. I presume that I need
> LBA mode for Windows to work. (Does anyone know whether this is still a
> requirement for Windows?)


.... i cant be for sure, but my guess is, "yes"

> I want to repartition the drive, make the partitions end on a cylinder
> boundary, allocate all space on the hard drive, and dual boot into Windows 2003
> using LILO.


why not use parted or fdisk - i've heard people
having issues with cfdisk

--
<< http://michaeljtobler.homelinux.com/ >>
Committees have become so important nowadays that
subcommittees have to be appointed to do the work.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 01-18-2008, 06:34 AM
Darklight
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

maybe this will help

linux:/home/usrname # fdisk -l

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 5100 40965718+ 7 HPFS/NTFS
/dev/hda2 5101 14593 76252522+ f W95 Ext'd (LBA)
/dev/hda5 5101 8925 30724281 b W95 FAT32
/dev/hda6 8926 9117 1542208+ 82 Linux swap
/dev/hda7 9118 14593 43985938+ 83 Linux
linux:/home/usrname #



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 01-18-2008, 06:34 AM
David Efflandt
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

On Sun, 07 Nov 2004, Mark Hobley <markhobley@hotpop.deletethisbit.co.uk> wrote:
> I have tried to partition my Maxtor 80Gb drive as follows, using cfdisk:
>
> hda1 Primary Linux ext2 [/boot] 32.00
> hda2 Primary Linux ext2 [/] 120.26
> hda3 Boot Primary W95 FAT32 (LBA) 32767.97
> hda5 Logical Linux ext2 [/usr] 120.26
> hda6 Logical Linux ext2 [/var] 649.77
> hda7 Logical Linux ext2 47506.13
> hda8 Logical Linux swap 767.96
>
> If I run fdisk, and print the partition table, I get the following information:
>
> Device Boot Start End Blocks Id System
> /dev/hda1 1 62 31216+ 83 Linux
> Partition 1 does not end on cylinder boundary.
> /dev/hda2 63 295 117432 83 Linux
> Partition 2 does not end on cylinder boundary.
> /dev/hda3 * 296 63787 31999968 c W95 FAT32 (LBA)
> Partition 3 does not end on cylinder boundary.
> /dev/hda4 63788 158816 47894616 5 Extended
> Partition 4 does not end on cylinder boundary.
> /dev/hda5 63788 64020 117400+ 83 Linux
> /dev/hda6 64021 65279 634504+ 83 Linux
> /dev/hda7 65280 157328 46392664+ 83 Linux
> /dev/hda8 157329 158816 749920+ 82 Linux swap
>
> If I use the v command in fdisk to check the partition table, I get the
> following errors:
>
> Partition 1 does not end on cylinder boundary.
> Partition 1: head 227 greater than maximum 16
> Partition 2 does not end on cylinder boundary.
> Partition 2: head 130 greater than maximum 16
> Partition 3 does not end on cylinder boundary.
> Partition 3: head 82 greater than maximum 16
> Partition 5: head 240 greater than maximum 16
> Partition 6: head 239 greater than maximum 16
> Partition 7: head 143 greater than maximum 16
> Partition 8: head 236 greater than maximum 16
> 310 unallocated sectors
>
> What is going on? Is this some kind of Geometry issue?
>
> I have an Asrock K7S8XE motherboard.
>
> The BIOS reveals:
>
> Maxtor 6Y080P0 Type: Auto Cylinders: 39237 Heads: 16 Sectors: 255
> Maximum Capacity: 82Gb


What is the complete output of "fdisk -l /dev/hda"?

Apparently something changed the geometry of your partition table from
whatever it was (240 or more heads) to 16 heads, 63 sectors/track, 158816
cyls.

When 64-bit XP Pro beta altered my partition table (from 240 heads to 255
heads) and could not reboot itself or XP Home, at least I had the original
number of heads and start/end of one partition from when I did ntfsresize.
So I was able to play with partition table geometry in fdisk expert mode
from a Linux rescue CD until the numbers came out right (no data loss).

But without the original output of fdisk -l before it was altered, I would
not know what to tell you to change it back to. I have never used cfdisk,
but maybe "gpart" could help.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 01-18-2008, 06:34 AM
Mark Hobley
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

In alt.comp.os.linux Mark Hobley <markhobley@hotpop.deletethisbit.co.uk> wrote:
> I have tried to partition my Maxtor 80Gb drive as follows, using cfdisk:
>
> hda1 Primary Linux ext2 [/boot] 32.00
> hda2 Primary Linux ext2 [/] 120.26
> hda3 Boot Primary W95 FAT32 (LBA) 32767.97
> hda5 Logical Linux ext2 [/usr] 120.26
> hda6 Logical Linux ext2 [/var] 649.77
> hda7 Logical Linux ext2 47506.13
> hda8 Logical Linux swap 767.96
>
> If I run fdisk, and print the partition table, I get the following information:
>
> Device Boot Start End Blocks Id System
> /dev/hda1 1 62 31216+ 83 Linux
> Partition 1 does not end on cylinder boundary.
> /dev/hda2 63 295 117432 83 Linux
> Partition 2 does not end on cylinder boundary.
> /dev/hda3 * 296 63787 31999968 c W95 FAT32 (LBA)
> Partition 3 does not end on cylinder boundary.
> /dev/hda4 63788 158816 47894616 5 Extended
> Partition 4 does not end on cylinder boundary.
> /dev/hda5 63788 64020 117400+ 83 Linux
> /dev/hda6 64021 65279 634504+ 83 Linux
> /dev/hda7 65280 157328 46392664+ 83 Linux
> /dev/hda8 157329 158816 749920+ 82 Linux swap
>
> If I use the v command in fdisk to check the partition table, I get the
> following errors:
>
> Partition 1 does not end on cylinder boundary.
> Partition 1: head 227 greater than maximum 16
> Partition 2 does not end on cylinder boundary.
> Partition 2: head 130 greater than maximum 16
> Partition 3 does not end on cylinder boundary.
> Partition 3: head 82 greater than maximum 16
> Partition 5: head 240 greater than maximum 16
> Partition 6: head 239 greater than maximum 16
> Partition 7: head 143 greater than maximum 16
> Partition 8: head 236 greater than maximum 16
> 310 unallocated sectors
>


I partition the drive using fdisk. All is ok.

I install Windows on partition 3. That works ok.

I need to restore the master boot record.

The debian installer disk (sarge) does not offer this facility on boot up.

I choose linux26 and perform a base installation.

I choose install LILO on master boot record. LILO crashes out and screen goes
all fuzzy.

I choose install grub on master book record. Ok, that works.

Reboot the computer.

fdisk /dev/hda

aaarrrgggghhh !

The partition table is screwed again. Partitions do not fall in line with the
cylinder boundaries and the number of heads is not correct.

Why have the partitions got a head number greater than 16 ?

This is a nightmare!

Mark.

--

Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Reply to: markhobley at hotpop dot do_not_type_this_bit com

http://markhobley.yi.org/
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 01-18-2008, 06:34 AM
Mark Hobley
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

In alt.comp.os.linux Darklight <nglenb702@netscape.net> wrote:
> maybe this will help
>
> Device Boot Start End Blocks Id System
> /dev/hda1 * 1 5100 40965718+ 7 HPFS/NTFS
> /dev/hda2 5101 14593 76252522+ f W95 Ext'd (LBA)
> /dev/hda5 5101 8925 30724281 b W95 FAT32
> /dev/hda6 8926 9117 1542208+ 82 Linux swap
> /dev/hda7 9118 14593 43985938+ 83 Linux


Ok, I have made most of the drive W95 EXT LBA type F, as above. In this I put a
W95 FAT32 for Windows, and my other linux partitions.

When I attempt to install Windows on the FAT32 partition, I get an error:

To install Windows on the partition you selected, Setup must write some files
to the following disk:

78160MB Disk 0 at ID 0 on bus 0 on ATAPI [MBR]

However this disk does not contain a Windows compatible partition.

Regards,

Mark.

--

Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Reply to: markhobley at hotpop dot do_not_type_this_bit com

http://markhobley.yi.org/
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 01-18-2008, 06:34 AM
Mark Hobley
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

In alt.comp.os.linux David Efflandt <efflandt@xnet.com> wrote:

>What is the complete output of "fdisk -l /dev/hda"?


Disk /dev/hda: 81.9 GB, 81964302336 bytes
16 heads, 63 sectors/track, 158816 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 62 31216+ 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hda2 63 295 117432 83 Linux
Partition 2 does not end on cylinder boundary.
/dev/hda3 * 296 63787 31999968 c W95 FAT32 (LBA)
Partition 3 does not end on cylinder boundary.
/dev/hda4 63788 158816 47894616 5 Extended
Partition 4 does not end on cylinder boundary.
/dev/hda5 63788 64020 117400+ 83 Linux
/dev/hda6 64021 65279 634504+ 83 Linux
/dev/hda7 65280 157328 46392664+ 83 Linux
/dev/hda8 157329 158816 749920+ 82 Linux swap

> Apparently something changed the geometry of your partition table from
> whatever it was (240 or more heads) to 16 heads, 63 sectors/track, 158816
> cyls.


I have a crappy Asrock motherboard. The BIOS reports 16 heads, 255 sectors,
39237 cylinders. (LBA Mode enabled).

I don't know where the (255?) heads came from. Is that something that Windows
2003 is doing during the install process?

If I install Linux, create a FAT32 partition in Linux, and reboot into Linux,
all is well.

The partition table contains the errors after Windows is installed, and I run
the debian installer a second time to install a boot mananger on the disk.

Windows formats the FAT32 partition and removes LILO from the master boot
record.

The debian installer runs some sort of partitioning software, during the
second installation (cfdisk?). I key all the mount points, partition
types, etc, debian writes the partition table (possibly), installs the base
system, and allows me to install LILO. If I try to install LILO, it crashes
out and the screen goes funny. I choose to install grub. This works fine, and
I can dual boot the computer into Linux or Windows.

From Linux, I run fdisk, and get the partition errors above.

> But without the original output of fdisk -l before it was altered, I would
> not know what to tell you to change it back to.


I'll do a reinstall over the next few days, and run fdisk before Windows gets
installed, so that I can obtain the correct geometry information.

> but maybe "gpart" could help.


Ok, I'm investigating that. Thanks.

Regards,

Mark.

--

Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Reply to: markhobley at hotpop dot do_not_type_this_bit com

http://markhobley.yi.org/
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old 01-18-2008, 06:34 AM
mjt
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

Mark Hobley wrote:

> However this disk does not contain a Windows compatible partition.


.... windows is soooooo friggin brain-dead. i assisted
a buddy to restore their box with ONLY eXPensive; first,
wiped out all partitions using the eXPensive "partitioner",
then created an NTFS and then got to the install step
and it said, "...does not contain a valid windows partition"
and the friggin partition was CREATED BY THE WIN INSTALLER"

why ANYONE continues to fight with that friggin cr@p is
way beyond me.
--
<< http://michaeljtobler.homelinux.com/ >>
Vidi, vici, veni.
(I saw, I conquered, I came.)

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #9 (permalink)  
Old 01-18-2008, 06:34 AM
Stefan Patric
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

On Sunday 07 November 2004 05:06, Mark Hobley wrote:

> I have tried to partition my Maxtor 80Gb drive as follows, using
> cfdisk:
>
> hda1 Primary Linux ext2 [/boot]
> 32.00
> hda2 Primary Linux ext2 [/]
> 120.26
> hda3 Boot Primary W95 FAT32 (LBA)
> 32767.97
> hda5 Logical Linux ext2 [/usr]
> 120.26
> hda6 Logical Linux ext2 [/var]
> 649.77
> hda7 Logical Linux ext2
> 47506.13
> hda8 Logical Linux swap
> 767.96
>
> If I run fdisk, and print the partition table, I get the following
> information:
>
> Device Boot Start End Blocks Id System
> /dev/hda1 1 62 31216+ 83 Linux
> Partition 1 does not end on cylinder boundary.
> /dev/hda2 63 295 117432 83 Linux
> Partition 2 does not end on cylinder boundary.
> /dev/hda3 * 296 63787 31999968 c W95 FAT32
> (LBA) Partition 3 does not end on cylinder boundary.
> /dev/hda4 63788 158816 47894616 5 Extended
> Partition 4 does not end on cylinder boundary.
> /dev/hda5 63788 64020 117400+ 83 Linux
> /dev/hda6 64021 65279 634504+ 83 Linux
> /dev/hda7 65280 157328 46392664+ 83 Linux
> /dev/hda8 157329 158816 749920+ 82 Linux swap
>
> If I use the v command in fdisk to check the partition table, I get
> the following errors:
>
> Partition 1 does not end on cylinder boundary.
> Partition 1: head 227 greater than maximum 16
> Partition 2 does not end on cylinder boundary.
> Partition 2: head 130 greater than maximum 16
> Partition 3 does not end on cylinder boundary.
> Partition 3: head 82 greater than maximum 16
> Partition 5: head 240 greater than maximum 16
> Partition 6: head 239 greater than maximum 16
> Partition 7: head 143 greater than maximum 16
> Partition 8: head 236 greater than maximum 16
> 310 unallocated sectors
>
> What is going on? Is this some kind of Geometry issue?
>
> I have an Asrock K7S8XE motherboard.
>
> The BIOS reveals:
>
> Maxtor 6Y080P0 Type: Auto Cylinders: 39237 Heads: 16 Sectors: 255
> Maximum Capacity: 82Gb
>
> LBA Mode: On
> Block Mode: On
> 32 Bit Transfer Mode: On
> Fast Programmed I/O Modes: 4
> Ultra DMA Mode: Auto
>
> The settings for LBA and Block mode are greyed out as with the Type:
> Auto set in the BIOS.
>
> If I change the drive type to Type: User,
>
> I get the facility to enter the number of cylinders, heads and
> sectors, and the option to switch off LBA mode.
>
> I don't know what values to key in for non-LBA mode, if I can use
> this.
>
> In all of my other computers, I use Normal mode and have no problems
> partitioning the disks. (All other machines run Linux only, and LBA
> mode is not required). The BIOS on all other machines allows me to
> autodetect the hard drive and automatically fills in the values for
> cylinders, heads and sectors.
>
> This computer is going to dual boot into Windows 2003. I presume
> that I need LBA mode for Windows to work. (Does anyone know whether
> this is still a requirement for Windows?)
>
> The computer will boot both systems as it stands, but I want to
> correct the partitioning errors.
>
> I am also having problems with putting LILO on this computer, since
> it crashes out with a segmentation fault during the debian install.
> This has resulted in the grub boot loader being installed on the
> hard drive. LILO gives a segmentation fault from the command prompt.
> I presume this is due to the dodgy partitioning scheme that is being
> created on my drive.
>
> I want to repartition the drive, make the partitions end on a
> cylinder boundary, allocate all space on the hard drive, and dual
> boot into Windows 2003 using LILO.
>
> How can I achieve this ?


You're not going to be able to allocate ALL the space on the drive.
Windows usually reserves a "hidden" 8MB partition at the end of the
drive for its "private" system files. So, allow for that. If you
delete it, Windows won't boot or won't boot properly or it may just
wipe out the partition that's there and write a new 8MB one. Also,
when installing Linux and formatting your Linux partitions, do a
badblock check, too. This will take a long time, but it's worth it.

Now, try this: delete ALL the current partitions; then in Linux
create a single partition and format it in ext2, but don't install
anything. Reboot to your Linux install disk in Rescue Mode and do a
filesystem check on the new partiion -- fsck -t ext2 -v /dev/hda1 or
e2fsck -v /dev/hda1 -- to see that everthing is okay. If it is (It
should be.), reboot the Linux install disk and delete the single
partition and create your final partitioning (I like fdisk over
cfdisk. fdisk automatically ends a partition on the nearest block
boundary.), but plan to install Windows on the 1st, the C:, partition
and make it the ONLY bootable partition. Windows always works better
when it's on the 1st partition on the drive. (Arrogant little OS,
isn't it? Linux doesn't care. Gets along with everyone.) Once you're
all partitioned and the partition table is saved, shutdown the
computer, and reboot using your Windows install CD. Install Windows.
After that's done, shutdown and boot the Linux CD. Install Linux.
Linux should automatically recognize that Windows is installed and
ask, if you want to make a dual boot system. Say "Yes." You're
done.

FWIW, I find it better to partition for both Linux and Windows using
Linux rather than Windows. Windows sometimes does screwy things to
the HD geometry.

--
Stefan Patric
tootek2@yahoo.com
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #10 (permalink)  
Old 01-18-2008, 06:34 AM
mjt
 
Posts: n/a
Default Re: Partitioning problems on Maxtor 80Gb drive

Stefan Patric wrote:

> You're not going to be able to allocate ALL the space on the drive.
> Windows usually reserves a "hidden" 8MB partition at the end of the
> drive for its "private" system files.*


.... interesting. "which" windows and what exactly
is being persisted out in that 8mb? i asked because
i have three boxen here with Linux/winders on them
and there is no 8mb partition at the end.
--
<< http://michaeljtobler.homelinux.com/ >>
"Here's something to think about: How come you never see a headline like
`Psychic Wins Lottery'?"
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 11:49 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com