LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Disk Drive For .TMP Goes Missing Sometimes.......??? (http://www.linuxquestions.org/questions/linux-newbie-8/disk-drive-for-tmp-goes-missing-sometimes-822752/)

Sumguy 07-28-2010 09:54 PM

Disk Drive For .TMP Goes Missing Sometimes.......???
 
Hello There, Geeks and Geekettes!

I'm into my third week with Ubuntu, AND loving it!

Seem to be having one recurring problem though. I've Googled it and even tried a solution, but to no avail, so I thought I'd slide it past youse[sic] guys:

A lot of times when Ubuntu is booting up, I'll get a message that says: "The disk drive for .tmp is not ready yet or not present". I have to press "F" to fix it, and then it boots up normally after a while.

This has been happening about 50% of the time.

I can usually foretell when it will be happening, because it usually (but not always) happens when, in my previous session, I start to notice some strange behavior- like the shut-down confirmation dialogue box will be empty....or I can't get Chromium or Synaptic (etc.) to open, and other such things.

So...what is happening when I get this message at boot-up and why? And how do I fix it????

GrapefruiTgirl 07-28-2010 10:08 PM

Google search of your error message seems to indicate that it's a known/confirmed bug (some sort of race condition), and that you are not the only one having the problem. I did not see any signs of a solution though. Have a google again and look at some of the threads on launchpad and/or the Ubuntu mailing list. No guarantee there'll be a solution to be had, but maybe you can check regularly and see if they have it fixed yet.

Also - some folks (with various distros, myself included) have found that a good thing to look at if you suddenly find your session acting weird for no apparent reason, or apps won't run, is to check that your disk(s) are not full. Check your /home and / partitions and make sure they aren't filled up. A full disk can cause weird stuff to happen.

Sumguy 07-28-2010 10:27 PM

So....female geeks DO exist! Alright!!

Yes, I had also noticed in my Google search, that someone suggested pressing M to enter manual-fix-it mode; entering the root password and then entering something like "mount /.tmp" and then pressing Cntrl+D. But that did not seem to provide any lasting solution.(I guess that basically is just the manual way of doing what pressing the "F" does automatically)

Hehe, none of my partitions are even remotely close to being half way full- but they sure act like it sometimes. (And only sometimes....it's an intermittent problem. I'm beginning to think that Ubuntu is trying to remind me of Windos![shudder]

GrapefruiTgirl 07-28-2010 10:30 PM

Quote:

Originally Posted by Sumguy (Post 4048573)
I'm beginning to think that Ubuntu is trying to remind me of Windos![shudder]

You may be right ;)

Yep, I noticed too that the other folks who had this issue, also tried the M and F and whatever other keys were offered, but regardless, the problem returned anyhow. Nobody reported any massive failures that I read of - all seemed to report the system worked normally despite the error message.

I guess just hang in there and await some news on the bug/issue.

Sumguy 07-28-2010 10:43 PM

Quote:

Originally Posted by GrapefruiTgirl (Post 4048575)

Yep, I noticed too that the other folks who had this issue, also tried the M and F and whatever other keys were offered, .....

Back in my Windows days, I was using M-F quite a bit.....that's partly why I switched to LINUX! :D

GrapefruiTgirl 07-29-2010 07:58 AM

LOL - good one ;)

i92guboj 07-29-2010 08:35 AM

I have really next-to-nil experience with Ubuntu, but for the sound of it, the problem is that either /tmp or/and /var/tmp are running out of space. When temporary storage is full strange things will happen. It really doesn't matter if /tmp and /var/tmp are separate partitions of live on the same partition than / does, the real problem is that most programs will assume that there's temporary space so they often won't check for it, and programs will start acting weirdly.

The next time this happen you should really check the output of the dh and df -i commands, and paste it here if you can't make any sense of it.

If the problem is the one I describe, you could "solve" it by either regularly checking /tmp and deleting its contents or by putting /tmp on a bigger disk. You can even mount /tmp to a file on another disk if you can't or don't want to bother repartitioning the disk.

