Opened 9 months ago
Last modified 8 months ago
#638 new System Defect
init:: can't exec getty '/usr/libexec/getty' for port ...
| Reported by: | harlan | Owned by: | kris |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | System Configuration | Version: | 9.1-BETA1 |
| Keywords: | Cc: | trac-bugs@… |
Description
When I upgraded from 9.0 to the 9.1 beta I had the above problem. I just upgraded from the latest beta to RC1.
While the box was applying package updates there was a kernel panic after a fair number of packages were installed.
I rebooted the box and what I get is the system mounts the root filesystem and I immediately get the 'getty' messages described above. The system does not let me log in.
If I boot in to single-user mode I can mount the filesystems just fine, but when I exit single user mode I'm left at an Amnesiac login prompt - the system does not try and go multi-user.
Attachments (2)
Change History (7)
comment:1 Changed 9 months ago by harlan
comment:2 Changed 9 months ago by harlan
I've discovered that the "reboot" and "halt" command cause the panic - I'll be attaching a screen shot soon.
comment:3 Changed 9 months ago by harlan
If I issue the reboot command from multi-user mode the kernel panics.
If I 'init 1' then sync and reboot, the box reboots just fine.
Oh, I ran memtest86+ and got 7 completely clean passes.
comment:4 Changed 9 months ago by kris
- Owner set to kris
comment:5 Changed 8 months ago by kris
If the rc.conf file got removed, then you can grab a fresh copy from here:
http://trac.pcbsd.org/browser/pcbsd/current/overlays/desktop-overlay/etc/rc.conf
The real problem is the issue with the halt / reboot commands causing a kernel panic. When that happens if rc.conf had been recently written to, often it will get corrupted and then this occurs. This issue is being looked into on the FreeBSD end I think.
/etc/rc is 0 bytes long.