You are not logged in.

  1. Index
  2. » Basic Help & Support
  3. » Won't boot - btrfs problem

Pages: 1 2

#1 2017-12-22 01:51:52

MsMattie
Member
Registered: 2015-09-29
Posts: 99

Won't boot - btrfs problem

I'm traveling remotely in Asia and updated upgraded BunsenLabs Jessie to one of the big updates where the linux image was downloaded. It's a triple boot laptop - BunsenLabs Jessie which I used most of the time, but also with Xubuntu 16.04 and Windows 10.

After the update BunsenLabs won't boot up. I'm getting the error message below. Xubuntu and Windows 10 boots up fine. When I did this I updated BunsenLabs first, then Xubuntu. Xubuntu reinstalled Grub I think and I'm guessing it changed the name of partion where Grub is looking for BunsenLabs. Anyway, below is the error message. I can "ls" and "cd" around while in the BunsenLabs recovery and regular mode, but I don't know how to fix the BL booting problem.

The regular BunsenLabs boot error:
modprobe: can't load module btrfs (kernal /fs/btrfs/btrfs.ko): Invalid argument

The BunsenLabs safe boot error:

Giving up waiting for root device. Common problems:

- Boot arts (cat /proc/cmdline)
- Check rootdelay: (did the system wait long enough?)
- Check root (did the system wait for the right device?)
- Missing modeules (cat /proc/modules; ls /dev)

Alert! /dev/disk/by-uuid/20602d17-166a-4fd8-bffe-65415a16569f does not exist

Dropping to shell

modprove: module ehci-orion not found in modules.dep

BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built in shell (ash)

/bin/sh: can't access tty; job control turned off
(initramfs)

---

And from here I can "ls" and "cd" around in the folders.

BunsenLabs partion UUID as shown in gparted from Xubuntu is:
e0602d17-166a-4fd8-bffe-65415a16569f

The boot error message shows:
20602d17-166a-4fd8-bffe-65415a16569f does not exist

Comparing these UUID names, they are NOT the same, so I went to etc/fstab and changed that but it did not solve the problem.
20602d17-166a-4fd8-bffe-65415a16569f
e0602d17-166a-4fd8-bffe-65415a16569f

Suggestions?

...
Linux in the backwoods of the Rocky Mountains...

Offline

#2 2017-12-22 01:58:41

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

MsMattie wrote:

modprobe: can't load module btrfs (kernal /fs/btrfs/btrfs.ko): Invalid argument

This error will occur if the kernel image that is being booted is not actually installed in the operating system that is starting, for example if GRUB is attempting to boot BL with Ubuntu's kernel (or similar).

I went to etc/fstab and changed that

/etc/fstab is not read until after all of the kernel modules have been loaded so you should change that back so that it matches the actual UUIDs (use `sudo blkid` to find these).

I think the problem is in GRUB's configuration file so if we could see the content of /boot/grub/grub.cfg (from your Ubuntu system) then that will clear things up a bit, hopefully.

EDIT: it's late here so I'll be AFK for ~10 hours.

Last edited by Head_on_a_Stick (2017-12-22 02:00:05)

Para todos todo, para nosotros nada

Offline

#3 2017-12-25 11:26:37

MsMattie
Member
Registered: 2015-09-29
Posts: 99

Re: Won't boot - btrfs problem

Thanks much for the help. Internet here is problematic at best, so I won't be back online for 48-hours, or so.

Below is what is in the xubuntu /boot/grub/grub.cfg file:

