[Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

[Sapa Holliday]

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 hdd for storage/ backup and never had any problems before but now it's a real hassle to boot into the second hard drive because of this bug.
update grub gives me this mess

[sudo] password for sapa: 
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.4.0-93-generic
Found initrd image: /boot/initrd.img-4.4.0-93-generic
Found linux image: /boot/vmlinuz-4.4.0-92-generic
Found initrd image: /boot/initrd.img-4.4.0-92-generic
Found linux image: /boot/vmlinuz-3.19.0-80-generic
Found initrd image: /boot/initrd.img-3.19.0-80-generic
Found linux image: /boot/vmlinuz-3.19.0-26-generic
Found initrd image: /boot/initrd.img-3.19.0-26-generic
Found elementary OS Freya (0.3.2) on /dev/sda1
done
sda is the old drive, the new one is sdb1 with some linux swap space.
It tries to mount a non-existing /tmp on every boot into the new drive, is completely ok when booting into the old drive.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1091792

Title:
  The disk drive for /tmp is not ready yet or not present

Status in mountall package in Ubuntu:
  Won't Fix
Status in mountall source package in Precise:
  Triaged
Status in mountall source package in Quantal:
  Won't Fix
Status in mountall source package in Trusty:
  Triaged

Bug description:
  I'm using Ubuntu 13.04 dev with mountall 2.46 and on booting I'm
  getting the message "The disk drive for /tmp is not ready yet or not
  present". But it seems that this message doesn't make any troubles.
  I'm able to use /tmp without any problems. Maybe something is trying
  to mount /tmp too early.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+subscriptions