@notrin Welcome to the Rockstor community and thanks for bringing your prior email support query to the forum. There are more eyes here and certainly more expertise. I’ll do what I can to chip in here so we might sort what issues you may have run into.
We have had some reports of the 4.12 kernel not working where there was prior function with 4.10. But to flesh out the particular upgrade problems you encountered a little more I understand, from the email thread that lead to this forum post, that you also had issues with samba not working after an upgrade. This is most likely unrelated to the kernel failure and there is a little history of samba failing after a certain update, especially where that update was interrupted by a premature reboot. I’m not sure of the history in your case but just trying to tease out what we can look at independently here in the hope that we can divide and conquer.
So to summarise you updated to stable release, presumably from a 3.9.1-0 iso install. And given we have not release an iso for a very long time that ends up being quite a large update which incorporates an upstream CentOS version shift. Partly our failing due to long periods between isos but there are plans and mechanisms in the works to address this: but for now we have to go from where we find ourselves.
So given you have a stable subscription I’m going to suggest that we try and divide out your kernel issue from the rest of your system, given that a successful update should still allow you to boot into the older kernel. So lets get that bit sorted first.
Could you confirm the version of Rockstor you are currently running? I.e. top right of Web-UI and due to a bug when moving from testing to stable to also confirm an installed stable version via:
yum info rockstor
So assuming you are currently running 3.9.1-0, ie a non updated iso install. There is some sense in first updating to the latest testing channel release; as the resulting 3.9.1-16 was also released as the first of the next run of 3.9.2 stable channel versions. We droped testing channel releases after that point due to other, mostly resource related, background issues; but there is a will to re-establish this channel in time. Please see the following forum thread ‘Intro’ / ‘Quick history’ sections for some context:
So if you are on at least 3.9.1-0 I suggest that you first try updating to the latest testing channel version, by way of a step towards getting you ultimately to the latest stable, but via the command line so we can see what might be ‘breaking’ if in deed it does this time. So if on at least 3.9.1-0, ie last released clean iso install, subscribe to the testing channel first via the Web-UI but don’t initiate the update itself via the Web-UI. I suggest you then initiate the update on the command line there after thus:
yum update
That way we can see how it goes.
This should also bring with it the 4.12 kernel but if the update is successful this time we can work our way back around to the 4.12 kernel issue. For now once the update is complete and assuming it gives no errors you can reboot (but only once it’s actually finished) and re-select the 4.10 kernel to try and keep our changes to a minimum for now.
Lets take it from there and see how that goes. That update, if from 3.9.1-0 is still going to be very large as the rest of the system will still be updated to the most recent upstream CentOS. But at least this way we can see where / if the update fails this time.
Hope that helps and do past the ‘yum update’ output in the terminal. What we are looking for is a potential repeat of such events as previously broke the samba update that was associated with changes at around CentOS 7.4 ie see:
for some reports of broken updates breaking samba. @Haioken, @Bert, and @doenietzomoeilijk worked on this problem in that thread and I saw it myself temporarily on systems here:
But an interrupted update could have frozen this ‘broken samba’ state in-place and a whole host of other potential issues.
See how you go and if in doubt just post the output of:
yum info rockstor
and we can take it from there.