Bug#208809: Réf. : Re: Bug#208809: partition problem
I'll try to build a 2.4.20 kernel image and write it down on a floppy.
I suppose that if I use the same root/swap indications as in the kernels
present on the cd
(with rdev), the floppy will continue towards the CD ?
Concerning the proposal to remove all partitions above 128G :
The manufacturer installed all software restoring images in a partition
(Win32 FAT) in
the last 5 Gb of the disk. I'd better not remove that, because the recovery
CD uses
that partition's data to fix issues with the main Win XP partition.
Supposed that the new kernel will support the disk size beyond 128G for
fdisk purposes,
and I will install all stuff beyond 128G, could I loose the last partition
(recovery) when fdisk rewrites
the partition table(s) ?
Thank you : I feel that we are going quicky towards a solution and that
I've learned a lot today
with all responses I got.
Alain ROOS
wrote :
On Fri, Sep 05, 2003 at 10:18:28AM +0100, Steve McIntyre wrote:
> Sounds like the kernel is not able to read the full disk. 160GB is
> larger than old-style IDE hardware can address, and so older kernels
> will not support it.
I can confirm this, I hit the same problem about a year ago.
> I'm not sure if the 2.4.18 kernel available on the Woody install CDs will
> work here, but it's worth a try.
At the time I installed, bf2.4 didn't help - the relevant patch had not
made it into the main kernel tree, it was only in -ac. But I don't remember
whether bf2.4 used 2.4.16 or 2.4.18 then.
A workaround is to install using a filing system which you can later (once
a newer kernel is installed) grow beyond the 128G mark. These days, AFAIK
ext2, reiserfs and xfs allow resizing of the filesystem - I'd go for
reiserfs!
In contrast to Alain I started off with an unpartitioned HD, so cfdisk just
reported a size of 128G. Alain, to make cfdisk accept the HD, you should
try deleting _under_Windows_ the partition(s) on the disk which lie beyond
128G (L: AFAICT). The XP partition manager has a nice graphical display of
where the partitions are located on disk, they should be easy to identify.
Cheers,
Richard
--
__ _
|_) /| Richard Atterer | GnuPG key:
| \/¯| http://atterer.net | 0x888354F7
¯ '` ¯
Reply to: