Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17718 - [initscripts] Hardware clock read problem?
Attached to Project:
Arch Linux
Opened by Todd Partridge (Gen2ly) - Wednesday, 06 January 2010, 04:00 GMT
Last edited by Allan McRae (Allan) - Monday, 11 January 2010, 10:33 GMT
Opened by Todd Partridge (Gen2ly) - Wednesday, 06 January 2010, 04:00 GMT
Last edited by Allan McRae (Allan) - Monday, 11 January 2010, 10:33 GMT
|
DetailsDescription:
This is an example of how not to write a bug report but I'm putting it up in case someone else can add to this too. :D Updated to the new kernel today and a few other packages (not sure of the packages because accidental destruction of pacman db forcing a restore). I got this message after 'Arch Linux... copyright...': Cannot access the Hardware Clock via any know method. Use the --debug option to see the details of our search for an access method. After this the filesystem check fails: Arch_Linux: Superblock last write time (Tuesday Jan 5 15:02:20 2010 now = Tuesday Jan 5 09:02:59 2010) is in the future. The time of booting was 15:07. I rebooted into the live CD and checked the hardware clock and the time was correct. When I checked the disk (fsck -f...) and rebooted I noticed another message about the clock in the init scripts but went by too quickly (I'm guessing it's from /etc/rc.sysinit invoking hwclock). Like to be able to provide more details but hopefully this helps. |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 11 January 2010, 10:33 GMT
Reason for closing: Works for me
Additional comments about closing: Reporter can no longer replicate
Monday, 11 January 2010, 10:33 GMT
Reason for closing: Works for me
Additional comments about closing: Reporter can no longer replicate
upgraded alsa-lib (1.0.21.a-1 -> 1.0.22-1)
upgraded aria2 (1.7.1-2 -> 1.8.0-1)
upgraded bluez (4.58-1 -> 4.59-1)
upgraded gnupg2 (2.0.13-3 -> 2.0.14-1)
upgraded iptables (1.4.5-1 -> 1.4.6-1)
upgraded kernel26-firmware (2.6.31-1 -> 2.6.32.2-2)
upgraded kernel26 (2.6.31.6-1 -> 2.6.32.2-2)
upgraded lib32-nvidia-utils (190.42-2 -> 190.53-1)
upgraded libsndfile (1.0.20-3 -> 1.0.21-1)
upgraded macchanger (1.5.0-2 -> 1.5.0-3)
upgraded musicmanager (0.10.11-1 -> 0.10.14-1)
upgraded nvidia-utils (190.42-2 -> 190.53-1)
upgraded nvidia (190.42-1 -> 190.53-1)
upgraded oss (4.2_2002-1.1 -> 4.2_2002-2)
upgraded pam (1.1.0-1 -> 1.1.1-1)
upgraded pm-utils (1.2.6.1-2 -> 1.2.6.1-3)
upgraded postgresql-libs (8.4.1-1 -> 8.4.2-1)
upgraded rrdtool (1.4.1-1 -> 1.4.2-1)
upgraded rsync (3.0.6-1 -> 3.0.7-1)
upgraded syslinux (3.83-1 -> 3.84-2)