| 2009-09-17 19:32:40 |
Daniel Hahler |
bug |
|
|
added bug |
| 2009-09-17 19:33:47 |
Daniel Hahler |
attachment added |
|
dscf2274.jpg http://launchpadlibrarian.net/31982913/dscf2274.jpg |
|
| 2009-09-17 19:35:10 |
Daniel Hahler |
attachment added |
|
dscf2275.jpg http://launchpadlibrarian.net/31982949/dscf2275.jpg |
|
| 2009-09-17 19:35:58 |
Daniel Hahler |
attachment added |
|
dscf2276.jpg http://launchpadlibrarian.net/31982969/dscf2276.jpg |
|
| 2009-09-17 19:36:46 |
Daniel Hahler |
attachment added |
|
dscf2277.jpg http://launchpadlibrarian.net/31983056/dscf2277.jpg |
|
| 2009-09-17 19:37:47 |
Daniel Hahler |
attachment added |
|
dscf2278.jpg http://launchpadlibrarian.net/31983072/dscf2278.jpg |
|
| 2009-09-17 19:38:38 |
Daniel Hahler |
attachment added |
|
dscf2279.jpg http://launchpadlibrarian.net/31983096/dscf2279.jpg |
|
| 2009-09-17 19:39:26 |
Daniel Hahler |
summary |
UNEXPECTED INCONSISTENCY: fails to boot |
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future") |
|
| 2009-09-17 19:40:44 |
Daniel Hahler |
description |
Binary package hint: mountall
I get "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY" on booting, then it fails to start or provide me a shell.
I had this happening since some days already: the first boot would tell me that fsck failed, but a reboot (straight after pressing Ctrl-D) went through without any problems.
Now (IIRC) Ctrl-D did not do anything. I've used Alt-SysRq-K, which caused a kernel panic ("trying to kill init"). |
Binary package hint: mountall
I get "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY" on booting, then it fails to start or provide me a shell.
I had this happening since some days already: the first boot would tell me that fsck failed, but a reboot (straight after pressing Ctrl-D) went through without any problems.
Now (IIRC) Ctrl-D did not do anything. I've used Alt-SysRq-K, which caused a kernel panic ("trying to kill init").
I'm not sure if all that FAIL is caused by "Superblock last mount time is in the future". It's mentioned in the e2fsprogs changelog at least:
* E2fsck will now print much fuller information when the last mount
time or last written time is in the future, since most people can't
seem to believe their distribution has buggy init scripts, or they
have a failed CMOS/RTS clock battery. |
|
| 2009-09-17 20:07:19 |
Scott James Remnant (Canonical) |
mountall (Ubuntu): importance |
Undecided |
Medium |
|
| 2009-09-17 20:07:19 |
Scott James Remnant (Canonical) |
mountall (Ubuntu): status |
New |
Incomplete |
|
| 2009-09-19 00:33:15 |
Glenn Brumfield |
attachment added |
|
Karmic_alpha6.png http://launchpadlibrarian.net/32047186/Karmic_alpha6.png |
|
| 2009-09-19 02:56:03 |
Daniel Hahler |
affects |
mountall (Ubuntu) |
e2fsprogs (Ubuntu) |
|
| 2009-09-19 03:29:30 |
Daniel Hahler |
affects |
e2fsprogs (Ubuntu) |
ubuntu |
|
| 2009-09-19 03:29:47 |
Daniel Hahler |
ubuntu: status |
Incomplete |
Triaged |
|
| 2009-09-19 13:50:35 |
Daniel Hahler |
description |
Binary package hint: mountall
I get "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY" on booting, then it fails to start or provide me a shell.
I had this happening since some days already: the first boot would tell me that fsck failed, but a reboot (straight after pressing Ctrl-D) went through without any problems.
Now (IIRC) Ctrl-D did not do anything. I've used Alt-SysRq-K, which caused a kernel panic ("trying to kill init").
I'm not sure if all that FAIL is caused by "Superblock last mount time is in the future". It's mentioned in the e2fsprogs changelog at least:
* E2fsck will now print much fuller information when the last mount
time or last written time is in the future, since most people can't
seem to believe their distribution has buggy init scripts, or they
have a failed CMOS/RTS clock battery. |
Binary package hint: mountall
I get "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY" on booting, then it fails to start or provide me a shell.
I had this happening since some days already: the first boot would tell me that fsck failed, but a reboot (straight after pressing Ctrl-D) went through without any problems.
Now (IIRC) Ctrl-D did not do anything. I've used Alt-SysRq-K, which caused a kernel panic ("trying to kill init").
I'm not sure if all that FAIL is caused by "Superblock last mount time is in the future". It's mentioned in the e2fsprogs changelog at least:
* E2fsck will now print much fuller information when the last mount
time or last written time is in the future, since most people can't
seem to believe their distribution has buggy init scripts, or they
have a failed CMOS/RTS clock battery.
WORKAROUND:
Adding the following to "[options]" in /etc/e2fsck.conf, running update-initramfs and rebooting fixed it for me:
buggy_init_scripts = 1 |
|
| 2009-09-19 18:17:58 |
MichalM |
removed subscriber MichalM |
|
|
|
| 2009-09-19 19:12:23 |
Xandros Pilosa |
affects |
ubuntu |
mountall (Ubuntu) |
|
| 2009-09-19 19:20:57 |
Xandros Pilosa |
affects |
mountall (Ubuntu) |
linux (Ubuntu) |
|
| 2009-09-22 00:31:53 |
Scott James Remnant (Canonical) |
linux (Ubuntu): status |
Triaged |
Invalid |
|
| 2009-10-07 21:56:24 |
Daniel Hahler |
affects |
linux (Ubuntu) |
mountall (Ubuntu) |
|
| 2009-10-07 21:56:24 |
Daniel Hahler |
mountall (Ubuntu): status |
Invalid |
Triaged |
|
| 2009-10-07 23:03:58 |
Scott James Remnant (Canonical) |
affects |
mountall (Ubuntu) |
util-linux (Ubuntu) |
|
| 2009-10-12 12:31:51 |
Scott James Remnant (Canonical) |
marked as duplicate |
|
268808 |
|
| 2012-09-11 21:48:24 |
Glenn Brumfield |
removed subscriber Glenn Brumfield |
|
|
|
