Still having broblems conguring boot on different MB (was Recovering secure data for client)

From: Marcus (anyone_at_nowhere.com)
Date: 05/26/04


Date: Wed, 26 May 2004 12:17:05 GMT

First of all, Thanks Marcus, for your help so far...

This is what I get when I look at fstab and grub.conf and when I try
to do grub-install. Keep in ming that in knoppix I get the following:
hda1, hda2 and hda5...

root@ttyp0[/]# mount /dev/hda2 /mnt/root
root@ttyp0[/]# chroot /mnt/root
[root@Knoppix /]# mount /dev/hda1 /boot
[root@Knoppix /]# vi /etc/fstab
[root@Knoppix /]# vi /boot/grub/grub.conf
[root@Knoppix /]# grub-install /dev/hda
/dev/hdd1 does not have any corresponding BIOS drive.

contents of /boot (hda1)

[root@Knoppix /]# cd /boot
[root@Knoppix boot]# ls
System.map config-2.4.20-8 message.ja
vmlinux-2.4.20-8
System.map-2.4.20-19.9 grub module-info
vmlinuz
System.map-2.4.20-20.9 initrd-2.4.20-19.9.img
module-info-2.4.20-19.9 vmlinuz-2.4.20-19.9
System.map-2.4.20-8 initrd-2.4.20-20.9.img
module-info-2.4.20-20.9 vmlinuz-2.4.20-20.9
boot.b initrd-2.4.20-8.img module-info-2.4.20-8
vmlinuz-2.4.20-8
chain.b kernel.h os2_d.b
config-2.4.20-19.9 lost+found vmlinux-2.4.20-19.9
config-2.4.20-20.9 message vmlinux-2.4.20-20.9
[root@Knoppix boot]#

contents of / (hda2)

[root@Knoppix boot]# cd /
[root@Knoppix /]# ls
bin dev home lib lost+found mnt proc sbin
tmp usr
boot etc initrd localhost misc poweroff root tftpboot
users var
[root@Knoppix /]#

contents of (original) fstab

LABEL=/ / ext3 defaults
1 1
LABEL=/boot /boot ext3 defaults
1 2
none /dev/pts devpts gid=5,mode=620
0 0
none /proc proc defaults
0 0
none /dev/shm tmpfs defaults
0 0
LABEL=/users /users ext3 defaults
1 2
/dev/hda3 swap swap defaults
0 0
/dev/cdrom /mnt/cdrom udf,iso9660
noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto
noauto,owner,kudzu 0 0
someName-fast:/users /mnt/aharon-fast/users nfs rw,soft
0 0

contents of (original) grub.conf

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-20.9)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-20.9 ro root=LABEL=/
        initrd /initrd-2.4.20-20.9.img
title Red Hat Linux (2.4.20-19.9)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-19.9 ro root=LABEL=/
        initrd /initrd-2.4.20-19.9.img
title Red Hat Linux (2.4.20-8)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
        initrd /initrd-2.4.20-8.img

when I run grub-install:

root@ttyp0[/]# mount /dev/hda2 /mnt/root
root@ttyp0[/]# chroot
chroot: too few arguments
Try `chroot --help' for more information.
root@ttyp0[/]# chroot /mnt/root
[root@Knoppix /]# mount /dev/hda1 /boot
[root@Knoppix /]# grub-install /dev/hda
/dev/hdd1 does not have any corresponding BIOS drive.
[root@Knoppix /]#

Any help will be much appreciated....

Regards,

David

a grub newbie at the very least...



Relevant Pages

  • Re: Ubuntu upgrade gone bad
    ... mount your old root partition and use the chroot command to ... reinstalling the latest kernel through apt. ... then see if you can get it to boot and finish the upgrade. ...
    (Ubuntu)
  • Re: FC4 Crached / Hached or what it is, --- please help
    ... Normal boot time error is ... file data: invalid argument ... ok!here it guides chroot /mnt/sysimage! ... and I get prompt in rescue mode. ...
    (Fedora)
  • Re: 8.10 Rescue Mode
    ... I was able to do the following steps in live-cd boot succesfully: ... I did not try to do 'chroot /mnt/sysimage' since I was able to do my repairs ... I don't know how to get into the rescue mode. ... install and did not know where my install is mounted. ...
    (Ubuntu)
  • Re: upgrade glibc disaster
    ... >]Boot into the rescue mode or use a disk like tomsrtboot. ... >]RH9 CD with the glibc rpms on it. ... When you chroot (and you would have to ... So rescue boot and use rpm with --root option. ...
    (alt.os.linux)
  • Re: [PATCH 2.6.24] chroot= as a new kernel parameter
    ... etc.) i prefer adding boot options instead of modifying the initrd. ... I assume this is so you have have /distro1 /distro2 and use your boot ... "Use the initrd as an extended boot commandline" is a poor answer IMO. ... chroot= is useful, nonintrusive, and it just should be there. ...
    (Linux-Kernel)