have to use "ctrl d" to finish boot process

galego · 09-01-2006, 02:53 PM

i deleted MEPIS from my drive, and now everytime i try to boot into ubuntu i have to use "ctrl d" to finish the process. i am trying to boot into ubuntu, and all the files are intact, settings as well. i should say that i can boot into ubuntu after pressing "ctrl d". im just trying to make this step disappear. not sure what to do or what i did.

any help would be most helpful.

thanks

pda_h4x0r · 09-01-2006, 03:14 PM

What runlevel are you entering? This only happens if you enter runlevel 1; you probably want to enter runlevel 2 or 5.

galego · 09-01-2006, 04:10 PM

it is putting me in runlevel 1 and just sits there. this happens when it checks systemsfile during boot. i guess there is something in there that it does not like so then it puts me into prompt.

pda_h4x0r · 09-02-2006, 12:45 AM

So, in your /etc/inittab, there IS a line that says "id:2:initdefault:" or "id:5:initdefault:", but not "id:1:initdefault"?

galego · 09-02-2006, 01:42 PM

correct as you can see it id:2:initdefault.

# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:2:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

# What to do when the power fails/returns.
pf:

owerwait:/etc/init.d/powerfail start
pn:

owerfailnow:/etc/init.d/powerfail now
po:

owerokwait:/etc/init.d/powerfail stop

# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

pda_h4x0r · 09-02-2006, 07:14 PM

Very interesting. Could you show us the output of dmesg?

galego · 09-02-2006, 11:35 PM

it is quiet the large out-put. looking for something in perticular? dont think i can post the whole thing!

pda_h4x0r · 09-03-2006, 11:39 PM

We're looking for an error that prevents the system from launching multi-user services.

Actually, this may also be a bootloader problem. You see, you can pass an argument to the kernel to force it to enter runlevel 1 without looking into /etc/inittab. Could you post your bootloader configuration first?

galego · 09-04-2006, 12:12 PM

Code:

# Modified by YaST2. Last modification on Sat Sep  2 20:14:07 EDT 2006
color white/blue black/light-gray
default 1
timeout 8
gfxmenu (hd0,5)/boot/message

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
    rootnoverify (hd0,3)
    makeactive
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Desktop 10
    root (hd0,5)
    kernel /boot/vmlinuz root=/dev/sda6 vga=0x317 resume=/dev/sda5  splash=silent showopts
    initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: Ubuntu, kernel 2.6.15-26-386 (/dev/sda2)###
title Ubuntu, kernel 2.6.15-26-386 (/dev/sda2)
    kernel (hd0,1)/boot/vmlinuz-2.6.15-26-386 root=/dev/sda2 ro quiet splash
    initrd (hd0,1)/boot/initrd.img-2.6.15-26-386

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Desktop 10
    root (hd0,5)
    kernel /boot/vmlinuz root=/dev/sda6 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
    initrd /boot/initrd

thanks for the help!

pda_h4x0r · 09-04-2006, 11:30 PM

Try changing "ro" in the kernel argument list for Ubuntu to "rw."

galego · 09-06-2006, 07:12 AM

no difference; it still hangs at "systemfile check"

pda_h4x0r · 09-08-2006, 03:37 PM

By "systemfile check," do you mean that Ubuntu is doing a filesystem check? What are some of the lines above this point?

galego · 09-08-2006, 10:48 PM

just the lines being returned during system start. dont know if you are using ubuntu or not but even on other distros when boot is finished and the system begins to load it goes thruogh and configures USB port, HDDs, Ethernet, etc. when the line "checking systemfies" comes up it gets hung up instead of returning and "OK" like all the previous lines. now i catch it before it puts me into "init 3" mode and it continues the start up process.

kinda random, but its getting annoying so i think im just going to re-install. im just playing with XGL/Compiz so its no big deal.

thanks for the help though!

pda_h4x0r · 09-09-2006, 12:20 AM

I'm sorry I could not be of more help.