[SOLVED] init: open(/dev/console): No such file or directory
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
init: open(/dev/console): No such file or directory
Hello peeps!
I am attempting my second build of an LFS system. Everything seemed to go alright during compilation, and configuration. I can get the system to boot, and the kernel to load all the devices and mount the partitions. But after the NIC is loaded, I am getting
init: open(/dev/console): No such file or directory
I have verified that there is a file called 'console' in the /dev/ directory;
But I cannot figure out where to go next with this issue, short of rolling back to a previous snapshot and recompiling from there. I don't want to do that, cause I'm sure its just 1 package I messed up or a configuration file, that I did not configure correctly.
My environment:
VMware Vsphere - 1 Guest
2 Drives - sda "fedora 14" & sdb "LFS"
Building LFS 6.7
now when I boot "LFS" "SDB" I do Disconnect SDA "Fedora" from the Guest.
Then I change Grub to boot hd0,1 and change the kernel line to see sda1 instead of "old" sdb1.
this is the output of /var/sys.log
Quote:
Nov 19 06:28:00 Relay-v1 kernel: [ 4.609704] ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33
Nov 19 06:28:00 Relay-v1 kernel: [ 4.625979] ctnetlink v0.93: registering with nfnetlink.
Nov 19 06:28:00 Relay-v1 kernel: [ 4.627441] ata2.00: configured for UDMA/33
Nov 19 06:28:00 Relay-v1 kernel: [ 4.638336] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 19 06:28:00 Relay-v1 kernel: [ 4.653705] TCP cubic registered
Nov 19 06:28:00 Relay-v1 kernel: [ 4.653950] Initializing XFRM netlink socket
Nov 19 06:28:00 Relay-v1 kernel: [ 4.657586] NET: Registered protocol family 10
Nov 19 06:28:00 Relay-v1 kernel: [ 4.664480] scsi 2:0:0:0: CD-ROM NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5
Nov 19 06:28:00 Relay-v1 kernel: [ 4.679388] scsi 2:0:0:0: Attached scsi generic sg1 type 5
Nov 19 06:28:00 Relay-v1 kernel: [ 4.686773] ip6_tables: (C) 2000-2006 Netfilter Core Team
Nov 19 06:28:00 Relay-v1 kernel: [ 4.691315] IPv6 over IPv4 tunneling driver
Nov 19 06:28:00 Relay-v1 kernel: [ 4.697511] NET: Registered protocol family 17
Nov 19 06:28:00 Relay-v1 kernel: [ 4.701545] Using IPI No-Shortcut mode
Nov 19 06:28:00 Relay-v1 kernel: [ 4.706235] registered taskstats version 1
Nov 19 06:28:00 Relay-v1 kernel: [ 4.801379] EXT3-fs: barriers not enabled
Nov 19 06:28:00 Relay-v1 kernel: [ 4.823529] kjournald starting. Commit interval 5 seconds
Nov 19 06:28:00 Relay-v1 kernel: [ 4.825790] EXT3-fs (sda1): mounted filesystem with writeback data mode
Nov 19 06:28:00 Relay-v1 kernel: [ 4.832913] VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
Nov 19 06:28:00 Relay-v1 kernel: [ 4.836224] Freeing unused kernel memory: 340k freed
Nov 19 06:28:00 Relay-v1 kernel: [ 4.852773] Write protecting the kernel text: 3592k
Nov 19 06:28:00 Relay-v1 kernel: [ 4.856568] Write protecting the kernel read-only data: 1668k
Nov 19 06:28:00 Relay-v1 kernel: [ 4.981523] async/0 used greatest stack depth: 6560 bytes left
Nov 19 06:28:00 Relay-v1 kernel: [ 6.056194] stty used greatest stack depth: 6180 bytes left
Nov 19 06:28:00 Relay-v1 kernel: [ 6.453625] mount used greatest stack depth: 5824 bytes left
Nov 19 06:28:00 Relay-v1 kernel: [ 7.933416] EXT3-fs (sda1): using internal journal
Nov 19 06:28:00 Relay-v1 kernel: [ 7.981524] rm used greatest stack depth: 5744 bytes left
Nov 19 06:28:00 Relay-v1 kernel: [ 10.463335] pcnet32 0000:00:11.0: eth0: link up
Nov 19 06:28:01 Relay-v1 kernel: [ 11.347803] ip used greatest stack depth: 5660 bytes left
Nov 19 06:28:01 Relay-v1 init: open(/dev/console): No such file or directory
Nov 19 06:28:01 Relay-v1 last message repeated 5 times
Nov 19 06:28:11 Relay-v1 kernel: [ 21.529795] eth0: no IPv6 routers present
Nov 19 06:28:11 Relay-v1 init: open(/dev/console): No such file or directory
Nov 19 06:28:42 Relay-v1 last message repeated 18 times
Quote:
[root@Relay dev]# ll
total 0
crw-------. 1 root root 5, 1 Nov 15 20:21 console
crw-rw-rw-. 1 root root 1, 3 Nov 15 20:21 null
Can anyone try to point me in the right direction to look at why I cannot load a console?
Please any advice or help is much appreciated!
Last edited by zer0signal; 11-23-2010 at 07:08 PM.
The permissions on /dev/console do not look correct. It should be: crw--w--w- 1 root tty 5, 1 Nov 24 07:39 /dev/console
Chapter 6.2. Preparing Virtual Kernel File Systems does create /dev/console with the permissions you posted, but this is temporary. The /etc/udev/rules.d/25-lfs.rules file should set the correct permissions when booting (this line KERNEL=="console", MODE="0622", GROUP="tty").
You might want to check if udev was implemented correctly.
Hope this helps.
Last edited by druuna; 11-24-2010 at 05:18 AM.
Reason: fixed spelling
Thats one thing I will take a look at tonight, but I should have mentioned another thing. When the kernel boots it reads the /etc/fstab, and it is able to mount /dev/sda1. But fails right after tring to mount /dev/pts & /dev/shm
Thanks!! It ended up being an issue with Udev, so I just re-entered the Chroot environment and did a make uninstall ("which showed the Udev rules were not implemented!") Sooooo... I just reinstalled and reconfigured it "made sure the udev rules were there" rebooted the Guest and it worked! Thx again!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.