rebooting system HD from different motherboard (was recovering secure data for client)
From: Marcus (anyone_at_nowhere.com)
Date: 05/24/04
- Previous message: Crashdamage: "Re: Why you should NOT use Linux on your PC"
- Next in thread: WareKala: "Re: rebooting system HD from different motherboard (was recovering secure data for client)"
- Reply: WareKala: "Re: rebooting system HD from different motherboard (was recovering secure data for client)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 24 May 2004 11:25:40 GMT
Greetings,
First, thanks for all the help so far...
I am mounting each drive (hda1,hda2 and hda5) separately with:
mount /dev/hda# /mnt/root
(where number is 1,2, or 5)
I have reset the passwords ok but am still having problems
re-installing grub and have a question about grub and fstab. First,
when I look at the drive from knoppix I get 3 partitions: hda1, hda2
and hda5. However, fstab looks like this:
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boo 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
Is what was hda3 now being re-assigned to hda5? (I think this is what
might be happening, however, it appears as though the /boot section is
at the root of hda1 which is where /grub/grub.conf is located and the
bulk of the system is residing on hda2.)
the other problem is that I can't seem to chroot to hda1, only hda2
which is causing difficulty in re-installing grub with grub-install.
Like I said, /grub/grub.conf is on hda1. Here is my 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 /in:itrd-2.4.20-8.img
any help is appreciated in correct modification of grub.conf and fstab
as well as how I can re-install grub.
Thanks in advance,
David
- Previous message: Crashdamage: "Re: Why you should NOT use Linux on your PC"
- Next in thread: WareKala: "Re: rebooting system HD from different motherboard (was recovering secure data for client)"
- Reply: WareKala: "Re: rebooting system HD from different motherboard (was recovering secure data for client)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]