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

Bug#260225: Sarge installer not recognising partition table for disk larger than 137GB



package: installation-reports
Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/i386/20040718/sarge-i386-netinst.iso
uname -a: Linux swish 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004
i686 unkown
Date: Mon Jul 19 22:29:13 EST 2004
Method: downloaded image from above website, and ran the installer
Machine: desktop 
Processor: athlonXP 1.6Ghz
Memory: 256Mb
Root Device: IDE seagate (x2)
Root Size/partition table:  see description

-ommited check boxes-

I have detailed my problem at:
<http://www.cse.unsw.edu.au/~saraf/debian-install.html>

I'll paste it below for your convenience:

 Problems with the debian (sarge) installer

 I have a new 160Gb hard disk. I wanted to put debian on the first
 20GB of it (8GB /home, 12GB /), and have the rest as a big fat32
 partition for backup purposes. I first tried using the sarge
 installer, and found it couldn't see more than 137GB of my 160GB
 drive, but I went ahead and partitioned anyway. I finished the base
 install, putting grub in (hd1,0).

 I have another disk in the computer which has FreeBSD and
 windows-XP on it. The FreeBSD loader was unable to boot from
 (hd1,0). It told me to "PRESS ANY KEY TO REBOOT" when i choose that
 disk.

 I thought I'd start the process again, this time putting grub in
 the MBR of hd1. Before I did so, I booted into windows, and had a
 look at the partition table. It was as the debian installer had
 made it. I took the opportunity to format the 20GB at the end of
 the disk as a fat32 partition. I then rebooted, and inserted the
 sarge installer disk again.

 When I got to the partitioning section of the install process
 again, I noticed that the installer couldn't read my partition
 table at all. It just showed a 137Gb disk that was all Free Space.
 To verify things, I booted into windows again, and the partition
 table was fine. This is where I'm at now. 




Reply to: