== Comment: #0 - Ekaterina Teplova - 2016-04-04 13:15:52 ==
Can not IPL after installation
The system is not usable after installation
Please see attachment
Both reproduced on 441 and 443
== Comment: #6 - Ekaterina Teplova - 2016-04-05 07:22:40 ==
After successful installation, the system is not able to IPL. It always drops into initramfs. This happens on LPAR, KVM
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/dasda1] fsck.ext4 -a -C0 /dev/dasda1
/dev/dasda1: clean, 56293/1103760 files, 368171/4409184 blocks
done.
mount: mounting /dev/dasda1 on /root failed: Invalid argument
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... Warning: overlayroot: debug is
busted
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
run-init: current directory on the same filesystem as the root: error 0
Target filesystem doesn't have requested /sbin/init.
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
chvt: can't open console
No init found. Try passing init= bootarg.
Couldn't get a file descriptor referring to the console
/scripts/panic/console_setup: line 77: can't create /dev/tty1: No such
device or
address
[ 10.444115] 32regs_prefetch: 20981.600 MB/sec
[ 10.444117] xor: using function: 32regs (24004.400 MB/sec)
[ 10.450086] md: raid6 personality registered for level 6
[ 10.450088] md: raid5 personality registered for level 5
[ 10.450089] md: raid4 personality registered for level 4
[ 10.453796] md: raid10 personality registered for level 10
[ 10.471091] Btrfs loaded
[ 10.507400] EXT4-fs (dasda1): Unrecognized mount option "subvol=" or
missing
value
/scripts/panic/console_setup: line 77: can't open /dev/tty1: No such
device or a
ddress
/scripts/panic/console_setup: line 77: can't create /dev/tty2: No such
device or
address
/scripts/panic/console_setup: line 77: can't open /dev/tty2: No such
device or a
ddress
/scripts/panic/console_setup: line 77: can't create /dev/tty3: No such
device or
address
/scripts/panic/console_setup: line 77: can't open /dev/tty3: No such
device or a
ddress
/scripts/panic/console_setup: line 77: can't create /dev/tty4: No such
device or
address
/scripts/panic/console_setup: line 77: can't open /dev/tty4: No such
device or a
ddress
/scripts/panic/console_setup: line 77: can't create /dev/tty5: No such
device or
address
/scripts/panic/console_setup: line 77: can't open /dev/tty5: No such
device or a
ddress
/scripts/panic/console_setup: line 77: can't create /dev/tty6: No such
device or
address
/scripts/panic/console_setup: line 77: can't open /dev/tty6: No such
device or a
ddress
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) [6n
== Comment: #9 - Hendrik Brueckner - 2016-04-05 08:17:38 ==
(In reply to comment #6)
> After successful installation, the system is not able to IPL. It always
> drops into initramfs. This happens on LPAR, KVM
>
>
> Begin: Will now check root file system ... fsck from util-linux 2.27.1
> [/sbin/fsck.ext4 (1) -- /dev/dasda1] fsck.ext4 -a -C0 /dev/dasda1
> /dev/dasda1: clean, 56293/1103760 files, 368171/4409184 blocks
> done.
> mount: mounting /dev/dasda1 on /root failed: Invalid argument
Mounting the root file system fails.
> done.
> Begin: Running /scripts/local-bottom ... done.
> Begin: Running /scripts/init-bottom ... Warning: overlayroot: debug is
> busted
> mount: mounting /dev on /root/dev failed: No such file or directory
> done.
> mount: mounting /run on /root/run failed: No such file or directory
> run-init: current directory on the same filesystem as the root: error 0
> Target filesystem doesn't have requested /sbin/init.
> run-init: current directory on the same filesystem as the root: error 0
> run-init: current directory on the same filesystem as the root: error 0
> run-init: current directory on the same filesystem as the root: error 0
> run-init: current directory on the same filesystem as the root: error 0
> run-init: current directory on the same filesystem as the root: error 0
> chvt: can't open console
> No init found. Try passing init= bootarg.
> Couldn't get a file descriptor referring to the console
> /scripts/panic/console_setup: line 77: can't create /dev/tty1: No such
> device or
> address
> [ 10.444115] 32regs_prefetch: 20981.600 MB/sec
> [ 10.444117] xor: using function: 32regs (24004.400 MB/sec)
> [ 10.450086] md: raid6 personality registered for level 6
> [ 10.450088] md: raid5 personality registered for level 5
> [ 10.450089] md: raid4 personality registered for level 4
> [ 10.453796] md: raid10 personality registered for level 10
> [ 10.471091] Btrfs loaded
> [ 10.507400] EXT4-fs (dasda1): Unrecognized mount option "subvol=" or
> missing
> value
Looks like the btrfs subvol= option is specified but the ext4 is used as file system. Thus, mounting as ext4 fails because subvol= is not a valid ext4 mount options.
Seems to be a regression of
Bug 138903 - LP1557329 - Installation with btrfs ends in "initramfs" after final installation-reboot
== Comment: #14 - Thorsten Diehl - 2016-04-05 08:30:18 ==
rootfs can be mounted manually, content of fstab does not show any ugly things:
mount /dev/dasda1 /mnt
(initramfs) ?6n
? 7250.730119! EXT4-fs (dasda1): couldn't mount as ext3 due to feature incompati
bilities
? 7250.730386! EXT4-fs (dasda1): couldn't mount as ext2 due to feature incompati
bilities
? 7250.732954! EXT4-fs (dasda1): mounted filesystem with ordered data mode. Opts
: (null)
cat /mnt/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/dasda1 during installation
UUID=ee5d9e90-d769-4179-813b-4e2910362811 / ext4 errors=remount
-ro 0 1
# swap was on /dev/dasda2 during installation
UUID=a73e84d0-ad06-414b-bacc-2dd1b53e3bd0 none swap sw
0 0
(initramfs) ?6n
== Comment: #17 - Thorsten Diehl - 2016-04-05 10:01:12 ==
The problem seems to be that the kernel parameter line (in /etc/zipl.conf), created by the installer, has a subvol statement:
? 0.007949? Linux version 4.4.0-16-generic (buildd@z13-018) (gcc version 5.3.1 20160320 (Ubuntu/Linaro 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:32:30 UTC 2016 (Ubuntu 4.4.0-16.32-generic 4.4.6)
? 0.007951? setup: Linux is running as a z/VM guest operating system in 64-bit mode
? 0.008600? setup: Max memory size: 2048MB
? 0.009717? setup: Reserving 128MB of memory at 1920MB for crashkernel (System RAM: 1920MB)
? 0.009729? numa: NUMA mode: plain
? 0.018817? Zone ranges:
? 0.018818? DMA ?mem 0x0000000000000000-0x000000007fffffff?
? 0.018820? Normal empty
? 0.018821? Movable zone start for each node
? 0.018822? Early memory node ranges
? 0.018823? node 0: ?mem 0x0000000000000000-0x0000000077ffffff?
? 0.018824? Initmem setup node 0 ?mem 0x0000000000000000-0x0000000077ffffff?
? 0.023584? PERCPU: Embedded 17 pages/cpu @00000000755bc000 s30208 r8192 d31232 u69632
? 0.023637? Built 1 zonelists in Node order, mobility grouping on. Total pages: 483840
? 0.023637? Policy zone: DMA
? 0.023639? Kernel command line: root=UUID=bb3a3e14-a67e-42d2-9a48-576034828428 rootflags=subvol= crashkernel=128M BOOT_IMAGE=0
Default Comment by Bridge