Savannah Administration - News: Small downtime

Group

Main
- Main
- View members
- Search
Homepage
Download
Support
- Submit new
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Mailing lists
Source code
Tasks
- Submit new
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
News
- Browse
- Atom feed
- ~~Submit~~
- ~~Manage~~

Small downtime

Item posted by Sylvain Beucler <Beuc> on Thu 08 Nov 2007 12:47:55 AM UTC.

When trying to install a new kernel, we got an error where initrd would apparently failed to setup RAID correctly, but unfortunately it was not possible to get the exact error message via the remote serial interface. For now we're back to the old kernel.

initrd -- mkinitrd ? (posted by Aurélien DESBRIÈRES, Wed 19 Dec 2007 05:51:11 PM UTC)

Are you speaking about mkinitrd ?

when, i update the kernel, i update the mkinitrd first. because if it's not on ... it will not fit well.
and i put the line (at the end of the installation of the kernel):

...
cd /boot
mkinitrd -c -k 2.6.21 -m reiserfs

cd /
lilo

and all fit well

so no wrong message ...

RE: initrd -- mkinitrd ? (posted by Sylvain Beucler, Fri 21 Dec 2007 11:29:24 PM UTC)

In this case, we installed the Debian linux-image-2.6.22-3-vserver-686 package from backports.org. The post-install process normaly takes care of creating the initrd image - and it did create /boot/initrd.img-2.6.22-3-vserver-686.

To recap: I had managed to load the system, but all the additional partitions didn't mount. Then I changed AUTOSTART=true in /etc/default/mdadm; in that configuration, initrd loaded but failed to load the root filesystem and got stuck with a length error message that the virtual remote console doesn't let us fully inspect. We're waiting for a intervention at the collocation to have somebody watch the physical screen now ;)