I cannot get my system, which I'm using as a media server, vortexbox, to boot unless I use Ctrl-D. What is Ctrl-D?

Thanks all, I introduce myself with this perhaps, elementary question.

Thanks once more for your patience and answer.

welcome to LQ, Ctrl D normaly is your system not boot as normal and require a maintenance with entering root password,
actually what is the linux variant you are using ?
sometime better to provide more info of the system you are using

1 members found this post helpful.

Crtl-d is an escape for some programs in linux.

When you you press this sequence?

1 members found this post helpful.

Vortexbox is a suite of software used as a media server NAS/ripper/player, and the VBA, VortexBoxAppliance is an Atom based computer, running LINUX, basically used as a server. It is typically run 'headless' via a browser based GUI, as well as Apps available for iOS, Android etc.

This one runs on Fedora release 16 (Verne).

The device does not boot unless I exit the debug shell which cannot be done in headless mode and I need to attach a keyboard and screen to the device to be able to quit the debug shell.

Title of my post on vortex box forum: VortexBox boots after Ctrl-D

Problem: I must power off the vortex box appliance every time I try to access it after a period of inactivity. Is this normal behaviour, or is there a better (correct?) way? Seemingly, this has caused damage at some point and and I cannot get VBA to boot unless I use the keyboard with Ctrl-D to force it.

End result: The GUI is unable to find myvortexbox, unless coaxed by me through the USB keyboard + screen attached to the VBA.

All this seemed to happen whilst trying to install the Logitech Media Server version 7.7.3. I am running vortexbox SW 2.2, and had also tried to update my software via the GUI.

A screen attached to the VBA shows the messages:

at which point the Ctrl-D brings me to the login prompt.


Is there an easy fix?

Thanks for the wonderful device, guess there's a learning curve.

skipper

ps: rewording this query has answered half my doubts, can I run a repair without long the server, do I run the risk of having to clean install?

did you run as intructed?

# fsck

normally it will fix the error

Let me try . . .

Found this http://info.vortexbox.org/tiki-index...+will+not+boot it worked!

As a side note, Control D is the ASCII EOT (end of transmission) code - see manpage on ASCII. The control D is used in UNIX/Linux systems for an end of file notification to the terminal driver.

When the system has a boot error it will then fall into several possible modes depending on the distribution:

1) request root login (prompts for a password)
2) drop into a bash prompt

In either case, entering a control D terminates the input, and the system attempts to resume the boot from where the error was detected.

The system attempts to suggest recovery procedures - running fsck is intended to rebuild/recover a filesystem that had what was identified as a fatal error - usually on the root filesystem as that is the first one mounted.

Sometimes it can't find the root filesystem (errors in /etc/fstab file for instance, or errors in the "root=..." boot kernel option). This can still be recovered, though it is usually easier to fix the fstab file or fix the grub configuration file (tricky, as you have to mount the filesystem with the configuration file, and with grub2 being much more complex) make the repair and reboot. Most people consider it simpler to put a rescue CD/DVD and boot that to fix things.

If you like Fedora then please keep up with the release cycle.
Current is 20 with 21 slated for release end of this year.