#
# 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 ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  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="0"
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 recordfail {
  set recordfail=1
  if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; 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
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos7'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
else
  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
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_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=10
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=10
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="${1}"
	if [ "${1}" = "keep" ]; then
		set vt_handoff=vt.handoff=7
	else
		set vt_handoff=
	fi
}
if [ "${recordfail}" != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-454ca48d-628b-4703-9d2d-488d722b9992' {
	recordfail
	load_video
	gfxmode $linux_gfx_mode
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos7'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
	else
	  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
	fi
        linux	/boot/vmlinuz-4.4.0-104-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro  quiet splash $vt_handoff
	initrd	/boot/initrd.img-4.4.0-104-generic
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-454ca48d-628b-4703-9d2d-488d722b9992' {
	menuentry 'Ubuntu, with Linux 4.4.0-104-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-104-generic-advanced-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-104-generic ...'
	        linux	/boot/vmlinuz-4.4.0-104-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro  quiet splash $vt_handoff
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-104-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-104-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-104-generic-init-upstart-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-104-generic ...'
	        linux	/boot/vmlinuz-4.4.0-104-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro  quiet splash $vt_handoff init=/sbin/upstart
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-104-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-104-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-104-generic-recovery-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-104-generic ...'
	        linux	/boot/vmlinuz-4.4.0-104-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro recovery nomodeset 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-104-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-101-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-101-generic-advanced-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-101-generic ...'
	        linux	/boot/vmlinuz-4.4.0-101-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro  quiet splash $vt_handoff
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-101-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-101-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-101-generic-init-upstart-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-101-generic ...'
	        linux	/boot/vmlinuz-4.4.0-101-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro  quiet splash $vt_handoff init=/sbin/upstart
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-101-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-101-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-101-generic-recovery-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-101-generic ...'
	        linux	/boot/vmlinuz-4.4.0-101-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro recovery nomodeset 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-101-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-96-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-96-generic-advanced-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-96-generic ...'
	        linux	/boot/vmlinuz-4.4.0-96-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro  quiet splash $vt_handoff
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-96-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-96-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-96-generic-init-upstart-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-96-generic ...'
	        linux	/boot/vmlinuz-4.4.0-96-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro  quiet splash $vt_handoff init=/sbin/upstart
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-96-generic
	}
	menuentry 'Ubuntu, with Linux 4.4.0-96-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-96-generic-recovery-454ca48d-628b-4703-9d2d-488d722b9992' {
		recordfail
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos7'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
		else
		  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
		fi
		echo	'Loading Linux 4.4.0-96-generic ...'
	        linux	/boot/vmlinuz-4.4.0-96-generic root=UUID=454ca48d-628b-4703-9d2d-488d722b9992 ro recovery nomodeset 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.4.0-96-generic
	}
}

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

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

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

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Memory test (memtest86+)' {
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos7'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
	else
	  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
	fi
	knetbsd	/boot/memtest86+.elf
}
menuentry 'Memory test (memtest86+, serial console 115200)' {
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos7'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7  454ca48d-628b-4703-9d2d-488d722b9992
	else
	  search --no-floppy --fs-uuid --set=root 454ca48d-628b-4703-9d2d-488d722b9992
	fi
	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 10 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-E25E833B5E83080D' {
	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  E25E833B5E83080D
	else
	  search --no-floppy --fs-uuid --set=root E25E833B5E83080D
	fi
	parttool ${root} hidden-
	drivemap -s (hd0) ${root}
	chainloader +1
}
menuentry 'Windows 10 (loader) (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-A488CBBB88CB8A6E' {
	insmod part_msdos
	insmod ntfs
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  A488CBBB88CB8A6E
	else
	  search --no-floppy --fs-uuid --set=root A488CBBB88CB8A6E
	fi
	parttool ${root} hidden-
	drivemap -s (hd0) ${root}
	chainloader +1
}
menuentry 'BunsenLabs GNU/Linux 8.9 (Hydrogen) (8.9) (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-e0602d17-166a-4fd8-bffe-65415a16569f' {
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos5'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  e0602d17-166a-4fd8-bffe-65415a16569f
	else
	  search --no-floppy --fs-uuid --set=root e0602d17-166a-4fd8-bffe-65415a16569f
	fi
	linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=e0602d17-166a-4fd8-bffe-65415a16569f ro initrd=/install/initrd.gz quiet
	initrd /boot/initrd.img-3.16.0-4-amd64
}
submenu 'Advanced options for BunsenLabs GNU/Linux 8.9 (Hydrogen) (8.9) (on /dev/sda5)' $menuentry_id_option 'osprober-gnulinux-advanced-e0602d17-166a-4fd8-bffe-65415a16569f' {
	menuentry 'BunsenLabs GNU/Linux (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64--e0602d17-166a-4fd8-bffe-65415a16569f' {
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  e0602d17-166a-4fd8-bffe-65415a16569f
		else
		  search --no-floppy --fs-uuid --set=root e0602d17-166a-4fd8-bffe-65415a16569f
		fi
		linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=e0602d17-166a-4fd8-bffe-65415a16569f ro initrd=/install/initrd.gz quiet
		initrd /boot/initrd.img-3.16.0-4-amd64
	}
	menuentry 'BunsenLabs GNU/Linux, with Linux 3.16.0-4-amd64 (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64--e0602d17-166a-4fd8-bffe-65415a16569f' {
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  e0602d17-166a-4fd8-bffe-65415a16569f
		else
		  search --no-floppy --fs-uuid --set=root e0602d17-166a-4fd8-bffe-65415a16569f
		fi
		linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=e0602d17-166a-4fd8-bffe-65415a16569f ro initrd=/install/initrd.gz quiet
		initrd /boot/initrd.img-3.16.0-4-amd64
	}
	menuentry 'BunsenLabs GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode) (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64-root=UUID=e0602d17-166a-4fd8-bffe-65415a16569f ro single initrd=/install/initrd.gz-e0602d17-166a-4fd8-bffe-65415a16569f' {
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  e0602d17-166a-4fd8-bffe-65415a16569f
		else
		  search --no-floppy --fs-uuid --set=root e0602d17-166a-4fd8-bffe-65415a16569f
		fi
		linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=e0602d17-166a-4fd8-bffe-65415a16569f ro single initrd=/install/initrd.gz
		initrd /boot/initrd.img-3.16.0-4-amd64
	}
}

