Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Problem with booting: ERROR: urandom failed to star
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Fri Jan 04, 2013 9:27 pm    Post subject: [SOLVED] Problem with booting: ERROR: urandom failed to star Reply with quote

Hi All,

I have encountered a boot problem, that I can't solve. So far I have been able to solve problems after migrating from virtualmachine Gentoo installation to physical installation, thanks to great posts seen here at Gentoo forums.

Problem is that boot sequence goes quite far, until it stops in "ERROR: urandom failed to start" message. I can restart computer in this state with three-finger-salute and through SysRq, but I can't do anything else (interactive boot does not help with this).
I tried to set parallel="yes" in rc.conf, but that didn't help things, it still stops booting in same phase.

I think problem is related to udev and devfs, because in logs I get errors about /dev/console not being there, tty's not available, etc (See Ref2 below).

What I have done:

    * Copied a good virtualmachine installation to another host's physical harddisk partition
    * Modified configurations, recompiled kernel, etc basic stuff (from LiveCD chroot)
    * Emerged into deep updated world and got into trouble there (see Ref1 below)
    * Fixed troubles of the new world installation by changing profile to no-multilib
    * Then emerging deeply into this no-multilib world, which seemed to roll great, but then I got this problem in reboot...


I did make necessary env-update, source /etc/profile, revdep-rebuilds, etc, but I didn't remember to run selinux setfiles and rlpkg commands... so could SELinux inconsistency cause this? I also didn't do emerge --depclean (forgot :oops: ).

I also already earlier fixed kernel option about DEVFS, which caused boot problems earlier:
Code:

cat .config | grep DEVTMP
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y


sysinit links are there:
Code:

/etc/runlevels/sysinit# ls -la
total 8
drwxr-xr-x 2 root root 4096 2012-12-28 03:03 ./
drwxr-xr-x 6 root root 4096 2012-01-05 06:45 ../
lrwxrwxrwx 1 root root   17 2012-01-12 12:27 devfs -> /etc/init.d/devfs
lrwxrwxrwx 1 root root   17 2012-01-12 12:27 dmesg -> /etc/init.d/dmesg
lrwxrwxrwx 1 root root   17 2012-12-28 03:03 sysfs -> /etc/init.d/sysfs
lrwxrwxrwx 1 root root   16 2012-01-12 12:27 udev -> /etc/init.d/udev
lrwxrwxrwx 1 root root   22 2012-12-25 18:17 udev-mount -> /etc/init.d/udev-mount


I checked that I don't have SYSFS_DEPRECATED set:
Code:

# cat .config | grep DEPRECATED | grep SYSFS
# CONFIG_SYSFS_DEPRECATED is not set


In one point I modified booting so that it doesn't scramble my root password in every boot. I don't know if this "feature" came from emerging world from chrooted LiveCD env or where, but it didn't exist originally. Could there be some other elements from LiveCD laying around, that even might cause this problem? I never intentionally installed anything related to LiveCD.

I also recompiled kernel without CONFIG_GRKERNSEC_KMEM option if it could help, though it should not affect this, but it was on todo list anyway to get lm_sensors to work with /dev/port.

Sorry that I can't get you my emerge info at the moment[/code].

Ref1: Trouble I ended up was following:
Because I couldn't login into real system after transferring system to physical partition (as it didn't boot correctly), I had to use LiveCD and chroot into physical installation.
Executing emerge world from there (or something else) created another make.profile -link to /etc, while I already had a working make.profile link at /etc/portage. I noticed this way too late, as emerging world had used wrong profile (non-hardened - because of LiveCD?) to update software. So I ended up with wrong environment's software and toolchain was wrong too.
I tried many tricks to fix this, and got it rolling after installing hardened binary packages of toolchain and reinstalling after changing to a new profile (I couldn't get it working without changing profile). But key issue was to find out there was this another profile link to wrong profile.

So I think this boot problem might also come from those messes in Ref1 and change to no-multilib profile.

Ref2: This got me to thinking there is trouble with udev or/and missing devices:
Code:
Jan  4 13:40:11 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:11 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:11 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:11 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:11 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:11 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:21 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:21 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:21 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:21 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:21 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:21 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:31 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:31 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:31 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:31 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:31 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:31 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:41 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:41 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:41 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:41 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:41 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:41 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:52 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:52 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:52 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:52 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:52 hostname init: open(/dev/console): No such file or directory
Jan  4 13:40:52 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:02 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:02 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:02 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:02 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:02 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:02 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:06 hostname init: open(/dev/console): No such file or directory
Jan  4 13:41:06 hostname shutdown[3834]: shutting down for system reboot
Jan  4 13:41:06 hostname init: Switching to runlevel: 6
Jan  4 13:41:07 hostname ntpd[3257]: ntpd exiting on signal 15
Jan  4 13:41:09 hostname auditd[2432]: The audit daemon is exiting.
Jan  4 13:41:09 hostname syslog-ng[2946]: Termination requested via signal, terminating;
Jan  4 13:41:09 hostname syslog-ng[2946]: syslog-ng shutting down; version='3.2.5'



here's some bg material:
Rc log:
Code:
rc boot logging started at Fri Jan  4 13:39:45 2013

 * Setting system clock using the hardware clock [UTC] ...
 [ ok ]                                                   
 * Loading module vboxvideo ...                           
 * Failed to load vboxvideo                               
 [ !! ]                                                   
 * Autoloaded 0 module(s)                                 
 * Starting up RAID devices ...                           
mdadm: No arrays found in config file or automatically   
 [ !! ]                                                   
 * Setting up the Logical Volume Manager ...             
  No volume groups found                                 
  No volume groups found                                 
  No volume groups found                                 
 [ ok ]                                                   
 [ ok ]                                                   
 * Checking local filesystems  ...                       
LINUX_GENTOO: clean, 703109/1428000 files, 5014494/5711990 blocks
/dev/sde1: clean, 671590/3276800 files, 11488618/13107200 blocks
PRODUCTION: clean, 935827/16384000 files, 60062618/65535984 blocks
/dev/sdc1: clean, 569206/12210528 files, 9575880/12209392 blocks 
/dev/sdc3: clean, 36145/24421056 files, 11502860/24416791 blocks 
PRODUCTION: clean, 2786/11976704 files, 1684748/23932833 blocks (check in 4 mounts)
 [ ok ]                                                                           
 * Remounting root filesystem read/write ...                                       
 [ ok ]                                                                           
 * Remounting filesystems ...                                                     
 [ ok ]                                                                           
 * Updating /etc/mtab ...                                                         
 [ ok ]                                                                           
 * Activating swap devices ...                                                     
 [ ok ]                                                                           
 * Mounting local filesystems ...                                                 
Mount is denied because the NTFS volume is already exclusively opened.             
The volume may be already mounted, or another software may use it which           
could be identified for example by the help of the 'fuser' command.               
 * Some local filesystem failed to mount                                           
 [ !! ]                                                                           
 * Configuring kernel parameters ...                                               
 [ ok ]                                                                           
 * Creating user login records ...                                                 
 [ ok ]                                                                           
 * Cleaning /var/run ...                                                           
 [ ok ]                                                                           
 * Wiping /tmp directory ...                                                       
 [ ok ]                                                                           
 * Restoring Mixer Levels ...                                                     
alsactl: load_state:1713: Cannot find soundcard '0'...                             
 * Errors while restoring defaults, ignoring                                       
alsactl: load_state:1713: Cannot find soundcard '1'...
 * Errors while restoring defaults, ignoring
 [ ok ]
 * Starting auditd ...
 [ ok ]
touch: cannot touch '/var/lock/subsys/auditd': No such file or directory
 * Loading audit rules from /etc/audit/audit.rules
 * Setting hostname to hostname ...
 [ ok ]
 * Setting terminal encoding [UTF-8] ...
 [ ok ]
 * Setting keyboard mode [UTF-8] ...
Couldn't open /dev/tty1
Couldn't open /dev/tty2
Couldn't open /dev/tty3
Couldn't open /dev/tty4
Couldn't open /dev/tty5
Couldn't open /dev/tty6
Couldn't open /dev/tty7
Couldn't open /dev/tty8
Couldn't open /dev/tty9
Couldn't open /dev/tty10
Couldn't open /dev/tty11
Couldn't open /dev/tty12
 [ ok ]
 * Loading key mappings [fi-latin1] ...
 [ ok ]
 * Bringing up interface lo
 *   127.0.0.1/8 ...
 [ ok ]
 *   Adding routes
 *     127.0.0.0/8 via 127.0.0.1 ...
 [ ok ]
 * Bringing up interface eth0
 *   Starting netplug on eth0 ...
 [ ok ]
 *     Backgrounding ...
 * WARNING: net.eth0 has started, but is inactive
 * Starting mdadm monitor ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Activating additional swap space ...
 [ ok ]
 * setting up tmpfiles.d entries ...
 [ ok ]
 * ERROR: urandom failed to start

rc boot logging stopped at Fri Jan  4 13:40:07 2013



Kernel's GRKERNSEC configs:
Code:

CONFIG_GRKERNSEC=y                                                                                                                                                                                                                     
# CONFIG_GRKERNSEC_CONFIG_AUTO is not set                                                                                                                                                                                               
CONFIG_GRKERNSEC_CONFIG_CUSTOM=y                                                                                                                                                                                                       
CONFIG_GRKERNSEC_PROC_GID=102                                                                                                                                                                                                           
CONFIG_GRKERNSEC_SYMLINKOWN_GID=81                                                                                                                                                                                                     
# CONFIG_GRKERNSEC_KMEM is not set                                                                                                                                                                                                     
# CONFIG_GRKERNSEC_IO is not set                                                                                                                                                                                                       
CONFIG_GRKERNSEC_PROC_MEMMAP=y                                                                                                                                                                                                         
CONFIG_GRKERNSEC_BRUTE=y                                                                                                                                                                                                               
CONFIG_GRKERNSEC_MODHARDEN=y                                                                                                                                                                                                           
CONFIG_GRKERNSEC_HIDESYM=y                                                                                                                                                                                                             
CONFIG_GRKERNSEC_KERN_LOCKOUT=y                                                                                                                                                                                                         
# CONFIG_GRKERNSEC_NO_RBAC is not set                                                                                                                                                                                                   
CONFIG_GRKERNSEC_ACL_HIDEKERN=y                                                                                                                                                                                                         
CONFIG_GRKERNSEC_ACL_MAXTRIES=3                                                                                                                                                                                                         
CONFIG_GRKERNSEC_ACL_TIMEOUT=30                                                                                                                                                                                                         
CONFIG_GRKERNSEC_PROC=y                                                                                                                                                                                                                 
# CONFIG_GRKERNSEC_PROC_USER is not set                                                                                                                                                                                                 
CONFIG_GRKERNSEC_PROC_USERGROUP=y                                                                                                                                                                                                       
CONFIG_GRKERNSEC_PROC_ADD=y
CONFIG_GRKERNSEC_LINK=y
CONFIG_GRKERNSEC_SYMLINKOWN=y
CONFIG_GRKERNSEC_FIFO=y
# CONFIG_GRKERNSEC_SYSFS_RESTRICT is not set
# CONFIG_GRKERNSEC_ROFS is not set
CONFIG_GRKERNSEC_CHROOT=y
CONFIG_GRKERNSEC_CHROOT_MOUNT=y
CONFIG_GRKERNSEC_CHROOT_DOUBLE=y
CONFIG_GRKERNSEC_CHROOT_PIVOT=y
CONFIG_GRKERNSEC_CHROOT_CHDIR=y
CONFIG_GRKERNSEC_CHROOT_CHMOD=y
CONFIG_GRKERNSEC_CHROOT_FCHDIR=y
CONFIG_GRKERNSEC_CHROOT_MKNOD=y
CONFIG_GRKERNSEC_CHROOT_SHMAT=y
CONFIG_GRKERNSEC_CHROOT_UNIX=y
CONFIG_GRKERNSEC_CHROOT_FINDTASK=y
CONFIG_GRKERNSEC_CHROOT_NICE=y
CONFIG_GRKERNSEC_CHROOT_SYSCTL=y
CONFIG_GRKERNSEC_CHROOT_CAPS=y
CONFIG_GRKERNSEC_AUDIT_GROUP=y
CONFIG_GRKERNSEC_AUDIT_GID=76
CONFIG_GRKERNSEC_EXECLOG=y
CONFIG_GRKERNSEC_RESLOG=y
CONFIG_GRKERNSEC_CHROOT_EXECLOG=y
CONFIG_GRKERNSEC_AUDIT_PTRACE=y
CONFIG_GRKERNSEC_AUDIT_CHDIR=y
CONFIG_GRKERNSEC_AUDIT_MOUNT=y
CONFIG_GRKERNSEC_SIGNAL=y
CONFIG_GRKERNSEC_FORKFAIL=y
CONFIG_GRKERNSEC_TIME=y
CONFIG_GRKERNSEC_PROC_IPADDR=y
CONFIG_GRKERNSEC_RWXMAP_LOG=y
# CONFIG_GRKERNSEC_AUDIT_TEXTREL is not set
CONFIG_GRKERNSEC_DMESG=y
CONFIG_GRKERNSEC_HARDEN_PTRACE=y
CONFIG_GRKERNSEC_PTRACE_READEXEC=y
# CONFIG_GRKERNSEC_SETXID is not set
# CONFIG_GRKERNSEC_TPE is not set
CONFIG_GRKERNSEC_RANDNET=y
CONFIG_GRKERNSEC_BLACKHOLE=y
CONFIG_GRKERNSEC_SOCKET=y
# CONFIG_GRKERNSEC_SOCKET_ALL is not set
CONFIG_GRKERNSEC_SOCKET_CLIENT=y
CONFIG_GRKERNSEC_SOCKET_CLIENT_GID=103
CONFIG_GRKERNSEC_SOCKET_SERVER=y
CONFIG_GRKERNSEC_SOCKET_SERVER_GID=104
CONFIG_GRKERNSEC_SYSCTL=y
CONFIG_GRKERNSEC_SYSCTL_ON=y
CONFIG_GRKERNSEC_SELINUX_AVC_LOG_IPADDR=y
CONFIG_GRKERNSEC_FLOODTIME=10
CONFIG_GRKERNSEC_FLOODBURST=7

_________________
In which level of metalanguage are you now speaking?


Last edited by arackhaen on Sun Jan 13, 2013 11:07 pm; edited 2 times in total
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6551
Location: Goose Creek SC

PostPosted: Sat Jan 05, 2013 4:41 am    Post subject: Reply with quote

Does your kernel config have

-> File systems
-> Pseudo filesystems
-*- /proc file system support
[*] /proc/kcore support
[*] Tmpfs virtual memory file system support (former shm fs)
[*] Tmpfs POSIX Access Control Lists
-*- Tmpfs extended attributes
[*] HugeTLB file system support
<*> Userspace-driven configuration filesystem
_________________
Defund the FCC.
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Sun Jan 06, 2013 7:47 am    Post subject: Reply with quote

DONAHUE wrote:
Does your kernel config have

-> File systems
-> Pseudo filesystems
-*- /proc file system support
[*] /proc/kcore support
[*] Tmpfs virtual memory file system support (former shm fs)
[*] Tmpfs POSIX Access Control Lists
-*- Tmpfs extended attributes
[*] HugeTLB file system support
<*> Userspace-driven configuration filesystem


Hi Donahue,

Checked these and all are selected from Pseudo filesystems.
This kernel config has worked for me for couple years that I have had Gentoo installations, but now with these latest software updates I did some modifications and also additions, because hardened kernel version changed from 3.1.5 to 3.5.4 (boot will result in totally same problem also with older 3.1.5 kernel).
_________________
In which level of metalanguage are you now speaking?
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6551
Location: Goose Creek SC

PostPosted: Sun Jan 06, 2013 3:23 pm    Post subject: Reply with quote

take a look at http://www.linuxquestions.org/questions/linux-from-scratch-13/init-open-dev-console-no-such-file-or-directory-846133/

neddy's advice in http://forums.gentoo.org/viewtopic-t-880045.html about making /dev/console and its permissions
_________________
Defund the FCC.
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Sun Jan 06, 2013 7:04 pm    Post subject: Reply with quote

Thanks for these pointers!

I tried creating those three device nodes manually (from this old Slack installation) to /dev, but boot did still halt to same position.

Created the devices:
Code:

# mknod null c 1 3
# mknod zero c 1 5
# mknod console c 5 1
# chmod 666 null
# chmod 666 zero
# chmod 600 console


And the output was like this in /dev:
Code:

# ls -la
total 8
drwxr-xr-x  2 root root 4096 2013-01-06 19:22 ./
drwxr-xr-x 36 root root 4096 2013-01-04 00:02 ../
-rw-r--r--  1 root root    0 2012-11-09 00:13 .udev
crw-------  1 root root 5, 1 2013-01-06 19:22 console
crw-rw-rw-  1 root root 1, 3 2013-01-06 19:22 null
crw-rw-rw-  1 root root 1, 5 2013-01-06 19:22 zero



Next I'll check udev reinstallation through LiveCD's chroot environment... let's see if that helps.
_________________
In which level of metalanguage are you now speaking?
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Sun Jan 06, 2013 9:21 pm    Post subject: Reply with quote

Nope, udev reinstallation didn't help.

I saw this thread about switching to eudev (never heard of), do you think it might help (worth to try)?
http://forums.gentoo.org/viewtopic-t-946454.html
_________________
In which level of metalanguage are you now speaking?
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6551
Location: Goose Creek SC

PostPosted: Mon Jan 07, 2013 12:10 am    Post subject: Reply with quote

which version of udev openrc are you using
/
_________________
Defund the FCC.
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Mon Jan 07, 2013 6:02 am    Post subject: Reply with quote

Booted to chrooted env with LiveCD and got these:

    udev:
    * sys-fs/eudev
    Latest version available: 0
    Latest version installed: [ Not Installed ]
    Size of files: 614 kB
    Homepage: http://www.freedesktop.org/wiki/Software/systemd
    Description: A copy of sys-fs/udev-171-r9 to support migration from <=udev-180 to eudev
    License: GPL-2

    * sys-fs/udev
    Latest version available: 171-r9
    Latest version installed: 171-r9
    Size of files: 614 kB
    Homepage: http://www.freedesktop.org/wiki/Software/systemd
    Description: Linux dynamic and persistent device naming support (aka userspace devfs)
    License: GPL-2

    * sys-fs/udev-init-scripts [ Masked ]
    Latest version available: 9999
    Latest version installed: [ Not Installed ]
    Size of files: 0 kB
    Homepage: http://www.gentoo.org
    Description: udev startup scripts for openrc
    License: GPL-2

    * virtual/udev
    Latest version available: 171
    Latest version installed: 171
    Size of files: 0 kB
    Homepage:
    Description: Virtual for udev implementation
    and number of its features
    License:


    OpenRC:
    * app-admin/openrc-settingsd [ Masked ]
    Latest version available: 1.0.1
    Latest version installed: [ Not Installed ]
    Size of files: 237 kB
    Homepage: http://gnome.gentoo.org/openrc-settingsd.xml
    Description: System settings D-Bus service for OpenRC
    License: GPL-2

    * sec-policy/selinux-openrc [ Masked ]
    Latest version available: 9999
    Latest version installed: [ Not Installed ]
    Size of files: 0 kB
    Homepage: http://www.gentoo.org/proj/en/hardened/selinux/
    Description: SELinux policy for openrc
    License: GPL-2

    * sys-apps/openrc
    Latest version available: 0.11.8
    Latest version installed: 0.11.8
    Size of files: 170 kB
    Homepage: http://www.gentoo.org/proj/en/base/openrc/
    Description: OpenRC manages the services, startup and shutdown of a host
    License: BSD-2


I wondered why sys-fs/udev-init-scripts is masked and should I have it?
_________________
In which level of metalanguage are you now speaking?
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6551
Location: Goose Creek SC

PostPosted: Mon Jan 07, 2013 6:46 am    Post subject: Reply with quote

emerge -s udev openrc done here on 3 machines shows the same results you have.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Tue Jan 08, 2013 1:05 pm    Post subject: Reply with quote

Because I have no more clues how to fix this, I'm trying software upgrades one more time (through LiveCD chroot).
Executed emerge --sync and emerge --depclean. Then emerge --update --deep --new @world and it did update 16 packages, including hardened-sources 3.7.0.
So I compiled that new kernel version (using same old config) and testing if some of those updates could help with the problem, but they didn't (though I didn't expect much hope there).

For selinux, I tried rlpkg -a before updates, but it said all is fine. And selinux is set on permissive in system, so I don't think it should cause this problem.

If the problem is not udev, nor selinux, I can only think of those LiveCD problems that I got in some point (when root password was scrambled in every boot same way like in LiveCD). Though I don't remember when/how I had done something that caused this kind of behavior. Maybe there is some LiveCD specific in system's boot now, that causes problems with these devices not being there and boot freezing because of that... but I'm only guessing.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6551
Location: Goose Creek SC

PostPosted: Tue Jan 08, 2013 5:22 pm    Post subject: Reply with quote

you had company http://www.gossamer-threads.com/lists/gentoo/hardened/250763?do=post_view_threaded#250763 maybe still do
another guy says:
Code:
removed 50-udev.rules from /etc/udev/rules.d/ and working fine again
can't hurt
_________________
Defund the FCC.
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Thu Jan 10, 2013 1:35 pm    Post subject: Reply with quote

Now I think I got a little grip of this thingy... booted to system with init=/bin/sh and started different rc levels manually from there.

Two things seem to be obvious:
1. not all devices are there even as udev is started
2. boot doesn't transition to default level at all.

For the 1st problem, I don't know much what to do about it. I know I don't have that many udev rules in '/etc/udev.d/rules' directory. Maybe I should have more, but what I checked from my other Gentoo installations, neither do they. So it looks like udev is not creating all devices it should. I do see tty1-12, but not tty0 (and X complains about that if I try to start it). dev is also missing '/dev/initctl' and probably many other devices too.

For the 2nd problem, it looks like there is no real "problem", preventing default startup level from initializing. But I don't know OpenRC that well, that I would how its transitioning between those different startup levels. Maybe this is simply because there is no device '/dev/initctl', it can't go on changing init level (which was the problem when I tried to switch to init level 3 manually).
If this is the case, then 2nd problem is inherited from 1st problem and I would need to got figured out, why so many devices are missing (while there still are so many devices after devfs has started and some devices added when udev has been started - why some are missing but some or not).
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Thu Jan 10, 2013 1:59 pm    Post subject: Reply with quote

Now I did find out, that some of those devices do exist when I'm manually on boot runlevel. I did see /dev/tty0 and /dev/urandom there, but when I manually switched to default runlevel, those were gone. '/dev/initctl' didn't exist in earlier startup levels either.

Maybe something in default startup level does mess up with devices...
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Sun Jan 13, 2013 11:00 pm    Post subject: [SOLVED] Problem with booting: ERROR: urandom failed to star Reply with quote

Finally got it solved... :D

Can't really be sure if it was just this one simple issue, but final solution was uncommenting udev mounting line from fstab.

I think I didn't originally have udev mount line in fstab at all, but when I did those updates with emerge world, I red somewhere that I should add this line to fstab:
Code:

udev                           /dev            tmpfs           rw,rootcontext=system_u:object_r:device_t,seclabel,nosuid,relatime,size=10m,mode=755  0 0

