[gentoo-user] Install issue

[gentoo-user] Install issue

[Colleen Beamer]

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

Hi,

I've been trying to update my gentoo system for a couple of months and
couldn't seem to resolve block issues.  Since it has been a couple of years
or more since i did a fresh install, I decided to do one.

I followed the handbook - 1st run, I screwed up and missed a step, 2nd run,
I was careful that I didn't miss anything and I couldn't boot, the 3rd time
I rechecked everything and the same issue arose.

I am able to get my boot menu, the drivers appear to load - the last one
being tg3 which is the one that was typically loaded last on my old gentoo
install.  However, after this I get this message:

ERROR: your real /dev is missing files required to boot (console and null)..

When I was in the chroot'd environment and after I had done the 'mount
--rbind /dev ....' command, I checked and there appeared to be a console
file there.  This is just and fyi

Anyway, I did a google search and this was one of the responses:

Some "stage3" archives lack few items (like /dev/console and /dev/null)
necessary for boot.
To fix your installation, you need to:
- mount your gentoo root device in read/write mode (for example to
/mnt/gentoo)
- create missing pseudo-files (something like the following):
mknod /mnt/gentoo/dev/console c 5 1
mknod /mnt/gentoo/dev/null c 1 3
- unmount your gentoo root device or execute "sync" command
- reboot

Since I am a "chicken-shit", I am deferring to the more knowledgeable people
on this list and asking, is this a valid fix or is there a better one.

Thanks in advance for your help.

Regards,

Colleen

[-- Attachment #2: Type: text/html, Size: 1920 bytes --]

Re: [gentoo-user] Install issue

[Alan McKinnon]

Apparently, though unproven, at 22:35 on Sunday 29 May 2011, Colleen Beamer 
did opine thusly:

> Hi,
> 
> I've been trying to update my gentoo system for a couple of months and
> couldn't seem to resolve block issues.  Since it has been a couple of years
> or more since i did a fresh install, I decided to do one.
> 
> I followed the handbook - 1st run, I screwed up and missed a step, 2nd run,
> I was careful that I didn't miss anything and I couldn't boot, the 3rd time
> I rechecked everything and the same issue arose.
> 
> I am able to get my boot menu, the drivers appear to load - the last one
> being tg3 which is the one that was typically loaded last on my old gentoo
> install.  However, after this I get this message:
> 
> ERROR: your real /dev is missing files required to boot (console and
> null)..
> 
> When I was in the chroot'd environment and after I had done the 'mount
> --rbind /dev ....' command, I checked and there appeared to be a console
> file there.  This is just and fyi
> 
> Anyway, I did a google search and this was one of the responses:
> 
> Some "stage3" archives lack few items (like /dev/console and /dev/null)
> necessary for boot.
> To fix your installation, you need to:
> - mount your gentoo root device in read/write mode (for example to
> /mnt/gentoo)
> - create missing pseudo-files (something like the following):
> mknod /mnt/gentoo/dev/console c 5 1
> mknod /mnt/gentoo/dev/null c 1 3
> - unmount your gentoo root device or execute "sync" command
> - reboot
> 
> Since I am a "chicken-shit", I am deferring to the more knowledgeable
> people on this list and asking, is this a valid fix or is there a better
> one.

Google is correct, just do it. All you are doing is making files somewhere 
that have special characteristics (i.e. you are not unleashing Armageddon or 
looking Medusa in the eye)

But you looked in the wrong place. null and console must be in /dev on the 
root partition *before* mounting /dev, you looked after. The reason it must be 
there before is that null and console are needed very early in the boot 
process at a point before udev runs. After udev runs it is no longer relevant 
as udev will provide those nodes.

I wonder if you haven't just tripped over a bug in baselayout or recent 
stage3's. I just did a new install here but used an old stage3 that was still 
baselayout-1. I did not run into the issues you did. What does b.g.o. say?


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Install issue

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2902 bytes --]

On Sunday 29 May 2011 21:57:21 Alan McKinnon wrote:
> Apparently, though unproven, at 22:35 on Sunday 29 May 2011, Colleen Beamer
> 
> did opine thusly:
> > Hi,
> > 
> > I've been trying to update my gentoo system for a couple of months and
> > couldn't seem to resolve block issues.  Since it has been a couple of
> > years or more since i did a fresh install, I decided to do one.
> > 
> > I followed the handbook - 1st run, I screwed up and missed a step, 2nd
> > run, I was careful that I didn't miss anything and I couldn't boot, the
> > 3rd time I rechecked everything and the same issue arose.
> > 
> > I am able to get my boot menu, the drivers appear to load - the last one
> > being tg3 which is the one that was typically loaded last on my old
> > gentoo install.  However, after this I get this message:
> > 
> > ERROR: your real /dev is missing files required to boot (console and
> > null)..
> > 
> > When I was in the chroot'd environment and after I had done the 'mount
> > --rbind /dev ....' command, I checked and there appeared to be a console
> > file there.  This is just and fyi
> > 
> > Anyway, I did a google search and this was one of the responses:
> > 
> > Some "stage3" archives lack few items (like /dev/console and /dev/null)
> > necessary for boot.
> > To fix your installation, you need to:
> > - mount your gentoo root device in read/write mode (for example to
> > /mnt/gentoo)
> > - create missing pseudo-files (something like the following):
> > mknod /mnt/gentoo/dev/console c 5 1
> > mknod /mnt/gentoo/dev/null c 1 3
> > - unmount your gentoo root device or execute "sync" command
> > - reboot
> > 
> > Since I am a "chicken-shit", I am deferring to the more knowledgeable
> > people on this list and asking, is this a valid fix or is there a better
> > one.
> 
> Google is correct, just do it. All you are doing is making files somewhere
> that have special characteristics (i.e. you are not unleashing Armageddon
> or looking Medusa in the eye)
> 
> But you looked in the wrong place. null and console must be in /dev on the
> root partition *before* mounting /dev, you looked after. The reason it must
> be there before is that null and console are needed very early in the boot
> process at a point before udev runs. After udev runs it is no longer
> relevant as udev will provide those nodes.
> 
> I wonder if you haven't just tripped over a bug in baselayout or recent
> stage3's. I just did a new install here but used an old stage3 that was
> still baselayout-1. I did not run into the issues you did. What does
> b.g.o. say?

I'm sure that I've come across the same problem some time in the distant past 
and had to create these two nodes manually.

However, it should be easy to prove if this is a bug or not - look in the 
stage3 tar file for /dev/console and /dev/null?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Install issue

[Alan McKinnon]

Apparently, though unproven, at 23:56 on Sunday 29 May 2011, Mick did opine 
thusly:

> > I wonder if you haven't just tripped over a bug in baselayout or recent
> > stage3's. I just did a new install here but used an old stage3 that was
> > still baselayout-1. I did not run into the issues you did. What does
> > b.g.o. say?
> 
> I'm sure that I've come across the same problem some time in the distant
> past  and had to create these two nodes manually.
> 
> However, it should be easy to prove if this is a bug or not - look in the 
> stage3 tar file for /dev/console and /dev/null?

True enough recent stage 3 tarballs for amd64 on my mirror are either faulty 
or do not contain /dev/console.

May 20 and 26 are faulty

April 28 is OK

Colleen, you should follow the tip you found on Google to fix this. What stage 
3 did you download and use?



-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Install issue

[Colleen Beamer]

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

On Sun, May 29, 2011 at 6:11 PM, Alan McKinnon <alan.mckinnon@gmail.com>wrote:

> Apparently, though unproven, at 23:56 on Sunday 29 May 2011, Mick did opine
> thusly:
>
> > > I wonder if you haven't just tripped over a bug in baselayout or recent
> > > stage3's. I just did a new install here but used an old stage3 that was
> > > still baselayout-1. I did not run into the issues you did. What does
> > > b.g.o. say?
> >
> > I'm sure that I've come across the same problem some time in the distant
> > past  and had to create these two nodes manually.
> >
> > However, it should be easy to prove if this is a bug or not - look in the
> > stage3 tar file for /dev/console and /dev/null?
>
> True enough recent stage 3 tarballs for amd64 on my mirror are either
> faulty
> or do not contain /dev/console.
>
> May 20 and 26 are faulty
>
> April 28 is OK
>
> Colleen, you should follow the tip you found on Google to fix this. What
> stage
> 3 did you download and use?
>

