All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: "Stelios A." <stelios.a@gmail.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub not working under software RAID
Date: Fri, 01 Apr 2011 14:16:20 +0200	[thread overview]
Message-ID: <4D95C214.2000204@gmail.com> (raw)
In-Reply-To: <BANLkTikqUkofwNNMBWQE=rLDzso8VUDj6w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]

On 01.04.2011 13:53, Stelios A. wrote:
> Hi,
>
> It's been almost 2 months and that was a production server so reverted
> back to grub legacy.
>
>   
Please keep the list CC'ed. You don't need to do a complete install to
gather the info in question. Just launch the said commands from compile
directory, adding "./" when necessary.
> Thanks however
>
> 2011/3/31 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>   
>> On 08.02.2011 07:48, Stelios A. wrote:
>>     
>>> Hi all,
>>>
>>> I performed an upgrade from Lenny to Squeeze and didn't manage to
>>> install successfully the grub boot loader.
>>> See below the errors.
>>>
>>> ##################
>>> backup:/tmp# grub-install /dev/md0
>>> /usr/sbin/grub-probe: error: no such disk.
>>> Auto-detection of a filesystem of /dev/md0 failed.
>>> Please report this together with the output of "/usr/sbin/grub-probe
>>> --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to
>>> <bug-grub@gnu.org>
>>>
>>> ###################
>>> backup:/tmp# /usr/sbin/grub-probe --device-map="/boot/grub/device.map"
>>> --target=fs -v /boot/grub
>>> /usr/sbin/grub-probe: info: changing current directory to /dev.
>>> /usr/sbin/grub-probe: info: changing current directory to net.
>>> /usr/sbin/grub-probe: info: changing current directory to shm.
>>> /usr/sbin/grub-probe: info: changing current directory to pts.
>>> /usr/sbin/grub-probe: info: opening md0.
>>> /usr/sbin/grub-probe: error: no such disk.
>>>
>>>
>>>       
>> Could you supply the output of following commands:
>> cat /proc/mdstat
>> grub-fstest -d all -c `ls /dev/sd?|wc -l` /dev/sd? ls -- -l
>>
>> as well as first and last 128K of every array member?
>>
>>     
>>> _______________________________________________
>>> Bug-grub mailing list
>>> Bug-grub@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/bug-grub
>>>
>>>
>>>       
>>
>> --
>> Regards
>> Vladimir 'φ-coder/phcoder' Serbinenko
>>
>>
>>
>>     
>
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

       reply	other threads:[~2011-04-01 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=F+Ow2tszKQ+FBDtwLSYgev=sJA6Pjubm1MSBs@mail.gmail.com>
     [not found] ` <4D94D452.3010702@gmail.com>
     [not found]   ` <BANLkTikqUkofwNNMBWQE=rLDzso8VUDj6w@mail.gmail.com>
2011-04-01 12:16     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
     [not found] <4D52EBFA.6040307@tortus.com>
     [not found] ` <4D94D420.8090505@gmail.com>
     [not found]   ` <4D95E486.8030803@tortus.com>
2011-04-01 14:54     ` Grub not working under software RAID Vladimir 'φ-coder/phcoder' Serbinenko
     [not found]       ` <4D95E852.20503@tortus.com>
2011-04-01 15:07         ` Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D95C214.2000204@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=stelios.a@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.