I really am not sure where I did read it, and don't even remember if it really was during those updates or while trying to solve this boot problem.
But commenting that line was final touche and then booting started work again. It was clear that devices were okay in sysinit level, and somewhat different again on boot level, but when I tried to go to default level, devices were quite lost.

I did change udev version quite many times, while trying to solve this, so it might have affected this, but that alone did not fix it.

Now I'm running these versions of udev:
Code:

*  sys-fs/eudev
      Latest version available: 0
      Latest version installed: [ Not Installed ]
      Size of files: 614 kB
      Homepage:      http://www.freedesktop.org/wiki/Software/systemd
      Description:   A copy of sys-fs/udev-171-r9 to support migration from <=udev-180 to eudev
      License:       GPL-2

*  sys-fs/udev
      Latest version available: 9999
      Latest version installed: 171-r9
      Size of files: 0 kB
      Homepage:      http://www.freedesktop.org/wiki/Software/systemd
      Description:   Linux dynamic and persistent device naming support (aka userspace devfs)
      License:       LGPL-2.1 MIT GPL-2

*  sys-fs/udev-init-scripts
      Latest version available: 18
      Latest version installed: 18
      Size of files: 4 kB
      Homepage:      http://www.gentoo.org
      Description:   udev startup scripts for openrc
      License:       GPL-2

*  virtual/udev
      Latest version available: 196
      Latest version installed: 196
      Size of files: 0 kB
      Homepage:     
      Description:   Virtual for udev implementation and number of its features
      License: 

_________________
In which level of metalanguage are you now speaking?
Back to top
View user's profile Send private message
arackhaen
n00b
n00b


Joined: 04 Jan 2013
Posts: 10
Location: Turku, Finland

PostPosted: Sun Jan 13, 2013 11:01 pm    Post subject: Reply with quote

And thanks Donahue for your help!!!
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6551
Location: Goose Creek SC

PostPosted: Sun Jan 13, 2013 11:46 pm    Post subject: Reply with quote

Wow. fstab, would never have guessed. Good work.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum