You are not logged in.
Hi all.
I operate several openfiler boxes for months without any noticeable problem.
I issued a "conary updateall" on monday on a single box, and it leaded to unbootable system.
Fortunately I can boot the system with the former kernel in the grub menu, so this is not disruptive, just very unsatisfying.
I cannot screenshot the result with the newest installed kernel, but it's a list of "missing /lib/<module.ko> "ending with a kernel panic. The path in the message itself is weird, since kernel modules aren't usually immediately in /lib/.
I investigated by creating a very regular openfiler sandbox: PC mobo with PERC 5 and a disk mirror.
I installed it with the certified media already used, OK.
I updated it with "conary updateall" and it got worse: after update, neither the newest kernel nor... the media-installed one are bootable, both lead to a kernel panic with this alledged loss of modules.
Can somebody confirm that issuing a "conary updateall" those very recent days is safe ? By the way BE VERY CAREFULL there may be a landmine somewhere...
Regards, Charles.
Offline
grandsifflet wrote:
Hi all.
I operate several openfiler boxes for months without any noticeable problem.
I issued a "conary updateall" on monday on a single box, and it leaded to unbootable system.
Fortunately I can boot the system with the former kernel in the grub menu, so this is not disruptive, just very unsatisfying.
I cannot screenshot the result with the newest installed kernel, but it's a list of "missing /lib/<module.ko> "ending with a kernel panic. The path in the message itself is weird, since kernel modules aren't usually immediately in /lib/.
I investigated by creating a very regular openfiler sandbox: PC mobo with PERC 5 and a disk mirror.
I installed it with the certified media already used, OK.
I updated it with "conary updateall" and it got worse: after update, neither the newest kernel nor... the media-installed one are bootable, both lead to a kernel panic with this alledged loss of modules.
Can somebody confirm that issuing a "conary updateall" those very recent days is safe ? By the way BE VERY CAREFULL there may be a landmine somewhere...
Regards, Charles.
Confirmed. See following links for more info but no fix available at the moment.
https://forums.openfiler.com/viewtopic.php?id=4721
https://forums.openfiler.com/viewtopic.php?id=4734
bye
Offline
Hi skp_123 and thanks.
The fact is, that each and every update attempt from a newly media installed OF box lead to the death of the box.
On a box running for several month, a rollback to former (and second in order after initial install) kernel is the fix: just ignore the failing update.
But on a newly media-installed box, as I tried again few minutes ago, even the original kernel installed from CDROM isn't a rescue anymore: "conary updateall" destroys the box without any possible rollback or alternate GRUB menu choice.
So DON'T update an OF box that wasn't already updated last month :-)
Hope this will be investigated and fixed soon, because all newbies trying OF could think that it is not usable as updating means killing.
Regards, Charles.
Offline
This was due to a strange situation where 64-bit version of binutils was not built and the group update succeeded regardless.
We have now resolved this issue. Apologies to all that were affected by it.
R.
Offline
Confirmed, upgrade to 2.6.29.6-0.16 with "conary updateall" from the "out-of-the-ISO" 2.6.26.8-1.0.11 now works fine.
Thanks to all :-)
Regards, Charles.
Offline