You are not logged in.

#1 2016-09-18 12:24:51

crackpipe
Member
Registered: 2016-09-17
Posts: 8

x686 Kernel update - ext 2 not recognized

Since a x686 kernel update Wednesday, Sept 13, I've been unable to boot. This update was only two items: a kernel and one other item, I think a python application. Following this update, booting leads an emergency shell, from which even basic commands are not available (eg no "uname", to give you guys a kernel number). Above the emergency prompt is a notice:

mount: unknown filesystem type 'ext2'
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off 

.
I used an install disk to chroot...

cat /etc/fstab

#UUID=(long number)
/dev/sda1  /ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 1

From chroot I did a fresh "mkinitcpio", "grub-mkconfig"  and "grub-install", all without errors. However, upon reboot, the same ext2 error noted above. Thanks.

Offline

#2 2016-09-18 12:34:34

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,463

Re: x686 Kernel update - ext 2 not recognized

That is not a valid fstab entry.

Online

#3 2016-09-18 18:16:54

crackpipe
Member
Registered: 2016-09-17
Posts: 8

Re: x686 Kernel update - ext 2 not recognized

You're suggesting a new genfstab? Not sure.

Offline

#4 2016-09-18 18:25:42

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: x686 Kernel update - ext 2 not recognized

Is /dev/sda1 your root partition?
Perhaps a space between the '/' and 'ext2' would help?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2016-09-18 19:15:40

crackpipe
Member
Registered: 2016-09-17
Posts: 8

Re: x686 Kernel update - ext 2 not recognized

Thanks. Yeah, dev/sda1 is the root partition. Apologies  --  I'm an idiot.  I can only boot the bad system with an install disk with no X, so I hand copied the fstab info into the post without the space between the / and the ext2.  Still, ran a fresh genfstab for verification -- the space after the "/" there of course on the unbooting system.

cat /etc/fstab
#UUID=(long hex number)
/dev/sda1  /    ext2   rw,relatime,block_validity,barrier,user_xattr,acl 0 1

And it's the same fail upon boot:  -- ext2 is an "unknown file system".  Again, this only  began directly after the "pacman -Syu"  on Wednesday. I rebooted thereafter and it's failed ever since each boot attempt. I can mount /dev/sda2 manually from the install/rescue disk, but of course that's a different kernel than the one on the HDD. I also updated again yesterday (Saturday), and that included another kernel update, but it still spawns the same fail.

Currently attempting to force the file system within GRUB2's boot configuration, though I'm not sure what or how. Thanks again. Open to all suggestions.

EDIT: Here's the current GRUB2 configuration, the one generated with "grub-mkconfig"...

 cat /boot/grub/grub.cfg
#
# 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="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 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,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
else
  search --no-floppy --fs-uuid --set=root ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
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
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 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
	else
	  search --no-floppy --fs-uuid --set=root ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
	fi
	echo	'Loading Linux linux ...'
	linux	/boot/vmlinuz-linux root=UUID=ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc rw  quiet
	echo	'Loading initial ramdisk ...'
	initrd  /boot/initramfs-linux.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc' {
	menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
		else
		  search --no-floppy --fs-uuid --set=root ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
		fi
		echo	'Loading Linux linux ...'
		linux	/boot/vmlinuz-linux root=UUID=ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc rw  quiet
		echo	'Loading initial ramdisk ...'
		initrd  /boot/initramfs-linux.img
	}
	menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
		else
		  search --no-floppy --fs-uuid --set=root ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc
		fi
		echo	'Loading Linux linux ...'
		linux	/boot/vmlinuz-linux root=UUID=ac8193d1-6d44-4111-a7c5-5ef8fd1c2afc rw  quiet
		echo	'Loading initial ramdisk ...'
		initrd  /boot/initramfs-linux-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 ###
### 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 ###

Last edited by crackpipe (2016-09-18 19:55:01)

Offline

#6 2016-09-18 20:40:39

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: x686 Kernel update - ext 2 not recognized

Please paste the output of `pacman -Q linux && uname -a`


Moving to NC...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#7 2016-09-18 21:11:34

crackpipe
Member
Registered: 2016-09-17
Posts: 8

Re: x686 Kernel update - ext 2 not recognized

Thanks for assistance.

