Docker requires Linux Kernel Version 4.1


#1

Hi Guys

I recently looked at the UMC App Center for the first time since the 4.1 upgrade to find it unavailable.

The error message is:
"Could not fulfill the request.
Server error message:
The command has failed: The docker service is not running! The App Center will not work properly. Make sure docker.io is installed, try starting the service with “service docker start”.

Trying to start docker service give the message:
“Docker requires Linux Kernel 4.1, if you just updated, a reboot may be required”

Multiple reboots don’t resolve the issue.

uname -a give:
Linux ##NAME## 3.16-ucs109-amd64 #1 SMP Debian 3.16.5-1.109.201412161258 (2014-12-16) x86_64 GNU/Linux

How do I resolve/further test this issue?

Thanks
Tommo


#2

Hello Tommo,

first, please check if univention-kernel-image is installed. That’s the meta package that should always install the latest available kernel:

dpkg -l univention-kernel-image

You should see something like this on a fully updated UCS 4.1:

... ii univention-kernel-image 9.0.0-5.83.20151201113 amd64 UCS - Linux kernel (standard)

ii at the beginning of the line marks a package as installed.
un at the beginning of the line marks a package as not installed.

If it’s not installed, install it:

univention-install univention-kernel-image

second, check which kernel version are installed:

dpkg -l linux-image-*

Output on my system:

...
ii  linux-image-3.16-ucs109-amd64       3.16.5-1.109.201412161 amd64     Linux 3.16 for 64-bit PCs
ii  linux-image-3.16-ucs109-amd64-signe 1.0.2-1.5.201412171459 amd64     UCS - Linux kernel (standard)
ii  linux-image-3.16.0-ucs135-amd64     3.16.7-ckt11-1~bpo70+1 amd64     Linux 3.16 for 64-bit PCs
ii  linux-image-3.16.0-ucs135-amd64-sig 1.0.3-2.7.201507171759 amd64     UCS - Linux kernel (standard)
ii  linux-image-4.1.0-ucs153-amd64      4.1.6-1.153.2015102708 amd64     Linux 4.1 for 64-bit PCs
ii  linux-image-4.1.0-ucs153-amd64-sign 2.0.0-2.9.201510271532 amd64     UCS - Linux kernel (standard)
ii  linux-image-4.1.0-ucs163-amd64      4.1.6-1.163.2015113013 amd64      Linux 4.1 for 64-bit PCs
ii  linux-image-4.1.0-ucs163-amd64-sign 2.0.0-3.11.20151201113 amd64     UCS - Linux kernel (standard)

#3

Hi Grandjean

Thanks for your reply - sorry for the delay in responding over the weekend.

kernel and packages on my system appear to match yours, except for an additional kernel for ucs102.

Thoughts?

Thanks
Tommo

||/ Name Version Architecture Description +++-===================================-======================-======================-=========================================================================== ii univention-kernel-image 9.0.0-5.83.20151201113 amd64 UCS - Linux kernel (standard)

un linux-image-2.6-amd64 <none> (no description available) un linux-image-2.6-openvz-amd64 <none> (no description available) un linux-image-2.6-vserver-amd64 <none> (no description available) un linux-image-2.6-xen-amd64 <none> (no description available) ii linux-image-3.16-ucs102-amd64 3.16.5-1.102.201411021 amd64 Linux 3.16 for 64-bit PCs ii linux-image-3.16-ucs102-amd64-signe 1.0.1-4.4.201411040125 amd64 UCS - Linux kernel (standard) ii linux-image-3.16-ucs109-amd64 3.16.5-1.109.201412161 amd64 Linux 3.16 for 64-bit PCs ii linux-image-3.16-ucs109-amd64-signe 1.0.2-1.5.201412171459 amd64 UCS - Linux kernel (standard) ii linux-image-3.16.0-ucs135-amd64 3.16.7-ckt11-1~bpo70+1 amd64 Linux 3.16 for 64-bit PCs ii linux-image-3.16.0-ucs135-amd64-sig 1.0.3-2.7.201507171759 amd64 UCS - Linux kernel (standard) ii linux-image-4.1.0-ucs153-amd64 4.1.6-1.153.2015102708 amd64 Linux 4.1 for 64-bit PCs ii linux-image-4.1.0-ucs153-amd64-sign 2.0.0-2.9.201510271532 amd64 UCS - Linux kernel (standard) ii linux-image-4.1.0-ucs163-amd64 4.1.6-1.163.2015113013 amd64 Linux 4.1 for 64-bit PCs ii linux-image-4.1.0-ucs163-amd64-sign 2.0.0-3.11.20151201113 amd64 UCS - Linux kernel (standard)


