Re: Grub2 reinstall on raid1 system.
On Sat, Jan 15, 2011 at 5:29 PM, Jack Schneider <puck@dp-indexing.com> wrote:
> On Fri, 14 Jan 2011 05:25:45 -0700
> Bob Proulx <bob@proulx.com> wrote:
>> Jack Schneider wrote:
>> >
>> > I have a raid1 based W/S running Debian Squeeze uptodate. (was
>> > until ~7 days ago) There are 4 drives, 2 of which had never been
>> > used or formatted. I configured a new array using Disk Utility from
>> > a live Ubuntu CD. That's where I screwed up... The end result was
>> > the names of the arrays were changed on the working 2 drives.
>> > IE: /dev/md0 to /dev/126 and /dev/md1 became md127.
>>
>> Something else must have happened too. Because normally just adding
>> arrays will not rename the existing arrays. I am not familiar with
>> the "Disk Utility" that you mention.
>
> As I mentioned in a prior post,Grub was leaving me at a Grub rescue>prompt.
>
> I followed this procedure:
> http://www.gnu.org/software/grub/manual/html_node/GRUB-only-offers-a-rescue-shell.html#GRUB-only-offers-a-rescue-shell
> Booting now leaves me at a busy box: However the Grub menu is correct.
> With the correct kernels. So it appears that grub is now finding the
> root/boot partitions and files.
Assemble the arrays at the busybox/initramfs prompt with
"--update=super-minor" in order to update the minor.
>> You can inspect the raid partitions with --detail and --examine.
>>
>> mdadm --examine /dev/sda1
>> mdadm --detail /dev/md0
>
> mdadm --examine /dev/sda1 & /dev/sda2 gives I think a clean result
> I have posted the output at : http://pastebin.com/pHpKjgK3
> mdadm --detail /dev/md0 --> gives mdadm: md device /dev/md0 does not
> appear to be active.
>
> There is no /proc/mdstat data output.
How about "mdadm --detail /dev/md125" given that
http://pastebin.com/pHpKjgK3 shows that sda1 and sdc1 have 125 as
their minor.
Reply to: