So after successfully convincing my boss to allow me to install linux at work on a dual boot machine, I did so this week. Guess what? The infamous (that I am now newly aware of) win XP dual boot bug rears its ugly head! Now I'm in trouble for screwing up a windows computer that other people need, and the case for linux at work has just recieved a nail in the coffin... So I get to try to fix this on my own time, thank you fedora, and just hope that in the far off future I can try again with fedora core 10 or something...
I mean, JESUS CHRIST, how can such a show-stopping bug be allowed in a full release?! If people are going to be migrating away from windows and giving linux a try, is it wise to trash their computers?! Now I have to become an expert on disk repair so I can fix the stupid thing.
Of course, I'm happy to use FC2 and say hasta la vista to windows xp forever... but back in the real world, we still need windows.
Kepa
On Tue, 22 Jun 2004 21:38:20 +0100, Kepa Lyman kepa@oceanvoyages.com wrote:
So after successfully convincing my boss to allow me to install linux at work on a dual boot machine, I did so this week. Guess what? The infamous (that I am now newly aware of) win XP dual boot bug rears its ugly head! Now I'm in trouble for screwing up a windows computer that other people need, and the case for linux at work has just recieved a nail in the coffin... So I get to try to fix this on my own time, thank you fedora, and just hope that in the far off future I can try again with fedora core 10 or something...
Prevention and Revovery: http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00908.html
fwiw, this isn't necessarily widely reproducible as can be assumed, its certaintly not clear that one can point to a specific bios/motherboard and know without fail that this issue is going to happen.
fwiw, the lastest suse and mandrake releases appear to have the same problem and its very much related to a decision made by the mainline kernel developers to change how disk geometry is handled. I would imagine that any 2.6 kernel based distribution that boots into a 2.6 kernel environment to do installation will have similar issues.
reference: http://qa.mandrakesoft.com/show_bug.cgi?id=7959#c27 http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html#troubleshoot http://www.eweek.com/article2/0,1759,1585840,00.asp
-jef"the real question is, why was there a communication breakdown upstream between mainline kernel development and partitioning tool projects like parted about the importance of dual boot situations invovling CHS"spaleta
Kepa Lyman wrote:
So after successfully convincing my boss to allow me to install linux at work on a dual boot machine, I did so this week. Guess what? The infamous (that I am now newly aware of) win XP dual boot bug rears its ugly head! Now I'm in trouble for screwing up a windows computer that other people need, and the case for linux at work has just recieved a nail in the coffin... So I get to try to fix this on my own time, thank you fedora, and just hope that in the far off future I can try again with fedora core 10 or something...
I mean, JESUS CHRIST, how can such a show-stopping bug be allowed in a full release?! If people are going to be migrating away from windows and giving linux a try, is it wise to trash their computers?! Now I have to become an expert on disk repair so I can fix the stupid thing.
Of course, I'm happy to use FC2 and say hasta la vista to windows xp forever... but back in the real world, we still need windows.
Kepa
I got this bug with a computer with pheonix bios. I'm not sure if this is common among this bios version. I just had to change the second selection that deals with selecting LBA and other modes. After changing the setting to LBA instead of auto, it worked.
This was on one of those half board industrial pcisa CPU boards. The sfdisk method for repair was not needed.
If memory serves me, this problem seemed to be pretty much not encountered before the release of FC2. I didn't hear about it until FC2 was released.
As on the real world comment..... We are moving to linux for an i686 based program (dimensioning program for FedEx, UPS, etc). The things that scares me with those developing the applications to run on linux are the two reasons listed below.
1) They run everything as root. (not kidding) 2) They do not bother with applying upgraded packages to the system. (Security or bug fixes)
I hope this does not mean that we are entering a domain filled with viruses and trojans on the linux based systems.
Good luck on getting the computer to boot back into the other operating system.
Jim
quit yer bitchin...it has been a documented bug from day one, you should do some research before doing anything on a production machine. Also you will be able to get off any critical data with a linux boot cd like knoppix STD or something. Then just throw an image or install windows or what ever you fellas do. On Tuesday 22 June 2004 14:38, Kepa Lyman wrote:
So after successfully convincing my boss to allow me to install linux at work on a dual boot machine, I did so this week. Guess what? The infamous (that I am now newly aware of) win XP dual boot bug rears its ugly head! Now I'm in trouble for screwing up a windows computer that other people need, and the case for linux at work has just recieved a nail in the coffin... So I get to try to fix this on my own time, thank you fedora, and just hope that in the far off future I can try again with fedora core 10 or something...
I mean, JESUS CHRIST, how can such a show-stopping bug be allowed in a full release?! If people are going to be migrating away from windows and giving linux a try, is it wise to trash their computers?! Now I have to become an expert on disk repair so I can fix the stupid thing.
Of course, I'm happy to use FC2 and say hasta la vista to windows xp forever... but back in the real world, we still need windows.
Kepa
On Tue, 2004-06-22 at 21:38 +0100, Kepa Lyman wrote:
So after successfully convincing my boss to allow me to install linux at work on a dual boot machine, I did so this week. Guess what? The infamous (that I am now newly aware of) win XP dual boot bug rears its ugly head! Now I'm in trouble for screwing up a windows computer that other people need, and the case for linux at work has just recieved a nail in the coffin... So I get to try to fix this on my own time, thank you fedora, and just hope that in the far off future I can try again with fedora core 10 or something...
Well, you're catching plenty of flack, but it is rather ironic that you posted this to fedora-test-list where it was endlessly discussed before the release, and where there is at least one pre-release post from you. I can't argue that it is a nasty bug and that it is unfortunate that FC2 was knowingly released containing it, at least without a large disclaimer at the top of the release notes; however, the information is out there prominently, and FCx is not being touted for production machines. Check out RHEL, WBEL, Tao, CentOS, ..., particularly in such a touchy situation as you chose to do a Linux demonstration for your management. Good luck recovering - the machine and your reputation.
Phil
On Tue, 2004-06-22 at 13:38, Kepa Lyman wrote:
Now I'm in trouble for screwing up a windows computer that other people need, and the case for linux at work has just recieved a nail in the coffin...
I mean, JESUS CHRIST, how can such a show-stopping bug be allowed in a full release?!
I mean, JESUS CHRIST, if that computer was so important, how come you install ANYTHING on it before doing a proper research on issues, known bugs, etc.?
I feel your pain (been there, done that) but it's your fault (it was my fault too when i did similar screwups).
On Tue, 2004-06-22 at 13:38, Kepa Lyman wrote:
I mean, JESUS CHRIST, how can such a show-stopping bug be allowed in a full release?!
Didn't stop my show. Dual-boot environments are inherently unstable... and should be avoided at all costs. And of course, an ounce of research prior to installation is worth a pound of post-install repairs.