1 |
2007/7/5, Dan Farrell <dan@×××××××××.cx>: |
2 |
> On Thu, 5 Jul 2007 18:40:20 +0200 |
3 |
> Galevsky <galevsky@×××××.com> wrote: |
4 |
> |
5 |
> > 2007/7/5, Albert Hopkins <marduk@g.o>: |
6 |
> > > On Thu, 2007-07-05 at 11:36 +0200, Galevsky wrote: |
7 |
> > > > Many thanks for you suggestion. I tried a boot with no fall back, |
8 |
> > > > but nothing added neither to boot.log nor to dmesg. I am sure to |
9 |
> > > > target the right kernel image with no typo into grub.conf . This |
10 |
> > > > new kernel is a =xen-sources-2.6.16.49, and I configured it |
11 |
> > > > making an oldconfig based on current =gentoo-sources-2.6.20 |
12 |
> > > > running kernel. So, errors cannot come from drivers or such |
13 |
> > > > things, but specific xen options. Does anyone know any xen option |
14 |
> > > > able to prevent the kernel to boot up ? |
15 |
> > > |
16 |
> > > I guess I (still) don't understand what your issue is. So I went |
17 |
> > > back and read your original post. Maybe I misunderstood it. |
18 |
> > > |
19 |
> > > * What do you mean by "remote host"? |
20 |
> > |
21 |
> > I rent a dedicated host. Thus, I have no physical access to the |
22 |
> > machine. And the reason why I used the fall-back feature into grub is |
23 |
> > to avoid the use of a boring rescue system (via a web interface) to |
24 |
> > take back the control of a not-responding box. |
25 |
> > |
26 |
> > > * If your box "does not boot" how would you expect to see a |
27 |
> > > boot.log or dmesg ? They don't exist if the system has not |
28 |
> > > booted. In fact "does not boot" implies that you can't |
29 |
> > > even log in to check for dmesg or boot logs. Perhaps you can |
30 |
> > > explain what it is exactly you mean by "does not boot". |
31 |
> > |
32 |
> > When I try to boot on the new kernel, I set it as the "default" one in |
33 |
> > grub.conf and reboot the box. And I wait for a few minutes. Then I try |
34 |
> > to log on, praying to find the box responding. |
35 |
> > |
36 |
> > First, with grub fall-back activated, the boot had fallen back and I |
37 |
> > was able to read the logs that contained the running kernel logs, but |
38 |
> > no info about the kernel boot that failed. That was the matter of my |
39 |
> > first mail: how to read the reasons of the first kernel-boot-attempt |
40 |
> > failure. |
41 |
> > |
42 |
> > Secondly, you advised me to turn fall back off. I do. The box is no |
43 |
> > more responding after reboot, and I have to launch the "rescue system" |
44 |
> > to log on my box, and read the /var/log/*. I thought previously that |
45 |
> > some pb happened -I didn't know when exactly-... and was waiting for |
46 |
> > more info in log files. But files were empty. So, I conclude that the |
47 |
> > boot procedure failed (and you too ;o)). |
48 |
> > |
49 |
> > Finally, I have to find out why my kernel is not booting. I tuned up |
50 |
> > well my previous kernel, a gentoo-sources-2.6.20 -this kernel runs |
51 |
> > currently my box very well- and the kernel I want to boot now is a |
52 |
> > xen-sources-2.6.16. I made an oldconfig on /proc/config.gz of the |
53 |
> > 2.6.20 running kernel, and fill in xen-dom0 specific options as |
54 |
> > indicated on the wiki tutorial [1]. So, I guess I did something wrong |
55 |
> > with the dom0 xen config, and asked for advice on xen specific options |
56 |
> > with my second post. |
57 |
> > |
58 |
> > > * Usually there is an error message on the console if there |
59 |
> > > is a boot loader/kernel issue with booting. |
60 |
> > > * Also you never posted your grub.conf. |
61 |
> > > |
62 |
> > > So hopefully you can come up with a specific explanation of "does |
63 |
> > > not boot" as well as your config and any console messages you get. |
64 |
> > > Else this becomes a "blind leading the blind" issue. |
65 |
> > |
66 |
> > I have no console message to provide you, I just know that my remote |
67 |
> > box is not responding when I try to boot another kernel (If you know |
68 |
> > the way to get logs, I'll be grateful :o)). And I checked the |
69 |
> > /var/log/* to be sure that the kernel was not running but just missing |
70 |
> > any network feature so that I could not log on the box despite the |
71 |
> > kernel was actually running. |
72 |
> > |
73 |
> > As for my grub.conf + 'ls -l /boot' , I will provide you in a while (I |
74 |
> > need to go home before), but I am not sure it is relevant. (just to |
75 |
> > check for typo I guess). |
76 |
> > |
77 |
> > > -- |
78 |
> > > Albert W. Hopkins |
79 |
> > > |
80 |
> > > -- |
81 |
> > > gentoo-user@g.o mailing list |
82 |
> > |
83 |
> > Many thanks to take care of my problem :o) |
84 |
> > |
85 |
> > Gal' |
86 |
> > |
87 |
> > [1]: http://gentoo-wiki.com/HOWTO_Xen_and_Gentoo |
88 |
> |
89 |
> from /etc/conf.d/rc: |
90 |
> # RC_BOOTLOG will generate a log of the boot messages shown on the |
91 |
> console. # Useful for headless machines or debugging. You need to |
92 |
> emerge the # app-admin/showconsole package for this to work. Note that |
93 |
> this probably # won't work correctly with boot splash. |
94 |
> |
95 |
> RC_BOOTLOG="no" |
96 |
> |
97 |
> I recommend you install showconsole and set RC_BOOTLOG to yes, that |
98 |
> might help you. It is possible that maybe something as mundane as |
99 |
> networking is failing for a stupid reason, and therefore you cant get |
100 |
> to the computer because it cant finish booting. |
101 |
> -- |
102 |
> gentoo-user@g.o mailing list |
103 |
> |
104 |
> |
105 |
|
106 |
Thank you Dan, but I did it before, and boot.log remains empty. In |
107 |
fact, the new kernel boot turns on like grub couldn't find the kernel |
108 |
image.... |
109 |
|
110 |
Hereafter my /boot content: |
111 |
|
112 |
sd-4421 boot # ll /boot |
113 |
total 13M |
114 |
-rw-rw-r-- 1 root root 767k Jul 6 00:02 |
115 |
System.map-2.6.16.49-xendedibox_r6_final |
116 |
-rw-r--r-- 1 root root 929k Jun 16 19:29 System.map-2.6.20-gentoo-r8 |
117 |
lrwxrwxrwx 1 root root 1 Apr 30 19:40 boot -> ./ |
118 |
-rw-rw-r-- 1 root root 31k Jul 6 00:02 config-2.6.16.49-xendedibox_r6_final |
119 |
-rw-r--r-- 1 root root 34k Jun 16 19:29 config-2.6.20-gentoo-r8 |
120 |
-rw-r--r-- 1 root root 753 Jul 4 23:30 gentoo-sources-2.6.18 |
121 |
drwxr-xr-x 2 root root 1.1k Jun 16 16:58 grub/ |
122 |
drwx------ 2 root root 13k Apr 30 19:40 lost+found/ |
123 |
drwxr-xr-x 2 root root 1.1k Jun 16 23:21 ref/ |
124 |
-rw-r--r-- 1 root root 5.9M Jul 6 00:02 |
125 |
vmlinux-syms-2.6.16.49-xendedibox_r6_final |
126 |
lrwxrwxrwx 1 root root 37 Jul 6 00:02 vmlinuz-2.6-xen -> |
127 |
vmlinuz-2.6.16.49-xendedibox_r6_final |
128 |
lrwxrwxrwx 1 root root 37 Jul 6 00:02 vmlinuz-2.6.16-xen -> |
129 |
vmlinuz-2.6.16.49-xendedibox_r6_final |
130 |
-rw-r--r-- 1 root root 2.4M Jul 6 00:02 vmlinuz-2.6.16.49-xendedibox_r6_final |
131 |
-rw-r--r-- 1 root root 2.4M Jun 16 19:29 vmlinuz-2.6.20-gentoo-r8 |
132 |
|
133 |
and my grub.conf: |
134 |
|
135 |
### START (grub.conf) |
136 |
sd-4421 boot # cat /boot/grub/grub.conf |
137 |
# Customized boot procedure |
138 |
|
139 |
default 0 |
140 |
timeout 1 |
141 |
#fallback 1 2 |
142 |
|
143 |
title Gentoo Linux 2.6.16-gentoo_xen_dom0 |
144 |
root (hd0,0) |
145 |
kernel /boot/vmlinuz-2.6-xen ro root=/dev/sda2 |
146 |
|
147 |
|
148 |
title Gentoo Linux 2.6.20-r8 |
149 |
root (hd0,0) |
150 |
kernel /boot/vmlinuz-2.6.20-gentoo-r8 ro root=/dev/sda2 |
151 |
|
152 |
|
153 |
title Gentoo Linux 2.6.18-r4-dedibox_r6_final |
154 |
root (hd0,0) |
155 |
kernel /boot/ref/2.6.18-gentoo-r4dedibox_r6_final ro root=/dev/sda2 |
156 |
### END (grub.conf) |
157 |
|
158 |
Well, let's try a boot on kernel /boot/vmlinuz-2.6-xen |
159 |
|
160 |
=> box not responding..... and via the rescue system: |
161 |
|
162 |
# ls /mnt/sda2/var/log/ |
163 |
portage user.log xen |
164 |
# more /mnt/sda2/var/log/user.log |
165 |
Jul 6 00:12:30 sd-4421 shutdown[4571]: shutting down for system reboot |
166 |
|
167 |
thus no log at all (xen log also empty). |
168 |
|
169 |
|
170 |
Gal' |
171 |
-- |
172 |
gentoo-user@g.o mailing list |