** Changed in: clock-setup (Ubuntu Karmic)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/423247
Title:
Superblock last mount times cause fsck to fail
To manage
reopening for karmic, as I've got a reproducable scenario:
- use the most recent karmic cd to get a shell,
mount your unstable /, /boot, bind-mount /dev /sys, /proc
issue grub-install /dev/sda
result: unstable bails out with errors (where the time is set
correctly), while the karmic cd sets the
I has made 3 Ubuntu 9.10 Installations (from disks shipped from
shipit.ubuntu.com) for my friends. All 3 computers can't boot from time
to time with Superblock last mount time error message. My friends
can't solve this problem themselv, because of very low computer
knowledge, Setting UTC=no in
Sorry about my english
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
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
The problem I was experiencing seems to be fixed with one of the recent
updates.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
since upgrading to karmic (release), I get the following very often:
/dev/sda1: Superblock last mount time (Thu Sep 24 20:58:00 2009,
now = Thu Sep 24 19:59:23 2009) is in the future.
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
** Tags added: iso-testing
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
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
** Also affects: clock-setup
Importance: Undecided
Status: New
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I seem to have some of the same, but with some additional errors.
Screenshot of terminal error:
http://picasaweb.google.com/lh/photo/PoGSZCs0jxecU8t2xLpYog?authkey=Gv1sRgCM3I
--H5qKjNCAfeat=directlink
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You
related: #422869
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
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 have instaled alpha 5.
- reboot and reboot always OK.
- after upgrading all the system to up-to-date packages, I got a fsck alert.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
** Changed in: clock-setup (Ubuntu Karmic)
Status: Fix Released = Incomplete
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
As noted in https://bugs.launchpad.net/ubuntu/+source/clock-
setup/+bug/423247/comments/10, this bug is about a fsck on first reboot
after install. There have been other (*many* other) bugs related to
spurious fscking due to timezone problems, including one recent one that
is a kernel bug. I'm
the big problem is that there is no way to set/unset UTC time, gnome utlities
for clock settings are not properly working.
I fixed the problem editing /etc/default/rcS, UTC=no.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug
Still here for me in a virtualbox installation:
- Install alpha 5, reboot == OK
- After, upgrade the all system to up-to-date packages, reboot == fsck alert.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you
non-first-boot-after-install issue appears to be bug 427822
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
In my case, leaving the system shut down for a day resulted in a clean
boot, but subsequent boot/reboots threw the error message. I think that
the non-first-boot-after-install issues may be because the system is not
shut down long enough to get beyond the time error.
--
Superblock last mount
In my case, leaving the system shut down for a day resulted in a clean
boot, but subsequent boot/reboots threw the error message. I think that
the non-first-boot-after-install issues may be because the system is not
shut down long enough to get beyond the time error.
--
Superblock last mount
In my case, leaving the system shut down for a day resulted in a clean
boot, but subsequent boot/reboots threw the error message. I think that
the non-first-boot-after-install issues may be because the system is not
shut down long enough to get beyond the time error.
--
Superblock last mount
Perhaps we could separate out non-first-boot-after-install issues to a
separate bug report? There's clearly more than one thing at work here.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of
I also saw this on a virtualbox system, a considerable number of boots
_after_ the install itself. System was updated just before reboot.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Hm I'm running Karmic on real hardware, and getting this sometimes
in regular operation - *not* first boot after install.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Package changed: Ubuntu Karmic = clock-setup (Ubuntu Karmic)
** Changed in: clock-setup (Ubuntu Karmic)
Status: Confirmed = Triaged
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of
I am not certain if this is the same bug as the reported one, but the
symptoms are similar and the ~bug only started happening in karmic this
week (around beginning of september 2009). I changed nothing in the
configs, just upgraded (it was karmic before, only few days worth of
packages).
This is
I can confirm this also from today's alternative amd64 build of Karmic
Alpha 5. Testing in VirtualBox shows same error, running fsck will
correct problem but this isn't good.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug
Same bug, and not only after the upgrade, but about every 2-3 boots.
[Ubuntu Karmic AMD64, GMT +1 Timezone]
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm on this; no need for anyone else to report similar symptoms.
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package clock-setup - 0.98ubuntu2
---
clock-setup (0.98ubuntu2) karmic; urgency=low
* Pass --utc or --localtime option to hwclock as appropriate, as well as
--noadjfile (LP: #423247).
-- Colin Watson cjwat...@ubuntu.com Thu, 03 Sep 2009 21:23:59
** Changed in: ubuntu
Status: New = Confirmed
** Changed in: ubuntu
Importance: Undecided = High
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
New bug created to track down fsck issue on first boot after install.
Fsck line reads:
/dev/sda1: Superblock last mount time (Wed 2 17:32:09 2009, now = Wed
Sep 2 16:33:11 2009) is in the future.
hwclock --debug --show reads:
+ hwclock from
** Attachment added: clock.txt
http://launchpadlibrarian.net/31252110/clock.txt
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: ubuntu
Assignee: (unassigned) = Colin Watson (cjwatson)
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thanks for the log, Dave
Up to During install, everything's fine:
Hw clock time : 2009/09/02 17:10:18 = 1251911418 seconds since 1969
Wed 02 Sep 2009 05:10:18 PM UTC -0.822584 seconds
UTC=yes
Wed Sep 2 17:10:35 UTC 2009
But then, once ubiquity has finished:
Hw clock time :
** Also affects: Ubuntu Karmic
Importance: High
Assignee: Colin Watson (cjwatson)
Status: Confirmed
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is
34 matches
Mail list logo
