Author Topic: [partially-SOLVED] : Kernel panic : Manjaro-16.06 NOT booting after CLIInstall  (Read 1872 times)

0 Members and 1 Guest are viewing this topic.

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
 Manjaro-KDE 16.06 x86_64, installed in REAL mode, and not in a VirtualBox.
Anyway,  doesn't matter which Manjaro 16.06, they all FAIL to boot with "kernel panic ..."
The laptop is in my sig. Asus K75DE, I have 2 separate internal drives, sda and sdb.
 Laptop is also set to BIOS/CSM mode in Uefi/Bios (non-uefi), so I have a choice to boot either drive separately.
 btw, every other distro can install fine in Bios/MBR mode if I so choose.

# lsblk
Code: [Select]
$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 698.7G  0 disk
├─sda1   8:1    0   100M  0 part
├─sda2   8:2    0 312.4G  0 part
├─sda3   8:3    0  15.9G  0 part [SWAP]
└─sda4   8:4    0 370.3G  0 part /
sdb      8:16   0 465.8G  0 disk
├─sdb1   8:17   0  97.7G  0 part
└─sdb2   8:18   0     8G  0 part
sr0     11:0    1  1024M  0 rom

Manjaro controls Grub(2) on /dev/sdb
 sdb -> Grub(2) as installed by Manjaro after successful installation
sdb1 -> /  (root)
sdb2 -> (swap)

I booted Manjaro 16.06-x86_64 (with the standard non-free boot install), successfully.
 It's a very simple Installation.
Installed with CLI-Installer, onto sdb, there's nothing else on sdb, it completed with no errors,  wrote grub(2) to mbr of /dev/sdb only, but upon rebooting into /dev/sdb, it failed with a kernel panic.

 here's the /boot/grub/grub.cfg from /dev/sdb1 (Manjaro)
Code: [Select]
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

set menu_color_normal=light-gray/black
set menu_color_highlight=green/black

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  6ab80a7b-51e6-4163-851c-fede327d5cae
else
  search --no-floppy --fs-uuid --set=root 6ab80a7b-51e6-4163-851c-fede327d5cae
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  6ab80a7b-51e6-4163-851c-fede327d5cae
else
  search --no-floppy --fs-uuid --set=root 6ab80a7b-51e6-4163-851c-fede327d5cae
fi
insmod png
background_image -m stretch /usr/share/grub/background.png
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-6ab80a7b-51e6-4163-851c-fede327d5cae' {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  6ab80a7b-51e6-4163-851c-fede327d5cae
else
  search --no-floppy --fs-uuid --set=root 6ab80a7b-51e6-4163-851c-fede327d5cae
fi
echo 'Loading Linux 4.4.8-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.4-x86_64 root=UUID=6ab80a7b-51e6-4163-851c-fede327d5cae rw  quiet resume=UUID=913d0a41-62c9-4969-aaae-cfcc65129406
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.4-x86_64.img
}
submenu 'Advanced options for Manjaro Linux' $menuentry_id_option 'gnulinux-advanced-6ab80a7b-51e6-4163-851c-fede327d5cae' {
menuentry 'Manjaro Linux (Kernel: 4.4.8-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.8-1-MANJARO x64-advanced-6ab80a7b-51e6-4163-851c-fede327d5cae' {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  6ab80a7b-51e6-4163-851c-fede327d5cae
else
  search --no-floppy --fs-uuid --set=root 6ab80a7b-51e6-4163-851c-fede327d5cae
fi
echo 'Loading Linux 4.4.8-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.4-x86_64 root=UUID=6ab80a7b-51e6-4163-851c-fede327d5cae rw  quiet resume=UUID=913d0a41-62c9-4969-aaae-cfcc65129406
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.4-x86_64.img
}
menuentry 'Manjaro Linux (Kernel: 4.4.8-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.8-1-MANJARO x64-fallback-6ab80a7b-51e6-4163-851c-fede327d5cae' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  6ab80a7b-51e6-4163-851c-fede327d5cae
else
  search --no-floppy --fs-uuid --set=root 6ab80a7b-51e6-4163-851c-fede327d5cae
fi
echo 'Loading Linux 4.4.8-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.4-x86_64 root=UUID=6ab80a7b-51e6-4163-851c-fede327d5cae rw  quiet resume=UUID=913d0a41-62c9-4969-aaae-cfcc65129406
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-4.4-x86_64-fallback.img
}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-AA4E5BD64E5B99C1' {
savedefault
insmod part_msdos
insmod ntfs
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  AA4E5BD64E5B99C1
else
  search --no-floppy --fs-uuid --set=root AA4E5BD64E5B99C1
