*** This bug is a duplicate of bug 554737 ***
https://bugs.launchpad.net/bugs/554737
** Also affects: linuxmint
Importance: Undecided
Status: New
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a
*** This bug is a duplicate of bug 554737 ***
https://bugs.launchpad.net/bugs/554737
When I upgraded to Ubuntu 10.4 (Lucid), fsck began taking too long to
complete. I once let it run for two hours before stopping it at 91%
complete.
As Neil wrote on 2010-05-15. Updating mountall eliminated
*** This bug is a duplicate of bug 554737 ***
https://bugs.launchpad.net/bugs/554737
Latest mountall update in lucid has fixed bug
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs,
Just to confirm that this is happening to me as well (physical machines,
as well as virtual machines), with all machines updated as of today (Apr
13, 2010).
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a
This freeze also happened to me on the Ubuntu Netbook Remix 10.04, on a asus
eee 901 with ssd and ext2 file system.
If the system was not properly shutdown, I think it is recommended to run fsck.
To solve the problem I booted from the Ubuntu USB disk and used the console to
run fsck:
Code:
possible duplicates 561317 ? 561312 ? 559761 ? 555753 ? 554737 ? 549824
? 538810 ?
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
no matter how you initiate fsck, be it by 'touch /forcefsck'' or by manually
increasing mount count by 'tune2fs -C no' fsckk either silently aborts or
with latest kernel update to 2.6.32-20 interrupst boot process ending with a
dead system.
Checked with root filesystems ext3 and ext4.
Se also
After creating /forcefsck all I get is this at startup by removing the
quiet splash options in grub (screenshot attached). And it stays
there. Video seems to be dead, I can't even change VT but a
control+alt+del seems to work ok (at least the system reboots).
Notice I can't boot the system
You might want to check
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/554737
I think it's what is talked about here.
Same symptoms.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Yes indeed; looks as if this might well be the same bug. Good news, if
so, as there seems to be some progress being made.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Further to my comments #28, #29, and #30: to confirm, the issue appears to be
unrelated to nvidia, xorg.conf, etc. Just had the same happen on my HP
G60-530US Notebook. That machine is using:
*-display:0
description: VGA compatible controller
product: Mobile 4 Series
*** This bug is a duplicate of bug 554737 ***
https://bugs.launchpad.net/bugs/554737
** This bug has been marked a duplicate of bug 554737
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
--
Lucid boot failed to complete after fsck
I also have this bug with 70% and freeze
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
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
Same here freeze at 71 % ..
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
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
Is it possible to make this bug critcal? Consequently freezes
(in)directly caused by a fscheck at boot voor many users..
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: sysvinit (Ubuntu)
Status: Confirmed = In Progress
** Changed in: sysvinit (Ubuntu)
Status: In Progress = Confirmed
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of
Reassigning to mountall for now, I seriously doubt sysvinit has anything
to do with this.
** Package changed: sysvinit (Ubuntu) = mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Importance: Undecided = High
--
Lucid boot failed to complete after fsck
I have made the following observations:
Although I am unable to cancel the disk checks by pressing 'C', when the
plymouth-animation (red white dots) is running, fsck is running in the
background doing the disk checks
The progress indicator percentage seems to increase while the disk check is
Similar experience In Lucid with Dell Mini-9, EXT4. But FSCK does not
finish or continue in the background and it freezes at 70%. Pressing C
does not cancel at any point in the check but I can get to TTY and
remove forcefsck. I have yet to get fsck to complete a full check but I
have not tried
I can confirm what Rune Svendsen describes!
the updates of udisks, libparted0, mountall (and other updates from the last
few days if involved at all) - may have changed the percentage level I am able
to get to (- now 97%, before there was no chance to get higher than 71%) but
the result is
Same here. However, I can reboot by pressing ctrl+alt+del.
It seems like the fsck goes up to 70% and then it just goes up in 1%
stages until it freezes completely. That's weird. Also, it always says 1
of 1 disk, then 1 of 2 disks and after that, 1 of 3 disks. Always
cheking 3 disks? That's weird.
Same thing on a Dell M1330, sticking at 90%.
This is a real showstopper bug.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same thing on Lenovo T400 2767-R9U
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
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
After using 'sudo touch /forcefsck' trying to solve a different issue,
my Acer AOD250 froze on 71% as well. Had to boot into Recovery Mode to
escape.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of
Could ureadahead have something to do with this?
I noticed this on my laptop when fooling around with ureadahead.
After testing in a vm I can do the following:
sudo touch /forcefsck
reboot.
fsck stalls at 70% for a sec, and the screen jumps directly to the desktop.
ls / shows forcefsck still
also after a successful reboot, I get a crash report for plymouthd
(#553745)
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Nevermind about ureadahead. I uninstalled it and got the same behavior.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Have the same problem here, gets stuck at 71%.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
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
** Tags added: lucid
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
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
Isn't that bug 553745 ?
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
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
bugs out after removing nvidia* !
Before, I was stopped with fsck @71% and just access to #2.
Problem with gdm-start/stop
I tried to remove nvidia* and reboot : display problem detected by
ubuntu, corrected and reboot : it works.
But no 3D effect n_n
Is the bug comes from nvidia driver ?
--
I doubt if the problem is with nVidia - I had (or have? - it happened to
me once so far) this bug on a Dell Mini 10v netbook with Intel graphics.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of
I understand ; I just reinstall nvidia-185 driver and bug re-happened.
This is my experiment ; maybe a way to find the problem ? :)
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which
This problem has hit me twice recently. The first time (iirc) I was able
to ctrl-alt-del at the Plymouth screen, and upon reboot it briefly
flashed the fsck message again but booted successfully. The second time
was just this morning (with a fully up to date system), and I had to
ctrl-alt-f2 to
Just happened to me as well (stuck at 75% complete). However I am able
to ssh into the machine. This happened after I put an previous karmic
xorg.conf back into /etc/X11/ to test an nvidia-96 problem (#523108
#539196) and rebooted.
2.6.32-19-generic (updated as of this morning)
$ apt-cache
The xorg.conf doesn't appear to have been the problem. Rebooted leaving
the xorg.conf in place no problem now. So much for that theory.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs,
'sudo touch /forcefsk' and reboot results in 75% complete again. Moved
the xorg.conf file completely out reboot - does the same (75%
complete), so it's repeatable. I can only reboot completely after
removing the /forcefsk file.
--
Lucid boot failed to complete after fsck
** Changed in: sysvinit (Ubuntu)
Status: New = Confirmed
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
did a little bit of experimenting:
removed splash from grub boot
and updated grub
forced a next boot check
and rebooted
the boot ended with a black tty screen with a blancking curser
control alt f1 opened a new tty with a login screen
start x / logged in
and everything worked fine
the control alt
Having the same issue. The checker stops at 2 points for me. With 1 HDD,
it stops at 71%, with 2 HDD it stops at 80%.
No, way to skip the checker by pressing C
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a
I had the same issue as well 2 days ago. I was stuck at 47% . I couldn't
boot into recovery mode either - kept getting something about needing to
run fsck manually.
I had to reinstall since I didn't have my live USB with me and my CD
drive doesn't work. The only USB drive I had at the time was
got this yesterday:
first boot: hang with fsck at 71 %
2d boot hang at 92 %
third boot boots well
since, all other boots are normal (but fsck not called at time, wait and
see next time)
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug
This sounds rather worrying and should be fixed before the RC. Is
sysvinit really the right component?
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@amano, That's a good question. As you can see, it hinted at
sysvinit.
aptitude search e2fsck
p e2fsck-static
But package e2fsck-static is not installed.
Since Scott James Remnant replied, I would think he would have changed
the package, if it was wrong.
--
Lucid boot failed to complete
Now that I think about it, I don't think fsck package is the problem.
mountall is.
If you issue a 'sudo touch /forcefsck', after it fails to complete, your
left with forcefsck file still intact.
Its mountall duty to remove it. It can't because it doesn't finish.
mountall.conf:
exec
My main desktop just hit this very problem today. at 70% it stops and
nothing else happens.
this has raid-1 disks so I'm afraid of booing from another source and
having to do all that manually.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this
This happened to me on Saturday after performing a large update. It
stopped at 73% during disk checking. After forcefully shutting down my
laptop by holding the power button and rebooting, system booted up
normally.
--
Lucid boot failed to complete after fsck
Yes, also the same freeze with the natural unforced
bootcheck..
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same for me on a Dell MIni 9; whether forced or natural, fsck hangs at
70% for a short time, then advances to 71% and the system promptly
freezes altogether.
If I shut down with the off button and boot into the recovery mode of
the same (latest) kernel, fsck completes and is followed by a lot of
Could this be related?
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/487744
I don't know when this mountall fix was released - might it have broken
something?
I'm pretty sure this behaviour is something that started within the last few
days.
--
Lucid boot failed to complete after
Confirmed
+ every boot a short glims of the message Your disk needs to be checked for
errors, this may take some time
+ same hangs after a 'sudo touch /forcechk' until I boot in recovery mode
Working on a 66bit with ext4 and the option data=writeback
--
Lucid boot failed to complete after fsck
I installed todays, Apt4, daily-live. Same problem.
What I did notice is a difference between aptitude version and mountall
version.
aptitude show mountall = Version 2.10
mountall --version = 2.8
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received
On Fri, 2010-04-02 at 20:33 +, vmc wrote:
Both installs have the same mountall and esfsck version numbers.
What are the version numbers of mountall and plymouth?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Lucid boot failed to complete after fsck
What are the version numbers of mountall and plymouth?
mountall version 2.8
e2fsck version 1.41.11
Vern
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same problem - fschk seems to hang (in my case at different
%-stages).
Noticeably - The scan process has already started before the number of disks to
be checked is suddenly increased from foo bar...% 1 of 1 to foo bar...% 1 of
2 !
The option to interupt with C is visible (all the
damn I forgot:
- version of mountall is 2.10
Any hints on other attachments that may help is appreciated
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I used todays daily-live APR3, to install with same results.
'sudo touch /forcefsck' , and rebooting.
Now mountall version = 2.10
e2fsck version = 1.41.11
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because
I'm sorry.
plymouth version = 0.8.1-4
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
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
I also noticed that on the Lucid install that does work I get the following
message
when I forcechk that partition :
Your disk needs to be checked for errors, this may take some time
press C to skip this test
On the Lucid install that fails I only get:
Checking disk 1 of 1
Something similar happened to me, the filesystem stopped at 78% for over
20 minutes. I couldn't figure out how to get to another vty or skip (as
vmc notes, the press C to skip message was not visible), so I
rebooted. Things booted up normally then.
--
Lucid boot failed to complete after fsck
60 matches
Mail list logo
