<div>The system works just fine now. I think there was a disk check or something at boot time which takes 15-20 minutes (I rarely reboot the system once or twice a year), and it made me think that the system does not boot.<br>
</div><div><br></div><div>Thanks for your help.</div><div><br></div><div>Bunyamin.</div><br><div class="gmail_quote">2011/9/8 Bünyamin İzzet <span dir="ltr"><<a href="mailto:bunyamin.izzet@gmail.com">bunyamin.izzet@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><br><div class="gmail_quote"><div class="im">On Thu, Sep 8, 2011 at 8:11 AM, Devin Reade <span dir="ltr"><<a href="mailto:gdr@gno.org" target="_blank">gdr@gno.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Bünyamin Ýzzet <<a href="mailto:bunyamin.izzet@gmail.com" target="_blank">bunyamin.izzet@gmail.com</a>> wrote:<br>
<br>
> On Wed, Sep 7, 2011 at 11:38 PM, Devin Reade <<a href="mailto:gdr@gno.org" target="_blank">gdr@gno.org</a>> wrote:<br>
><br>
</div>[snip]<br>
<div>>> # grub<br>
>> grub> device (hd0) /dev/sdb<br>
>> grub> root (hd0,0)<br>
>> grub> setup (hd0)<br>
>> grub> quit<br>
><br>
</div><div>> It still does not boot. I could not see the error message, because it is a<br>
> dedicated server and I am not sitting at the monitor of the server. So I<br>
> type the lines in grub.conf manually to see the error (I'm not sure if it is<br>
> the right thing to see the error).<br>
<br>
</div>If you mean that you typed the lines I gave above into grub.conf, then<br>
that was not what was intended (and I doubt that it would work). My<br>
intent was that you get the system booted and running normally (perhaps<br>
via the rescue disk), and after that execute 'grub' interactively<br>
and issue those commands.<br>
<div><div><br> Devin</div></div></blockquote><div><br></div></div><div>As you said, I booted the system via rescue disk, and execute grub and issue those commands. Then, I reboot the system, but it does not boot.</div>
<div><br></div><div>Then I searched on google about logging grub errors, which I could not find anything useful (meybe I did not look enough). So that, in rescue system, I execute grub and type commands in grub.conf (results are below) to see which error occurs.</div>
<div class="im">
<div><br></div><div><br></div><div><br></div><div># grub<br> Probing devices to guess BIOS drives. This may take a long time.<br><br><br> GNU GRUB version 0.97 (640K lower / 3072K upper memory)<br><br> [ Minimal BASH-like line editing is supported. For the first word, TAB<br>
lists possible command completions. Anywhere else TAB lists the possible<br> completions of a device/filename.]<br>grub> root (hd1,0)<br>root (hd1,0)<br> Filesystem type is ext2fs, partition type 0xfd<br>grub> kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317<br>
<br>kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317<br> [Linux-bzImage, setup=0x1e00, size=0x1fe01c]<br>grub> initrd /initrd-2.6.18-238.19.1.el5.img<br><br>initrd /initrd-2.6.18-238.19.1.el5.img<br><br>
Error 28: Selected item cannot fit into memory<br>grub> quit<br>quit</div></div></div>
</blockquote></div><br>