set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### 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 ###

...
Linux in the backwoods of the Rocky Mountains...

Offline

#4 2017-12-25 12:27:53

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

That grub.cfg is attempting to load BunsenLabs from UUID=e0602d17-166a-4fd8-bffe-65415a16569f so perhaps that is not the file being scanned by the bootloader.

We could try either running `grub-install` from Ubuntu to make sure that file is read (all of the details seem to be correct but I may have missed something) or we could chroot into BunsenLabs and run `grub-install` from there instead.

The second method would cause GRUB to read it's configuration from BunsenLabs' /boot/grub/grub.cfg so it would have a (slightly) better chance of working.

Method:

sudo -i
mount /dev/sda5 /mnt
for i in run proc sys dev dev/pts;do mount --bind /$i /mnt/$i;done
chroot /mnt /bin/bash
. /etc/profile
grub-install /dev/sda
update-grub
exit
reboot

Note that if you have /boot mounted on a separate partition then you will have to mount that also (under /mnt/boot) before running the `chroot` command.

Para todos todo, para nosotros nada

Offline

#5 2017-12-28 14:09:23

MsMattie
Member
Registered: 2015-09-29
Posts: 99

Re: Won't boot - btrfs problem

Thanks for the help Head_on_a_Stick

I ran these commands and it still turns up the btrfs problem. I'll put the terminal results from it at the bottom of this message. I ran from Xubuntu.

It appears it is just not seeing the partition with BunsenLabs on it. I am able to copy and get anything on any of the two ext4 linux partions or the Win10 ntfs partition by live booting Knoppiz USB and using the file manager in it. And Xubuntu still works fine. So, I'm not quite up the creek, yet...

mattie@ThinkPad-X200:~$ sudo -i
[sudo] password for mattie: 
root@ThinkPad-X200:~# mount /dev/sda5 /mnt
root@ThinkPad-X200:~# for i in run proc sys dev dev/pts;do mount --bind /$i /mnt/$i;done
root@ThinkPad-X200:~# chroot /mnt /bin/bash
root@ThinkPad-X200:/# . /etc/profile
root@ThinkPad-X200:/# grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
root@ThinkPad-X200:/# update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found Windows 10 (loader) on /dev/sda1
Found Windows 10 (loader) on /dev/sda2
Found Ubuntu 16.04.3 LTS (16.04) on /dev/sda7
done
root@ThinkPad-X200:/# exit
exit
root@ThinkPad-X200:~#

...
Linux in the backwoods of the Rocky Mountains...

Offline

#6 2017-12-28 14:23:57

MsMattie
Member
Registered: 2015-09-29
Posts: 99