#4

Hi Tommo,

okay, so you have all recent Kernel versions installed, but your system keeps booting an old one.

Your system boots:
[ul][li]linux-image-3.16-ucs109-amd64[/li][/ul]

Newer Kernels that are installed:
[ul][li]linux-image-3.16.0-ucs135-amd64[/li]
[li]linux-image-4.1.0-ucs153-amd64[/li]
[li]linux-image-4.1.0-ucs163-amd64[/li][/ul]

And because of Docker and general interest in an up-to-date Kernel, we want to boot the latest (linux-image-4.1.0-ucs163-amd64). That should be done automatically, but for some reason, your system doesn’t.

My first guess is, that somewhere in your GRUB configuration the 3.16-ucs109 Kernel is hardcoded. Could you please check if a file called /boot/grub/menu.lst exists and paste the content here? Additionally, please provide the output of:

ucr search --brief grub

Best regards,
Michael Grandjean


#5

Hi Michael

/boot/grub/menu.lst exists - content is:

default 0
timeout 5

Output from ucr search --brief grub:

grub/append: <empty>
grub/backgroundimage: /boot/grub/uniboot.png
grub/bootsplash: splash
grub/color/highlight: white/green
grub/color/normal: black/black
grub/efi: <empty>
grub/generate-menu-lst: yes
grub/gfxmode: 800x600@16
grub/gfxpayload: 800x600@24,800x600@16,800x600
grub/grub1root: <empty>
grub/loglevel: 0
grub/menu/color/highlight: white/green
grub/menu/color/normal: black/black
grub/quiet: yes
grub/rootdelay: <empty>
grub/timeout: 5
grub/title: <empty>
grub/xenhopt: <empty>

Thanks
Tommo


#6

Further to the last post - running univention-grub-generate-menu-lst doesn’t populate the menu.lst file


#7

Hi Tommo,

The menu.lst is a legacy from GRUB 1.x times and is not really necessary with GRUB 2. Nevertheless, if it’s present, it might overwrite other settings, e.g. which kernel to boot. I guessed that the kernel version would be “hardcoded” in your menu.lst. But obviously it isn’t and your menu.lst is fine (mine looks just the same).

So, let’s try something else. First, please set the GRUB timeout to something more comfortable:

ucr set grub/timeout=30

Now reboot your system. When the GRUB bootloader appears, it should look like this (not exactly the same, less german, etc. but you get the idea):


Do you also have a 4.1.0 Kernel there? Can you select it (arrow keys) and boot (enter/retun)?

If this is not working, can you please paste the output of

update-grub?

Best regards,
Michael Grandjean


#8

Hi Michael

Only the 3.16 kernels show in grub:


Update-grub gives:

Generating grub.cfg ... Found background: /boot/grub/uniboot.png Found linux image: /boot/vmlinuz-4.1.0-ucs163-amd64 Found initrd image: /boot/initrd.img-4.1.0-ucs163-amd64 Found linux image: /boot/vmlinuz-4.1.0-ucs153-amd64 Found initrd image: /boot/initrd.img-4.1.0-ucs153-amd64 Found linux image: /boot/vmlinuz-3.16.0-ucs135-amd64 Found initrd image: /boot/initrd.img-3.16.0-ucs135-amd64 Found memtest86+ image: /boot/memtest86+.bin done Generating legacy menu.lst from current kernels


#9

