** Changed in: gparted (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106565
Title:
Boot interrupted after feisty upgrade--gives a command prompt for no
No response received in a month, please re-open if you can supply the
requested information.
** Changed in: udev (Ubuntu)
Status: Incomplete = Invalid
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
https://bugs.launchpad.net/bugs/106565
You
When this occurs, please do ls -l /dev/disk/by-uuid and supply the
output
** Changed in: udev (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: udev (Ubuntu)
Importance: Undecided = High
** Changed in: udev (Ubuntu)
Importance: High = Medium
--
Boot interrupted after feisty
** Changed in: udev (Ubuntu)
Assignee: Brian Murray (brian-murray) = (unassigned)
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
https://bugs.launchpad.net/bugs/106565
You received this bug notification because you are a member of Ubuntu
Bugs, which
Just a few comments:
fsck died with exit status 8 - this means Operational error and not file
system error. It seems like it tries to check a device that doesn't exist. All
the text below CONTROL-D is due to another bug (bug #121992), where the
bashrc depends on stuff not in the path, and the
Not an issue for me. As I said last May updating non-functional fstab
entries provided a workaround. Now running Hardy and haven't seen any
repeat in over a year.
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
https://bugs.launchpad.net/bugs/106565
You
Yes, I've had the same problem subsequently on a different computer
after installing Hardy. On the original computer, I was able to resolve
the problem by changing the UUIDs in fstab to /dev/sdax. (I'm no longer
using that computer though.)
I think what caused it on the computer that currently
Assigning to udev.
Joehill, can you confirm that you've had the later issue after you've
changed a partition and not during a new installation ?
** Changed in: udev (Ubuntu)
Sourcepackagename: None = udev
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
Yes, here's what happened: I installed Hardy, then we used gparted on
the live CD to reformat and resize the /home partition. Then when we
restarted, we got the same command line I described above. When we do
Ctrl-D, it starts normally. Thanks.
--
Boot interrupted after feisty upgrade--gives
Thanks. I can see the point. I think that what happens is that when
you've updated your partition the uuid has changed but the fstab on your
primary hd has not been updated. This is even more complicated because
you've done it from the a livecd.
When you're doing this kind of operation, you can
You reported this bug a while ago and there hasn't been any activity in
it recently. Is this still an issue for you? Thanks in advance.
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
https://bugs.launchpad.net/bugs/106565
You received this bug
This might be coincidence but I updated fstab while working on an
unrelated problem and problem went away. A few updates later it came
back (I was re-booting a lot to test some fstab changes) so I sort of
noticed. Back tracking on the changes I'd made found it appeared to be
related to having
I had a similiar problem on upgrading to Feisty. I would get an error
similiar to this: fsck.ext3: No such file or directory while trying to
open /dev/.tmp-254-3 and the control-D to continue message, but after
the boot process the partitions would mount correctly and appeared error
free. in
Hi,
I too are seeing the fsck problem since Feisty upgrade but not on every re-boot
(just on most). Appear to be identical apart from last digit of /dev/.tmp-254-7
and no problem with system clock.
Contents of fstab are:
# /etc/fstab: static file system information.
#
# file system mount point
Just realized I never attached my fstab. Here it is:
# file system mount point type options dump pass
proc/proc procdefaults0 0
# /dev/hda7 -- converted during upgrade to edgy
UUID=c7bdef3c-9738-4421-ad3f-49fb85b101cc / ext3
I have the same problem, except that the mentioned file is
/dev/,tmp-254-3
My fstab is:
# /etc/fstab: static file system information.
#
# file system mount point type options dump pass
proc/proc procdefaults0 0
#/dev/hda2
Sorry, the correct filename in the above comment is /dev/.tmp-254-3
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
https://bugs.launchpad.net/bugs/106565
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Here is a screenshot when the boot stops.
** Attachment added: screenshot.png
http://librarian.launchpad.net/7415067/screenshot.png
--
Boot interrupted after feisty upgrade--gives a command prompt for no apparent
reason
https://bugs.launchpad.net/bugs/106565
You received this bug
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please add the contents of you '/etc/fstab'? Thanks
in advance.
** Changed in: Ubuntu
Assignee: (unassigned) = Brian Murray
Status: Unconfirmed = Needs Info
--
Boot interrupted after feisty
19 matches
Mail list logo
