经过一些更新/升级(不幸的是,我不记得软件包的名称),我无法启动Kubuntu。它冻结在“正在呼吸的kubuntu徽标”上。
当我碰到逃脱时,我会看到以下错误(我不得不在这里手动键入它们,因此有可能我可能会打一些错字):
[9.436029] [drm.intel_set_pch_fifo_underrun_reporting [1915]] *ERROR* uncleared pch fifo underrun
[9.436050] [drm.intel_pch_fifo_underrun_irq_handler [1915]] *ERROR* PCH transcoder A FIFO underrun
umount: Can't umount /cdrom: Device or resource busy
/init: line 7: can't open /dev/sr0: No medium found
(...) these two lines repeat quite a few times
[55.219834] SQUASHFS error: Unable to read fragment cache entry [aa3e07]
[55.220432] SQUASHFS error: Unable to read page, block aa3e07, size[7096]
(...) these two lines repeat quite a few times (just with different ...timecodes? in the square brackets at the beginning)
Bus error
[79.692133] SQUASHFS error: zlib decompression failed, data probably corrupt
[79.692701] SQUASHFS error: squashfs_read_data failed to read block 0xaa3e07
[55.219834] SQUASHFS error: Unable to read fragment cache entry [aa3e07]
[55.220432] SQUASHFS error: Unable to read page, block aa3e07, size[7096]
[79.753474] Kernel panic - not syncing: Attempt to kill init! exitcode 0x00000007
[79.753474]
[79.754639] CPU: 3 PID: 1 Comm: init Not tainted 4.4.0-31-generic #50-Ubuntu
[79.755230] Hardware name: LENOVO Lenovo G580/Product Name, BIOS SECN33WW (V2.03) 06/06/2012
[79.755836] 0000000000000086 00000000e62afd6d ffff88013a3f7c50 ffffffff813f1143
[79.756416] ffffffff81cb2b50 ffff88013a3f7ce8 ffff88013a3f7cd8 ffffffff8118bde7
[79.757006] ffff880000000010 ffff88013a3f7ce8 ffff88013a3f7c80 00000000e62afd6d
[79.757605] Call Trace:
(here I got lazy to hand-copy all timestamps and hexa information, I can provide it, if needed, information, that I skipped, is marked in {curly brackets})
[{timestamp}] [<{16 hexa digits}>] dump_stack+0x63/0x90
[{timestamp}] [<{16 hexa digits}>] panic+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] ? perf_event_exit_task+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] do_exit+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] do_group_exit+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] get_signal+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] do_signal+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] ? force sig_info_fault+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] ? __probe_kernel_read+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] ? mm_fault_error+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] exit_to_usermode_loop+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] prepare_exit_to_usermode+0x{hexa}/0x{hexa}
[{timestamp}] [<{16 hexa digits}>] retint_user+0x{hexa}/0x{hexa}
[79.765834] Kernel Offset: disabled
[79.766446] ---[ end Kernel panic - not syncing: Attempt to kill init! exitcode=0x00000007
[79.766446]
之后,我尝试通过USB重新安装Kubuntu 16.04。
在USB引导管理器中,我选择了“安装Kubuntu”。
结果如下:
/dev/sda5: clean, 448332/1509600 files, 3769787/6054443 blocks
~.mount
ureadahead.service
{list of many .services}
systemd-rfkill.service
dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart7.swap
dev-disk-by\x2did-wwn\x2d0x50004cf20a67e83f\x2dpart7.swap
dev-disk-by\x2did-ata\x2dST1000LM024_HN\x2dm101MBB_S2SMJ9CD547736\x2dpart7.swap
dev-sda7.swap
dev-disk-by\x2duuid-df2bfbbd\x2de7ca\x2d4e37\x2d9b35\x2de51a38e0ab13.swap
systemd-fsckd.service
fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress
fsckd:1:0,0:Checking in progress on 1 disk (0,0% complete)
(... more similar fsckd output)
fsckd:1:14,3:Checking in progress on 1 disk (14,3% complete)
此时,它冻结了一段时间,然后恢复启动([ OK ]
该行开头的“典型加载输出”)。
(...)
[ OK ] Started Run snappy firstboot setup.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):
在按Ctrl + D后,它重复了此确切消息。
我发现一些对其他用户有用的策略,例如在启动管理器中键入“ acpi = off”或禁用UEFI,但没有任何帮助。我还尝试使用Boot Repair可引导USB修复引导。“修复”没有错误,但是没有任何改变。在恢复模式下启动Kubuntu也不起作用。
我以为,也许我的硬盘坏了,但是双重引导进入Windows 10(安装在同一物理驱动器上(仅在另一个分区上))就可以了。
(我很抱歉我的英语。)
我终于尝试从Live USB安装Kubuntu 16.10,它对我来说几乎是完美的。我格式化了我的根分区并保留了/ home分区,所以我不得不重新安装所有程序(不格式化/分区,则安装无法正常进行)。
安装16.10之后,我必须解决此问题:“欢迎使用紧急模式!” 认为这是一个fsck问题。kyodake提供的解决方案对我来说很好。
现在我很好奇,如果它能在升级到16.10之前起作用...
本文收集自互联网,转载请注明来源。
如有侵权,请联系[email protected] 删除。
我来说两句