Re: Won't boot - btrfs problem

By the way, I apologize for taking awhile to get back. Where I'm at right now it is no small thing just to log in for email, or for posting to BunsenLabs forum...

...
Linux in the backwoods of the Rocky Mountains...

Offline

#7 2017-12-28 14:40:51

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

MsMattie wrote:

I ran these commands and it still turns up the btrfs problem

OK, that narrows it down nicely, thanks!

Which filesystem are you using?

This command will tell us for sure:

sudo wipefs /dev/sda5
MsMattie wrote:

It appears it is just not seeing the partition with BunsenLabs on it

Yes, that's normal — the output you see is from the `os-prober` command and that only search for "foreign" operating systems (ie, those on other partitions) so we wouldn't expect to see BL mentioned there (in fact, "/boot/vmlinuz-blah" is the BL kernel).

If you check /boot/grub/grub.cfg in BunsenLabs, it should now (roughly) match the Ubuntu version, search for "menuentry" to find the relevant bits.

We do need to check though: is the BunsenLabs system all on a single partition (/dev/sda5 in your case) or do you have /boot on a different partition?

If /boot is elsewhere then you should run through the procedure again but mount the /boot partition (under /mnt/boot) before `chroot`ing in and updating grub.cfg again.

It is probably worth running `apt update` and `apt upgrade` from the chrooted system (with all parts of the filesystem mounted) in order to ensure that the kernel, initramfs & installed modules are all in sync.

MsMattie wrote:

I apologize for taking awhile to get back

No need to apologise, we're not going anywhere smile

Last edited by Head_on_a_Stick (2017-12-28 14:42:49)

Para todos todo, para nosotros nada

Offline

#8 2017-12-28 14:44:18

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

Please also try running `sudo update-grub` from your Ubuntu system, I will look very silly if that actually works but we have to check.

Para todos todo, para nosotros nada

Offline

#9 2017-12-28 15:26:32

martix
Kim Jong-un Stunt Double
Registered: 2016-02-19
Posts: 1,267

Re: Won't boot - btrfs problem

@HoaS That's what I was wondering about too (what are sda3, 4 and 6? Was there maybe a separate boot partition?) .

@MsMattie Having a look at grug.cfg it looks like as you said: "Xubuntu reinstalled Grub I think". Indeed, it seems to me it messed up the kernels, which means Xubuntu started to use the newer 4.4.0-104 kernel and thought: Oh, there is an other distro and the kernel v. 3.16.0-4 belongs to it. I might be wrong but I had the experience that on a multiboot system a grub update by ubuntu can mess up the boot process. This is why it's a good idea to have a separate boot partition and always a recent backup of it. I'd have suggested the same as HoaS (chroot into #BĹ and update grub) but it still used the old kernel. Try as HoaS suggested, if it does not work, here is one more idea.

You could try to copy the following in grub.cfg before the ### END /etc/grub.d/40_custom ### line, save it, restart and look for the line with BunsenLabs TryMartix on the boot screen:

menuentry 'BunsenLabs TryMartix GNU/Linux 8.9 (Hydrogen) (8.9) (on /dev/sda5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-e0602d17-166a-4fd8-bffe-65415a16569f' {
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos5'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  e0602d17-166a-4fd8-bffe-65415a16569f
	else
	  search --no-floppy --fs-uuid --set=root e0602d17-166a-4fd8-bffe-65415a16569f
	fi
	linux /vmlinuz-4.4.0-104-generic root=UUID=e0602d17-166a-4fd8-bffe-65415a16569f ro initrd=/install/initrd.gz quiet
	initrd /initrd.img-4.4.0-104-generic
}

(It should be in the file /etc/grub.d/40_custom, but it works to copy it directly in grub.cfg and it supposed to boot with the newer kernel).

Offline

#10 2017-12-28 15:33:41

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

martix wrote:
	linux /vmlinuz-4.4.0-104-generic root=UUID=e0602d17-166a-4fd8-bffe-65415a16569f ro initrd=/install/initrd.gz quiet
	initrd /initrd.img-4.4.0-104-generic

Why would the OP's BunsenLabs system have copies of an Ubuntu kernel image (& initrd) in the root directory?

What exactly is this supposed to achieve?

Para todos todo, para nosotros nada

Offline

#11 2017-12-28 15:36:40

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

martix wrote:

It should be in the file /etc/grub.d/40_custom, but it works to copy it directly in grub.cfg

No, /etc/grub.d/40_custom is the correct location because /boot/grub/grub.cfg will be over-written every time the kernel is updated.

and it supposed to boot with the newer kernel

That looks like Ubuntu's kernel image to me and BL shouldn't have any installed modules that are loadable by that version so I would be surprised if it worked (even if the image was on the root directory).

Last edited by Head_on_a_Stick (2017-12-28 15:37:24)

Para todos todo, para nosotros nada

Offline

#12 2017-12-28 17:38:55

martix
Kim Jong-un Stunt Double
Registered: 2016-02-19
Posts: 1,267

Re: Won't boot - btrfs problem

Head_on_a_Stick wrote:

What exactly is this supposed to achieve?

There was "Found Ubuntu 16.04.3 LTS (16.04)", which makes me think that the 3.16 kernel might belong to Xubuntu and the 4.4.0-104 image actually to #BĹ. I might be wrong though, but I had this kind of kernel-mess-up before.

Head_on_a_Stick wrote:

No, /etc/grub.d/40_custom is the correct location because /boot/grub/grub.cfg will be over-written every time the kernel is updated.

That's correct, it will be overwritten, if there is an update. For simply trying to boot into #BĹ it does not matter though (and if it boots, update-grub will correct grub.cfg, in which case it won't have to be removed from 40_custom). At least it's worth a try as it would make it possible to run "update-grub" with the - possibly - right kernel. But again: I might be wrong and it simply won't boot.

