Ubuntu: Initramfs revisited (Error in Ubuntu 17.04)


My problem is different to others I have seen at the forum. When booting the system this is what appears:

[1.168307] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)  [1.1684911 ACPI Error: Method parse/execution failed [\_SB.PCIO.SATO.SPT2_ GTF] (Node ffff8914550e1938),AE_NOT_FOUND(20160930/psparse-543)    [1.210601] ACPI Error: [DSSP] Namespace lookup failure, AE. NOT_FOUND (201609 30/psargs-359)     [1.210773] ACPI Error: Method parse/execution failed [\_SB.PCIO.SATO.SPT2._GTF] (Node ffff8914550e1938), AE_NOT_FOUND (20160930/psparse-543)    BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash) Enter 'help' for a list of built-in commands.    (initramfs)   

Then, I write 'exit' and this is what happens:

mount: mounting /sys on /root/sys failed: No such file or directory     mount: mounting /proc on /root/proc failed: No such file or directory     /init: line 343: can't open /root/dev/console: no such file  [17.080779] Kernel panic - not syncing: Attempted to kill init! exitcode=040000200     [ 17.080779]    [17.080786] CPU: 0 PID: 1 Comm: init Not tainted 4.10.0-21-generic #23-Ubuntu    [17.080790] Hardware name: HSI MS-7850/H87-G41 PC Mate(MS-7850), BIOS V3.1 05/09/2013    [17.080793] Call Trace:    [ 17.080800] dump_stack+0x63/0x81    [ 17.080804] panic+0xe4/0x22d    [ 17.080808] do_exit+0xb09/0xb10    [ 17.080811] do_group_exit+0x43/0xb0    [ 17.080814] SyS_exit_group+0x14/0x20    [ 17.080818] entry_SYSCALL_64_fastpath+0x1e/0xad    [17.080822] RIP: 0033:0x7ff7adaa7b38    [17.080824] RSP: 002b:00007ffe0a976738 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7    [17.080828] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff7adaa7b38  [ 17.060632] RDX: 0000000000000002 RSI: 000000000000003c RDI: 0000000000000002    [17.080835] RBP: 0000562f9813642d8 R08: 00000000000000e7 R09: ffffffffffffff98    [ 17.080838] R10: 0000562f98b568f0 R11: 0000000000000202 R12: 0000000000000001   [ 17.080842] R13: 0000562f98b5c630 R14: 0000562f98b64358 R15: 0000000000000000    [17.080864] Kernel Offset: Ox4c00000 from Oxffffffff81000000 (relocation range: Oxffffffff80000000-Oxffffffffbfffffff)   [ 17.080869] ---[ end Kernel panic - not syncing: Attempted to kill initl exitcode=0x00000200   [ 17.080869]  

This is the second time I install Kubuntu 17.04 in a week, and the second time that it happens. I have Windows10 installed as well, but it works fine. ¿Any suggest? Thank you, very much.


From the comments...

It looks like the BIOS update may have solved some evils, but the boot problem still exists. With the ACPI errors gone, we may have you reinstall the OS one more time, but first let's check your existing file system.

To check the file system on your Ubuntu partition...

  • boot to the GRUB menu
  • choose Advanced Options
  • choose Recovery mode
  • choose Root access
  • at the # prompt, type sudo fsck -f /
  • repeat the fsck command if there were errors
  • type reboot

If for some reason you can't do the above...

  • boot to a Ubuntu Live DVD/USB
  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition
  • quit gparted
  • open a terminal window
  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier
  • repeat the fsck command if there were errors
  • type reboot

Update #1:

To further check the hard disk hardware...

Use the Disks app to review the SMART Data & Tests data and run the tests. You could install gsmartcontrol to monitor the disk. Since this is a HDD, you could badblock the drive with e2fsck -c -k /dev/sdb while running from a Ubuntu Live DVD/USB.


I chose "Recovery mode" at boot, and this is what appeared: EXT4 - fs (sdb5):VFS: found ext4 filesystem with invalid superblock checksum. Run e2fsck? mount: mounting /dev/sdb5 on /root failed: Bad message done. initramfs

I tried fsck -f / and this is what happened:

error 2 (no such file or directory) while executing fsck.ext2 for / Then I tried with: e2fsck -f /

and began to appear some messages with superblock invalid.... /dev/sdb5 was not cleanly mounted, check forced ... Inode 4325681 seems to contain garbage. Clear <y>?

I accepted and appeared a lot of similar messages with different Inode numbers. At last I checked with 'a' option (to answer 'yes' to all questions).

Began to appear hundreds and hundreds of similar messages fixing the problems, and finally ended. I made it again from the beggining with 'e2fsck' command. And the screen filled with negative numbers at a incredible speed. I waited 2,3, 4, 5 minutes and it didn't end, so I decided to reboot the computer. Well, then I tried with an Ubuntu Live DVD.

Started GParted, confirmed 'sdb5' as Linux partition. Opened a terminal and typed again: fsck and e2fsck. Again the same thing as before, but as I had it in a 'controlled' terminal window I didn't panic. At last the process ended. Made it again and the system didn't find any error, so I thought the problems had been corrected. Rebooted the system, but 'oh, surprise', the GRUB menu did not appear. Instead of it appears: Grub rescue I booted again with Live CD, and tried to reinstall the GRUB, but every time said me that was impossible to install GRUB at boot device (sda), so I didn't want to tempt fate and decided to maKe a clean install of Ubuntu. Now, everything is OK, with my Boot menu for Windows or Ubuntu. I am going to work some days with Ubuntu without installing anything to check if the problem recreates or what happens.

Note:If u also have question or solution just comment us below or mail us on toontricks1994@gmail.com
Next Post »