doherty pete writes:

> when kernel start ,display this
>
> Your system seems to be missing critical device files
> in /dev ! Although you may be running udev or devfs,
> the root partition is missing these required files !
>
> To rectify this situation, please do the following:
> mkdir /mnt/fixit
> mount --bind / /mnt/fixit
> cp -a /dev/* /mnt/fixit/dev/
> umount /mnt/fixit
> rmdir /mnt/fixit
>
> You may refer to these instructions at /etc/issue.
> If you previously had an issue file, it has been
> backed up at /etc/issue.devfix. Once you've fixed
> your system, you will have to restore your old issue
> file in order to get rid of this warning.
>
> Thanks for using Gentoo !
> http://bugs.gentoo.org/show_bug.cgi?id=40987
>
>
> i have done:
> mkdir /mnt/fixit
> mount --bind / /mnt/fixit
> cp -a /dev/* /mnt/fixit/dev/
> umount /mnt/fixit
> rmdir /mnt/fixit

Strange.
I think when I had forgotten to create the necessary items in /dev, the
system did not even come up. It needs at least console and null, and for
framebuffer stuff also tty1. So I have these:

weird ~ # ls -l /mnt/dev/
insgesamt 0
crw------- 1 root tty 5, 1 10. Jun 2010 console
crw-rw-rw- 1 root root 1, 3 10. Jun 2010 null
crw------- 1 root tty 4, 1 10. Jun 2010 tty1

The bug report has this, maybe this is your problem, too?

I just ran into this and managed to fix it with an extra step. The
problem was in changed permissions on /dev/null. ls -l /dev/null
gave crw-rw-rw- 1 root root 1, ... while /mnt/fixit/dev/null gave
crw-r--r-- 1 root root 19, ... In order to fix it I had to rm
/mnt/fixit/dev/null first, and then cp -a /dev/null /mnt/fixit/dev/null
as suggested.
I can't say I understand how this happens but now the computer boots
again.


I'd prefer to have only those in /dev, and not all the other stuff that udev
adds, but it shouldn't harm either.

How does your /fixit/dev/ look like? Are there any entries at all? Is
console and null there? Please show the output of this:

ls -l /fixit/dev | wc -l
ls -l /fixit/dev/{console,null}

I get this:
weird ~ # ls -l /fixit/dev | wc -l
4
weird ~ # ls -l /fixit/dev/{console,null}
crw------- 1 root tty 5, 1 10. Jun 2010 /mnt/dev/console
crw-rw-rw- 1 root root 1, 3 10. Jun 2010 /mnt/dev/null

Wonko

doherty pete wrote:
when*kernel*start*,display*this




Your system seems to be missing critical device files
in /dev ! *Although you may be running udev or devfs,
the root partition is missing these required files !



To rectify this situation, please do the following:
mkdir /mnt/fixit
mount --bind / /mnt/fixit
cp -a /dev/* /mnt/fixit/dev/
umount /mnt/fixit
rmdir /mnt/fixit



You may refer to these instructions at /etc/issue.
If you previously had an issue file, it has been
backed up at /etc/issue.devfix. *Once you've fixed
your system, you will have to restore your old issue
file in order to get rid of this warning.



Thanks for using Gentoo !
http://bugs.gentoo.org/show_bug.cgi?id=40987






i*have*done:


mkdir /mnt/fixit
mount --bind / /mnt/fixit
cp -a /dev/* /mnt/fixit/dev/
umount /mnt/fixit
rmdir /mnt/fixit

--

pete_doherty





It looks like some files are missing in /dev but before /dev is mounted
as tmpfs.* This is what I would do to fix it.* Boot a bootable CD,
Knoppix, systemrescue or whatever.* Mount the root partition of
Gentoo.* Copy null and console over to the dev directory on the hard
drive.* If you mount like in the install guide, cp -v /dev/null
/mnt/gentoo/dev and repeat for console.* If you mount differently,
replace the needed parts.* ;-)



Keep in mind, when you first start to boot, /dev/ is not mounted like
it is after you get booted.* So, before udev gets started making the
needed files, the system needs null and console.* It seems there was a
third one that was needed but I'm not 100% sure. I always make sure to
copy those two when I do a install.* No problems so far.



Hope that helps.



Dale



:-)* :-)*

On 14 January 2011 13:41, Dale <rdalek1967@gmail.com> wrote:
> doherty pete wrote:
>
> when*kernel*start*,display*this
> Your system seems to be missing critical device files
> in /dev ! *Although you may be running udev or devfs,
> the root partition is missing these required files !
> To rectify this situation, please do the following:
> mkdir /mnt/fixit
> mount --bind / /mnt/fixit
> cp -a /dev/* /mnt/fixit/dev/
> umount /mnt/fixit
> rmdir /mnt/fixit
> You may refer to these instructions at /etc/issue.
> If you previously had an issue file, it has been
> backed up at /etc/issue.devfix. *Once you've fixed
> your system, you will have to restore your old issue
> file in order to get rid of this warning.
> Thanks for using Gentoo !
> http://bugs.gentoo.org/show_bug.cgi?id=40987
>
> i*have*done:
> mkdir /mnt/fixit
> mount --bind / /mnt/fixit
> cp -a /dev/* /mnt/fixit/dev/
> umount /mnt/fixit
> rmdir /mnt/fixit
> --
> pete_doherty
>
> It looks like some files are missing in /dev but before /dev is mounted as
> tmpfs.* This is what I would do to fix it.* Boot a bootable CD, Knoppix,
> systemrescue or whatever.* Mount the root partition of Gentoo.* Copy null
> and console over to the dev directory on the hard drive.* If you mount like
> in the install guide, cp -v /dev/null /mnt/gentoo/dev and repeat for
> console.* If you mount differently, replace the needed parts.* ;-)
>
> Keep in mind, when you first start to boot, /dev/ is not mounted like it is
> after you get booted.* So, before udev gets started making the needed files,
> the system needs null and console.* It seems there was a third one that was
> needed but I'm not 100% sure. I always make sure to copy those two when I do
> a install.* No problems so far.

This problem was created because Pete did not follow to the letter the
handbook, which advises to mount -o bind /dev /mnt/gentoo/dev, or if
he did, he did not untar the stage 3 fs properly, or if he used a
stage 4 tar file he did not create the necessary /dev files manually.

--
Regards,
Mick

i�did�not�follow�the�handbook,i�instal l�gentoo�with�ubuntubut�i�sure�i�use �the�commend:
sudo mount /dev/sda10 /media/gentoosudo mount -t proc none /media/gentoo/procsudo mount -o bind /dev/ /media/gentoo/dev

and stage�isstage3-i686-20101109.tar.bz2
ls -l /fixit/dev/{console,null}

crw------- 1 root tty �5, 1 10. Jun 2010 �/mnt/dev/console
crw-rw-rw- 1 root root 1, 3 10. Jun 2010 �/mnt/dev/null

i�have�the�same�result�
�
2011/1/14 Mick <michaelkintzios@gmail.com>

On 14 January 2011 13:41, Dale <rdalek1967@gmail.com> wrote:

> doherty pete wrote:

>

> when�kernel�start�,display�this

> Your system seems to be missing critical device files

> in /dev ! �Although you may be running udev or devfs,

> the root partition is missing these required files !

> To rectify this situation, please do the following:

> mkdir /mnt/fixit

> mount --bind / /mnt/fixit

> cp -a /dev/* /mnt/fixit/dev/

> umount /mnt/fixit

> rmdir /mnt/fixit

> You may refer to these instructions at /etc/issue.

> If you previously had an issue file, it has been

> backed up at /etc/issue.devfix. �Once you've fixed

> your system, you will have to restore your old issue

> file in order to get rid of this warning.

> Thanks for using Gentoo !

> http://bugs.gentoo.org/show_bug.cgi?id=40987

>

> i�have�done:

> mkdir /mnt/fixit

> mount --bind / /mnt/fixit

> cp -a /dev/* /mnt/fixit/dev/

> umount /mnt/fixit

> rmdir /mnt/fixit

> --

> pete_doherty

>

> It looks like some files are missing in /dev but before /dev is mounted as

> tmpfs.� This is what I would do to fix it.� Boot a bootable CD, Knoppix,

> systemrescue or whatever.� Mount the root partition of Gentoo.� Copy null

> and console over to the dev directory on the hard drive.� If you mount like

> in the install guide, cp -v /dev/null /mnt/gentoo/dev and repeat for

> console.� If you mount differently, replace the needed parts.� ;-)

>

> Keep in mind, when you first start to boot, /dev/ is not mounted like it is

> after you get booted.� So, before udev gets started making the needed files,

> the system needs null and console.� It seems there was a third one that was

> needed but I'm not 100% sure. I always make sure to copy those two when I do

> a install.� No problems so far.



This problem was created because Pete did not follow to the letter the

handbook, which advises to mount -o bind /dev /mnt/gentoo/dev, or if

he did, he did not untar the stage 3 fs properly, or if he used a

stage 4 tar file he did not create the necessary /dev files manually.



--

Regards,

Mick





--
pete_doherty

On Friday 14 January 2011 14:47:41 doherty pete wrote:
> i did not follow the handbook,i install gentoo with ubuntu
> but i sure i use the commend:
>
> sudo mount /dev/sda10 /media/gentoo
> sudo mount -t proc none /media/gentoo/proc
> sudo mount -o bind /dev/ /media/gentoo/dev

Instead try exactly as typed in handbook:
sudo mount -o bind /dev /media/gentoo/dev

no trailing slash after /dev

> and stage is
> stage3-i686-20101109.tar.bz2
>
> ls -l /fixit/dev/{console,null}
> crw------- 1 root tty 5, 1 10. Jun 2010 /mnt/dev/console
> crw-rw-rw- 1 root root 1, 3 10. Jun 2010 /mnt/dev/null

This is correct.

--
Regards,
Mick

i*tried,but*it*no*effect.

2011/1/15 Mick <michaelkintzios@gmail.com>

On Friday 14 January 2011 14:47:41 doherty pete wrote:

> i did not follow the handbook,i install gentoo with ubuntu

> but i sure i use the commend:

>

> sudo mount /dev/sda10 /media/gentoo

> sudo mount -t proc none /media/gentoo/proc

> sudo mount -o bind /dev/ /media/gentoo/dev



Instead try exactly as typed in handbook:

sudo mount -o bind /dev /media/gentoo/dev



no trailing slash after /dev



> and stage is

> stage3-i686-20101109.tar.bz2

>

> ls -l /fixit/dev/{console,null}

> crw------- 1 root tty *5, 1 10. Jun 2010 */mnt/dev/console

