Re: boot problem after disk change on raid1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



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.

Thanks for your help.

Bunyamin.

2011/9/8 Bünyamin İzzet <bunyamin.izzet@xxxxxxxxx>


On Thu, Sep 8, 2011 at 8:11 AM, Devin Reade <gdr@xxxxxxx> wrote:
Bünyamin Ýzzet <bunyamin.izzet@xxxxxxxxx> wrote:

> On Wed, Sep 7, 2011 at 11:38 PM, Devin Reade <gdr@xxxxxxx> wrote:
>
[snip]
>>                        # grub
>>                        grub> device (hd0) /dev/sdb
>>                        grub> root (hd0,0)
>>                        grub> setup (hd0)
>>                        grub> quit
>
> It still does not boot. I could not see the error message, because it is a
> dedicated server and I am not sitting at the monitor of the server. So I
> type the lines in grub.conf manually to see the error (I'm not sure if it is
> the right thing to see the error).

If you mean that you typed the lines I gave above into grub.conf, then
that was not what was intended (and I doubt that it would work).  My
intent was that you get the system booted and running normally (perhaps
via the rescue disk), and after that execute 'grub' interactively
and issue those commands.

 Devin

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.

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.



# grub
Probing devices to guess BIOS drives. This may take a long time.


GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> root (hd1,0)
root (hd1,0)
Filesystem type is ext2fs, partition type 0xfd
grub> kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317

kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317
[Linux-bzImage, setup=0x1e00, size=0x1fe01c]
grub> initrd /initrd-2.6.18-238.19.1.el5.img

initrd /initrd-2.6.18-238.19.1.el5.img

Error 28: Selected item cannot fit into memory
grub> quit
quit

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux