Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The mysql-socket-error thread was causing my HD to go full, thus the 2nd HD thread and eventually put me in disk full and then recovery.
However nothing I've done recovers me!
What I've tried are:
Recovery mode + networking (makes HD r/w), and file deletes,
Attempted LiveDVD, for chroot, but LiveDVD will not boot,
Removed drive to external HD cabinet and from Laptop deleted 32GB from HD,
After all that I still get the lnusertemp disk full message when I attemp to login. System boots to that point now, where login screen comes up and then get the error after properly entering my UID/PWD combo.
I'm on Kubuntu 14.04 LTS on all machines, including this server.
Guessing swap is full or corrupted, but never had to clean or reformat swap. Do y'all have any other ideas on this?
Remember I tried to boot from the LiveDVD and it halts half way through, because of these errors. Know the LiveDVD is good as I just used it 3 months back to rebuild this laptop!
if that LiveDVD is what you are relaying on to get you where you need to be, have you just tired to trouble shoot that first? in the form of creating a USB Stick live boot -- they are rewriteable
if that LiveDVD is what you are relaying on to get you where you need to be, have you just tired to trouble shoot that first? in the form of creating a USB Stick live boot -- they are rewriteable
BW-userx,
No I listed everything I've tried and the only way I was able to come from /dev/sda1 @ 99% was via the external HD enclosure, where I deleted the 32G that is now showing from the df -hT I posted previously.
I'm assuming, but maybe not correctly, that the system wrote either a file or a flag somewhere, which is now the reason for the error, but where, as you can see there is nothing showing anything close to "disk full"!
I also know that the LiveDVD creates a temp ramfs, and wondering if RAM is now having issues. I get no errors indicating a RAM problem however.
Would like a solution on this by tomorrow, but have to work. If no solution, then I'll have to pull the 80GB HD, copy all pertinent info off and do a fresh install.
I hate fresh installs, because it takes 3 weeks of constant running of bash scripts to get everything re-installed, running, configured and totally in the right places on the computer and desktop!
The first bash script I run, to install all the basics on a box take a min of 48 hours to run. Yup that much stuff on my servers.
I'm recovered and even avoided all the hours of loading stuff onto the computer. I had a desktop fail, as chipset started getting squirrely and mouse quit working, so it had a 1.0TB HD and as development desktop has 80+% of what I need for the server, so installed that HD to my server and running again. Now just downloading the server stuff needed and checking on what else is missing.
I'm leaving this open, however, because the guru's should already know and have an answer for this problem and if not this should be added as a bug for the "CORE" guys to address and fix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.