Shows grub the new kernels now after you have executed update-grub? If not, can paste the content of the file /boot/grub/grub.cfg


#10

grub boot menu still only show the 3.16 kernels.

/boot/grub/grub.cfg contains:

[code]#

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
load_env
fi
set default=“0”

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
fi
}

if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
set gfxmode=800x600@16
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_NZ
insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
insmod png
background_image -m stretch /boot/grub/uniboot.png
set timeout=30

END /etc/grub.d/00_header

BEGIN /etc/grub.d/05_debian_theme

set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue

END /etc/grub.d/05_debian_theme

BEGIN /etc/grub.d/08_linux_xen

END /etc/grub.d/08_linux_xen

BEGIN /etc/grub.d/10_linux

menuentry ‘Univention Corporate Server, with Linux 4.1.0-ucs163-amd64’ --class univention --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=800x600@24,800x600@16,800x600
insmod gzio
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
linux /boot/vmlinuz-4.1.0-ucs163-amd64 root=/dev/mapper/vg_ucs-root ro quiet loglevel=0 rootdelay=5 splash
initrd /boot/initrd.img-4.1.0-ucs163-amd64
}
menuentry ‘Univention Corporate Server, with Linux 4.1.0-ucs163-amd64 (recovery mode)’ --class univention --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=800x600@24,800x600@16,800x600
insmod gzio
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
linux /boot/vmlinuz-4.1.0-ucs163-amd64 root=/dev/mapper/vg_ucs-root ro single
initrd /boot/initrd.img-4.1.0-ucs163-amd64
}
menuentry ‘Univention Corporate Server, with Linux 4.1.0-ucs153-amd64’ --class univention --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=800x600@24,800x600@16,800x600
insmod gzio
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
linux /boot/vmlinuz-4.1.0-ucs153-amd64 root=/dev/mapper/vg_ucs-root ro quiet loglevel=0 rootdelay=5 splash
initrd /boot/initrd.img-4.1.0-ucs153-amd64
}
menuentry ‘Univention Corporate Server, with Linux 4.1.0-ucs153-amd64 (recovery mode)’ --class univention --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=800x600@24,800x600@16,800x600
insmod gzio
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
linux /boot/vmlinuz-4.1.0-ucs153-amd64 root=/dev/mapper/vg_ucs-root ro single
initrd /boot/initrd.img-4.1.0-ucs153-amd64
}
menuentry ‘Univention Corporate Server, with Linux 3.16.0-ucs135-amd64’ --class univention --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=800x600@24,800x600@16,800x600
insmod gzio
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
linux /boot/vmlinuz-3.16.0-ucs135-amd64 root=/dev/mapper/vg_ucs-root ro quiet loglevel=0 rootdelay=5 splash
initrd /boot/initrd.img-3.16.0-ucs135-amd64
}
menuentry ‘Univention Corporate Server, with Linux 3.16.0-ucs135-amd64 (recovery mode)’ --class univention --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=800x600@24,800x600@16,800x600
insmod gzio
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
linux /boot/vmlinuz-3.16.0-ucs135-amd64 root=/dev/mapper/vg_ucs-root ro single
initrd /boot/initrd.img-3.16.0-ucs135-amd64
}

END /etc/grub.d/10_linux

BEGIN /etc/grub.d/20_memtest86+

menuentry “Memory test (memtest86+)” {
insmod part_msdos
insmod lvm
insmod ext2
set root=‘lvm/vg_ucs-root’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=‘lvm/vg_ucs-root’ d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
else
search --no-floppy --fs-uuid --set=root d64fd054-d7d5-4f9c-ac6d-6c07977a3de9
fi
linux16 /boot/memtest86+.bin
}

END /etc/grub.d/20_memtest86+

BEGIN /etc/grub.d/30_os-prober

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 ###[/code]


#11

The grub.cfg seems to be correct. So GRUB should offer you the actual 4.1 kernel. Is the partition that you use for booting really mounted on /boot? Whats the output from

mount
ls -l /boot/grub/

#12

I’m not too familiar with disk operations in linux, so apologies if I’m overlooking anything obvious!

mount:

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=253455,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=205772k,mode=755) /dev/mapper/vg_ucs-root on / type ext4 (rw,relatime,data=ordered) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=411520k) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu) cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct) cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event) cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)

ls -l /boot/grub

-r--r--r-- 1 root root 7384 Jan 27 12:50 grub.cfg -rw-r--r-- 1 root root 192 Jan 27 12:50 menu.lst -rw-r--r-- 1 root root 192 Jan 27 12:50 menu.lst.bak -rw-r--r-- 1 root root 370185 Nov 18 15:26 uniboot.png -rw-r--r-- 1 root root 2226340 Jul 7 2015 unicode.pf2


#13

There’s no boot partition mounted. AFAIK normally there should exist a own partion for /boot. What’s the output of

ls -l /dev/sd*
cat /etc/fstab

#14

ls -l /dev/sd*

brw-rw---T 1 root disk 8, 0 Jan 28 10:04 /dev/sda brw-rw---T 1 root disk 8, 1 Jan 28 10:04 /dev/sda1 brw-rw---T 1 root disk 8, 2 Jan 28 10:04 /dev/sda2 brw-rw---T 1 root disk 8, 5 Jan 28 10:04 /dev/sda5

cat /etc/fstab

[code]#Warning: This file is auto-generated and might be overwritten by

univention-config-registry.

Please edit the following file(s) instead:

#Warnung: Diese Datei wurde automatisch generiert und kann durch

univention-config-registry überschrieben werden.

Bitte bearbeiten Sie an Stelle dessen die folgende(n) Datei(en):

/etc/univention/templates/files/etc/apt/sources.list.d/20_ucs-online-component.list

deb http://updates.software-univention.de/4.0/maintained/component/ 4.0-0-errata/all/
deb http://updates.software-univention.de/4.0/maintained/component/ 4.0-0[/code]


#15

Is the second really your /etc/fstab? It should look like this.


#16

Um - that’s pretty different!

That’s definitely the contents of the fstab file.

So a couple of things -

  1. the fstab has obviously been overwritten by some UCS code - should I log this as a bug?
  2. How do I rebuild the fstab file?

Thanks


#17

I think for submitting a you need more informations over the circumstances. The easiest way to rebuild the /etc/fstab would be from a backup. The only other way I now is doing it by hand. If you are lucky, the result it should look like this

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
UUID=c04be00c-89ec-4cb2-aaea-67df7a3ceef0       /       ext4    acl,errors=remount-ro,user_xattr        0       1
proc    /proc   proc    defaults        0       0
/dev/sda1      /boot   ext4    defaults,acl,user_xattr 0       0
/dev/mapper/vg_ucs-root    /home   ext4    defaults,acl,user_xattr 0       0
/dev/sda2        none    swap    sw      0       0
/dev/sr0        /cdrom  auto    user,noauto,exec        0       0
/dev/fd0        /floppy vfat    user,noauto,exec        0       0

But should check first that /dev/sda1 is really the boot partion. If it is so you should move the missing content from /boot to the boot partition. First please paste the output of

mount /dev/sda1 /mnt
ls -l /mnt
ls -l /boot

#18

I’ll look back through the backups, but in the meantime - output as follows:

mount /dev/sda1 /mnt returns nothing.

ls -l /mnt

