OpenVZ Forum: Support » Lost /boot after installing fza kernel

Home » General » Support » Lost /boot after installing fza kernel

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Lost /boot after installing fza kernel [message #33094]

Mon, 22 September 2008 13:31

dcgva
Messages: 3
Registered: September 2008
Location: Geneva

Junior Member

Hi,

After installing a fresh minimal Debian 4.0, I updated my sources.list and installed a 'fzakernel-2.6.18-686' kernel, then rebooted.

Everything works fine except that my separated /boot partition is not mounted... The current kernel complains that 'ext2' file system type is unknown ! Well, has ext2 been removed from the standard kernel ?

Besides, a /etc/init.d/vz start yields :

Starting OpenVZ: failed to load module vzmon..failed

... while this modules exist on the system.

Any clue ?

Report message to a moderator

Re: Lost /boot after installing fza kernel [message #33096 is a reply to message #33094]

Mon, 22 September 2008 14:04

dcgva
Messages: 3
Registered: September 2008
Location: Geneva

Junior Member

(Additional infos)

Initially, I created more than 4 partitions on the physical disk (no LVM).

/dev/sda1 /boot
/dev/sda2 swap
/dev/sda3 /
(extended partition -> 4)
/dev/sda5 /var
/dev/sda6 /home

A 'df -h' doesn't show /boot, but the system was able to boot. Could it be that the kernel 'sees' only the last four partitions ?

Report message to a moderator

Re: Lost /boot after installing fza kernel [message #33097 is a reply to message #33094]

Mon, 22 September 2008 14:32

maratrus
Messages: 1495
Registered: August 2007
Location: Moscow

Senior Member

Hello,

this is not self compiled kernel, isn't it?
Please, show the config file of that kernel.

please, also "modinfo vzmon" output.

Quote:

Starting OpenVZ: failed to load module vzmon..failed

anything in dmesg, logs?
you can try to probe that module manually to find out the exact error message.

Report message to a moderator

Re: Lost /boot after installing fza kernel [message #33098 is a reply to message #33097]

Mon, 22 September 2008 15:30

dcgva
Messages: 3
Registered: September 2008
Location: Geneva

Junior Member

Well,

Since all was rather strange, I decided to restart from scratch. I did :

- Reinstall a fresh minimal Debian Sarge
- aptitude update -> upgrade (which I didn't do the last time)
- Included deb http://download.openvz.org/debian-systs etch openvz
in /etc/apt/sources.list
- aptitude install fzakernel-2.6.18-686
- aptitude install vzctl vzquota vzctl-ostmpl-debian vzprocps vzdump
- configured sysctl & vz
- rebooted

And everything worked fine ! /boot is visible and I can start /etc/init.d/vz.

The only difference with my previous attempt is that I attempted to install the fzakernel before making sure the initial installation had been 'stabilized' with an 'upgrade'. That may be the source of the problem...

Thanks for your help. It triggered some thoughts and I decided to reinstall properly Smile

Report message to a moderator

Previous Topic:	WHY apt-get does´nt work in new container.
Next Topic:	SOLVED: Destination Host Unreachable from VE on Public IP

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Aug 11 21:38:21 GMT 2024

Total time taken to generate the page: 0.02907 seconds