<!DOCTYPE html>
<html>
<head>
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
</head>
<body><div>Ubuntu upgrades make me very nervous, so I still haven't upgraded from 16.04 to 18.04.<br></div>
<div><br></div>
<div>Did you do an "upgrade" upgrade, or did you back up your files and do a bare metal install?<br></div>
<div><br></div>
<div><br></div>
<div>On Tue, Jan 29, 2019, at 1:15 PM, Khalid Baheyeldin wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Over the weekend, I upgraded my home server from Ubuntu 16.04 LTS to 18.04.<br></div>
<div>This is a bare metal machine, with a SATA disk.<br></div>
<div><br></div>
<div>I rebooted it then, and all worked well.<br></div>
<div><br></div>
<div>Then a kernel update came along today, so I applied it and rebooted.<br></div>
<div><br></div>
<div>Now, that server does not boot, with this kernel panic:<br></div>
<div><br></div>
<div>"Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"<br></div>
<div>Followed by a stack trace.<br></div>
<div><div><div><br></div>
<div>Searching around the recommended remedy is this, from a bootable DVD:<br></div>
<div><br></div>
<div><div># mount /dev/sda1 /mnt<br></div>
<div># mount --bind /dev /mnt/dev<br></div>
<div># mount --bind /dev/pts /mnt/dev/pts<br></div>
<div># mount --bind /proc /mnt/proc<br></div>
<div># mount --bind /sys /mnt/sys<br></div>
<div># chroot /mnt<br></div>
</div>
<div># update-initramfs -u -k 4.15.0-44-generic<br></div>
<div># update-grub2<br></div>
<div><br></div>
<div>The output from the last command is:<br></div>
<div><br></div>
<div><div># update-grub2 <br></div>
<div>Generating grub configuration file ...<br></div>
<div>Found linux image: /boot/vmlinuz-4.15.0-44-generic<br></div>
<div>Found initrd image: /boot/initrd.img-4.15.0-44-generic<br></div>
<div>Found linux image: /boot/vmlinuz-4.15.0-43-generic<br></div>
<div>Found initrd image: /boot/initrd.img-4.15.0-43-generic<br></div>
<div>Found memtest86+ image: /boot/memtest86+.elf<br></div>
<div>Found memtest86+ image: /boot/memtest86+.bin<br></div>
<div> WARNING: Failed to connect to lvmetad. Falling back to device scanning.<br></div>
<div>done<br></div>
</div>
<div><br></div>
<div>Note the warning, but I am not using LVM.<br></div>
<div><br></div>
<div>Still, I get the same panic error upon reboot. <br></div>
<div><br></div>
<div>Using the grub menu when booting, the previous kernel version works fine. <br></div>
</div>
<div><div><br></div>
<div><div>Also, the /boot directory is not a separate partition, so it has all the space it needs.<br></div>
<div><br></div>
<div>Any one else got a borked system after today's kernel upgrade?<br></div>
<div>-- <br></div>
</div>
<div><div dir="ltr"><div dir="ltr"><div><div>Khalid M. Baheyeldin<br></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div><u>_______________________________________________</u><br></div>
<div>kwlug-disc mailing list<br></div>
<div><a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a><br></div>
<div><a href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br></div>
</blockquote><div><br></div>
</body>
</html>