@ asmrl
when it happens, you can solve it like i do, just enter manual recovery and
mount the partition manually;
In my case:
mount /dev/mapper/vg0_lv_tmp /tmp
exit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I'm getting the error
"The disc drive for /tmp is not ready yet or not present" every random number
of boots.
I've tried:
root@Lenovo:~# sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgra
If i didn't know how to mount the partition, i would be unable to boot
the system at all, since it doesn't recover except skipping the mounting
operation, why in case of / or /home would be even more serious than in
my case
--
You received this bug notification because you are a member of Ubuntu
I'm also experiencing this.
I use LVM and it seems it doesn't happen when doing reboot, only from cold start
In my case, the kernel always complains about the /tmp
lisrferre@porf0003n:~$ sudo lvdisplay | grep "LV Name"
LV Name/dev/vg0/lv_root
LV Name/dev/vg0/l
** Changed in: udev (Ubuntu)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive for / is not ready yet or not present
--
ubuntu-bu
There is some race in the system initialization.
On a laptop (natty, kubuntu 64bit, with LVM) every 10 boots I am getting
at least once the message that
The disc drive for /home is not ready yet or not present
to boot, one needs to get to the recovery shell and manually mount the
disk.
This IM
yeah i wrote that whilst fixing my own workstation, apt-get install -f
isnt needed.
to clarify for anyone else:
Choose M to enter recovery console.
where sda1 is my installation partition:
$ mount -w -o remount /dev/sda1 /
$dpkg --configure -a
mine got as far as mysql then hung again, i reboo
Thanks a lot, that solved my problem. The dpkg command took very long,
it actually installed Ubuntu 11.04, I guess from where it was left. Then
I didn't even need the last command, first the computer switched off,
which got me nervous, but the system was up and working after switching
it on. Thanks
you basically have to remount / from recovery shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive for / is not ready yet or not present
--
ubuntu-bugs mailing
just to clarify: /dev/sda1 is MY partition. make sure you choose your
own
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive for / is not ready yet or not present
-
http://ubuntuforums.org/showthread.php?t=1735240
Choose M
# mount -w -o remount /dev/sda1 /
dpkg --configure -a
apt-get install -f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[na
I'm also pretty much stuck here, after choosing M, while being root,
entering apt-get install -f yields:
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run 'dpkg --configure --a' to
correct the problem.
Then when enter dpkg --configure
** Changed in: udev (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive for / is not ready yet or not present
--
ubuntu-
Is your /var partition separate from /?
fdisk -l should show the available partitions. Wiping the directory is really
uncommon in this case, probably it is simply not mounted.
Robert Muil <753...@bugs.launchpad.net> wrote:
>Hi all, I've been hit by this one, and for the time being cannot solve i
An addendum to my last comment: it seems the entire /var/lib directory
has been wiped out. I am going to run a fresh CD install. Not good news
for ubuntu, this is a pretty serious gotcha.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi all, I've been hit by this one, and for the time being cannot solve it.
Attempting to run apt-get install -f gives me:
"E: Could not open lock file /var/lib/dpkg/lock - open (2: No such file or
directory)
E: Unable to lock the administration directory (/var/lib/dpkg), are you root?"
I am roo
[This is a total showstopper for everyone that we are trying to hard to
encourage to use Linux. Once any of those hit by this, will never ever
come back. We should have another category for this type of bugs. But
that gets me off-topic. I better file an RFE for this.]
The situation shows - aside f
Is there a fix for this? The upgrade has properly completed, but I still
get this error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive for / is not ready yet or
@ Sense Hofstede
Excuse me, my fault, should have investigated further. Didn't mean to offend
you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive for / is not re
@ Sense Hofstede
Can you please stop with infecting every bug with this specific
unrelated problem that you got?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive f
** Description changed:
UPDATE:
This is not udev bug. If you experience this issue please complete the
- upgrade (sudo apt-get update; sudo apt-get upgrade). Broken branding-
- ubuntu package was causing apt to stop prematurely leaving the system in
- an inconsistent state.
+ upgrade (sudo
Yes, this is not a valid bug for udev and completing upgrade makes the
system bootable again.
** Changed in: udev (Ubuntu)
Status: Confirmed => Invalid
** Attachment removed: "UdevDb.txt"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/753853/+attachment/1995842/+files/UdevDb.txt
It seems that this is caused by the fact that branding-ubuntu failed to
update to 0.6 today, crashing aptd and interrupting the udev update
process. Running dpkg --configure -a using chroot fixed the problem for
me. All thanks to the great Stéphane Graber. Thank you for your help!
--
You received
apport information
** Description changed:
Binary package hint: udev
After the latest update my Acer aspire One stopped booting:
init: udevtrigger main process (297) terminated with status 1
init: udevtrigger post-stop process (300) terminated with status 1
init: udevmonitor main
I can confirm that the latest update for udev on Natty has left the
system in an unbootable state. I can confirm that the four processes
from udev die as listed in the bug's description. This seems to be a
pretty critical bug.
--
You received this bug notification because you are a member of Ubun
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753853
Title:
[natty] The disc drive for / is not ready yet or not present
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
26 matches
Mail list logo
