From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: Wilson Jonathan <piercing_male@hotmail.com>, linux-raid@vger.kernel.org
Subject: Re: Growing array, duplicating data, shrinking array questions.
Date: Wed, 04 Dec 2013 09:36:13 +1100 [thread overview]
Message-ID: <529E5CDD.9030702@websitemanagers.com.au> (raw)
In-Reply-To: <BLU0-SMTP122E4AB9F76CD51C2F7AD5A98D50@phx.gbl>
On 04/12/13 05:15, Wilson Jonathan wrote:
>> Now here is where I know/think I have a big problem with a 3tb drive in
>> a "bios" system and need confirmation before going any further...
>>
>> ___question 2___
>> I'm guessing that as the bios can only see the tail end of the hard
>> drive it would not be able to load the data from the "mbr" (still there
>> despite being a GPT formatted disk) and proceed to load the first stage
>> boot loader because it will think the "mbr" should be at the start of
>> the "700GB" which in reality is 2.2TB into the disk, would this be a
>> correct assumption? (
>>
>> Actually I could probably test this by installing
>> (grub-install /dev/sdX) then going into the bios and telling it to boot
>> from that disk while the original boot drives (containing
>> biosboot /boot /root) were still pluged in, if it failed then I know its
>> not going to work.
> I've concluded that I'm going to have to create some form of work around
> as the bios cannot load the mbr from the 3tb drive, and then the grub2
> stuff in the bios boot partition which can then load additional grub2
> stuff from the /boot partition.
I don't know why you seem to have an issue here... IME (limited), the
only thing I had to do was create a small 1M partition at the beginning
of the disk, from memory the OS installer did this automatically for me.
Then grub can get installed to the drive and it all works magically. I'm
really not sure of all the technical details, and I can't actually find
the machine I did this on right now, but I do remember that is how I
made it work.....
BTW, I'd suggest that if grub can "see" the partitions/etc properly,
then just install grub to the USB, and leave the kernel/initrd/etc on
the raid on the hard drives. Keep a image of the USB (or at least the
first few MB that grub is using), so if the USB dies you can boot from a
live CD, mount the hard drives, and use dd to write the grub image to a
new USB.
Personally, I'd try and get grub working from the HDD, I don't like to
find out that I have a problem *after* a reboot for either an upgrade or
as part of recovering from another problem.
Regards,
Adam
--
Adam Goryachev Website Managers www.websitemanagers.com.au
prev parent reply other threads:[~2013-12-03 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 18:09 Growing array, duplicating data, shrinking array questions Wilson Jonathan
2013-11-30 16:07 ` Wilson Jonathan
2013-12-03 18:15 ` Wilson Jonathan
2013-12-03 22:36 ` Adam Goryachev [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=529E5CDD.9030702@websitemanagers.com.au \
--to=mailinglists@websitemanagers.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=piercing_male@hotmail.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 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).