-rw-r--r-- 1 root root 318 Feb 2 2015 boot.msg -rw-r--r-- 1 root root 155840 Nov 3 2014 config-3.16-ucs102-amd64 -rw-r--r-- 1 root root 155845 Dec 17 2014 config-3.16-ucs109-amd64 drwxr-xr-x 5 root root 1024 Jan 23 2015 grub -rw-r--r-- 1 root root 28620794 Jan 23 2015 initrd.img-3.16-ucs102-amd64 -rw-r--r-- 1 root root 28626676 Jan 23 2015 initrd.img-3.16-ucs109-amd64 drwxr-xr-x 2 root root 12288 Jan 23 2015 lost+found -rw-r--r-- 1 root root 176764 Sep 25 2014 memtest86+.bin -rw-r--r-- 1 root root 178944 Sep 25 2014 memtest86+_multiboot.bin -rw-r--r-- 1 root root 2680773 Nov 3 2014 System.map-3.16-ucs102-amd64 -rw-r--r-- 1 root root 2682560 Dec 17 2014 System.map-3.16-ucs109-amd64 -rw-r--r-- 1 root root 4128720 Nov 3 2014 vmlinuz-3.16-ucs102-amd64 -rw-r--r-- 1 root root 4132640 Nov 4 2014 vmlinuz-3.16-ucs102-amd64.efi.signed -rw-r--r-- 1 root root 4132400 Dec 17 2014 vmlinuz-3.16-ucs109-amd64 -rw-r--r-- 1 root root 4136320 Dec 18 2014 vmlinuz-3.16-ucs109-amd64.efi.signed

ls -l /boot

-rw-r--r-- 1 root root 318 Nov 18 15:20 boot.msg -rw-r--r-- 1 root root 158137 Jul 17 2015 config-3.16.0-ucs135-amd64 -rw-r--r-- 1 root root 167319 Oct 28 00:19 config-4.1.0-ucs153-amd64 -rw-r--r-- 1 root root 167319 Dec 1 04:33 config-4.1.0-ucs163-amd64 drwxr-xr-x 2 root root 4096 Jan 27 12:50 grub -rw-r--r-- 1 root root 28701600 Nov 18 15:22 initrd.img-3.16.0-ucs135-amd64 -rw-r--r-- 1 root root 28838051 Nov 18 15:28 initrd.img-4.1.0-ucs153-amd64 -rw-r--r-- 1 root root 28835916 Dec 3 23:04 initrd.img-4.1.0-ucs163-amd64 -rw-r--r-- 1 root root 176764 Feb 28 2015 memtest86+.bin -rw-r--r-- 1 root root 178944 Feb 28 2015 memtest86+_multiboot.bin -rw-r--r-- 1 root root 2687620 Jul 17 2015 System.map-3.16.0-ucs135-amd64 -rw-r--r-- 1 root root 2851250 Oct 28 00:19 System.map-4.1.0-ucs153-amd64 -rw-r--r-- 1 root root 2851250 Dec 1 04:33 System.map-4.1.0-ucs163-amd64 -rw-r--r-- 1 root root 4141952 Jul 17 2015 vmlinuz-3.16.0-ucs135-amd64 -rw-r--r-- 1 root root 4145872 Jul 18 2015 vmlinuz-3.16.0-ucs135-amd64.efi.signed -rw-r--r-- 1 root root 4365360 Oct 28 00:16 vmlinuz-4.1.0-ucs153-amd64 -rw-r--r-- 1 root root 4369280 Oct 28 03:26 vmlinuz-4.1.0-ucs153-amd64.efi.signed -rw-r--r-- 1 root root 4365424 Dec 1 04:31 vmlinuz-4.1.0-ucs163-amd64 -rw-r--r-- 1 root root 4369344 Dec 1 07:33 vmlinuz-4.1.0-ucs163-amd64.efi.signed


#19

Nothing recoverable from my backup images. Whatever caused this - it happened over a year ago.

It looks like manually building fstab is the only option.


#20

Ok then you should take this as base (in the post above is a mistake):

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/vg_ucs-root      /       ext4    acl,errors=remount-ro,user_xattr        0       1
proc    /proc   proc    defaults        0       0
/dev/sda1      /boot   ext4    defaults,acl,user_xattr 0       0
/dev/sda2        none    swap    sw      0       0
/dev/sr0        /cdrom  auto    user,noauto,exec        0       0

Then you should copy the new kernel to the boot parttion (it must of course be first mounted on /mnt):

rsync -avzog --protect-args --delete --progress --include=* --include=. /boot/ /mnt/

Then you can check for other volumes:

ls -l /dev/vg_ucs/*