How to repair kernel version

AlexEv1337

Member
Credits
395
I install Ubuntu 20.10 in cloud provider and receive

# uname -r
4.15.0-60-generic

# ls -ls /boot
total 147484
248 -rw-r--r-- 1 root root 248258 Jan 18 17:01 config-5.8.0-41-generic
248 -rw-r--r-- 1 root root 248258 Feb 5 03:41 config-5.8.0-43-generic
4 drwxr-xr-x 4 root root 4096 Feb 11 21:21 grub
0 lrwxrwxrwx 1 root root 27 Feb 11 21:21 initrd.img -> initrd.img-5.8.0-43-generic
54552 -rw-r--r-- 1 root root 55795996 Feb 11 01:07 initrd.img-5.8.0-41-generic
54552 -rw-r--r-- 1 root root 55798352 Feb 11 21:21 initrd.img-5.8.0-43-generic
0 lrwxrwxrwx 1 root root 27 Jan 28 07:27 initrd.img.old -> initrd.img-5.8.0-41-generic
16 drwx------ 2 root root 16384 Feb 11 01:07 lost+found
5516 -rw------- 1 root root 5635676 Jan 18 17:01 System.map-5.8.0-41-generic
5516 -rw------- 1 root root 5635676 Feb 5 03:41 System.map-5.8.0-43-generic
0 lrwxrwxrwx 1 root root 24 Feb 11 21:21 vmlinuz -> vmlinuz-5.8.0-43-generic
13416 -rw------- 1 root root 13715296 Jan 18 17:08 vmlinuz-5.8.0-41-generic
13416 -rw------- 1 root root 13715296 Feb 5 04:04 vmlinuz-5.8.0-43-generic
0 lrwxrwxrwx 1 root root 24 Jan 28 07:27 vmlinuz.old -> vmlinuz-5.8.0-41-generic

# ls -lha /lib/modules
total 16K
drwxr-xr-x 4 root root 4.0K Feb 11 21:21 .
drwxr-xr-x 47 root root 4.0K Feb 11 21:22 ..
drwxr-xr-x 5 root root 4.0K Jan 28 07:27 5.8.0-41-generic
drwxr-xr-x 5 root root 4.0K Feb 11 21:21 5.8.0-43-generic

# dpkg -l | grep linux-
ii linux-base 4.5ubuntu4 all Linux image base package
ii linux-firmware 1.190.3 all Firmware for Linux kernel drivers
ii linux-generic 5.8.0.43.48 amd64 Complete Generic Linux kernel and headers
ii linux-headers-5.8.0-41 5.8.0-41.46 all Header files related to Linux kernel version 5.8.0
ii linux-headers-5.8.0-41-generic 5.8.0-41.46 amd64 Linux kernel headers for version 5.8.0 on 64 bit x86 SMP
ii linux-headers-5.8.0-43 5.8.0-43.49 all Header files related to Linux kernel version 5.8.0
ii linux-headers-5.8.0-43-generic 5.8.0-43.49 amd64 Linux kernel headers for version 5.8.0 on 64 bit x86 SMP
ii linux-headers-generic 5.8.0.43.48 amd64 Generic Linux kernel headers
ii linux-image-5.8.0-41-generic 5.8.0-41.46 amd64 Signed kernel image generic
ii linux-image-5.8.0-43-generic 5.8.0-43.49 amd64 Signed kernel image generic
ii linux-image-generic 5.8.0.43.48 amd64 Generic Linux kernel image
ii linux-modules-5.8.0-41-generic 5.8.0-41.46 amd64 Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP
ii linux-modules-5.8.0-43-generic 5.8.0-43.49 amd64 Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP
ii linux-modules-extra-5.8.0-41-generic 5.8.0-41.46 amd64 Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP
ii linux-modules-extra-5.8.0-43-generic 5.8.0-43.49 amd64 Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP

How to repair UNAME and kernel version?
 


f33dm3bits

Gold Member
Gold Supporter
Credits
25,629
What does your Grub file(/boot/grub/grub.cfg) look like?
 

AlexEv1337

Member
Credits
395
Ups, I have undertand this issue! server booting from /dev/sda
but my system setting into /dev/sdb and /dev/sda has old grub from Ubuntu 16.04

# cat /etc/fstab
proc /proc proc defaults 0 0
# /dev/sda1
UUID=e9774f22-de84-45a3-847c-a2ae6b347676 /boot ext3 defaults 0 0
# /dev/sda2 belongs to LVM volume group 'vg0'
/dev/vg0/root / ext4 defaults 0 0
/dev/vg0/swap swap swap defaults 0 0

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 447.1G 0 disk
├─sda1 8:1 0 512M 0 part
└─sda2 8:2 0 446.6G 0 part
sdb 8:16 0 447.1G 0 disk
├─sdb1 8:17 0 512M 0 part /boot
└─sdb2 8:18 0 446.6G 0 part
├─vg0-root 253:0 0 435.6G 0 lvm /
└─vg0-swap 253:1 0 10G 0 lvm [SWAP]
sdc 8:32 0 447.1G 0 disk

# fdisk -l
Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: SAMSUNG MZ7LM480
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: 0xa8dfb7c3

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1050623 1048576 512M 83 Linux
/dev/sda2 1050624 937701039 936650416 446.6G 8e Linux LVM


Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: SAMSUNG MZ7LM480
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: 0x7b9f5e42

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 1050623 1048576 512M 83 Linux
/dev/sdb2 1050624 937701039 936650416 446.6G 8e Linux LVM


Disk /dev/sdc: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: SAMSUNG MZ7LM480
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: 432C0825-6733-4FD4-9B5B-96B8C2C099A0


Disk /dev/mapper/vg0-root: 435.63 GiB, 467757170688 bytes, 913588224 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/mapper/vg0-swap: 10 GiB, 10737418240 bytes, 20971520 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
 
Last edited:

f33dm3bits

Gold Member
Gold Supporter
Credits
25,629
/boot/grub/grub.cfg looks correct, can your run update-grub and share the output?
 

AlexEv1337

Member
Credits
395
No, sorry. I decide erase this server at all and now I waiting result of
# dd if=/dev/zero of=/dev/sda
and
# dd if=/dev/zero of=/dev/sdb
118751232000 bytes (119 GB, 111 GiB) copied, 281.246 s, 422 MB/s
if issue will be repeated in next generation of this system I will continue this topic
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Top