Offline

#13 2017-12-28 18:18:05

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

martix wrote:

the 3.16 kernel might belong to Xubuntu and the 4.4.0-104 image actually to #BĹ

No, the current BL kernel version should be https://packages.debian.org/jessie/linu … .0-4-amd64

That "generic" one has an Ubuntu-style nomenclature.

Para todos todo, para nosotros nada

Offline

#14 2017-12-28 20:26:56

martix
Kim Jong-un Stunt Double
Registered: 2016-02-19
Posts: 1,267

Re: Won't boot - btrfs problem

^Ah, ok, I had that image version on Stretch, with an entry showing "linux    /vmlinuz-4.4.0-104-generic".

It'll be helpful to clear what those other partitions sda3,4 and 6 are. That error message is a bit confusing though, because in grub.cfg above the uuid looks correct (so where is that other uuid might come from?).

Offline

#15 2017-12-28 23:20:39

MsMattie
Member
Registered: 2015-09-29
Posts: 99

Re: Won't boot - btrfs problem

$ sudo update-grub
[sudo] password for mattie:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-104-generic
Found initrd image: /boot/initrd.img-4.4.0-104-generic
Found linux image: /boot/vmlinuz-4.4.0-101-generic
Found initrd image: /boot/initrd.img-4.4.0-101-generic
Found linux image: /boot/vmlinuz-4.4.0-96-generic
Found initrd image: /boot/initrd.img-4.4.0-96-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 10 (loader) on /dev/sda1
Found Windows 10 (loader) on /dev/sda2
Found BunsenLabs GNU/Linux 8.9 (Hydrogen) (8.9) on /dev/sda5
done

---

mattie@ThinkPad-X200:~$ sudo wipefs /dev/sda5
[sudo] password for mattie:
offset               type
----------------------------------------------------------------
0x1fe                dos   [partition table]

0x438                ext4   [filesystem]
                     UUID:  e0602d17-166a-4fd8-bffe-65415a16569f

---

And I did read the other grub post on this forum and the only thing I did on the update was to first in BunsenLabs:

$ sudo apt-get update && sudo apt-get upgrade

This had the linux-image download so I knew it was a major update, which it did.

Then I rebotted and went directly to Xubuntu where I used their Software Update to do that update and I think but am not absolutely positive that it did the Linux-image update download too, and then I think it automatically did "update-grub" or something like that, but I didn't note anything down because I didn't expect this problem. I didn't manually do any other kind of grub update or install or reinstall or anything like that. I did as I mentioned afterward when BL would not boot, go change fstab to make them match what gparted was showing for partition labels or numbers. I've since changed fstab back to what it was previously. I tried the solution with both fstabs.