> crw-rw-rw- 1 root root 1, 3 10. Jun 2010 */mnt/dev/null



This is correct.



--

Regards,

Mick



--
pete_doherty

On Saturday 15 January 2011 11:09:46 doherty pete wrote:
> i tried,but it no effect.

Pete, the fact that you are using Ubuntu or any other Linux OS or LiveCD to
install Gentoo would not cause the problem you are describing. Such a problem
is related to the *correct* mounting of /mnt/gentoo, /proc and /dev before
you chroot.

To avoid typing errors it is best that you cut and paste commands from the
Gentoo Installation Handbook and only edit any parameters that relate to your
partitions.
--
Regards,
Mick

> ls -l /fixit/dev/{console,null}
> crw------- 1 root tty 5, 1 10. Jun 2010 /mnt/dev/console
> crw-rw-rw- 1 root root 1, 3 10. Jun 2010 /mnt/dev/null

Eh? You list /fixit/dev and get files in /mnt/dev, did you symlink
/fixit to /mnt?

I would have expected

ls -l /fixit/dev/{console,null}
crw------- 1 root root 5, 1 Jun 26 2010 /fixit/dev/console
crw-rw-rw- 1 root root 1, 3 Jun 26 2010 /fixit/dev/null


The warning message is stored in /etc/issue I believe. The gentoo init
scripts, put it there if /dev/null or /dev/console don't exist.

