*** This bug is a duplicate of bug 436076 ***
https://bugs.launchpad.net/bugs/436076
I had this issue while upgrading to ext4 so I added the FS features
and touched the /forcefsck.
I was able to get out of the trap... but it drove me insane...
1. enter GRUB and modify the root= parameter
*** This bug is a duplicate of bug 436076 ***
https://bugs.launchpad.net/bugs/436076
Screenshot taken via IPMI
** Attachment added: "fsck.jpg"
http://launchpadlibrarian.net/43561087/fsck.jpg
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You receive
*** This bug is a duplicate of bug 436076 ***
https://bugs.launchpad.net/bugs/436076
** This bug has been marked a duplicate of bug 436076
system clock not adjusted when hardware clock in localtime
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You r
I'm afraid I can't provide a screenshot, but I can confirm that the bug
happens. I've had to boot into an alternate installation after seeing
fsck run gazillions of times. It even does this after booting with
init=/bin/bash and manually fscking the filesystems. The diagnosis above
of timezone issue
On Mon, 2009-09-21 at 19:07 +, Renzo Bagnati wrote:
> Well, if this is the correct behaviour, then I still wonder why the fsck loop
> lasts so long.
>
Because you have about a dozen filesystems that are all being checked.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
mountall loops in
Well, if this is the correct behaviour, then I still wonder why the fsck loop
lasts so long. The first time it happened to me I observed the same messages
pass on the screen for at least 5 minutes. I resisted the temptation to press
the reset key, but I suspect that most users would have pressed
** Changed in: mountall (Ubuntu)
Status: In Progress => Invalid
** Changed in: mountall (Ubuntu)
Milestone: ubuntu-9.10-beta => None
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubu
** Changed in: mountall (Ubuntu)
Status: Invalid => In Progress
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
The screenshots provided by Renzo Bagnati show the correct behaviour,
each of his filesystems has failed and once checks are complete mountall
drops to a shell to allow the user to repair the problem
** Changed in: mountall (Ubuntu)
Status: Incomplete => Invalid
--
mountall loops indefini
** Attachment added: "mountall-fsck-2.jpg"
http://launchpadlibrarian.net/32037436/mountall-fsck-2.jpg
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I have experienced the same bug on my home box, which has several partitions,
one of which has karmic installed.
Yesterday evening I booted first a jaunty partition, and then the karmic
partition to make a dist-upgrade. After the upgrade I rebooted karmic and saw
the mountall loop on fsck failur
** Attachment added: "mountall-fsck-1.jpg"
http://launchpadlibrarian.net/32036317/mountall-fsck-1.jpg
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
A kludgey fix is to have in /etc/e2fsck.conf something like:
[options]
buggy_init_scripts = 1
The trigger for this seems to be an incomplete/faulty restore of the syetm
time from the hardware clock before running the fsck -a. To the best I can
see, hwclock is not being set/corrected at all befor
** Changed in: mountall (Ubuntu)
Milestone: None => ubuntu-9.10-beta
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
The fsck failure is caused by the superblock's last mount time being
into the future. The message printed is fsck repeatedly complaining that
each of my 3 partitions has that last mount time in the future. I'm in a
GMT-04 timezone, and the time difference being printed by fsk is exactly
those 4 hou
On Thu, 2009-09-17 at 15:52 +, Rick Spencer wrote:
> set to critical as it blocks a service from starting or the computer
> from booting
>
Then all my bugs are critical. Please don't do that.
Scott
--
Scott James Remnant
sc...@canonical.com
--
mountall loops indefinitely on fsck failure
** Changed in: mountall (Ubuntu)
Importance: Critical => High
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
set to critical as it blocks a service from starting or the computer
from booting
** Changed in: mountall (Ubuntu)
Importance: High => Critical
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
--
mountall loops indefinitely on fsck failure
https://b
Test-tools: please don't jump onto other people's bug reports. If you
are having problems, please open a new bug so that I can triage your
issues independently.
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you ar
Hello,
the last thing the users is seeing, is that fsck message, but it doesn't
exactly hang there,
it hangs inside mountall tool.
For example, I have attached my fstab, same symptom.
If I comment out line 10, the one with aufs, and the 2nd one with mountpoint
/usr,
it continues to boot.
Once l
** Changed in: mountall (Ubuntu)
Importance: Undecided => High
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I can't see anything in the code that would cause fsck to loop in case
of failure, it should instead cause mountall to exit and present you a
shell.
If possible could you get a screenshot (if in a VM) or photo of the
screen as mountall loops over fsck repeatedly.
Thanks
** Changed in: mountall
** Description changed:
- if there is a failure in fsck, the new upstrat-based mountall will loop
+ if there is a failure in fsck, the new upstart-based mountall will loop
(almost) indefinitely trying to mount/check partitions that keep on
- failing. Eventually the script dies with some erros th
23 matches
Mail list logo
