DISQUS

Ruben · 5 years ago

A better solution: Dont install Linux!!!

a prevention that is better than any cure.

WiraOne · 5 years ago

Well, this is a well know bug now .. it has been reported since FC2 T1 and nobody had taken any initiative to fix it and trying to blame it on the kernel .. I've been using FC1 with the latest kernel 2.6.X and I've no problem at all.. am wondering .. if this has to do with the kernel .. why change things that ain't broken? Why there is a need to have a work around by changing the BIOS value etc? Just couldn't believe it .. am sticking with FC1 for now .. it tossed by WinXP and I won't upgrade until the fix (and not workaround) has been identified ..

byte · 5 years ago

Ah, WiraOne, this is where you haven't done enough homework. All 2.6 based distros currently are suffering. Why, you might ask, do we blame the kernel? Because the kernel removed drive geometry handling support, and during installation, anaconda uses parted - parted doesn't handle all this as well as it should. Previously it had kernel support, nowadays it doesn't - so its eating up partitions, or so it may seem - its not 100% reproducible either, which makes it harder to debug.

So since userspace is taking control of hard disk geometry, and parted isn't handling it as well, it breaks. Of course, if you aren't doing an anaconda install, and are say, yum updating from FC1->FC2 (or in your case running a custom compiled kernel), it will just work and this "bug" won't bite.

This is confirmed to be a 2.6 kernel issue, read the lkml archives... And remember, it bits every 2.6-based distro out there - Mandrake 10, SuSE 9.1, and so on. It's not a Fedora isolated problem.

WiraOne · 5 years ago

Ah .. get it now .. as long as I don't run parted/anaconda install using the new kernel .. I'm safe. But as I said, still wondering why the kernel guy change thing that ain't broken .. and why they don't relayed/warned the developers (parted) .. well, I didn't do the homework well until I got bitten. I did a yum upgrade from FC1 to FC2 T2 and I didn't get this one and I thought hey, it is safe to do a fresh install of FC2 .. and I was too excited (you can tell by the tone when I got to know the FC2 final was avail on bittorrent network last time :) ).

byte · 5 years ago

Well, the "kernel guy" made the change because it was a decision made by all - let the kernel do less of handling partition tables, and let a userspace utility do it. They have "warned" the developers of parted, but that aside, time probably didn't permit such fixtures. Yum upgrading probably would've "saved" you, so to speak.

Gareth Russell · 5 years ago

I think its unfair how the majority of the bad press was aimed solely at Fedora Core 2, and hardly touched upon Mandrake or Suse.

wahlau · 5 years ago

it shows something positive: FC2 is getting all the attention :)

Chhoy Yam · 5 years ago

Fedora Core 2 and SuSE 9.1 eat-up partitions. I have had bad experient with both of them. I have destroyed 5 partitions on three hard disk drives in two PC in one week running Windows XP and SuSE 9.1 Pro(I played with Yast configure the system). I belive the disk subsystem and it utility need a major bug fix, but I like the interface.