fi
parttool ${root} hidden-
chainloader +1
}
menuentry 'Linux Mint 17.3 Rosa (17.3) (on /dev/sda4)' --class linuxmint --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-a8c6e55a-535b-4895-a05e-ffc80015f258' {
savedefault
insmod part_msdos
insmod ext2
set root='hd0,msdos4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  a8c6e55a-535b-4895-a05e-ffc80015f258
else
  search --no-floppy --fs-uuid --set=root a8c6e55a-535b-4895-a05e-ffc80015f258
fi
linux /boot/vmlinuz-3.19.0-32-generic root=UUID=a8c6e55a-535b-4895-a05e-ffc80015f258 ro
initrd /boot/initrd.img-3.19.0-32-generic
}
submenu 'Advanced options for Linux Mint 17.3 Rosa (17.3) (on /dev/sda4)' $menuentry_id_option 'osprober-gnulinux-advanced-a8c6e55a-535b-4895-a05e-ffc80015f258' {
menuentry 'Linux Mint 17.3 MATE 64-bit (on /dev/sda4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.19.0-32-generic--a8c6e55a-535b-4895-a05e-ffc80015f258' {
savedefault
insmod part_msdos
insmod ext2
set root='hd0,msdos4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  a8c6e55a-535b-4895-a05e-ffc80015f258
else
  search --no-floppy --fs-uuid --set=root a8c6e55a-535b-4895-a05e-ffc80015f258
fi
linux /boot/vmlinuz-3.19.0-32-generic root=UUID=a8c6e55a-535b-4895-a05e-ffc80015f258 ro
initrd /boot/initrd.img-3.19.0-32-generic
}
menuentry 'Linux Mint 17.3 MATE 64-bit, with Linux 3.19.0-32-generic (on /dev/sda4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.19.0-32-generic--a8c6e55a-535b-4895-a05e-ffc80015f258' {
savedefault
insmod part_msdos
insmod ext2
set root='hd0,msdos4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  a8c6e55a-535b-4895-a05e-ffc80015f258
else
  search --no-floppy --fs-uuid --set=root a8c6e55a-535b-4895-a05e-ffc80015f258
fi
linux /boot/vmlinuz-3.19.0-32-generic root=UUID=a8c6e55a-535b-4895-a05e-ffc80015f258 ro
initrd /boot/initrd.img-3.19.0-32-generic
}
menuentry 'Linux Mint 17.3 MATE 64-bit, with Linux 3.19.0-32-generic (recovery mode) (on /dev/sda4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.19.0-32-generic--a8c6e55a-535b-4895-a05e-ffc80015f258' {
savedefault
insmod part_msdos
insmod ext2
set root='hd0,msdos4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos4 --hint-efi=hd0,msdos4 --hint-baremetal=ahci0,msdos4  a8c6e55a-535b-4895-a05e-ffc80015f258
else
  search --no-floppy --fs-uuid --set=root a8c6e55a-535b-4895-a05e-ffc80015f258
fi
linux /boot/vmlinuz-3.19.0-32-generic root=UUID=a8c6e55a-535b-4895-a05e-ffc80015f258 ro recovery nomodeset
initrd /boot/initrd.img-3.19.0-32-generic
}
}

### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/60_memtest86+ ###
if [ "${grub_platform}" == "pc" ]; then
    menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
        search --fs-uuid --no-floppy --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  6ab80a7b-51e6-4163-851c-fede327d5cae
        linux16 /boot/memtest86+/memtest.bin
    }
fi
### END /etc/grub.d/60_memtest86+ ###


