Putting grub back on new mirror disk

Putting grub back on new mirror disk

[Timothy D. Lenz]

Have a computer with 4 500Gb seagate drives setup in 2 mirror pairs. The 
first pair, sda/sdb have 3 partitions, Boot/os/programs, Swap, 
data/storage for vdr.

I've had to replace drives several times. These seagates are junk, but 
warranty is up this year and then, if I manage to get some money, I'd 
like to replace them with a pair of WD 1Tb reds.

This time it was sda that went bad. Got it replaced, got the partitions 
back in the arrays and no sign of errors during rebuilds. but when I 
tried to put grub back on, I got some kind of error. Thought I did it 
the same way I've done it before, the way I was told in #grub.

---------------------------------------------------------------------
vorg@x64VDR:~$ su
Password:
x64VDR:/home/vorg# grub-install /dev/sda && grub-install /dev/sdb
/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>
x64VDR:/home/vorg# exit
exit
vorg@x64VDR:~$
---------------------------------------------------------------------

Re: Putting grub back on new mirror disk

[Timothy D. Lenz]

When I last checked the grub version was when I got the help in the 
#grub channel on freenode irc: (GNU GRUB 1.98~20100115-1)

I may have done an apt-get update/upgrade since, but it would have been 
a long time ago. I didn't ask on irc this time because a busy day and 
couldn't wait for response. I already am on this list which is why I 
checked here. I want to do a full upgrade, and build a new kernel when I 
get some time. But wanted to get it back to where it was before the 
drive dies first. I'll take a closer look at the replies here tommrow 
when I get a chance.

Still trying to figure out why I also lost audio on DVI output for vdr. 
I sent the computer to a shop this time thinking they would be able to 
take care of things. They replaced a sata cable and the power supply 
(said it was dieing which is possible) and reset the cmos :( but missed 
the fact that the drive was bad or 3 arrays where down.

On 3/13/2013 8:34 PM, Chris Murphy wrote:
>
> On Mar 13, 2013, at 8:29 PM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
>>
>> x64VDR:/home/vorg# grub-install /dev/sda && grub-install /dev/sdb
>
> What happens when you issue the commands separately?
>
>> /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>
>
> I'm going to guess an old version of prerelease GRUB2 since device.map isn't used anymore. Dollars to donuts help-grub@ will ask you to upgrade to current upstream GRUB2.
>
> grub-install --version
>
> If installing to sda or sdb fail separately, use --debug flag and put that up on pastebin. Many, many changes are in the final release of 2.00, which is now about 9 months old.
>
>
> Chris Murphy
>
>
>

Re: Putting grub back on new mirror disk

[Timothy D. Lenz]

Had a couple minutes, so here is the paste for just sda.

http://pastebin.com/5eMJELyx


x64VDR:/home/vorg# grub-install --version
grub-install (GRUB) 1.98+20100804-14


On 3/13/2013 8:34 PM, Chris Murphy wrote:
>
> On Mar 13, 2013, at 8:29 PM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
>>
>> x64VDR:/home/vorg# grub-install /dev/sda && grub-install /dev/sdb
>
> What happens when you issue the commands separately?
>
>> /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>
>
> I'm going to guess an old version of prerelease GRUB2 since device.map isn't used anymore. Dollars to donuts help-grub@ will ask you to upgrade to current upstream GRUB2.
>
> grub-install --version
>
> If installing to sda or sdb fail separately, use --debug flag and put that up on pastebin. Many, many changes are in the final release of 2.00, which is now about 9 months old.
>
>
> Chris Murphy
>
>
>

Re: Putting grub back on new mirror disk

[Chris Murphy]

On Mar 14, 2013, at 3:01 PM, "Timothy D. Lenz" <tlenz@vorgon.com> wrote:

> Had a couple minutes, so here is the paste for just sda.
> 
> http://pastebin.com/5eMJELyx

It's looking at the device.map, and it's also considering md0 as a grub device which doesn't seem correct. Try:

grub-install --recheck /dev/sda


Chris Murphy

Re: Putting grub back on new mirror disk

[Chris Murphy]

On Mar 14, 2013, at 3:31 PM, Timothy D. Lenz <tlenz@vorgon.com> wrote:

> This message said no errors. does that mean grub is now back on sda correctly?

That should be the case yes.

> 
> Here is the current device.map:
> (fd0)	/dev/fd0
> (hd0)	/dev/disk/by-id/ata-ST3500413AS_Z3T69GCE
> (hd1)	/dev/disk/by-id/ata-ST3500418AS_5VMJ49P1
> (hd2)	/dev/disk/by-id/ata-ST3500320AS_9QM35MY5
> (hd3)	/dev/disk/by-id/ata-ST3500820AS_9QM6V6JF
> 
> 
> Hmm, wonder if that didn't update correctly as the replacement drive would have a different number.

? All four entries are different.

Chris Murphy

Re: Putting grub back on new mirror disk

[Timothy D. Lenz]

hd0 would have changed because it's a new drive. But all the numbers 
match the device list at /dev/disk/by-id


On 3/14/2013 2:39 PM, Chris Murphy wrote:
>
> On Mar 14, 2013, at 3:31 PM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
>
>> This message said no errors. does that mean grub is now back on sda correctly?
>
> That should be the case yes.
>
>>
>> Here is the current device.map:
>> (fd0)	/dev/fd0
>> (hd0)	/dev/disk/by-id/ata-ST3500413AS_Z3T69GCE
>> (hd1)	/dev/disk/by-id/ata-ST3500418AS_5VMJ49P1
>> (hd2)	/dev/disk/by-id/ata-ST3500320AS_9QM35MY5
>> (hd3)	/dev/disk/by-id/ata-ST3500820AS_9QM6V6JF
>>
>>
>> Hmm, wonder if that didn't update correctly as the replacement drive would have a different number.
>
> ? All four entries are different.
>
> Chris Murphy--
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Putting grub back on new mirror disk

[Timothy D. Lenz]

Ok, was thinking it was checking that grub got installed. So the map may 
have had the old drive listed instead of the new drive. But the map was 
force updated to match.

On 3/14/2013 5:57 PM, Chris Murphy wrote:
> On Mar 14, 2013, at 6:48 PM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
>
>> hd0 would have changed because it's a new drive. But all the numbers match the device list at /dev/disk/by-id
>
> I don't understand what you're saying or asking. The --recheck flag causes grub-install to look at /dev/disk/by-id to create a new device.map. So the device.map and /dev/disk/by-id should be the same, at least with this variant of GRUB. Some use /dev/sdX designations, some use UUID.
>
>
> Chris Murphy
>

Re: Putting grub back on new mirror disk

[Chris Murphy]

On Mar 14, 2013, at 10:41 PM, "Timothy D. Lenz" <tlenz@vorgon.com> wrote:

> Ok, was thinking it was checking that grub got installed. So the map may have had the old drive listed instead of the new drive. But the map was force updated to match.

Yeah. Grub is dense and really non-obvious. And has changed a LOT in the three years since 1.98.

Chris Murphy