Re: issue with mdadm and mirroring drives
- To: debian-user@lists.debian.org
- Subject: Re: issue with mdadm and mirroring drives
- From: Marc Auslander <marcausl@gmail.com>
- Date: Wed, 18 Jan 2012 21:04:04 -0500
- Message-id: <[🔎] 87wr8o1m97.fsf@aptiva.optonline.net>
- In-reply-to: <ikJ3s-3G5-33@gated-at.bofh.it> (tv's message of "Wed\, 18 Jan 2012 20\:10\:02 +0100")
- References: <ikGyB-7EC-15@gated-at.bofh.it> <ikGRY-85T-15@gated-at.bofh.it> <ikHbj-nI-1@gated-at.bofh.it> <ikHO2-1gu-25@gated-at.bofh.it> <ikIAq-2D6-23@gated-at.bofh.it> <ikJ3s-3G5-33@gated-at.bofh.it>
This discussion opens a question I've been curious about.
IIUC, bios choses a boot device and runs the MBR code. Assuming
that's GRUB2 MBR code, GRUB2 then loads the 1.5 code hidden before the
first partition of the same device. Next step is to process grub.cfg.
Now, does that code contain a copy of grub.cfg? Or
does it read it from someplace? If the second, how does it decide
where/how to read grub.cfg.
I understand how, once it has grub.cfg, it decides what to boot. It's
where grub.cfg comes from that I don't understand.
Reply to: