*** This bug is a duplicate of bug 268808 ***
https://bugs.launchpad.net/bugs/268808
** This bug has been marked a duplicate of bug 268808
superblock last write time is in the future
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net
On Mon, Oct 12, 2009 at 9:38 AM, Luke wrote:
> so this fix solved that problem as well. This indicates the bug is NOT
> in mountall but somewhere else, as the clock should not be getting moved
> after boot to a wrong time anyway.
Read the whole thread, please. There is more than one bug.
Of cour
There is another workaround for this, though you will have to have a
root password for a fsck run at the end of daylight savings time: Set
the BIOS clock to local time, run sudo dpkg-reconfigure tzdata, set the
timezone to Universal or whatever they call it (I forgot the exact
designation), mak
Ubuntu Karmic beta (encrypted hard drive) updated to 11 Oct 09 in VBox
3.0.8 on Ubuntu 3.04.3 updated to 11 Oct 09.
Update:
Still having the same error message. We've had the superblock issue since late
alpha 5, latest updates in clean beta install won't even allow manual fsck
because it passes
David Gibson wrote:
> It seems like there are two main issues here. First, what is getting
> the dates wrong so that fsck reports the inconsistency on the
> filesystem. It sounds like that is covered in one of the other bugs
> referenced.
>
> Second problem, is why is mountall just jamming up and
It seems like there are two main issues here. First, what is getting
the dates wrong so that fsck reports the inconsistency on the
filesystem. It sounds like that is covered in one of the other bugs
referenced.
Second problem, is why is mountall just jamming up and not dropping back
to a shell t
** Package changed: mountall (Ubuntu) => util-linux (Ubuntu)
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Re-opening. It's clearly a bug (but I have not checked, if it is solved, i.e.
the workaround (buggy_init_scripts = 1) is still needed - because of bug
444563).
Assigning to mountall, but I'm not sure about it.
** Package changed: linux (Ubuntu) => mountall (Ubuntu)
** Changed in: mountall (Ubun
> I'm seeing the same thing in a virtualbox image of Karmic. I could try
> and do a screencast if you really need me to. It asks me to do an fsck
> every time I reboot. I'm running Karmic on a netbook too, but on there I
> don't see this.
Yes, amazing. I myself have the same experience, on the net
I'm seeing the same thing in a virtualbox image of Karmic. I could try
and do a screencast if you really need me to. It asks me to do an fsck
every time I reboot. I'm running Karmic on a netbook too, but on there I
don't see this.
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in
Scott James Remnant wrote:
>
> Daniel, the screenshots you provided CLEARLY show that the console is
> asking for your root password to fix the filesystem problem.
>
Is it? Sure? In my case the messages are flashing by, for all the 5 or
so partitions, in circles. If I gave you a screenshot, yo
> Daniel, the screenshots you provided CLEARLY show that the console is
> asking for your root password to fix the filesystem problem.
>
> Your report claims otherwise, thus I'm marking this Invalid.
a) I have no root password/user setup (this is the default!)
b) the "UNEXPECTED INCONSISTENCY" c
Can people stop reassigning bugs around to random packages?
Daniel, the screenshots you provided CLEARLY show that the console is
asking for your root password to fix the filesystem problem.
Your report claims otherwise, thus I'm marking this Invalid.
** Changed in: linux (Ubuntu)
Status:
Please check if this is similar to bug 433829 that I just encountered
after uprade to Alpha 6, and reported immediately.
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
You received this bug notification because you are a memb
It seems to me that the problem here is with the new upstart/initscripts
and the ordering of hwclock, tz, and mount. Every time I reboot my
Karmic system the clock goes back another 6 hours (my timezone is 6
hours from GMT) and every time I boot it complains that the superblock
was last mounted in
** Package changed: mountall (Ubuntu) => linux (Ubuntu)
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
** Package changed: ubuntu => mountall (Ubuntu)
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Description changed:
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 af
Not an e2fsprogs issue. Please assign a matching package, I don't know.
** Package changed: e2fsprogs (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Incomplete => Triaged
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432
Adding the following to options in /etc/e2fsck.conf, running update-initramfs
and rebooting fixed it for me:
buggy_init_scripts = 1
So, neither the fix for bug 423247 (first time reboot) nor bug 427822
(the more general one) have fixed it for, but this workaround does.
Finally, I'm in my KDE4 ag
Re-reading the text in Glenn's image, this looks like yet another
instance of bug 423247.
The workaround is to type 'fsck /dev/THEDEVICEINERROR' at the recovery
shell (don't type Ctrl+D, type your root password), and reboot.
If you don't have a root password, press Ctrl+D to continue booting if
y
Daniel Hahler's bug appears to be an instance of bug 423247, from the
messages appearing on the screen; Glenn Brumfield's appears to be
another bug completely, an ecryptfs-related one. Glenn, I would suggest
trying to find a bug related to ecryptfs and filing a new one if you
find none; your new bu
Assigning to e2fsprogs, that's where the message comes from at least.
I'm trying http://www.mail-archive.com/debian-bugs-
d...@lists.debian.org/msg388846.html now.
** Package changed: mountall (Ubuntu) => e2fsprogs (Ubuntu)
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the
Let me guess, Glenn: your timezone is GMT+4?!
Mine is GMT+2 and it always says that it has been mounted ~2h hours ago.
This appears to be an issue with timezone settings being applied to late
or not recognized correctly.
Probably no bug in mountall, I've filed it again by mistake anyways.
Scott
Ubuntu Karmic alpha 6 (encrypted hard drive) updated to 18 Sep 09 in
VBox 3.0.6 on Ubuntu 3.04.3 updated to 18 Sep 09.
Same error message after todays updates. We've had the superblock issue
since late alpha 5, latest updates in clean alpha 6 install won't even
allow manual fsck because it passes
I get no recovery shell - or I have not realized that I'm in there
already. (wouldn't I have to give a root password, which I do not
have?!)
The main problem appears to be that I get the fsck failure _all the
time_ since a few days, but it only appears on the first boot. Normally,
the second try w
It's hard to figure out what you think the problem is here, due to the
number of different things you report.
>From the pictures you attached, it looks like mountall is correctly
running fsck on each of your disks, and correctly identifies that one of
them has a problem.
It looks like it *waits*
Running fsck manually:
ubu...@ubuntu:/mnt$ sudo fsck /dev/md0
fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
/dev/md0 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pas
28 matches
Mail list logo
