Gentoo failed to start

satimis · 08-31-2006, 11:08 AM

Hi folks,

New installation - Gentoo amd64
Guide:- Gentoo Linux AMD64 Handbook
http://www.gentoo.org/doc/en/handboo...book-amd64.xml

Kernel - linux-2.6.17-gentoo-r7

# fdisk -l

Code:

/dev/hda1 * 83 System (for /boot)
/dev/hda2   83 Linux (for /)
/dev/hda3   82 swap
/dev/hda4   8e Linux LVM (for /usr /home /var /opt /tmp)

/vg/usr
/vg/home
/vg/var
/vg/opt
/vg/tmp

Installation went through quite smoothly except following problems found:-

1)
# USE="-doc symlink" emerge gentoo-sources

Code:

.....
......
 * GNU info directory index is up-to-date.
 * IMPORTANT: 7 config files in /etc need updating.
 * Type emerge --help config to learn how to update config files.

# find /etc -iname '._cfg????_*'
No printout. Can't find the config files to be updated.

2)
# grep -v rootfs /proc/mounts > /etc/mtab
-
cursor hanging there

# grub install /dev/hda

Code:

df: Warning: cannot read table of mounted filesystems
df: Warning: cannot read table of mounted filesystems
Could not find device for /boot: Not found or not a block device.

3)
/boot/grub/grub.conf

Code:

default 0
timeout 30

title=Gentoo linux 2.6.17.-r7
root (hd0,0)
kernel /boot/kernel-2.6.17-gentoo-r7 root=/dev/hda2

Should I put (hd0,1) for my case? I followed the sample in the guide book.

4)
# cat /etc/fstab

Code:

# <fs>			<mountpoint>	<type>		<opts>		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/BOOT		/boot		ext2		noauto,noatime	1 2
/dev/ROOT		/		ext3		noatime		0 1
/dev/SWAP		none		swap		sw		0 0
/dev/cdroms/cdrom0	/mnt/cdrom	iso9660		noauto,ro	0 0
#/dev/fd0		/mnt/floppy	auto		noauto		0 0

# NOTE: The next line is critical for boot!
proc			/proc		proc		defaults	0 0

shm			/dev/shm	tmpfs		nodev,nosuid,noexec	0 0

On reboot only a black screen displayed. Please advise how to fix the problem. TIA

B.R.
satimis

gruven · 08-31-2006, 03:37 PM

You didn't edit your fstab correctly. I suggest reading the gentoo documentation again to edit the fstab to fit your filesystem.

satimis · 08-31-2006, 09:04 PM

Hi gruven,

Quote:

You didn't edit your fstab correctly.

Noted with tks.

I major problem is unable to boot.

B.R.
satimis

gasparov · 09-01-2006, 04:40 PM

A question: what version of gentoo install cd did you use?Did you notice the gcc nasty update?

1)etc-update gived no joy?

My suggestion is to retry chrooting with the live cd and repeating the grub installation as the manual says.

satimis · 09-01-2006, 06:59 PM

Hi gasparov,

Quote:

A question: what version of gentoo install cd did you use? Did you notice the gcc nasty update?

I think the latest version "install-amd64-2006.0". I did not notice "gcc nasty update"

Quote:

1)etc-update gived no joy?

IIRC I did not ran it.

Quote:

My suggestion is to retry chrooting with the live cd and repeating the grub installation as the manual says.

Now I manage to have grub started;

Code:

root (hd0,0)
Filesystem type is ext2fs  Partition type 0x83
kernel (hd0,0)/boot/kernel-2.6.17-gentoo-r7 root=/dev/hda2
Error 15:File not found.
Press any key to contiue

Ran
# ls -l /mnt/gentoo/boot

Code:

boot -> .
grub
lost+found

The kernel image was not there.

I completed all steps listed on the respective handbook at least in 2 rounds. I found;
# ls -l /usr/src/linux

Code:

lrwxrwxrwx    1 root   root    12 Oct 13 11:04 /usr/src/linux -> linux-2.6.17-gentoo-r7

there. But now it disppears. I don't know why? Even I can't find the directory "src" after re-chroot. Another directory I failed to find was "modules". I ran;

# find / -name src -type d
and
# find / -name modules -type d
Both no printout

and could not find it. Beside after re-entering chroot environment the command "env-update", emerge, etc. were not found on "bash". I discovered this problem at least in the last 3 rounds

I think I have to run another round again wiping out the complete HD.

Tks.

B.R.
satimis

serverjunkie · 09-02-2006, 03:51 AM

Quote:

Now I manage to have grub started;
Code:
root (hd0,0)
Filesystem type is ext2fs Partition type 0x83
kernel (hd0,0)/boot/kernel-2.6.17-gentoo-r7 root=/dev/hda2
Error 15:File not found.
Press any key to contiue

remove kernel from /boot/kernel-2.6.17-gentoo-r7 so it comes as

Code:

/boot/2.6.17-gentoo-r7

and if that doesnt work re-copy your kernel to /boot as 2.6.17-gentoo-r7

hope this helps as I had the same problem

gasparov · 09-02-2006, 07:27 AM

Hi,
the latest version is 2006.1 not 2006.0,that's way I asked.I don't remember well the gentoo installation procedure but maybe that could be the problem.It was a big change from 2006.0 to 2006.1 ,gcc3 to gcc4 and a glibc update.I had to rebuild the toolchain a couple of time and it's 24 hours I'm rebuilding the world.
For example it could be that you downloaded the 2006.0 base tarball then you did emerge --sync and everything is broken.
New baselayout breaks things if you don't do etc-update and you didn't,new gcc4 breaks things if you don't do the proper upgrade procedure.
Even if it is not the problem IMHO is not smart installing with 2006.0 medium knowing that you'll have to spend hours compiling just for upgrading....and your are also following thw wrong handbook.

satimis · 09-02-2006, 07:54 AM

Hi serverjunkie,

My problme is no kernel image on /boot

# ls -l /boot

Code:

boot -> .
grub
lost+found

It is impossible to re-run some steps on re-chroot. Because after re-chroot I failed to find following command;
env-update
emerge

Alwasy displaying;
-/bin/bash : env-update: command not found

Also I cna't find "src", "modules"

satimis

serverjunkie · 09-03-2006, 01:16 AM

all you need to do is put the live cd back in and re-mount your /boot and / on /mnt/gentoo/boot and /mnt/gentoo then follow the instuctions in the handbook about copying the kernel image into /boot (i cant remember)

Hope this helps

satimis · 09-03-2006, 09:09 AM

Hi serverjunkie,

Tks for your advice.

I tried dozen times. Once exiting chroot and re-chroot again bash command such as env-update, emerge can't be found. Even the directories "src", "modules" etc. got lost. I can't find out the cause/reason. The only way is to wipe out the HD and start from the beginning again.

I already started another round, running "install-amd64-minimal-2006.1", the lastest version. However I encountered problem on connecting network "broadband". I'll start a new posting.

B.R.
satimis