How can I undo workaround of #14, I can not reach the recovery console
anymore.
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Bug still exists for me (same message as #20).
Workaround of #14 did not work for me (if you try it, DO NOT FORGET TO
CHANGE RIGHTS TO 755!)
I use encrypted home volumes
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification
Same bug here on a fresh Karmic install on a notebook. As far as I can
tell, the message started appearing after applying the "proposed"
updates.
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
/home/waiting for UUID=e2cca39c-70bb-46be-a5d1-2fdafe1dd2a1
Press ESC to enter a r
Xzmgirfx gxcfrknmndetc, r
On Jan 15, 2010 11:32 AM, "LuSio" wrote:
But it's resolved? I was affected now...
-- 'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859 You rec...
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs
Xsdgee
On Jan 15, 2010 11:32 AM, "LuSio" wrote:
But it's resolved? I was affected now...
-- 'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859 You rec...
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You receive
But it's resolved? I was affected now...
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Screenshot
** Attachment added: "karmic_boot_msg.png"
http://launchpadlibrarian.net/37403308/karmic_boot_msg.png
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Same bug on Karmic i386 with all updates (mountall 1.0, usplash 0.5.49).
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
I ran into this on upgrading from Kubuntu 9.04 to 9.10 - booting freezes
and gives a screen asking for ESC to drop to a rescue shell - mountall
is at V1.0, so unless the above changes aren't in the online updates
yet, I'm fairly sure the problem isn't fully fixed yet. The problem
appears to be th
I'm affected as well : (ubuntu 9.10 amd64 on dell lattitude E6500). At
present I can boot with the live CD but I can't boot from the disk
itself. It started after I edited fstab to mount nas shares. to the best
of my knowledge there are no errors in the fstab file and in any case
the modified/added
** Changed in: mountall (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: mountall (Ubuntu)
Status: Confirmed => Fix Released
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a memb
me too. Same bug, even with mountall 1.0 and usplash 0.5.49
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
P-S: I experience the bug, even with mountall 1.0.
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
I have exactly the same problem. It happens to me at every boot. I have
checked that the ouput of a "blkid" command is the same as the content
of my /etc/fstab so it would be nice to know what is causing the bug.
Also, it gives me the opportunity to press ESC to access a recovery
shell, which then
"re OK, I found the solution"
I don't think this has anything to do with whether the UUID or /dev/sd??
is used in fstab to identify the drive. Nor in my case does disabling
drive checking by zeroing out fstab column 6 (last digit). It stops
checking alright, but I still finish up with a read-onl
OK, I found the solution:
http://creativeinstantia.blogspot.com/2009/11/upgrade-to-karmic-koala-kubuntu-910.html
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
How am I supposed to fix this bug by updating Ubuntu, if I cannot even
boot into it??
It stops booting after:
/home waiting for UUID=blahblafadfasasffsafsafa
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you
** Attachment added: "waiting_fstab.txt"
http://launchpadlibrarian.net/35129386/waiting_fstab.txt
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Attachment added: "dmesg"
http://launchpadlibrarian.net/35129304/waiting.txt
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I have just been getting this message appearing on my usplash screen;
except it's trying to mount my ext3 /home.
The system starts up normally except for this message, which also offers
to open a recovery shell.
As far as I can tell, the message started appearing after applying the
"proposed" upd
This bug was fixed in the package mountall - 1.0
---
mountall (1.0) karmic; urgency=low
[ Kees Cook ]
* Call out to restorecon after mounting tmpfs filesystems. LP: #456942.
[ Johan Kiviniemi ]
* Fix a bug introduced by the 0.2.6 change. In certain situations, we’d
quit
** Branch linked: lp:~ubuntu-core-dev/ubuntu/karmic/mountall/ubuntu
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Changed in: mountall (Ubuntu)
Status: New => Fix Committed
** Changed in: mountall (Ubuntu)
Importance: Undecided => Low
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Changed in: mountall (Ubuntu)
Milestone: None => ubuntu-9.10
*
** Tags added: ubuntu-boot-experience
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34326517/Dependencies.txt
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the relevant fstab entry:
/dev/sda1 /media/sda1 ext3defaults0 0
--
'cannot yet be mounted', 'waiting for /dev/sda1'
https://bugs.launchpad.net/bugs/459859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
26 matches
Mail list logo