Sumguy 07-30-2010 01:48 AM

Quote:

Originally Posted by i92guboj (Post 4049059)
I have really next-to-nil experience with Ubuntu, but for the sound of it, the problem is that either /tmp or/and /var/tmp are running out of space. When temporary storage is full strange things will happen. It really doesn't matter if /tmp and /var/tmp are separate partitions of live on the same partition than / does, the real problem is that most programs will assume that there's temporary space so they often won't check for it, and programs will start acting weirdly.

The next time this happen you should really check the output of the dh and df -i commands, and paste it here if you can't make any sense of it.

If the problem is the one I describe, you could "solve" it by either regularly checking /tmp and deleting its contents or by putting /tmp on a bigger disk. You can even mount /tmp to a file on another disk if you can't or don't want to bother repartitioning the disk.

Ah! You know, that makes sense to me-

Says I need to install "Deb helper" for the Dh command (would it pay tyo do this?)

The Df -i command yielded this:

Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda5 4464640 158084 4306556 4% /
none 111023 751 110272 1% /dev
none 112078 7 112071 1% /dev/shm
none 112078 44 112034 1% /var/run
none 112078 1 112077 1% /var/lock
none 112078 1 112077 1% /lib/init/rw
/dev/sda1 39134664 124066 39010598 1% /media/COMPAQ


Not 100% sure...but if this says what I think it is saying, I have plenty of room right now- no? (I will do this command when the system is actually acting weird though- and compare it. Today, it is working fine.)

One thing I don't "get" though, is even if I were out of space, wouldn't .tmp dump at shutdown and therefore be empty at start-up again? (As opposed to giving me the "disk drive for .tmp is not ready or not present"?

i92guboj 07-30-2010 02:17 AM

Code:

Filesystem            Inodes  IUsed  IFree IUse% Mounted on
/dev/sda5            4464640  158084 4306556    4% /
none                  111023    751  110272    1% /dev
none                  112078      7  112071    1% /dev/shm
none                  112078      44  112034    1% /var/run
none                  112078      1  112077    1% /var/lock
none                  112078      1  112077    1% /lib/init/rw
/dev/sda1            39134664  124066 39010598    1% /media/COMPAQ

Please, next time use code tags just as I did now to paste this kind of info so the layout gets preserved, otherwise it's quite hard to read.

Quote:

Not 100% sure...but if this says what I think it is saying, I have plenty of room right now- no? (I will do this command when the system is actually acting weird though- and compare it. Today, it is working fine.)
df -i shows i-node info. You have plenty of i-nodes and that's fine. df alone (without -i) will show the free space on each partition, you need to look at that as well. You need both free i-nodes and free space to store a file.

Quote:

One thing I don't "get" though, is even if I were out of space, wouldn't .tmp dump at shutdown and therefore be empty at start-up again? (As opposed to giving me the "disk drive for .tmp is not ready or not present"?
This entirely depends on your distro and how you configured it (if at all). And that's why I mentioned explicitly that I know nothing about Ubuntu.

However, even if that was true it still wouldn't solve the fact that the partition might become full while you are using it, and hence the programs would continue to act weirdly as you described. It would only guarantee a safe boot, but not a safe operation.

Sumguy 07-30-2010 03:30 AM

Oooopppsss!! Sorry about not using the code tag. It's late.....

Code:

Filesystem          1K-blocks      Used Available Use% Mounted on
/dev/sda5            70251968  16288716  50394612  25% /
none                    444092      260    443832  1% /dev
none                    448312      700    447612  1% /dev/shm
none                    448312        72    448240  1% /var/run
none                    448312        0    448312  0% /var/lock
none                    448312        0    448312  0% /lib/init/rw
/dev/sda1            76249752  37278928  38970824  49% /media/COMPAQ

'puter's been on for 18 hours...if that helps.

Thanks.


All times are GMT -5. The time now is 07:07 AM.