The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: mountall (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mountall (Ubuntu Trusty)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
I bought a second hand hdd from ebay that had previously been in a sky box. I
gave it a good formatting and then installed elementary freya on it and ran
update. My old hdd is still in but is full, so I have dual boot same opsys. I
am getting this exact bug. I have a fat32 partition on the old
Manually adding
tmpfs /tmp tmpfs defaults 0 0
to fstab does seem to be a functional workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready
I'm pretty sure I'm still seeing the on a up-to-date trusty install as
well. This is in a rented dedicated server too, so it's extra
spectacularly annoying, because I have to wait for someone to go press a
key on the keyboard to fix it.
mountall -v says "mountall 2.49"
--
You received this bug
I also encountered this problem， I used the following version
mountall 2.49
Linux version 4.4.0-46-genric(root@quorm)(gcc version 4.8.4(Ubuntu
4.8.4-2ubuntu1~14.04.3)) #67 SMP Fri Dec 23 14:57:30 CST 2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is there any workaround for this on on trusty in the meantime ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage
mountall is still available in Ubuntu 17.04 dev and the bug might still
exist in this package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet
Edit: Weird, even as reporter I can't change the Won't Fix state.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage
Note xenial no longer uses mountall.
Trusty is the last affected and supported release.
** Changed in: mountall (Ubuntu)
Status: Confirmed => Won't Fix
** Also affects: mountall (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu Trusty)
I am experiencing this too on Trusty!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage notifications about this bug go
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1091792
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have a few partitions on my machine. I can remove them, but would
rather not. Anyone know if removing them will elivate this bug?
To be honest I don't think this will make any difference, so I wouldn't try it.
I only have the usual set of /boot, /root and /home and the system sets up a
/tmp
I have a few partitions on my machine. I can remove them, but would
rather not. Anyone know if removing them will elivate this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: mountall (Ubuntu Quantal)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also seeing this on Trusty in the Cloud Images:
* Stopping log initial device creation [74G[ OK ]
* Starting configure network device [74G[ OK ]
* Stopping Mount network filesystems[74G[ OK ]
The disk drive for /tmp is not ready yet or not present.
keys:Continue to wait, or Press S to skip
** Branch linked: lp:debian/mountall
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage notifications about this bug go
I've got this also - on 12.04, does the latest mountall fix it? And,
while I'm here what does triaged mean on this package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk
The bug is marked as Fix released, but I'm still seing this problem on
Ubuntu 12.04, mountall version 2.36.4?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is
Correct, this is fix released in 2.48, thus Ubuntu 13.04 and up.
** Also affects: mountall (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: mountall (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu Precise)
Status:
I have added series tasks, to clearly reflect that this is fixed in
Ubuntu 13.04. In practice this message is shown at times too early, when
/tmp is still being cleared from files generated at previous boot. Thus
one can ignore and wait for it to go away.
--
You received this bug notification
I also have this bug on Ubuntu 12.04 (Precise) 3.8.0-33-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage
I can confirm this bug on Ubuntu 12.04.2, 3.5.0-42-generic
#65~precise1-Ubuntu, running on a macbook pro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not
I have this bug this morning. Ubuntu desktop 12.04 LTS, GNU/Linux
3.8.0-32-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not
This bug affects me too on Ubuntu 12.04.3 and even after updates it
persists! I have being using Linux Mint 13 (which based on Ubuntu 12.4)
and never had any issues like that and my hardware is not defective!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay this is getting silly really, after the last round of updates it
fixed this issue on my 12.04.3 Desktop system. I thought Cool. Well
after another round of updates; and all I am doing is using the Update
Manager for this, this message is back on boot up. The download and
install finishes just
how to solve this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage notifications about this bug go to:
It still happens with 2.48build1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage notifications about this bug go to:
Yes, please file a separate bug. Having /tmp as a real filesystem on a
separate partition is an unusual configuration; I'm not sure why it
would behave wrongly but we should figure that out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Dear Steve,
It came out that this was just a consequence of a bug in e2fsck hanging up the
boot process when the external journal for / is on another partition. I filed
bug #1186331 which also contains a patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm still experiencing this on 13.04 x64 with up-to-date mountall. The
only difference is that /tmp is bound to another partition as specified
in fstab. If I press S to skip mounting it and continue booting and
then CTRL+ALT+F1 to access the tty and do a 'sudo mountall', the tmp
partition gets
same problem
workaround mounting /tmp to tmpfs, using fstab, works fine
tmpfs /tmp tmpfs defaults 0 0
...waiting for new version of mountall in updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have tested this with mountall 2.48 but I have still get this message
about /dev/mapper/cryptswap1 on booting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp
Yes, the message about /dev/mapper/cryptswap1 has a different cause that
we have not yet isolated. I thought there was a separate bug report
open about cryptswap1, but I'm not finding it now. Would you mind
opening a separate bug report for that?
--
You received this bug notification because
Here is the new bug report:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1153661
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or
This bug was fixed in the package mountall - 2.48
---
mountall (2.48) unstable; urgency=low
[ Steve Langasek ]
* Make sure we don't show the error message claiming a device is not
ready when we're actually already handling it but are just waiting for
related upstart jobs
Will it be included in quantal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage notifications about this bug go to:
I'm using Xubuntu 12.04.2 LTS with mountall 2.36.4 and I'm affected by
this bug too. It is causing the boot to take up a few minutes when
before the update to mountall it took about 30 seconds. I worked up a
temporary solution by changing fstab to include a line for /tmp as shown
below. This
So one thing that's happening here (per private duplicate bug #1122910)
is that the time spent running /etc/init/mounted-tmp.conf is being
counted against the idle timer for devices not showing up. It really
shouldn't, since the device is obviously present by that point and it's
just waiting for
** Branch linked: lp:ubuntu/mountall
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage notifications about this bug go
Sometimes I'm seeing this message with /dev/mapper/cryptswap1 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk drive for /tmp is not ready yet or not present
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
** Attachment added: mtab
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+attachment/3463862/+files/mtab
** Changed in: mountall (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: fstab
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+attachment/3463861/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Title:
The disk
Thanks. Could you please install the attached file as
/etc/init/mountall.conf on your system (not as mountall-debug.conf -
you'll have to rename it), reboot until you reproduce the problem, and
then attach the resulting /run/mountall.log to this bug?
** Attachment added: mountall-debug.conf
** Attachment added: mountall.log
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+attachment/3464122/+files/mountall.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091792
Thanks for the report. I've heard this issue reported informally on
IRC, but have not reproduced it myself.
Can you attach the /etc/fstab and /etc/mtab from the affected system?
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you
47 matches
Mail list logo