...
Linux in the backwoods of the Rocky Mountains...

Offline

#16 2017-12-29 00:16:46

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

OK, let's try a custom grub.cfg (in your BunsenLabs system) to check that is what's being loaded.

From Ubuntu:

sudo -i
mount /dev/sda5 /mnt
mv /mnt/boot/grub/grub.cfg{,.orig}
tee /mnt/boot/grub/grub.cfg <<!
menuentry 'BunsenLabs' {
    set root=(hd0,5)
    linux /vmlinuz root=/dev/sda5 ro
    initrd /initrd.img
}
menuentry 'Ubuntu' {
    set root=(hd0,7)
    linux /vmlinuz root=/dev/sda7 ro
    initrd /initrd.img
}
menuentry 'Windoze' {
    set root=(hd0,1)
    chainloader +1
}
!
umount -R /mnt
exit

If the boot menu does not change then BL is _not_ controlling it.

To get things back the way they were, copy /boot/grub/grub.cfg.orig back.

I think we also need to know which other operating systems you have installed, as martix mentioned.

EDIT: added Win10 entry.

Last edited by Head_on_a_Stick (2017-12-29 00:21:33)

Para todos todo, para nosotros nada

Offline

#17 2017-12-29 02:40:49

MsMattie
Member
Registered: 2015-09-29
Posts: 99

Re: Won't boot - btrfs problem

Head_on_a_Stick wrote:

OK, let's try a custom grub.cfg (in your BunsenLabs system) to check that is what's being loaded.

This results in a generic looking screen now with BunsenLabs, Ubuntu and Windoze

Xubuntu and Win10 still boots properly. When I try to boot the BunsenLabs it goes through what looks like the loading procedure for the BL Safe Boot Mode and ends with the same no-boot error screen.

I haven't put back the original grub file to it's previous state.

...
Linux in the backwoods of the Rocky Mountains...

Offline

#18 2017-12-29 12:14:25

unklar
Back to the roots 1.9
From: #! BL
Registered: 2015-10-31
Posts: 2,709

Re: Won't boot - btrfs problem

^ HoaS,

please remember that this is a btrfs file system and ubuntu still seems to have been unable to solve the bug.

Offline

#19 2017-12-29 12:42:40

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Won't boot - btrfs problem

unklar wrote:

please remember that this is a btrfs file system

MsMattie wrote:
mattie@ThinkPad-X200:~$ sudo wipefs /dev/sda5
[sudo] password for mattie:
offset               type
----------------------------------------------------------------
0x1fe                dos   [partition table]

0x438                ext4   [filesystem]
                     UUID:  e0602d17-166a-4fd8-bffe-65415a16569f

^ Not according to that output wink

MsMattie wrote:

Xubuntu and Win10 still boots properly. When I try to boot the BunsenLabs it goes through what looks like the loading procedure for the BL Safe Boot Mode and ends with the same no-boot error screen.

So I can get Ubuntu & Win10 booting but not BL? That's not good hmm

At the moment I'm leaning towards a possible problem with your hard drive (and filesystem) because everything else looks fine.

You can try gsmartcontrol to check drive health, I'm pretty sure they should have that in Ubuntu:

sudo apt-get install gsmartcontrol
gsmartcontrol # or sudo gsmartcontrol-root

Just to be absolutely sure, if you wouldn't mind going through the `mount` & `chroot` sequence I posted earlier and this time run these commands from the chroot shell:

apt update
aptitude reinstall linux-image-amd64

The reinstall command should also refresh the initrd.img and it would be useful to see the entire output as that may have some clues.

Thanks!

Para todos todo, para nosotros nada

Offline

#20 2017-12-29 13:10:12

unklar
Back to the roots 1.9
From: #! BL
Registered: 2015-10-31
Posts: 2,709

Re: Won't boot - btrfs problem

^ Thanks, HoaS,
I overlooked!  :8


You are unbeatable!   ]:D

Offline

Pages: 1 2

  1. Index
  2. » Basic Help & Support
  3. » Won't boot - btrfs problem

Board footer

Powered by FluxBB