At 07:43 PM 12/22/2008, Carl Lowenstein wrote:
On Mon, Dec 22, 2008 at 7:21 PM, James G. Sack (jim)
<[email protected]> wrote:
> Lief Hendrickson wrote:
>> At 01:16 PM 12/22/2008, Carl Lowenstein wrote:
>>> On Sun, Dec 21, 2008 at 10:30 PM, Lief Hendrickson <[email protected]>
>>> wrote:
>>> >
>>> > It's a friends computer. The distribution is Fedora, but we don't know
>>> > which version until I can boot.
>>> >
>>> > I booted into Knoppix. I may have been wrong about where the boot
>>> manager
>>> > is located. The Knoppix desktop shows a hda1 and hda2. When I
>>> click on the
>>> > hda1 icon to show its contents, grub is one of items shown in the file
>>> > manager window. Continuing with the steps above. I opened a
>>> command window
>>> > and entered
>>> > $ sudo su -
>>> > # fdisk -l /dev/hda
>>> >
>>> > The result was
>>> >
>>> > Device Boot Start End Blocks id System
>>> > /dev/hda1 * 1 13 104391 83
>>> Linux
>>> > /dev/hda2 14 23421 19525401 8e Linux LVM
>>>
>>> OK, it' looks like a standard default Fedora installation.
>>>
>>> > I then entered
>>> > #mount -o dev,rw /mnt/hda1
>>> > Result:
>>> > mount: /dev/hda1 already mounted or mnt/hda1 busy
>>> > mount: according to mtab, /dev/hda1 is already mounted on /mnt/hda1
>>>
>>> > (is this because the Knoppix desktop shows hda1 and hda2, which may
>>> indicate
>>> > they are already mounted?)
>>>
>>> The Knoppix desktop shows hda1 and hda2 but in my experience does not
>>> mount them. It just recognizes that they are present. But your
>>> Knoppix might be different from mine.
>>>
>>> If Knoppix has mounted hda1, you should be able to make it writeable
>>> by right-clicking on its icon and selecting something like "make
>>> writeable". That's the purpose of the "rw" in the command line,
>>> stands for "read and write". On the command line, to make an
>>> already-mounted disk writeable:
>>>
>>> # mount -o remount,dev,rw /mnt/hda1
>>>
>>> > I then entered
>>> > #chroot /mnt/hda1 grub-install /dev/hda
>>>
>>> This shows that Fedora has hidden grub-install from you, it must be
>>> somewhere in the LVM on hda2.
>>>
>>> > Result:
>>> > chroot: cannot run command 'grub-install' :No such file or directory
>>>
>>> So you have to use the grub-install that resides on the Knoppix disk.
>>>
>>> # grub-install --root-directory=/mnt/hda1 /dev/hda
>>>
>>> > Since grub is on hda1, as mentioned above, is there a way to get rid
>>> of the
>>> > dual boot option, since the other hard drive (the one with Windows)
>>> is no
>>> > longer present? or is there something else that should be done?
>>> Thanks.
>>>
>>> There will be no dual-boot option, since grub-install will not find
>>> any Windows to make part of a dual-boot system.
>>>
>>> This is the second approximation. Again, if this works you are done,
>>> if it doesn't work, give the details of what happened and we can try
>>> for the third approximation.
>>>
>>> carl
>>> --
>>> carl lowenstein marine physical lab u.c. san diego
>>> [email protected]
>>
>>
>> It worked partly. I got to grub install part and entered:
>> # grub-install --root-directory=/mnt/hda1 /dev/hda
>>
>> The result was:
>> This is the contents of the device map /mnt/hda1/boot/grub/device.map
>> (fd0) /dev/fd0
>> (hd0) /dev/hda
>>
>> I then shutdown, removed Knoppix CD and rebooted.
>>
>> It was able to boot from the HD, but it only got to the prompt
>> grub>
>>
>> What should I enter at this prompt?
>
> Hi Lief-
>
> It's hard to guess what the original boot configuration was, but the
> (removed) Windows disk may have "chained" to the loader on the Linux
> disk. In any case, there may be either a missing or incorrect boot
> configuration file on the Linux disk.
>
> It would be useful if you could boot Knoppix once again, and mount the
> /dev/hda1 filesystem again, and post the contents of grub/grub.conf file
> from there. If you can only copy by hand, and that's too much to copy,
> just grab the first "boot stanza", that looks something like
> """
> root (hdN,1)
> kernel /vmlinuz-XXXX ro root=/dev/VolumeGroup0001/LogicalVolume0001
> initrd /initrd-XXXX.img
> """
> The hdN is likely hd1, and the VolumeGroup, LogicalVolume stuff might be
> quite different, actually.
>
> For good measure, post the contents of grub/device/map.
That's grub/device.map
>
> If there is no grub directory, or no grub.conf file, just report that
> and be sure to get the LVM information, below-next.
>
> It might also be useful to post the output from these commands
> sudo vgs
> sudo lvs
>
> Regards,
> ..jim
>
> --
> [email protected]
> http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
>
Hi, Jim.
My surmise is that the computer had a standard default Fedora
installation, with grub booting Fedora and chaining to the Windows
loader.
I didn't stop to think that the grub.conf was probably pointing to
what is now the wrong drive (hdb). So contents of grub.conf would be
good to know.
This is really an install-fest project, just because there are too
many variables to second-guess. For what it's worth, the next
InstallFest should be January 10.
carl
--
carl lowenstein marine physical lab u.c. san diego
[email protected]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
I'm going out of town tomorrow. I'll try again when I get
back. Installfest might be the best bet. Thanks.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
