<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="-1"><font face="Courier New, Courier, monospace">Ian,
that is not expected at all, especially not booting with the
old kernel.<br>
Since you still have the old contents, can you paste the
contents of /boot/extlinux/extlinux.conf?<br>
BTW, which BananaPi do you use? I've updated all my BPi-M1
without issues, but it is a rule for me to update in this
order:<br>
1) yum and rpm<br>
2) all but kernel<br>
3) kernel<br>
To maybe that is why it didn't happen to me.<br>
<br>
Thanks.<br>
Pablo.</font></font><br>
</p>
<div class="moz-cite-prefix">El 14/5/18 a las 18:36, Ian Pilcher
escribió:<br>
</div>
<blockquote type="cite"
cite="mid:052382cb-d822-b031-a8eb-96b509b7f15b@gmail.com">Ran a
'yum update' on my Banana Pi firewall this morning and ended up
<br>
with an unbootable system. (The previous kernel wouldn't boot
either.)
<br>
<br>
I ended up copying my entire SD card, installing the latest image,
<br>
growing the / partition, and copying the old root filesystem over.
<br>
Ultimately, I was able to get everything up and running.
<br>
<br>
This system was originally installed with
<br>
CentOS-Userland-7-armv7hl-Minimal-1611-BananaPi.img.xz.
<br>
<br>
I'm mainly wondering if this was expected. If so, did I miss the
<br>
warnings? If not, I do still have the dump of the unbootable
post-
<br>
upgrade SD card sitting around, if anyone who understands the boot
<br>
process on these things wants to investigate.
<br>
<br>
Either way, thanks for all the work that you all do!
<br>
<br>
</blockquote>
</body>
</html>