Your message dated Mon, 23 May 2011 09:45:30 +0800
with message-id <878vtymbph....@jidanni.org>
and subject line seems an apt-get upgrade fixed it
has caused the Debian Bug report #627507,
regarding Cannot access the Hardware Clock via any known method.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
627507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.38-5
Setting the system clock.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Unable to set System Clock to: Sat May 21 10:29:45 UTC 2011 ...
^[[33m(warning).^[[39;49m
^[%@findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
Activating swap...done.
Usage: mountpoint [-q] [-d] [-x] path
Checking root file system...fsck from util-linux-ng 2.17.2
/run/rootdev: clean, 166520/492880 files, 1523037/1969962 blocks
done.
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
One can change the type of mount containing the directory dir:
mount --make-shared dir
mount --make-slave dir
mount --make-private dir
mount --make-unbindable dir
One can change the type of all the mounts in a mount subtree
containing the directory dir:
mount --make-rshared dir
mount --make-rslave dir
mount --make-rprivate dir
mount --make-runbindable dir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
Cleaning up ifupdown....
udevd[47]: failed to create queue file: No such file or directory
udevd[47]: failed to create queue file: No such file or directory
udevd[47]: failed to create queue file: No such file or directory
udevd[47]: failed to create queue file: No such file or directory
Setting the system clock.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Unable to set System Clock to: Sat May 21 10:29:45 UTC 2011 ...
^[[33m(warning).^[[39;49m
Loading kernel modules...done.
findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
findfs: unable to resolve 'UUID=cfc96b80-b2ec-45b2-90d7-c4b64d4651b6'
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
fsck.ext2: Unable to resolve 'UUID=c914c362-4b46-48be-afaf-6e061825b2ed'
fsck died with exit status 8
^[[31mfailed (code 8).^[[39;49m
File system check failed. A log is being saved in /var/log/fsck/checkfs if that
location is writable. Please repair the file system manually. ...
^[[31mfailed!^[[39;49m
A maintenance shell will now be started. CONTROL-D will terminate this shell
and resume system boot. ... ^[[33m(warning).^[[39;49m
Give root password for maintenance
(or type Control-D to continue):
^[[?17;0;64c
^[[01;41;35m18:30 ~#^[[00m lsusb
unable to initialize libusb: -99
^[[01;41;35m18:30 1 ~#^[[00m reboot
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal
error: 'stop-bootlogd-single' exited outside the expected code flow.
Using makefile-style concurrent boot in runlevel 6.
Shutting down ALSA...done (none loaded).
Stopping anac(h)ronistic cron: anacron.
Stopping MTA:.
Stopping deferred execution scheduler: atd.
Stopping resolvconf...done.
Stopping NTP server: ntpd.
Stopping pdnsd.
resolvconf: Error: /etc/resolvconf/run/interface is not a directory
Stopping Network connection manager: wicd.
Stopping HTTP cache proxy server: wwwoffledStopping X font server: xfstt
^[[31mfailed!^[[39;49m
...can't connect to control socket.
--- End Message ---
--- Begin Message ---
Seems an apt-get upgrade fixed it. Closing.
See you tomorrow for sure though.
--- End Message ---