The output below is from an install disk boot. The system doesn't currently boot from HDD and only drops into an emergency prompt, with no apparent commands ( for example, no pacman or uname) available. So this is after booting with the install CD.
Hand-copied...

# pacman -Q linux && uname -a
Linux archiso 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:21:20 CEST 2016 i686 GNU/Linux

But here also, in order to see most recent kernel download(s)...

$ ls /var/cache/pacman/pkg |grep linux
archlinux-keyring-20160812-1-any.pkg.tar.xz
libutil-linux-2.28.2-1-i686.pkg.tar.xz
linux-4.7.2-1-i686.pkg.tar.xz
linux-4.7.3-2-i686.pkg.tar.xz
linux-4.7.4-1-i686.pkg.tar.xz
linux-api-headers-4.7-1-i686.pkg.tar.xz
linux-firmware-20160730.6bc2c60-1-any.pkg.tar.xz
util-linux-2.28.2-1-i686.pkg.tar.xz

Offline

#8 2016-09-18 21:16:12

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: x686 Kernel update - ext 2 not recognized

From the live media, chroot into your install, make sure /boot is mounted and reinstall the kernel and regenerate your initramfs.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#9 2016-09-18 22:36:13

crackpipe
Member
Registered: 2016-09-17
Posts: 8

Re: x686 Kernel update - ext 2 not recognized

Will do...

# pacman -S linux
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-4.7.4-1

Total Installed Size:  70.20 MiB
Net Upgrade Size:       0.00 MiB

checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
reinstalling linux...
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.7.4-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.7.4-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

Upon reboot...

[ 0.932621] Failed to find cpu0 device node
starting version 231
/dev/sda1 clean, 91489/3932160 files, 1020619/15728640 blocks
mount: unknown filesystem type 'ext2'
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

Offline

#10 2016-09-18 22:48:10

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,786
Website

Re: x686 Kernel update - ext 2 not recognized

At the rootfs prompt, run

ls /usr/lib/modules

What is the output?


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#11 2016-09-18 23:25:07

crackpipe
Member
Registered: 2016-09-17
Posts: 8

Re: x686 Kernel update - ext 2 not recognized

Thanks...

# ls /usr/lib/modules
4.7.4-1 ARCH

Offline

#12 2016-09-18 23:41:45

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,786
Website

Re: x686 Kernel update - ext 2 not recognized

That looks okay, it means you're booting an initrd generated for the latest kernel at least. Can you try booting the fallback kernel initramfs and see if you have the same problem?

Last edited by WorMzy (2016-09-19 00:15:50)


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#13 2016-09-19 02:53:01

crackpipe
Member
Registered: 2016-09-17
Posts: 8

Re: x686 Kernel update - ext 2 not recognized

I went back two, since that was the last one that worked. Nevertheless...

[ 0.932621] Failed to find cpu0 device node
starting version 231
/dev/sda1 clean, 91489/3932160 files, 1020619/15728640 blocks
mount: unknown filesystem type 'ext2'
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

Getting late on a Sunday so I guess I'll capitulate and just clean install. Hate to do it, but time is fleeting. Thanks again.

Offline

#14 2016-09-19 10:11:06

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,786
Website

Re: x686 Kernel update - ext 2 not recognized

Rather than downgrading, I meant use the fallback option you have under grub's advanced options menu. The fallback initramfs has all the built kernel modules in it, whereas the regular initramfs only has the modules that your system 'should' need to boot.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#15 2016-09-20 08:21:57

crackpipe
Member
Registered: 2016-09-17
Posts: 8

Re: x686 Kernel update - ext 2 not recognized

Good to know, thank you.

I did a fresh install, and so far no problems. Two mildly interesting idiosyncracies: 1) boot hangs at the point in the boot it was failing previously, but now passes it after a 2-3 second delay, and I get a normal runlevel2 login prompt. 2) cannot enter X from runlevel2 (eg "startx") if I first su up to pacman some package, and then exit sudo down to user level and then attempt to start X.  I first must log entirely out and then log back in at user level, or the tty refuses connection, lol.

These are not problems so far, just interesting... at least to an idiot like me. Thanks again.

Offline

#16 2016-09-20 08:29:16

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: x686 Kernel update - ext 2 not recognized

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

Board footer

Powered by FluxBB