Actually, I used the most recent one - I think May 26th,  However, my first
install (that I screwed up on was the May 25th one, but I got the same
message.  Don't know if it makes a difference, but I used a tarball for x86.

Think I'll try the fix that I found on google first before attempting to
find a stage 3 tarball that is not faulty.

BTW, I can't recall from previous installs when I'm supposed to do this, but
I thought that baselayout got emerged somewhere during the install prior to
rebooting.  There was no place in the handbook that mentioned installing
baselayout ...... and yes, I did read the news item about baselayout2 and
openrc migration.

Regards,

Colleen



>
>
>
> --
> alan dot mckinnon at gmail dot com
>
>

[-- Attachment #2: Type: text/html, Size: 2425 bytes --]

Re: [gentoo-user] Install issue

[Alan McKinnon]

Apparently, though unproven, at 01:09 on Monday 30 May 2011, Colleen Beamer 
did opine thusly:

> > Colleen, you should follow the tip you found on Google to fix this. What
> > stage
> > 3 did you download and use?
> 
> Actually, I used the most recent one - I think May 26th,  However, my first
> install (that I screwed up on was the May 25th one, but I got the same
> message.  Don't know if it makes a difference, but I used a tarball for
> x86.

I'm not sure how the stages are built. it might be a hand-crafted list of 
stuffs, or maybe it's a script that builds the (mostly) same thing for each 
arch.

I reckon the latter, in which case x86 and amd64 will probably give similar 
results.

> Think I'll try the fix that I found on google first before attempting to
> find a stage 3 tarball that is not faulty.

The google fix will work. Really, trust me, I'm a sysadmin :-)

It's just a missing file that the install process should have made. You simply 
need to make it manually.

> BTW, I can't recall from previous installs when I'm supposed to do this,
> but I thought that baselayout got emerged somewhere during the install
> prior to rebooting.  There was no place in the handbook that mentioned
> installing baselayout ...... and yes, I did read the news item about
> baselayout2 and openrc migration.

The initial stage contains baselayout already, it's one of those things that 
is absolutely needed for a gentoo system to even exist at all. All a stage 
really is, is a large archive of an actual install with all it's various bits 
- files, dirs, and the matching entries in portage's database of things 
installed.

OK, it's not really built like that but the analogy will suffice. The end 
result is the same and portage cannot tell the difference between baselayout 
coming out of the stage and you installing it yourself.

The only time you install baselayout during an install is when you update 
world and there's a newer baselayout available than the one in the stage. 
That's true for almost every package in portage (except kernel sources, those 
are special)


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Install issue

[James Wall]

[-- Attachment #1: Type: text/plain, Size: 156 bytes --]

I have had that particular problem if I mounted /dev before extracting the
stage3 tarball. Just follow those instructions and you sill be fine.

James Wall

[-- Attachment #2: Type: text/html, Size: 169 bytes --]

Re: [gentoo-user] Install issue

[Colleen Beamer]

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

On Mon, May 30, 2011 at 9:47 AM, James Wall <wallservices@gmail.com> wrote:

> I have had that particular problem if I mounted /dev before extracting the
> stage3 tarball. Just follow those instructions and you sill be fine.
>
> James Wall
>
I tried doing the steps that I found in my google search as previously
posted.  It somewhat resolved the problem, but I still got error messages.
Since I was tired at this point, I gave up.

This morning, I tried what was suggested and used an earlier stage 3 tarball
(Apr. 24th, I believe it was).  This solved the problem and I was able to
boot.  Must have been an issue with the stage 3 tarball I had previously
tried.

Thanks for the help and comments, everyone!

Regards,

Colleen

[-- Attachment #2: Type: text/html, Size: 1100 bytes --]

Re: [gentoo-user] Install issue

[William Hubbs]

[-- Attachment #1: Type: text/plain, Size: 133 bytes --]

Hi all,

this issue is being worked currently. The bug you want to follow is
http://bugs.gentoo.org/show_bug.cgi?id=368597

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Install issue

[Alan McKinnon]

Apparently, though unproven, at 19:22 on Monday 30 May 2011, Colleen Beamer 
did opine thusly:

> On Mon, May 30, 2011 at 9:47 AM, James Wall <wallservices@gmail.com> wrote:
> > I have had that particular problem if I mounted /dev before extracting
> > the stage3 tarball. Just follow those instructions and you sill be fine.
> > 
> > James Wall
> 
> I tried doing the steps that I found in my google search as previously
> posted.  It somewhat resolved the problem, but I still got error messages.
> Since I was tired at this point, I gave up.
> 
> This morning, I tried what was suggested and used an earlier stage 3
> tarball (Apr. 24th, I believe it was).  This solved the problem and I was
> able to boot.  Must have been an issue with the stage 3 tarball I had
> previously tried.
> 
> Thanks for the help and comments, everyone!

If you are interested in that kind of thing, the full detail of what the 
problem is can be found here:

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



-- 
alan dot mckinnon at gmail dot com