• Linux Cant Start up
    13 replies, posted
[IMG]imgur.com/dzc7GrQ.png[/IMG] okay so that started happening after i turned on my ubuntu computer after not using it in a week ive trying just waiting nothing happends but sometimes around 15 minutes the screen just turn black and my screen looses signal What could this be ? please help as i really need my ubuntu computer rn [editline]9th August 2016[/editline] i think i might know whats wrong basicly recently theres been an error log filling up to over 150gb and now i think its filling my entire harddrive so it cant boot the thing is its an error log from a uninstalled printer driver
You could try removing the XAMPP executables from /etc/ from a live usb.
[QUOTE=x8BitRain;50853566]You could try removing the XAMPP executables from /etc/ from a live usb.[/QUOTE] still how would that help, it has nothing to do with that
Enable verbose booting (remove "quiet" boot parameter), this will help you see where exactly it stops booting.
[QUOTE=Megalan;50854708]Enable verbose booting (remove "quiet" boot parameter), this will help you see where exactly it stops booting.[/QUOTE] How would i do this?
Since you are probably using grub boot loader: 1) Press escape after starting/rebooting your pc until you see grub menu 2) Select desired boot option (probably first one) and press "e" 3) Find something like "linux /boot/vmlinuz ....." and remove "quiet" option from that line 4) Press Ctrl+X or F10 to boot [IMG]http://i.imgur.com/zybxkMq.png[/IMG]
[QUOTE=Megalan;50854920]Since you are probably using grub boot loader: 1) Press escape after starting/rebooting your pc until you see grub menu 2) Select desired boot option (probably first one) and press "e" 3) Find something like "linux /boot/vmlinuz ....." and remove "quiet" option from that line 4) Press Ctrl+X or F10 to boot [IMG]http://i.imgur.com/zybxkMq.png[/IMG][/QUOTE] okay ill try this when i get home from school
so this is what is happening is it possible to dump this to a usb so its easier to read? [url]http://imgur.com/a/lHOGa[/url]
[QUOTE=Zortex;50866056]so this is what is happening is it possible to dump this to a usb so its easier to read? [url]http://imgur.com/a/lHOGa[/url][/QUOTE] Nope, that's plenty readable. [url=https://wiki.archlinux.org/index.php/General_troubleshooting#Recovery_shells]According to here[/url], the first step is to add "rescue" to your boot parameters (the same place you removed "quiet" from). Then disable XAMPP from starting on boot, because that's where your system is hanging.
[QUOTE=lavacano;50866741]Nope, that's plenty readable. [url=https://wiki.archlinux.org/index.php/General_troubleshooting#Recovery_shells]According to here[/url], the first step is to add "rescue" to your boot parameters (the same place you removed "quiet" from). Then disable XAMPP from starting on boot, because that's where your system is hanging.[/QUOTE] Nope figured it out, i connected to it via ssh then deleted the cups error_log file and now i can start up just normally the problem is i dont think ive uninstalled cups completly
If deleting a log file is what got your system to start, then the problem was that you were out of drive space. The fact that the log file happened to belong to CUPS is irrelevant.
[QUOTE=lavacano;50867468]If deleting a log file is what got your system to start, then the problem was that you were out of drive space. The fact that the log file happened to belong to CUPS is irrelevant.[/QUOTE] this log file fills up all my harddrive on seconds, ive managed to uninstall cups now
if CUPS manages to create a log so freaking large it chokes your drive space, you need to figure out why the hell a printing daemon is managing to occupy as much drive real estate as possible with its log file, or limit the maximum size of the log itself. CUPS should itself limit its default log size to 1MB. So unless this machine has about 2MB of free space, then what the shit? You can limit your logsize in cups.conf, look for MaxLogSize.
[QUOTE=Richard Simmons;50871528]if CUPS manages to create a log so freaking large it chokes your drive space, you need to figure out why the hell a printing daemon is managing to occupy as much drive real estate as possible with its log file, or limit the maximum size of the log itself. CUPS should itself limit its default log size to 1MB. So unless this machine has about 2MB of free space, then what the shit? You can limit your logsize in cups.conf, look for MaxLogSize.[/QUOTE] okay thanks
Sorry, you need to Log In to post a reply to this thread.