You are not logged in.

#1 2017-07-05 15:30:22

superipermeganoob
Member
Registered: 2011-05-03
Posts: 26

[SOLVED] unable to boot on F2FS with systemd-boot

hi, i installed arch into a ssd in dualboot with android x86, i follow the installation guide but I must have missed something, I followed this partitioning scheme:

  • BOOT  /dev/mmcblk0p12         vfat

  • / (root) /dev/mmcblk0p13       f2fs

  • SWAP /dev/mmcblk0p14          swap

  • HOME /dev/mmcblk0p15         f2fs

this is the error i get on screen at boot -> https://imgur.com/a/xNmQJ
summarize -> error device '' not found
i think there is a problem with the kernel module that load the F2FS partition, I tried to force the kernel load it without success; What can I do to solve it?
Below are the system settings:
fstab

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/mmcblk0p13
PARTUUID=41f33f90-7796-49ef-8268-9cb6744a692f     	/         	f2fs      	rw,relatime,lazytime,background_gc=on,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6	0 0

# /dev/mmcblk0p12 LABEL=SYSTEM
PARTUUID=c6142c3c-fb75-473e-9206-0724336d8b05      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/mmcblk0p15
PARTUUID=b0868c62-2ce2-4f92-b9e8-0e24d098550e     	/home     	f2fs      	rw,relatime,lazytime,background_gc=on,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6	0 0

# swap
PARTUUID=73d93cd3-35a6-4cf7-b466-59f5f82e50c5	none	swap	defaults

# uefi
#efivarfs	/sys/firmware/efi/efivars	efivarfs	ro,nosuid,nodev,noexec,noatime

blkid

/dev/mmcblk0p2: SEC_TYPE="msdos" LABEL="ANDROIDIA" UUID="4127-547D" TYPE="vfat" PARTLABEL="android_bootloader" PARTUUID="2568845d-2332-4675-bc39-8fa5a4748d15"
/dev/mmcblk0p7: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" PARTLABEL="android_system" PARTUUID="38f428e6-d326-425d-9140-6e0ea133647c"
/dev/mmcblk0p8: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" PARTLABEL="android_cache" PARTUUID="a893ef21-e428-470a-9e55-0668fd91a2d9"
/dev/mmcblk0p9: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" PARTLABEL="android_data" PARTUUID="dc76dda9-5ac1-491c-af42-a82591580c0d"
/dev/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" PARTLABEL="android_config" PARTUUID="bd59408b-4514-490d-bf12-9878d963f378"
/dev/mmcblk0p12: UUID="D5D3-956C" TYPE="vfat" PARTUUID="c6142c3c-fb75-473e-9206-0724336d8b05"
/dev/mmcblk0p13: UUID="d2fc6b16-c172-4fff-90b7-b0698131e4d2" TYPE="f2fs" PARTUUID="41f33f90-7796-49ef-8268-9cb6744a692f"
/dev/mmcblk0p14: UUID="98515508-e0ba-4668-9d6e-7a35014b7d20" TYPE="swap" PARTUUID="73d93cd3-35a6-4cf7-b466-59f5f82e50c5"
/dev/mmcblk0p15: UUID="550d1e7c-ad42-48f6-8a37-277255f76c2b" TYPE="f2fs" PARTUUID="b0868c62-2ce2-4f92-b9e8-0e24d098550e"
/dev/sda1: UUID="2017-05-01-07-05-35-00" LABEL="ARCH_201705" TYPE="iso9660" PTUUID="7887f83f" PTTYPE="dos" PARTUUID="7887f83f-01"
/dev/sda2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="E149-3759" TYPE="vfat" PARTUUID="7887f83f-02"
/dev/loop0: TYPE="squashfs"
/dev/sdb1: UUID="E3CB-5F47" TYPE="vfat"
/dev/mmcblk0: PTUUID="1f6d174d-13c1-11e7-939a-806e6f6e6963" PTTYPE="gpt"
/dev/mmcblk0p1: PARTLABEL="android_bootloader2" PARTUUID="114eaffe-1552-4022-b26e-9b053604cf84"
/dev/mmcblk0p3: PARTLABEL="android_boot" PARTUUID="49a4d17f-93a3-45c1-a0de-f50b2ebe2599"
/dev/mmcblk0p4: PARTLABEL="android_recovery" PARTUUID="4177c722-9e92-4aab-8644-43502bfd5506"
/dev/mmcblk0p5: PARTLABEL="android_misc" PARTUUID="ef32a33b-a409-486c-9141-9ffb711f6266"
/dev/mmcblk0p6: PARTLABEL="android_metadata" PARTUUID="20ac26be-20b7-11e3-84c5-6cfdb94711e9"
/dev/mmcblk0p10: PARTLABEL="android_persistent" PARTUUID="ebc597d0-2053-4b15-8b64-e0aac75f4db1"

fdisk -l

Disk /dev/mmcblk0: 58.2 GiB, 62537072640 bytes, 122142720 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: gpt
Disk identifier: 1F6D174D-13C1-11E7-939A-806E6F6E6963

Device             Start       End  Sectors  Size Type
/dev/mmcblk0p1      2048    206847   204800  100M Microsoft basic data
/dev/mmcblk0p2    206848    411647   204800  100M EFI System
/dev/mmcblk0p3    411648    473087    61440   30M unknown
/dev/mmcblk0p4    473088    534527    61440   30M unknown
/dev/mmcblk0p5    534528    536575     2048    1M unknown
/dev/mmcblk0p6    536576    569343    32768   16M unknown
/dev/mmcblk0p7    569344   5812223  5242880  2.5G Linux filesystem
/dev/mmcblk0p8   5812224   6336511   524288  256M Linux filesystem
/dev/mmcblk0p9   6336512  33599487 27262976   13G Linux filesystem
/dev/mmcblk0p10 33599488  33601535     2048    1M Linux filesystem
/dev/mmcblk0p11 33601536  33617919    16384    8M Linux filesystem
/dev/mmcblk0p12 33617920  34666495  1048576  512M EFI System
/dev/mmcblk0p13 34666496  64026623 29360128   14G Linux filesystem
/dev/mmcblk0p14 64026624  66123775  2097152    1G Linux swap
/dev/mmcblk0p15 66123776 122142686 56018911 26.7G Linux home




Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 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/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 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/sda: 15 GiB, 16039018496 bytes, 31326208 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: 0x7887f83f

Device     Boot Start    End Sectors  Size Id Type
/dev/sda1  *        0 985087  985088  481M  0 Empty
/dev/sda2         164 131235  131072   64M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 369.5 MiB, 387477504 bytes, 756792 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/sdb: 28.7 GiB, 30752000000 bytes, 60062500 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: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1          32 60062499 60062468 28.7G  c W95 FAT32 (LBA)

kernel

Linux archiso 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux

loader.conf

timeout 3
default arch
editor 0

arch.conf

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
optios root=PARTUUID=41f33f90-7796-49ef-8268-9cb6744a692f rw

mkinit

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="crc32_generic crc32-pclmul libcrc32c crc32c_generic crc32c-intel"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

Last edited by superipermeganoob (2017-07-05 16:59:48)

Offline

#2 2017-07-05 15:34:23

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

Re: [SOLVED] unable to boot on F2FS with systemd-boot

This has nothing to do with the filesystem, it can't even find the device. Try booting the fallback initramfs.

EDIT: LOL, there's a typo in arch.conf that would explain this. optios -> options

Last edited by Scimmia (2017-07-05 15:42:58)

Offline

#3 2017-07-05 16:16:02

superipermeganoob
Member
Registered: 2011-05-03
Posts: 26

Re: [SOLVED] unable to boot on F2FS with systemd-boot

Scimmia wrote:

This has nothing to do with the filesystem, it can't even find the device. Try booting the fallback initramfs.

EDIT: LOL, there's a typo in arch.conf that would explain this. optios -> options

ROTFL
Are you kidding me?
It's an hour I'm doing tests to make it go, and all for a simple N
Arch does not forgive even 8 bit? smile

the system completes the boot without problems, but in the tty1 i stay with the systemd log and does not allow to interact for make a login, is it normal?
I can log in other tty but not in tty1

Offline

#4 2017-07-05 16:48:00

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

Re: [SOLVED] unable to boot on F2FS with systemd-boot

Offline

Board footer

Powered by FluxBB