linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul van der Vlis <paul@vandervlis.nl>
To: linux-raid@vger.kernel.org
Subject: Re: Good hardware for mdadm
Date: Sat, 30 Aug 2014 10:45:11 +0200	[thread overview]
Message-ID: <lts2un$j2o$1@ger.gmane.org> (raw)
In-Reply-To: <CAH3kUhE1veLpy1k4=SvQO4vwNkkUevLUaaZ=B5Q3RB5rDWRV_Q@mail.gmail.com>

op 30-08-14 02:44, Roberto Spadim schreef:
> i'm considering that you are using x86, x86_64 hardware, what's your
> application?

I am a sysadmin and I administrate many machines: webservers and
mailservers located in a datacenter, fileservers located at firms, etc.

> there's no bios test (must check if the newer version of this server
> have uefi and work differente), it just don't boot the disk and go to
> next boot
> but for your question: yes... maybe with 'lucky' it can't boot, a
> "bad" (crashed) grub could stop server startup
> 
> maybe others questions that you could check before solving this boot
> problem is why use a "bad" disk?

I would replace it when I would know it's bad.

> why shutdown a server?

Kernel updates.

> why remote startup a server?

Because it's work to go to such a location.

> why use a 'bad' disk?

I would replace it when I would know it's bad.

> if it's a ha system, 

Not really. Maybe.

> include a human to check monthly, or something
> like it, if the server is ok clean,something like it, 

You can't check that way if a MBR boots.

> since ha
> probably include a real time application or a security or risk
> application, or anything like it

I don't know about such an application. But maybe it would be possible
to read the MBR and check it with a copy. I was looking for a redundant
solution, maybe I must forget that.

> probably you must check others solutions at hardware level, some
> computers have dual bios (yes if one bios is lost you have the other
> to boot the computer), 

That's not the problem. I did not see often problems with a bad bios on
a good-running system.

> maybe an openbios could help

It's difficult to buy hardware for coreboot. And I don't think coreboot
can check the booting process.

>, or a uefi bios, must check what's better

Do you know about UEFI bios-es who can check the process?

With regards,
Paul van der Vlis.

> 
> 
> 2014-08-29 18:47 GMT-03:00 Paul van der Vlis <paul@vandervlis.nl>:
>> Hi Roberto,
>>
>> op 29-08-14 22:44, Roberto Spadim schreef:
>>> i use two or more boot disks, if the first raid1 disk don't boot bios
>>> go to second boot disk, third, etc etc,
>>
>> In my opinion this only works when the boot-disk is completely defect or
>> removed. Not when the data in the MBR on that boot-disk is corrupt.
>>
>> Or did you test this, or do you have other reasons to believe that your
>> bios will handle this correct?
>>
>> With the boot-disk I mean the disk what's in the bios the first disk. So
>> this could also be the second raid1 disk. Or an USB stick.
>>
>>> you must write grub to mbr of each disk
>>
>> Of course.
>>
>> With regards,
>> Paul van der Vlis.
>>
>>> i'm using dell server r410 if i'm not wrong
>>>
>>> 2014-08-29 17:31 GMT-03:00 Paul van der Vlis <paul@vandervlis.nl>:
>>>> Hello,
>>>>
>>>> I like mdadm and I am using it many years. But in my opinion it has one
>>>> disadvantage: when the MBR of the boot-disk is corrupt, the machine will
>>>> not boot.
>>>>
>>>> A bios could check this. Wait for some kind of signal from Grub or
>>>> Linux, and after a timeout boot from another disk. But I don't know
>>>> about a bios with that feature.
>>>>
>>>> A PCIe card could do something like that, but I don't know about such a
>>>> PCIe card.
>>>>
>>>> Is there such hardware?
>>>> What do you do to avoid this problem?
>>>>
>>>> With regards,
>>>> Paul van der Vlis.
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Paul van der Vlis Linux systeembeheer, Groningen
>>>> http://www.vandervlis.nl/
>>>>
>>>> --
>>>> 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
>>>
>>>
>>>
>>
>>
>>
>>
>>
>> --
>> Paul van der Vlis Linux systeembeheer, Groningen
>> http://www.vandervlis.nl/
>>
>> --
>> 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
> 
> 
> 





-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl/


      reply	other threads:[~2014-08-30  8:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 20:31 Good hardware for mdadm Paul van der Vlis
2014-08-29 20:44 ` Roberto Spadim
2014-08-29 21:47   ` Paul van der Vlis
2014-08-29 21:52     ` Adam Talbot
2014-08-30  8:25       ` Paul van der Vlis
2014-08-29 22:38     ` Roger Heflin
2014-08-30  8:35       ` Paul van der Vlis
2014-08-30  9:53         ` Roger Heflin
2014-08-30 10:37           ` Paul van der Vlis
2014-08-30 15:56             ` Brad Campbell
2014-08-30  0:44     ` Roberto Spadim
2014-08-30  8:45       ` Paul van der Vlis [this message]

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='lts2un$j2o$1@ger.gmane.org' \
    --to=paul@vandervlis.nl \
    --cc=linux-raid@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).