Re: Grub + DualBoot + ChainLoader
by Andrew Farris
On Sun, 2004-06-06 at 15:46 +0200, Chris Chabot wrote:
> You have just experianced this bug:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115980
>
> The good news is that you can fix it by running this command in linux
> (either boot straight to linux if that works, or use the rescue cd):
> sfdisk -d /dev/hda | sfdisk --no-reread --force -H255 /dev/hda
>
> IMHO this is why FC2 should be recalled or atleast re-released with a
> fix or refusal to install when this bug hits; Because what a nice
> introduction to linux it is "We blow your shit up!"
Recalled, no (overkill). However, it should be more prominently
acknowledged -- fedora.redhat.com should have direct mention of this bug
specifically because of that new user mentality -- it broke things or
caused data loss. For most average computer users, not even to mention
complete beginners, data is gone when they cannot get the OS to start.
And FC2 is at at fault.
> I bet most people fall in the silent majority category, who never find
> their way to the mailing lists and just think "A so thats how 'well'
> linux works, it wrecked my computer and caused me to loose all my data..
> Use linux? Naaahhhhh"
Yes, it undoubtedly effects more users than those that get help -- how
many adventurous, would-be linux advocates have reformatted their
Windows boxes due to not being aware of this single line fix?
--
Andrew Farris, CPE senior (California Polytechnic State University, SLO)
fedora(a)andrewfarris.com :: lordmorgul on irc.freenode.net
19 years, 11 months
RE: Fedora Core 2 upgrade FAILURE
by Otto Haliburton
> -----Original Message-----
> From: fedora-devel-list-bounces(a)redhat.com [mailto:fedora-devel-list-
> bounces(a)redhat.com] On Behalf Of Richard Emberson
> Sent: Monday, June 07, 2004 2:50 PM
> To: For users of Fedora Core releases; fedora-devel-list(a)redhat.com
> Subject: Re: Fedora Core 2 upgrade FAILURE
>
> SUCCESS (see below)
>
>
> Richard Emberson wrote:
> > I have an older machine that can not boot from cdrom. Also, I had
> > some user data in one of the accounts.
> >
> > So I mounted disc1, copied vmlinuz and initrd.img to /boot, unmounted
> > disc1, added entry to /etc/grub.conf, then rebooted:
> >
> > mount /dev/cdrom
> > cp -a /mnt/cdrom/isolinux/vmlinuz /boot/FC2-install
> > cp -a /mnt/cdrom/isolinux/initrd.img /boot/FC2-install.img
> > umount /mnt/cdrom
> > and add entry like:
> > title Fedora Core 2 Installation
> > root (hd0,0)
> > kernel /FC2-install
> > initrd /FC2-install.img
> > to /etc/grub.conf (use /boot/FC2... when not relative to /boot)
> >
> > Everything was going along fine; I did an upgrade (not install) and
> > after 1 1/2 hours it said that the installation was a success and that
> > I should click the reboot button ... which I did.
> >
> > Well, reboot started out ok, there was a single boot option on the
> > grub boot page, but then it asked me to insert disc1. I did so
> > and it then asked me if I wanted to upgrade or install.
> >
> > hmmm.....
> >
> > I selected upgrade and it proceeded to "upgrade" a php rpm from disc1
> > and compat-db rpm from disc3 and announced that the installation was
> > successful and that I should click on the reboot button.
> >
> > Ok, reboot started and then once again it requested that I insert disc1
> > and once again it installed the same two rpm's, php from disc1 and
> > compat-db from disc3 and announced that the installation was a success.
> >
> > I tried one more time with the same result.
> >
> > So how do I break out of this? I really dont care about either
> > php or compat-db, I'd like to somehow bypass installing them and
> > get on with the boot. Are there parameters one can give at the grub
> > command line to force a kernel load?
> >
> > Help! Thanks.
> >
> >
> >
> > Richard
> >
> >
>
> Thanks to the many replies.
>
> What I ended up doing ....
>
> My original system had two scsi disks: disk1 with /boot and /
> and the other, disk2, with /home and /usr/local and I did not want to
> lose /home and /usr/local - which is why I wanted to upgrade,
> not install.
>
> So I bought a new scsi (I do plan to build a new machine at home
> some time this Summer, so its not as extreme as one might think)
> using it to replace disk2
> and did a redhat 9.0 on my old machine.
> I then mounted FC2 disc1 and copied vmlinux and initrd as described
> above. I then via grub booted using the FC2 code and did a full
> install. It worked. Now I can just replace the new disk2 with the
> old and the upgrade is complete.
>
> IMPORTANT: the first time I did this - yes I did this twice - I
> for some unknown reason had disk1 contain /boot and /usr while
> the new disk2 had / - the redhat 9 install succeeded this succeeded but
> not the subsequent FC2 install!! - so the second time I had disk1
> contain /boot and / while the new disk2 had /home and /usr/local and
> for this combination FC2 install (after installing redhat 9 a
> second time) worked.
>
> Thanks again.
>
>
> Richard
>
>
maybe I'm missing something here, but I believe that you can download the
iso's to your hard drive and mount them and install. Maybe I'm wrong but
that would seem to have been a lot simpler. If this worked for you though
great.
19 years, 11 months
Re: Fedora Core 2 upgrade FAILURE
by Richard Emberson
SUCCESS (see below)
Richard Emberson wrote:
> I have an older machine that can not boot from cdrom. Also, I had
> some user data in one of the accounts.
>
> So I mounted disc1, copied vmlinuz and initrd.img to /boot, unmounted
> disc1, added entry to /etc/grub.conf, then rebooted:
>
> mount /dev/cdrom
> cp -a /mnt/cdrom/isolinux/vmlinuz /boot/FC2-install
> cp -a /mnt/cdrom/isolinux/initrd.img /boot/FC2-install.img
> umount /mnt/cdrom
> and add entry like:
> title Fedora Core 2 Installation
> root (hd0,0)
> kernel /FC2-install
> initrd /FC2-install.img
> to /etc/grub.conf (use /boot/FC2... when not relative to /boot)
>
> Everything was going along fine; I did an upgrade (not install) and
> after 1 1/2 hours it said that the installation was a success and that
> I should click the reboot button ... which I did.
>
> Well, reboot started out ok, there was a single boot option on the
> grub boot page, but then it asked me to insert disc1. I did so
> and it then asked me if I wanted to upgrade or install.
>
> hmmm.....
>
> I selected upgrade and it proceeded to "upgrade" a php rpm from disc1
> and compat-db rpm from disc3 and announced that the installation was
> successful and that I should click on the reboot button.
>
> Ok, reboot started and then once again it requested that I insert disc1
> and once again it installed the same two rpm's, php from disc1 and
> compat-db from disc3 and announced that the installation was a success.
>
> I tried one more time with the same result.
>
> So how do I break out of this? I really dont care about either
> php or compat-db, I'd like to somehow bypass installing them and
> get on with the boot. Are there parameters one can give at the grub
> command line to force a kernel load?
>
> Help! Thanks.
>
>
>
> Richard
>
>
Thanks to the many replies.
What I ended up doing ....
My original system had two scsi disks: disk1 with /boot and /
and the other, disk2, with /home and /usr/local and I did not want to
lose /home and /usr/local - which is why I wanted to upgrade,
not install.
So I bought a new scsi (I do plan to build a new machine at home
some time this Summer, so its not as extreme as one might think)
using it to replace disk2
and did a redhat 9.0 on my old machine.
I then mounted FC2 disc1 and copied vmlinux and initrd as described
above. I then via grub booted using the FC2 code and did a full
install. It worked. Now I can just replace the new disk2 with the
old and the upgrade is complete.
IMPORTANT: the first time I did this - yes I did this twice - I
for some unknown reason had disk1 contain /boot and /usr while
the new disk2 had / - the redhat 9 install succeeded this succeeded but
not the subsequent FC2 install!! - so the second time I had disk1
contain /boot and / while the new disk2 had /home and /usr/local and
for this combination FC2 install (after installing redhat 9 a
second time) worked.
Thanks again.
Richard
19 years, 11 months
Re: Shrinking/splitting up core Was: Why are there only i686 and i586 Version of glibc...
by Tom Diehl
On Mon, 7 Jun 2004, Steven Pritchard wrote:
> On Mon, Jun 07, 2004 at 08:24:11AM -0600, Stephen Smoogen wrote:
> > I dont think Anaconda is meant to look at anything beyond the bare
> > installation Cd's the rest should be done with first-boot. Maybe first
> > boot should have a yum configuration section where you can enter the yum
> > places you want to to point ot.
>
> How's that going to work with kickstart-based installs/upgrades?
>
> I'd really like to see a day where a person could fire up
> kickstart-based upgrades on 200 cluster servers and have *everything*
> upgraded when the systems reboot (assuming all of their local apps
> were in an appropriate repository).
For the most part yum can do this today. It is not perfect but machines
that I kickstart from scratch do a stripped down minimal install. In the
%post I then do a yum groupinstall somegroup. I have a comps file that
knows what packages are to be installed in the group. Generally the group
is the fqdn of the machine. That way I edit the group for that machine
and poof you have a very easy to reproduce machine. Upgrades for the most
part work today by simply doing a yum update. There are some problems with
FC1 -> fc2 upgrades with lvm involved but other than that AFAIK this is
doable today.
My feeling is that this is doable with a little more work.
Kickstart in its current form has the ability to do upgrades. It is a
simple matter of putting about a dozen lines in the ks-cfg file and rebooting
the machine. You can launch this via pxe or from an entry in the grub.conf
file if you do not want to play around with cd's or floppies.
Someone mentioned on one of these lists in the last couple of weeks about
no longer doing upgrades but doing migrations. IIRC the general idea was
save all of the known config files somewhere format, install the new os,
restore the configs and presto chango you have a new working system.
I like the idea but I do not see how thay are going to account for all
of the variables. It will be interesting to see if they can make it work.
> FWIW, I was doing stuff like this with engineering workstations
> running HP-UX at a previous job 5 years ago using HP's Ignite-UX
> tool... It still scares me a little that we don't have a tool even
> that good yet.
>
> That employer is using a *ton* of RHL now, and upgrades are nearly
> unmanageable. Paying for RHEL would reduce the frequency of necessary
> upgrades, and the money isn't necessarily a problem for them, but how
> would they do all those upgrades? (In other words, I don't think this
> is just a problem for Fedora Core/Extras/etc. users.)
If you are upgrading from RHL to RHEL Red Hat says reinstall. Some
people have used yum with varying success. If I had a bunch of machines
to upgrade that is the path I would explore. If for whatever reason you
do not want to do RHEL there are always the clones. I have not used them
but I have heard some good things about them.
Tom
19 years, 11 months
Re: Grub + DualBoot + ChainLoader
by Chris Chabot
You have just experianced this bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115980
The good news is that you can fix it by running this command in linux
(either boot straight to linux if that works, or use the rescue cd):
sfdisk -d /dev/hda | sfdisk --no-reread --force -H255 /dev/hda
IMHO this is why FC2 should be recalled or atleast re-released with a
fix or refusal to install when this bug hits; Because what a nice
introduction to linux it is "We blow your shit up!"
I bet most people fall in the silent majority category, who never find
their way to the mailing lists and just think "A so thats how 'well'
linux works, it wrecked my computer and caused me to loose all my data..
Use linux? Naaahhhhh"
Morteza A. Nia wrote:
>I was installed FC2 on my PC (HDD with one Disk) , 1 month ago , but
>on my friends' pc ( HDD with 2 disks) the Grub use chainloader for M$
>WindowsXP but it couldn't load WindowsXP by chainloder. and did not
>know chainloader command on hda , .. ( else hda ).
>if you know, so help me! ;)
>Tanx.
>
>Morteza A. Nia
>
>
>
>
19 years, 11 months
Grub + DualBoot + ChainLoader
by Morteza A. Nia
I was installed FC2 on my PC (HDD with one Disk) , 1 month ago , but
on my friends' pc ( HDD with 2 disks) the Grub use chainloader for M$
WindowsXP but it couldn't load WindowsXP by chainloder. and did not
know chainloader command on hda , .. ( else hda ).
if you know, so help me! ;)
Tanx.
Morteza A. Nia
19 years, 11 months
mkinitrd failed problems yuming the kernel 2.6.6-1.421
by Brian Millett
This is a trace of the process.
I do not know what this means as far as the stability of the new installed
kernel.
kernel-sourcecode 100 % done 18/43
kernel 100 % done 19/43
memlock: Cannot allocate memory
Couldn't lock into memory, exiting.
mkinitrd failed
a listing of /boot:
ls /boot
boot.b initrd-2.6.6-1.403.img System.map-2.6.6-1.406
chain.b initrd-2.6.6-1.406.img System.map-2.6.6-1.414
config-2.6.6-1.391 initrd-2.6.6-1.414.img System.map-2.6.6-1.421
config-2.6.6-1.397 kernel.h vmlinuz
config-2.6.6-1.403 lost+found vmlinuz-2.6.6-1.391
config-2.6.6-1.406 memtest86+-1.15 vmlinuz-2.6.6-1.397
config-2.6.6-1.414 os2_d.b vmlinuz-2.6.6-1.403
config-2.6.6-1.421 System.map vmlinuz-2.6.6-1.406
grub System.map-2.6.6-1.391 vmlinuz-2.6.6-1.414
initrd-2.6.6-1.391.img System.map-2.6.6-1.397 vmlinuz-2.6.6-1.421
initrd-2.6.6-1.397.img System.map-2.6.6-1.403
It sure does look like the initrd is missing.
Thanks.
--
Brian Millett
Enterprise Consulting Group "Shifts in paradigms
(314) 205-9030 often cause nose bleeds."
bpmATec-groupDOTcom Greg Glenn
19 years, 11 months
Re: Fedora Core 2 upgrade FAILURE
by David Hollis
Quoting Luciano Miguel Ferreira Rocha <strange(a)nsk.no-ip.org>:
> On Thu, Jun 03, 2004 at 10:44:44AM -0700, Richard Emberson wrote:
> > root (hd0,0)
> > kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/
> > initrd /initrd-2.6.5-1.358.img
> > boot
>
> Try without initrd and with root pointing to a device file
> root (hd0,0)
> kernel /vmlinuz-2.6.5-1.358 ro root=/dev/hda2
> boot
> (or wherever is your root partition)
>
>
use:
kernel /vmlinuz-2.6.5-1.358 ro root=/dev/hda2 single
(note the addition of single to go into single user mode)
That should get you booted and to a command prompt. Apparently, the kernel was
upgraded, but the postinstall failed to do it's bit and add itself to grub,
create the initrd etc. If you can get to the command prompt, run this:
[ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --mkinitrd --depmod
--install 2.6.5-1.358
[ -x /usr/sbin/hardlink ] && /usr/sbin/hardlink -c /lib/modules/2.6.* || :
That's taken straight from the RPM. It should add an entry to grub, create the
initrd, and you should be in good shape.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
19 years, 11 months
Re: Fedora Core 2 upgrade FAILURE
by Luciano Miguel Ferreira Rocha
On Thu, Jun 03, 2004 at 10:44:44AM -0700, Richard Emberson wrote:
> root (hd0,0)
> kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/
> initrd /initrd-2.6.5-1.358.img
> boot
Try without initrd and with root pointing to a device file
root (hd0,0)
kernel /vmlinuz-2.6.5-1.358 ro root=/dev/hda2
boot
(or wherever is your root partition)
Initrd adds support for access by LABEL of root partition and for ext3,
that can be ignored in the meantime as an ext3 filesystem can be mounted
as an ext2.
(It also adds support for scsi and more uncommon hardware, that you
probably don't need. Anyway, try it.)
If it boots, create an initrd with mkinitrd and change grub's
configuration.
As an alternative, boot the installation kernel with the "rescue" option,
mount the partitions and then create the initrd.
Regards,
Luciano Rocha
--
Consciousness: that annoying time between naps.
19 years, 11 months
Fedora Core 2 upgrade FAILURE
by Richard Emberson
I've tried the fedora-list without success so please bear with me
while I discribe my plight:
I've got an older VALinux machine and I can not boot from CD.
So I mounted disc1, copied vmlinuz and initrd.img to /boot, unmounted
disc1, added entry to /etc/grub.conf, then rebooted:
mount /dev/cdrom
cp -a /mnt/cdrom/isolinux/vmlinuz /boot/FC2-install
cp -a /mnt/cdrom/isolinux/initrd.img /boot/FC2-install.img
umount /mnt/cdrom
and add entry like:
title Fedora Core 2 Installation
root (hd0,0)
kernel /FC2-install
initrd /FC2-install.img
to /etc/grub.conf (use /boot/FC2... when not relative to /boot)
Everything was going along fine; I did an upgrade (not install) and
after 1 1/2 hours it said that the installation was a success and that
I should click the reboot button ... which I did.
Well, reboot started out ok, there was a single boot option on the
grub boot page, but then it asked me to insert disc1. I did so
and it then asked me if I wanted to upgrade or install.
hmmm.....
I selected upgrade and it proceeded to "upgrade" a php rpm from disc1
and compat-db rpm from disc3 and announced that the installation was
successful and that I should click on the reboot button.
Ok, reboot started and then once again it requested that I insert disc1
and once again it installed the same two rpm's, php from disc1 and
compat-db from disc3 and announced that the installation was a success.
I tried one more time with the same result.
At this point (with advise from the fedora-list) at the grub gui
I entered the command mode and looked at what was in the /boot
directory. Well, vmlinuz-2.6.5-1.358 is there (the only vmlinuz file)
but initrd-2.6.5-1.358.img is not there (neither is memtest86+-1.11),
though there are some initrd-2.4.* files still.
I wanted to try the following from grub:
root (hd0,0)
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/
initrd /initrd-2.6.5-1.358.img
boot
but since initrd-2.6.5-1.358.img is not there I can not.
So, what can I do? None of the grub network commands, e.g., ifconfig,
seem to be available. How do I get a copy of initrd-2.6.5-1.358.img
onto the disk?
Thanks
Richard
19 years, 11 months
