Service restored

atreus has been rebooted and should be running normally. If any services have not restarted, please let me know (even if you can start them manually via userv or similar) so I can fix problems in the boot sequence.

atreus downtime

atreus is currently down. I suspect this was a kernel panic or something similar; the ISP will reboot it Monday (to avoid ridiculous out of office charges) and it should come back up smoothly at that point.

Upgraded to 7.1: remaining problems should be notified to me

Basically, we're done. If you spot problems, please let me know.

Upgrade largely complete

dovecot is going to need hammering back into shape, but everything else should be okay. Let me know if not…

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.

Atreus upgrade to Debian 7.1

This is now underway, starting with some tests of the old system, then a minimal upgrade, followed by the full upgrade. There will be a number of reboots, which I will try to announce (`wall` to logged-in users) before I do them.

Ongoing information as it happens…