Gentoo!

I slap you with a wet fish
haddock.gif
. Whats happened is your're not in your gentoo, you're in the livecd. The livecd doesn't have merge. OK follow me:

1. Setup your net connection. Either by ifconfig and route or using the net-setup proggy you used all the way back at the beginning.

2. mount all your partitions i.e
Code:
mount /dev/hda3 /mnt/gentoo
mount /dev/hda1 /mnt/gentoo/boot
mount /dev/hda4 /mnt/gentoo/home
swapon /dev/hda2
mount -t proc proc /mnt/gentoo/proc

3 Chroot back into your gentoo system from the livecd
Code:
chroot /mnt/gentoo /bin/bash
env-update
source /etc/profile

4. Now you can emerge
 
Lovely, that appears to have done the trick as Grub is now emerging. :)

There was something a bit unusual, which I had to research, hence me being a bit slow. When I mounted the boot partition, it did mount but it was recommended to me that I run e2fsck due to it not unmounting cleanly last time or some such. I unmounted it again with /umount /dev/hda1, as it warned about running the check whilst mounted, the check was done and I used -fvp, and it seemed fine. I then mounted boot oncemore, and went onto the chroot part (having mounted everything else remaining first of course), and all was well. :)

Thanks very much for your help both of you, it's much appreciated. With luck, there won't be anymore problems now, other than me still being a Linux learner. :D
 
Last edited:
Originally posted by Deadly Ferret
Lovely, that appears to have done the trick as Grub is now emerging. :)

There was something a bit unusual, which I had to research, hence me being a bit slow. When I mounted the boot partition, it did mount but it was recommended to me that I run e2fsck due to it not unmounting cleanly last time or some such. I unmounted it again with /umount /dev/hda1, as it warned about running the check whilst mounted, the check was done and I used -fvp, and it seemed fine. I then mounted boot oncemore, and went onto the chroot part (having mounted everything else remaining first of course), and all was well. :)

Thanks very much for your help both of you, it's much appreciated. With luck, there won't be anymore problems now, other than me still being a Linux learner. :D
Good job mate :)
 
Grr, 29 hours since my last reboot and now I can get it to shutdown:(. I type
Code:
shutdown now -r
which I think is right, but I get the error:

init: /dev/initctl: no such file or directory

How am I going to reboot?
 
Oh ****. First I get:
Not found any [active partition] in HDD
DISK BOOT FAILURE , INSERT SYSTEM DISK AND PRESS ENTER.

I can boot off a floppy and get to grub, which then gives me error 2:confused:. Damn.
 
Originally posted by burns
Oh ****. First I get:
Not found any [active partition] in HDD
DISK BOOT FAILURE , INSERT SYSTEM DISK AND PRESS ENTER.

I can boot off a floppy and get to grub, which then gives me error 2:confused:. Damn.

dont know what that error message is, but did you remember to flag your boot partition as bootable in fdisk? because it sounds maybe like that.
 
I don't remember doing it, can a re-do the boot partition using fdisk without loosing my install?
//edit, this is what error 2 is supposed to mean aparently:
2 : "Selected disk doesn't exist"

This error is returned if the device part of a device- or full filename refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system.
 
give it a go. Boot up with the floppy or bootcd. When you're in the commandline type
Code:
fdisk /dev/hda
p
a
1
p
w
the first "p" should show you the partition table like so
Code:
Command (m for help): p

Disk /dev/hda: 120.0 GB, 120034123776 bytes
16 heads, 63 sectors/track, 232581 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          20       10048+  83  Linux
/dev/hda2              21        1013      500472   82  Linux swap
/dev/hda3            1014        4889     1953504   83  Linux
/dev/hda4            4890      232581   114756768   83  Linux
if the boot partition (hda1 in my case above) doesn't have a * on the boot column, then set it but typing "a" then selecting the partition "1" in my case. Finally write the changes by typing "w".
 
Also you didn't forget to do this part of the handbook right?
Code:
Code Listing 3: Installing GRUB in the MBR

grub> root (hd0,0)          (Specify where your /boot partition resides)
grub> setup (hd0)           (Install GRUB in the MBR)
grub> quit                  (Exit the GRUB shell)
 
Originally posted by Mpemba Effect
Also you didn't forget to do this part of the handbook right?
Code:
Code Listing 3: Installing GRUB in the MBR

grub> root (hd0,0)          (Specify where your /boot partition resides)
grub> setup (hd0)           (Install GRUB in the MBR)
grub> quit                  (Exit the GRUB shell)

No, I definatley did that, then set up the grub config file.
 
Okay, so I somehow managed to not set the boot flag, I must have not written the changes or somthing. Damn noobs:D. Rebooting now to see what happens. Cheers guys:).
 
Hmm, the disk is found by the BIOS now when it tries to boot, but I'm still getting error 2 from Grub. I'll boot off the cd and see if I can remember how to fing the grub config file.
 
Originally posted by burns
Hmm, the disk is found by the BIOS now when it tries to boot, but I'm still getting error 2 from Grub. I'll boot off the cd and see if I can remember how to fing the grub config file.

When you get back to the livecd commandline you can simple mount the boot partition and access it's contents without having to do the whole chrooting part.
 
H'okay, I have /boot/grub/grub.conf open in front of me and it says:
Code:
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.7-r11
root (hd0,0)
kernel /kernel-2.6.7-gentoo-r11 root=/dev/hda3 vga=788
 
Code:
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.7-r11
root (hd0,0)
kernel [B](hd0,0)/boot[/B]/kernel-2.6.7-gentoo-r11 root=/dev/hda3 vga=788

you missed a bit, see bold ^^^^^^^^^

i assume the name of that kernel is correct
 
Back
Top Bottom