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:
/dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
Dropping to debug shell.
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.
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?