can't boot to ubuntu: session lasted less than 10 sec.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
can't boot to ubuntu: session lasted less than 10 sec.
Just when I think I am getting close to thumbing my nose at Bill Gates, I get stuck again. Auuuuugh.
I always boot to Ubuntu first, today after I log in I get message along these lines:
Your session lasted less than 10 seconds, could be an installation problem or you are low on disk space, try booting in a safe mode.
Well damned if I know what to do.
I tried booting to Ubuntu recovery mode, which got me to something that looked like a terminal to enter a command. I entered my password and got the message "no such command", or "command unknown" and could go no further.
Then I tried booting off of Ubuntu CD. That worked fine, and after a little experimenting got to where I could browse my "/home". I thought I would try to delete some files, see if I could free up space, though I don't know how that could have happened. At any rate, it didn't matter, because the live cd would not let me move anything to the trash.
I was just going to make a post to see if I understood the partitions/file system in Linux.
When I installed Ubuntu 7.04 I had a clean hard drive, created a 1 gig swap, a 10 gig "/" and about 120 gig "/home". IF I understand the Linux file system, whatever I store in my home/user folder is written to this 120 gig /home partition? If that is so, there is no way I have run out of disk space.
I have a dual-boot system, and am now back in XP. Yuck.
Can anyone help me out, get me back to Ubuntu again?
I can not copy and paste your commands, as I have to reboot, and I do not know hoe to enter your last command line.
the df -hT did show that my "/" was completely used. It reported a size of 9.2 gig, with 9.2 used.
My /home was size of 115 gig, with 108 gig available.
Obviously I am doing something wrong. I did transfer five pictures, and ripped two CD's (lossless), but had hoped that I was storing them on the large home partition.
I have only been using V7.04 for a couple of weeks, and have only installed a few programs with synaptic. Just finding my way around my first Linux distro, so have not done very much. Very much the NOOB.
Many thanks for the reply.
Now can I find out how I filled up my root, and how I can free up space? Is that the next step?
Yep - that's what the other command (line) was for. I don't understand why you can't enter it - just type it in. It's 3 commands piped to each other (for convenience). That vertical line is the pipe command - usually above the backslash on the keyboard.
Be patient - might take minutes to come back; especially with the sort in it, and you having no disk space left.
Obviously somebody is spitting out warnings - and they are going to all three logs. Tail each of the logs and see if you can see anything obvious - maybe try 20 lines; "tail /var/log/kern.log -n 20" (do it for each log in turn).
Fix whatever the problem is (if it still exists), else this will just keep happening.
Then erase a couple of those logs to free up some space - I'd probably only keep the syslog
I can't tail the /var/log (error reading /var/log is a directory).
I can the other three large /var/log's. I am afraid it did not do me any good, as I can hardly make sense out of any of it. I do see a lot of "Bluetooth" in the /log/messages and /log/kern.log.
Now if I knew that was the problem, I would have to find what was creating a "bluetooth" log?
If I type the "echo "" " at the command line, will that erase the file?
I do not know how to type the arrow head symbol at any rate.
If I could type the echo line, followed by /var/log, I would delete that entire directory?
Sorry, I am getting very frustrated. I was determined to keep working through the Linux issues so I could migrate away from XP, but this is very discouraging. Ubuntu was working very well for me up to this point.
Is this typical Linux stuff? Does everyone have to go through these kinds of things to get their system to work? I hate to think of reinstalling some day and going through all of this again.
No, this is not what happens under normal circumstances. It only does when something is badly misconfigured. I have been running nine Linux systems for ten months and this has never happened - and I'm sure I'm not the only one.
As for the arrow, I'm afraid I don't know what your keyboard layout looks like being an azerty user - but I believe the arrows are next to the letter M.
You can't use the echo command on /var/log because it is a directory, not a file.
You should do as pointed out:
echo "" > /var/log/kern.log
or as an alternative
cat /dev/null > /var/log/kern.log
Either will clear out the logfile in question.
Repeat this for the other logs.
Simply clearing up logfiles is not a solution, of course. It is vital that you pinpoint the problem that is producing all those messages being logged. If you suspect it's bluetooth-related, you should verify whether some misconfiguration is involved - or if you don't use bluetooth at all, it may as well be disabled.
I only cleared the kern.log and the messages log. That freed up enough space so that I could boot to Ubuntu.
As you say, this is not the solution. That I fear could be a bigger problem to try and solve. I did uncheck bluetooth in administration/services. I guess time will tell if that helps. Presumably I still have a couple of gig in the syslog file taking up space.
Thanks again to both of you for helping me out of this.
My experience so far with Linux has been an inconsistent one. One thing that has been consistent is the willingness of the Linux community to help out. I have been disappointed with a couple of the issues I have had, but every time there has been someone willing to take the time to work me through it.
I am going to monitor those log files for a while to see what happens.