# here is /etc/fstab (from sdb1) Manjaro
Code: [Select]
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# DEVICE DETAILS: /dev/sdb1 UUID=6ab80a7b-51e6-4163-851c-fede327d5cae LABEL=root
# DEVICE DETAILS: /dev/sdb2 UUID=913d0a41-62c9-4969-aaae-cfcc65129406 LABEL=swap
UUID=6ab80a7b-51e6-4163-851c-fede327d5cae / ext4 defaults 0 1
UUID=913d0a41-62c9-4969-aaae-cfcc65129406 swap swap defaults 0 0


and yes, I've looked at this:
https://forum.manjaro.org/index.php?topic=33429.msg273538#msg273538
and some others around here, nuthin' worked.
 Also, I'm NOT using another distro's grub to boot, I'm only using Manjaro/Arch to boot from sdb.

...everything looks good, but I'm embarassingly stumped ?!

« Last Edit: 09. May 2016, 14:43:13 by archiebunker »

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Need 3 more things from you.

[1]
Code: [Select]
sudo fdisk -l
sudo blkd

[2]
Also to help in eliminating one of the possible causes, can you let us know if Manjaro is the first (top) entry when the grub menu appears when your computer start up?
Or is it Linux Mint?

[3]
Does the following make Manjaro boot (From your info, I am assuming there is only one Manjaro in your system)?
At grub menu, press 'c' to get to grub prompt (grub>).
Type and press 'enter' after each line.
Code: [Select]
grub> search -f /boot/intel-ucode.img --set=root
grub> configfile /boot/grub/grub.cfg
Boot up the first entry (Manjaro). Does that boot okay into Manjaro?


Life is a sexually transmitted disease with a 100% mortality rate.

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
Hi gohlip, and thanks for helping out.

Code: [Select]
sudo blkd                                                                                                     
sudo: blkd: command not found

 any idea where it is on the Manjaro 16.06 Live image ?

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Hi gohlip, and thanks for helping out.

Code: [Select]
sudo blkd                                                                                                     
sudo: blkd: command not found

 any idea where it is on the Manjaro 16.06 Live image ?
Very sorry, it should be "sudo blkid".
And you can get all these from Linux Mint (figuring it is easier to boot LM than livecd).
« Last Edit: 08. May 2016, 21:33:21 by gohlip »
Life is a sexually transmitted disease with a 100% mortality rate.

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
 booted off the Manjaro 16.06 Live  (Note: sdc is just the manjaro-16.06-x86_64 image on a USB flash drive)
[1]
 # sudo fdisk -l
Code: [Select]
$ sudo fdisk -l
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000a9589

Device     Boot     Start        End   Sectors   Size Id Type
/dev/sda1  *         2048     206847    204800   100M  7 HPFS/NTFS/exFAT
/dev/sda2          206848  655362047 655155200 312.4G  7 HPFS/NTFS/exFAT
/dev/sda3       655362048  688564223  33202176  15.9G 82 Linux swap / Solaris
/dev/sda4       688564224 1465147391 776583168 370.3G 83 Linux


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0004c25f

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdb1            2048 204802047 204800000 97.7G 83 Linux
/dev/sdb2       204802048 221579263  16777216    8G 82 Linux swap / Solaris




Disk /dev/sdc: 7.5 GiB, 8017412096 bytes, 15659008 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x17bbbe98

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1  *        0 3909119 3909120  1.9G  0 Empty
/dev/sdc2         220   63707   63488   31M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 31.5 MiB, 33038336 bytes, 64528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 178.2 MiB, 186847232 bytes, 364936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.3 GiB, 1345179648 bytes, 2627304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 350.9 MiB, 367927296 bytes, 718608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 931.5 GiB, 1000204885504 bytes, 1953525167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0xb73c13b0

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdd1             2048 1024002047 1024000000 488.3G 83 Linux
/dev/sdd2       1024002048 1953523711  929521664 443.2G  7 HPFS/NTFS/exFAT

# sudo blkid
Code: [Select]
sudo blkid                                                                                                     
/dev/sdc1: UUID="2016-04-26-21-06-00-00" LABEL="MJRO1606" TYPE="iso9660" PTUUID="17bbbe98" PTTYPE="dos" PARTUUID="17bbbe98-01"
/dev/sda1: LABEL="System Reserved" UUID="AA4E5BD64E5B99C1" TYPE="ntfs" PARTUUID="000a9589-01"
/dev/sda2: UUID="C0567D13567D0C02" TYPE="ntfs" PARTUUID="000a9589-02"
/dev/sda3: UUID="af6bde93-c37b-4fee-b833-9fd4946a312c" TYPE="swap" PARTUUID="000a9589-03"
/dev/sda4: UUID="a8c6e55a-535b-4895-a05e-ffc80015f258" TYPE="ext4" PARTUUID="000a9589-04"
/dev/sdb1: LABEL="root" UUID="6ab80a7b-51e6-4163-851c-fede327d5cae" TYPE="ext4" PARTUUID="0004c25f-01"
/dev/sdb2: LABEL="swap" UUID="913d0a41-62c9-4969-aaae-cfcc65129406" TYPE="swap" PARTUUID="0004c25f-02"
/dev/sdc2: SEC_TYPE="msdos" LABEL="MISO_EFI" UUID="2835-A0B1" TYPE="vfat" PARTUUID="17bbbe98-02"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/sdd1: UUID="2681b3f7-1a22-45ac-ad1c-4215b26389c4" TYPE="ext4" PARTUUID="b73c13b0-01"
/dev/sdd2: LABEL="NTFS" UUID="07760DC52E47D632" TYPE="ntfs" PARTUUID="b73c13b0-02"

[2]
 yes, when the Laptop boots I just hit [F2] and select sdb and there is only Manjaro first, there is nothing else on that sdb disk.

[3]
 ok, I booted Laptop to "sdb" -(the lone Manjaro install), while quickly hitting [c], and it dropped me to grub>, where I entered your two commands, line-by-line, with their respective outputs.

grub> search -f /boot/intel-ucode.img --set=root
Code: [Select]
hd0,msdos1
grub> configfile /boot/grub/grub.cfg
Code: [Select]
...well here it errors back to the "kernel panic...", can not boot.

 still no boot, just kernel panic.
 The above output, "hd0,msdos1" is showing me, maybe there's some weirdness with manjaro/os-prober, since it's  trying to grab hd0 -which is sda ?!, that's the wrong disk, in fact, it should be sdb,
 and manjaro is misconfiguring the grub(2) installation, even though i explicitly told manjaro to select only sdb as it's grub(2)/MBR install.
« Last Edit: 08. May 2016, 22:14:06 by archiebunker »

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
First, sorry have to ask you so much info, because I cannot assume it is msdos partitioning in all disks (which is the case) as you have a 100MB partition in sda, pointing to a possible gpt partition and because your bios can do both bios and uefi.


Now, everything appears to be in order but lets check each one out.

[1] Start up using Linux Mint grub (that I think is the 'normal' sda boot)
[2] Press 'c' to go to grub prompt, at LM grub prompt, type
the following...
Code: [Select]
grub> search -f /boot/intel-code.imgNote the output, possibly (hd1, msdos4)   <but can be (hd2, msdos4), don't worry what this is, just note it down>
If there is an output type
Code: [Select]
grub> search -f /boot/intel-ucode.img --set=root     (2 dashes in front of "set" no space anywhere in "--set=root", and no output this time)
Verify again with
Code: [Select]
grub> echo $root that should be the same as the above output from search (hd1,4 or hd2,4).
[3]
Code: [Select]
grub> ls ($root)/boot/Note among items listed must have  vmlinuz-4.4-x86_64 and initramfs-4.4-x86_64.img
If the vmlinuz are different, say  vmlinuz-4.5-x86_64 and initramfs-4.5-x86_64.img, it is still okay, but must have both corresponding vmlinuz and initramfs.
[4] Continue typing as follows
Code: [Select]
grub> insmod part_msdos
grub> insmod ext2
grub> probe -u $root --set=abc
grub> linux /boot/vmlinuz-4.4-x86_64 root=UUID=$abc rw
grub> initrd /boot/initramfs-4.4-x86_64.img
grub> boot
(change kernel number if different, meaning 4.4 to 4.5)