Once you are sure that that /dev/null and /dev/console are on your root
partition, you should find the original in /etc/issue.devfix, mine looks
like:
"

This is
.O (s m
)

"

swap this with /etc/issue and reboot.

so,i*don't*known*what*problem,but*swap*issue*and*i ssue.devfix,and*there*no*warning*...
2011/1/15 Ian Lee <ian@leehouse.eclipse.co.uk>



> ls -l /fixit/dev/{console,null}

> crw------- 1 root tty *5, 1 10. Jun 2010 */mnt/dev/console

> crw-rw-rw- 1 root root 1, 3 10. Jun 2010 */mnt/dev/null



Eh? You list /fixit/dev and get files in /mnt/dev, did you symlink

/fixit *to /mnt?



I would have expected



ls -l /fixit/dev/{console,null}

crw------- 1 root root 5, 1 Jun 26 *2010 /fixit/dev/console

crw-rw-rw- 1 root root 1, 3 Jun 26 *2010 /fixit/dev/null





The warning message is stored in /etc/issue I believe. The gentoo init

scripts, put it there if /dev/null or /dev/console don't exist.



Once you are sure that that /dev/null and /dev/console are on your root

partition, you should find the original in /etc/issue.devfix, mine looks

like:

"



This is
.O (s m
)



"



swap this with /etc/issue and reboot.









--
pete_doherty

On 2011-01-14, Mick <michaelkintzios@gmail.com> wrote:
> On 14 January 2011 13:41, Dale <rdalek1967@gmail.com> wrote:
>> doherty pete wrote:
>>
>> when?kernel?start?,display?this
>> Your system seems to be missing critical device files
>> in /dev ! ?Although you may be running udev or devfs,
>> the root partition is missing these required files !
>> To rectify this situation, please do the following:
>> mkdir /mnt/fixit
...

> This problem was created because Pete did not follow to the letter
> the handbook, which advises to mount -o bind /dev /mnt/gentoo/dev, or
> if he did, he did not untar the stage 3 fs properly, or if he used a
> stage 4 tar file he did not create the necessary /dev files manually.

When I had the /mnt/fixit problem a couple years ago, it was indeed
because I had accidentally skipped a step in the install process. I
won't swear 100% that it was the "mount -o bind /dev /mnt/gentoo/dev"
step, but that does sound familiar.