WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: Xen 3.2.1 @ Debian 5.0 - /boot/grub is gone after hangon

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: Xen 3.2.1 @ Debian 5.0 - /boot/grub is gone after hangon
From: Adrian Gajan <admin@xxxxxxxxxx>
Date: Sat, 15 Aug 2009 14:28:01 +0100 (GMT+01:00)
Delivery-date: Sat, 15 Aug 2009 06:28:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <25913726.1941250339384590.JavaMail.root@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello again,

it's running now, ramdisk created via mkinitramfs -o /tmp/initramfs-$(uname -r) 
, then moved to to right place /boot/ and everythings fine. But I haven't found 
anything relevant what would explain how that came.

Regards,

Adrian

----- Original Message -----
From: "Adrian Gajan" <admin@xxxxxxxxxx>
To: "xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Sent: Saturday, August 15, 2009 2:29:44 PM GMT +01:00 Amsterdam / Berlin / Bern 
/ Rome / Stockholm / Vienna
Subject: Xen 3.2.1 @ Debian 5.0 - /boot/grub is gone after hangon

Hello,

dom0 freezed, after reboot /boot/grub is completely gone. I recognized it first 
as I was about starting a DomU and taking a look on xm list (no domain running 
except of dom0). 
/boot:
-rw-r--r-- 1 root root  90K 2009-08-14 07:05 config-2.6.26-2-686-bigmem
-rw-r--r-- 1 root root  85K 2009-08-14 07:15 config-2.6.26-2-xen-686
drwxr-xr-x 2 root root 4.0K 2009-08-15 14:05 grub
-rw-r--r-- 1 root root 7.0M 2009-08-15 13:28 initrd.img-2.6.26-2-686-bigmem
-rw-r--r-- 1 root root 928K 2009-08-14 07:05 System.map-2.6.26-2-686-bigmem
-rw-r--r-- 1 root root 885K 2009-08-14 07:15 System.map-2.6.26-2-xen-686
-rw-r--r-- 1 root root 1.5M 2009-08-14 07:05 vmlinuz-2.6.26-2-686-bigmem
-rw-r--r-- 1 root root 1.5M 2009-08-14 07:14 vmlinuz-2.6.26-2-xen-686
-rw-r--r-- 1 root root 368K 2008-06-28 17:28 xen-3.2-1-i386.gz

/boot/grub:
-rw-r--r-- 1 root root  191 2009-08-15 13:28 default
-rw-r--r-- 1 root root   15 2009-08-15 13:28 device.map
-rw-r--r-- 1 root root 4.0K 2009-08-15 14:05 menu.lst
-rw-r--r-- 1 root root 4.5K 2009-08-15 14:05 menu.lst~

it shoulb be like on my other xen host:
/boot/*xen*
-rw-r--r-- 1 root root   85149 2008-05-29 05:01 /boot/config-2.6.24-18-xen
-rw-r--r-- 1 root root   85174 2008-10-22 05:27 /boot/config-2.6.24-21-xen
-rw-r--r-- 1 root root   85174 2008-11-25 00:05 /boot/config-2.6.24-22-xen
-rw-r--r-- 1 root root 7801677 2009-03-11 20:19 /boot/initrd.img-2.6.24-18-xen
-rw-r--r-- 1 root root 7771954 2009-02-23 15:35 
/boot/initrd.img-2.6.24-18-xen.bak
-rw-r--r-- 1 root root 7771699 2008-11-20 20:57 /boot/initrd.img-2.6.24-21-xen
-rw-r--r-- 1 root root 7771665 2008-11-20 20:57 
/boot/initrd.img-2.6.24-21-xen.bak
-rw-r--r-- 1 root root 7478554 2009-04-04 21:33 /boot/initrd.img-2.6.24-22-xen
-rw-r--r-- 1 root root  883490 2008-05-29 05:01 /boot/System.map-2.6.24-18-xen
-rw-r--r-- 1 root root  883938 2008-10-22 05:27 /boot/System.map-2.6.24-21-xen
-rw-r--r-- 1 root root  883938 2008-11-25 00:05 /boot/System.map-2.6.24-22-xen
-rw-r--r-- 1 root root 1731090 2008-05-29 05:01 /boot/vmlinuz-2.6.24-18-xen
-rw-r--r-- 1 root root 1732645 2008-10-22 05:27 /boot/vmlinuz-2.6.24-21-xen
-rw-r--r-- 1 root root 1732951 2008-11-25 00:05 /boot/vmlinuz-2.6.24-22-xen
-rw-r--r-- 1 root root  370588 2009-02-20 07:56 /boot/xen-3.2.gz

In other words, no ramdisks are available.
I tried reinstall the xen packages; there comes:
/boot/initrd.img-2.6.26-2-xen-686 does not exist. Cannot update.

How do I create all missing files (ramdisks)? vmlinux is present 
(vmlinuz-2.6.26-2-xen-686).

Thanks a lot for every help.

Adrian 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>