5] Then when/If booted to manjaro, do the following at terminal
good practice to do this first,,,
Code: [Select]
sudo pacman-mirrors -g
sudo pacman -Syyu
Now do this...
Code: [Select]
sudo pacman -S grubIf asked if you want to reinstall, answer 'yes'.
Code: [Select]
sudo grub-install /dev/sda (note it is sda not sdb)
Code: [Select]
sudo update-grub
Good luck, archiebunker.





     



« Last Edit: 08. May 2016, 23:04:24 by gohlip »
Life is a sexually transmitted disease with a 100% mortality rate.

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
First, sorry have to ask you so much info, because I cannot assume it is msdos partitioning in all disks (which is the case) as you have a 100MB partition in sda, pointing to a possible gpt partition and because your bios can do both bios and uefi.


Now, everything appears to be in order but lets check each one out.

[1] Start up using Linux Mint grub (that I think is the 'normal' sda boot)
[2] Press 'c' to go to grub prompt, at LM grub prompt, type
the following...
Code: [Select]
grub> search -f /boot/intel-code.imgNote the output, possibly (hd1, msdos4)   <but can be (hd2, msdos4), don't worry what this is, just note it down>
If there is an output type
Code: [Select]
grub> search -f /boot/intel-ucode.img --set=root     (2 dashes in front of "set", but no output this time)
Verify again with
Code: [Select]
grub> echo $root that should be the same as the above output from search.
[3]
Code: [Select]
grub> ls ($root)/boot/Note among items listed must have  vmlinuz-4.4-x86_64 and initramfs-4.4-x86_64.img
If the vmlinuz are different, say  vmlinuz-4.5-x86_64 and initramfs-4.5-x86_64.img, it is still okay,but must have both corresponding vmlinuz and initramfs.

To be continued.



The 100MB partition in sda is just Win7_64 in NON-UEFI.

[1] and [2] booted/started in Linuxmint (sda) and pressed [c]...

#grub> search -f /boot/intel-code.img
 got "error:no such device: /boot/intel-code.img"

# grub> search -f /boot/intel-ucode.img --set=root
 no output

# grub> echo $root
 hd1,msdos1

regarding [3] and [4], and [5]:
wow, back in 15 minutes after I write down all that stuff, 'cause there's no other way.
 LoL, what's going on with Arch/Manjaro?, this is a complete mess,
and there's NO reason for Arch/Manjaro to behave like this..., but then again.
 :) thanks man, I appreciate this, but I'm starting to wonder if ALL this is something we'll have to do from now on, and for how long?
 But hey, it's no wonder syslinux, and NOT grub, is used for all servers.


« Last Edit: 08. May 2016, 22:59:59 by archiebunker »

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Man, your manjaro installation is not okay at all.
Too bad, but you will need to reinstall.

ps: use calamares or cli

Glad to help, buddy. though didn't get anywhere.
Late here. Good night.
Life is a sexually transmitted disease with a 100% mortality rate.

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
 Ok, no probs, but I did use the CLI-Installer, unkless of course, it is the CLI-Installer, or is it? wtf?
 anyway, just to PROVE that these installer issues are constantly recuring,
  while I was hacking around with your commands I installed the same Manjaro-16.06... on a plain-jane Desktop with only one empty drive, gave it ALL to Manjaro, and oh look ! -the same fsckin' issue occurs all over again, "Kernel panic ..." and can't boot.

 so Let me guess, @philm is completely unaware of these obvious issues, arch or not?

 I mean, DOES ANYBODY/DEVS at Manjaro actually test "real" installs, instead of just phoney, virtual ones ???>
« Last Edit: 08. May 2016, 23:58:41 by archiebunker »

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Morning.

I had lots of manjaro installations a couple of months back [1] on calamares, though my usual installs are on cli.
All work out fine both on bios-legacy and on uefi (no luks or lvm).
But I have this (good) habit of making sure partitions to be installed is ready (no resizing, creation...) at installation, though I usually do format / partition at installation.

A few things.
First I assume your install iso checksum works out fine.
Now, since your bios can do both uefi and bios-legacy, it is possible (not saying that is your case, just possible) your install media (usb) is booted up in uefi mode.
Remember that for bios-legacy installation, install media must be booted in bios-legacy, likewise uefi installations needed to be booted in uefi.
To be sure, instead of setting bios to have both uefi and bios-legacy, find a way to have it set only to one mode of boot. Some bios cannot do that but have a 'priority' setting for it.

Other than that, i hope you find out what's causing this, because you said it happens every time you try to install.
Well. good luck and take care.

[1] just to test -  and LXQT had back to back revisions which I installed in all 3 computers
     also, calamares now enable grub to be set to own partition (called 'system') which I must have for bios-legacy.
« Last Edit: 09. May 2016, 07:56:51 by gohlip »
Life is a sexually transmitted disease with a 100% mortality rate.

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
Re: Kernel panic : Manjaro grub(2) alone on one disk, NOT booting ?
« Reply #10 on: 09. May 2016, 07:22:26 »
Man, your manjaro installation is not okay at all.
Too bad, but you will need to reinstall.

ps: use calamares or cli

Glad to help, buddy. though didn't get anywhere.
Late here. Good night.

Ok, so far so good:

 Calamares-Installer worked !,  BUT, CLI-Installer still fails with "Kernel panic..." upon reboot.

 And now there is a very slight difference, (with fdisk -l, and blkid),  between Calamares -below,  vs.CLI-Installer -(Reply #4) above?

Code: [Select]
$ sudo fdisk -l
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000a9589

Device     Boot     Start        End   Sectors   Size Id Type
/dev/sda1  *         2048     206847    204800   100M  7 HPFS/NTFS/exFAT
/dev/sda2          206848  655362047 655155200 312.4G  7 HPFS/NTFS/exFAT
/dev/sda3       655362048  688564223  33202176  15.9G 82 Linux swap / Solaris
/dev/sda4       688564224 1465147391 776583168 370.3G 83 Linux


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00038740

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdb1  *         2048 204802047 204800000 97.7G 83 Linux
/dev/sdb2       204802048 223234047  18432000  8.8G 82 Linux swap / Solaris


$ sudo blkid
/dev/sda1: LABEL="System Reserved" UUID="AA4E5BD64E5B99C1" TYPE="ntfs" PARTUUID="000a9589-01"
/dev/sda2: UUID="C0567D13567D0C02" TYPE="ntfs" PARTUUID="000a9589-02"
/dev/sda4: UUID="a8c6e55a-535b-4895-a05e-ffc80015f258" TYPE="ext4" PARTUUID="000a9589-04"
/dev/sda3: UUID="af6bde93-c37b-4fee-b833-9fd4946a312c" TYPE="swap" PARTUUID="000a9589-03"
/dev/sdb1: UUID="99df5172-631f-43dc-b326-971ab34f56e5" TYPE="ext4" PARTUUID="00038740-01"                                                     
/dev/sdb2: UUID="1d3151fb-f362-433a-ad3e-689874d2edcc" TYPE="swap" PARTUUID="00038740-02"         

 It appears CLI-installer messes up the UUID's ?

I also changed nothing when I used Calamares, except to "re-format" sdb1 to ext4, and sdb2 to swap, simple test setup again.- the same as I used with the CLI-Installer above
Code: [Select]
/dev/sdb -> Manjaro Grub(2)mbr
/dev/sdb1 -> "/"
/dev/sdb2 -> swap

Also, I didn't set any partition flags, I let Calamares decide what to do for a simple "/" and swap parttion on /dev/sdb, and let it have the disk., again, same as I used with CLI-Installer.
 So there is definitely something wrong with the CLI-Installer in Manjaro 16.06
Too tired to look into this anymore right now, just gonna finish updating this Manjaro 16.06 KDE monster,  and verify I can boot again, from the OS's in sda as well.

Thanks for your help, thus far.
Man, using a Virtualbox is so much easier and faster lol, but it's not as much fun as this.
« Last Edit: 09. May 2016, 08:22:47 by archiebunker »

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
Re: Kernel panic : Manjaro grub(2) alone on one disk, NOT booting ?
« Reply #11 on: 09. May 2016, 07:29:48 »
Morning.

I had lots of manjaro installations a couple of months back (just to test) on calamares, though my usual installs are on cli.
All work out fine both on bios-legacy and on uefi (no luks or lvm).
But I have this (good) habit of making sure partitions to be installed is ready (no resizing, creation...) at installation, though I usually do format / partition at installation.

A few things.
First I assume your install iso checksum works out fine.
Now, since your bios can do both uefi and bios-legacy, it is possible (not saying that is your case, just possible) your install media (usb) is booted up in uefi mode.
Remember that for bios-legacy installation, install media must be booted in bios-legacy, likewise uefi installations needed to be booted in uefi.
To be sure, instead of setting bios to have both uefi and bios-legacy, find a way to have it set only to one mode of boot. Some bios cannot do that but have a 'priority' setting for it.

Other than that, i hope you find out what's causing this, because you said it happens every time you try to install.
Well. good luck and take care.

 Yes, I'm ok with everything you mentioned above.
 In my most recent post I mentioned Calamares-Installer worked, whereas the CLI-Installer didn't inmycase -(as per my top few posts).

I'm just updating this Manjaro 16.06 KDE now, there's 2.G of installation updates to get yet to go, but sofar so good...

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Re: Kernel panic : Manjaro grub(2) alone on one disk, NOT booting ?
« Reply #12 on: 09. May 2016, 07:35:30 »
Quote
It appears CLI-installer messes up the UUID's ?
Shouldn't, unless you specifically ask to use partuuid's (I think, cannot remember for sure). I always liked cli because it lets do label, ..lots more at install, and I always have to 'manual' install (too many partitions and OS) and cli is good in this.

Anyway, good you got this worked out nice this time.
Cheers.

Quote
...there's 2.G of installation updates to get yet to go...
2G? What old install iso did you use?  ;D

Life is a sexually transmitted disease with a 100% mortality rate.

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
Re: Kernel panic : Manjaro grub(2) alone on one disk, NOT booting ?
« Reply #13 on: 09. May 2016, 08:05:22 »
 Actually, I always use the CLI, and I prefer CLI-Installer,  this was the first time I tried Calamares.
I pick the top "default" FSUUID's, or I thnk it's called that, out of the 3 choices, during a CLI-Install, they usually work.
 I'm aware of the Arch and other Distro's and grub, regarding the "intel-ucode.img", I've been following up on some of those posts as well.

 Ya this Manjaro KDE is quite beautiful, but it's effin' HUGE !
BTW, I used "manjaro-kde-16.06-pre3-x86_64.iso", checksums were fine, I think it's called Manjaro 16.06 pre3 Daniella, or whatever  ;)
Code: [Select]
Linux manjkde 4.4.9-1-MANJARO #1 SMP PREEMPT Thu May 5 15:49:15 UTC 2016 x86_64 GNU/Linux

I'm going to mark this thread as partially-Solved, since I'm still getting "Kernel panic's" when using CLI-Installer, for this particular .iso.

« Last Edit: 09. May 2016, 08:24:17 by archiebunker »

Offline archiebunker

  • Vollwertiges Mitglied
  • ***
  • Posts: 247
  • Branch: Stable
  • Desktop: OB, FB, Mate
  • GPU Card: A10/APU/GPU/7670M
  • GPU driver: AMD/ATI OpenSource Graphics
  • Kernel: manjaro-*.*-x86_64
  • Skill: Intermediate
[Minor UPDATE_01] :

Normally, in my BIOS, SATA0=sda=hd0 and SATA1=sdb=hd1

 But after I successfuly installed Manjaro-KDE-16.06, (using CALAMARES-GUI-Installer), with grub(2) onto /dev/sdb, and initially booted into the "grub>" cli, I noticed that it had switched my sda with sdb, within my system.
Code: [Select]
grub> echo $root
hd0,msdos1

...which now explains HOW Calamares succeded to boot, whereas, the CLI-Installer had failed with a "kernel panic..."
 Interestingly enough, after I connected to my wifi network, and did a pacman -Syyu, and then rebooted, it magically switched my sda and sdb harddrives back again to original, and all was fine. ?!

 Confused yet? -well yes, and so am I still ;)
 It must be the magic of Calamares   :D

 Something is telling me that Grub2 and Systemd are looking and acting more and more like a weird Windows Registry table every day, but shhhh,... we're not supposed to know.
« Last Edit: 09. May 2016, 14:43:35 by archiebunker »