Monday, July 08, 2013

Kernel upgrade held back

Our /boot is…tiny. It probably made sense when Martin did the sizing on install back under (I think) the 2.4 series kernel, but it's not big enough to contain two 2.6+ kernels and the initrd with MODULES=most.

Accordingly I'm holding back the kernel upgrade, and doing the rest of the system (which shouldn't depend on it). I've generated an initrd for our 2.6 kernel with MODULES=dep, which looks largely sane, but I don't want to install the 3.2 series kernel until I've had a chance to research a little more and convince myself it's found the modules we actually care about. Once I've done that, and probably rebooted for good measure, we should be able to move up to the 3.2 kernel, assuming it can do a dependency scan off a 2.6 kernel; I may have to do some work by hand to ensure the early user space has access to the 3ware RAID controller and its file systems.

Main upgrade now going ahead.

No comments: