新装 Debian squeeze 启动时遇到错误

ch_fb

正常重启，绝非异常关机。

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: The Dec 10 15:14:03 UTC 2009 ... (warning).
Activation swap...done.
Checking root file system...fsck from util-linux-ng 2.16.1
/lib/init/rw/rootdev: clean, 18434/612000 files, 164691/2441872 blocks done.
[        5.838201] EXT3 FS on sda1, internal journal
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: The Dec 10 15:14:03 UTC 2009 ... (warning).
Activation swap...done.
Checking root file system...fsck from util-linux-ng 2.16.1
fsck.ext3: No such file or directory while trying to open /dev/sda5
/dev/sda5:
The superblock could not be read or dose not describe a correct ext2 filesystem.  If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>

fsck died with ext status 8
failed (code 8).
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. ... failed!
Give root password for maintenance
(or type Control-D to continue):

两分区文件系统均为新创建，无任何污染。

1. ~ # cat /etc/fstab
2. proc                /proc        proc        defaults        0 0
4. /dev/sda1        /        ext3        defaults        0 1
5. /dev/sda5        /home        ext3        defaults        0 2
6. ~ # cat /var/log/fsck/checkfs
7. Log of fsck -C -R -A -a
8. Thu Dec 10 23:26:27 2009
10. fsck from util-linux-ng 2.16.1
11. /dev/sda5: clean, 212/1224000 files, 109480/4883752 blocks
13. The Dec 10 23:26:28 2009
14. ----------------------
15. ~ #

复制代码

blue_stone

重启机器, 进入单用户模式, 对这2个文件系统, 进行fsck.
如果这种现象多次发生, 建议提交bug给Debian

ch_fb

文件系统无误，就是有时启动会冒出。网上搜出一堆什么时间问题，看不懂。

blue_stone

貌似问题出在了hwclockfirst.sh 脚本上.
你如果有兴趣, 可以debug一下这个脚本.

ch_fb

就是这个问题，一模一样。
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=69;bug=535130
怎么解决？是不是右边那个图，把 udev 升到 148 ？我现在的是 146-5。
怎么升啊？sid 里面才有个 149-1 ，难道要开 sid 源？

blue_stone

Post by ch_fb;2054943
就是这个问题，一模一样。
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=69;bug=535130
怎么解决？是不是右边那个图，把 udev 升到 148 ？我现在的是 146-5。
怎么升啊？sid 里面才有个 149-1 ，难道要开 sid 源？

146-6以上的版本看上去解决了这个问题.
如果需要从sid单独升udev, 可以去mirror下载udev和libudev0, 并用dpkg安装

adam8157

升级就好了,懒得升级就再重启一遍吧,sid前一段时间就经常这样...好久没犯了

HFUTec

我新装的testing一开始也常有这个问题，这两天不见了

ch_fb

testing 的 udev 更新了，149-1 ，不过我打算换 stable 了。

聚焦深空

您至少有两种变通解法：
内核命令行，增加 "apic=off"；
或，修改 /etc/init.d/hwclock.sh，添加 --directisa 参数。

您升级到 sid，也许能直接解决问题。