Hi,
Somewhere around 70% into the install process some file conflict results and installation halts. I am not sure what package is having the problem. I selected all options for all packages. Basically, I am trying to install everything.
What next? Start over?
Thanks, Ernest
On Sun, 2006-10-01 at 10:50 -0400, Ernest L. Williams Jr. wrote:
Hi,
Somewhere around 70% into the install process some file conflict results and installation halts. I am not sure what package is having the problem. I selected all options for all packages. Basically, I am trying to install everything.
What next? Start over?
I tried to upgrade to recover my batched install but now all I get is the "grub>" prompt.
Can anyone help me get out of this mess?
Thanks, Ernest
Thanks, Ernest
On Sun, Oct 01, 2006 at 11:02:41AM -0400, Ernest L. Williams Jr. wrote:
On Sun, 2006-10-01 at 10:50 -0400, Ernest L. Williams Jr. wrote:
Somewhere around 70% into the install process some file conflict results and installation halts.
I tried to upgrade to recover my batched install but now all I get is the "grub>" prompt.
Can anyone help me get out of this mess?
If you are really something like 70% done then most likely you do have a bootable if an incomplete system (unless initrd for your kernel was not written yet). Pretty good chance that you have at least a workable text-mode console. The catch is that a grub installation, which means a boot sector among other things, is done close to the very end.
You can do two things. You can boot your system typing boot commands directly at a grub prompt. Start with root(<whatever>) to point to that device where your kernel and initrd reside. grub helps expanding possible choices. See 'info grub' for more information. Once you booted then you can install grub yourself. Check "Installing GRUB natively" section in 'info grub'.
Other option is to boot from your installation media in a "rescue" mode, use that to get to your disk and install grub on a disk from there.
After that you may proceed with fixing your installation manually. 'yum update' as the first step should at least fill out all missing dependencies.
Michal
On Sun, 2006-10-01 at 10:58 -0600, Michal Jaegermann wrote:
On Sun, Oct 01, 2006 at 11:02:41AM -0400, Ernest L. Williams Jr. wrote:
On Sun, 2006-10-01 at 10:50 -0400, Ernest L. Williams Jr. wrote:
Somewhere around 70% into the install process some file conflict results and installation halts.
I tried to upgrade to recover my batched install but now all I get is the "grub>" prompt.
Can anyone help me get out of this mess?
If you are really something like 70% done then most likely you do have a bootable if an incomplete system (unless initrd for your kernel was not written yet). Pretty good chance that you have at least a workable text-mode console. The catch is that a grub installation, which means a boot sector among other things, is done close to the very end.
I am completely hosed. The only prompt that I get is the "grub>" prompt. I can no longer boot from neither CDROM 1 nor the rescue CD.
You can do two things. You can boot your system typing boot commands directly at a grub prompt. Start with root(<whatever>)
root (hd0,1)
to point to that device where your kernel and initrd reside. grub helps expanding possible choices.
I don't know where this is?? If it is similar to FC5, I can look at my other system.
See 'info grub' for more information. Once you booted then you can install grub yourself. Check "Installing GRUB natively" section in 'info grub'.
Will do.
Other option is to boot from your installation media in a "rescue" mode, use that to get to your disk and install grub on a disk from there.
After that you may proceed with fixing your installation manually. 'yum update' as the first step should at least fill out all missing dependencies.
Michal
On Sun, Oct 01, 2006 at 01:08:52PM -0400, Ernest L. Williams Jr. wrote:
I am completely hosed. The only prompt that I get is the "grub>"
Yes, that is what you need. Somewhat minimal but may be good enough. :-)
I can no longer boot from neither CDROM 1 nor the rescue CD.
Because? Your BIOS should let you specify a boot order and maybe even pick up a boot device for that particular boot. Details vary with a particular BIOS.
root (hd0,1)
Very good. "root" here means "grub-root", i.e. that partition on which boot images reside and not '/' of a Linux file system.
to point to that device where your kernel and initrd reside. grub helps expanding possible choices.
I don't know where this is??
Well, you wrote that on (hd0,1). Is that incorrect? If yes, then change it.
If it is similar to FC5, I can look at my other system.
Yes, this is really the same stuff you see in /etc/grub.conf. So you have to type something like
kernel /vm... ro root=LABEL=/ s (or "3" instead of "s")
(grub expands so let it help you) and in the next line
initrd /init...
and on the next line
boot
Check "General boot methods" in 'info grub' and in particular "GNU/Linux" there.
You are likely also seeing something like this:
[ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.]
Michal
On Sun, 2006-10-01 at 10:58 -0600, Michal Jaegermann wrote:
On Sun, Oct 01, 2006 at 11:02:41AM -0400, Ernest L. Williams Jr. wrote:
On Sun, 2006-10-01 at 10:50 -0400, Ernest L. Williams Jr. wrote:
Somewhere around 70% into the install process some file conflict results and installation halts.
I tried to upgrade to recover my batched install but now all I get is the "grub>" prompt.
Can anyone help me get out of this mess?
If you are really something like 70% done then most likely you do have a bootable if an incomplete system (unless initrd for your kernel was not written yet). Pretty good chance that you have at least a workable text-mode console. The catch is that a grub installation, which means a boot sector among other things, is done close to the very end.
You can do two things. You can boot your system typing boot commands directly at a grub prompt. Start with root(<whatever>) to point to that device where your kernel and initrd reside. grub helps expanding possible choices. See 'info grub' for more information. Once you booted then you can install grub yourself. Check "Installing GRUB natively" section in 'info grub'.
Okay, I did the following: ================================================================== grub> root (hd0,1) Filesystem type is ext2fs, partition type 0x83
grub> kernel /vmlinuz-2.6.18-1.2708.fc6 [Linux-bzImage, setup=0x1e00, size=0x1e6599]
grub> initrd /initrd-2.6.18-1.2708.fc6.img [Linux-initrd @ 0x37ddc000, 0x213a86 bytes]
grub> boot =================================================================
After booting up, I got a console login. Of course, I don't have a login/password. Now, I need to reset the root password. Can I do this from grub as well?
Ultimately, I need to get back to the rescue CD as I will want to do a fresh install. Wow, what a weekend and I am still spending it just for the install. Well, hopefully my experience may help others.
Thanks for all who are helping me get FC6Pre installed. :)
-- Ernest
Other option is to boot from your installation media in a "rescue" mode, use that to get to your disk and install grub on a disk from there.
After that you may proceed with fixing your installation manually. 'yum update' as the first step should at least fill out all missing dependencies.
Michal
On Sun, Oct 01, 2006 at 02:02:51PM -0400, Ernest L. Williams Jr. wrote:
Okay, I did the following:
grub> root (hd0,1) Filesystem type is ext2fs, partition type 0x83
grub> kernel /vmlinuz-2.6.18-1.2708.fc6 [Linux-bzImage, setup=0x1e00, size=0x1e6599]
grub> initrd /initrd-2.6.18-1.2708.fc6.img [Linux-initrd @ 0x37ddc000, 0x213a86 bytes]
grub> boot
After booting up, I got a console login.
Yes, that's the ticket.
Now, I need to reset the root password. Can I do this from grub as well?
No, you cannot. But you can, as it was suggested before, boot in a single-user mode by appending "s", or "1", to your "kernel" command and then you can set that password any way you want.
Ultimately, I need to get back to the rescue CD as I will want to do a fresh install.
Well, apparently your hardware decided to quit so not before that is fixed. OTOH if you are that far you should be able to install from a disk partition (one on which you are _not_ installing).
Michal
On Sun, 2006-10-01 at 13:57 -0600, Michal Jaegermann wrote:
On Sun, Oct 01, 2006 at 02:02:51PM -0400, Ernest L. Williams Jr. wrote:
Okay, I did the following:
grub> root (hd0,1) Filesystem type is ext2fs, partition type 0x83
grub> kernel /vmlinuz-2.6.18-1.2708.fc6 [Linux-bzImage, setup=0x1e00, size=0x1e6599]
grub> initrd /initrd-2.6.18-1.2708.fc6.img [Linux-initrd @ 0x37ddc000, 0x213a86 bytes]
grub> boot
After booting up, I got a console login.
Yes, that's the ticket.
Now, I need to reset the root password. Can I do this from grub as well?
No, you cannot. But you can, as it was suggested before, boot in a single-user mode by appending "s", or "1", to your "kernel" command and then you can set that password any way you want.
Ultimately, I need to get back to the rescue CD as I will want to do a fresh install.
Well, apparently your hardware decided to quit so not before that is fixed. OTOH if you are that far you should be able to install from a disk partition (one on which you are _not_ installing).
I managed to get the CDROM drive talking long enough to get an FTP install started from one of the rawhide mirrors.
Thanks for your help, Ernest
Michal