On Saturday, 8 June 2019 20:45:45 BST Grant Taylor wrote: > On 6/8/19 12:26 PM, Mick wrote: > > Were these contents not there, or is it that the new version of > > modules do not work? > > The old (original for the sake of this thread) versions (restored from > backups) work just fine. > > The version produced during the first emerge -DuNe @world worked. At > least I'm not aware of any problems. > > The version produced during the second emerge -DuNe @world did not work.
This sounds as if it may be related to a move from an older gcc to a newer version. Checking my understanding: 1. The old modules, compiled with the old gcc and toolchain worked fine. 2. The new modules, compiled with the new gcc but old libtool, binutils and glibc worked (usually you update these or @system, before you update the whole world). 3. The new modules, compiled with the new gcc and toolchain rebuilt the second time do not work (this would use libtools, binutils, glibc, now compiled with the new gcc). 4. All of the above happens with the old kernel, which was not rebuilt with the new toolchain. 5. New kernel(s) compiled thereafter will not boot. You have not mentioned if you upgraded gcc. The error you get about modules failing to load sounds like a path/symlink error, or a linux headers error, or a change of arch. Since both vbox and zfs modules fail to boot I would not think this is a zfs isolated problem. Have you tried forcing the loading of these modules? modprobe --force --verbose <module_name> What errors do you get with the new non-booting kernels? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
