linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: Neil Conway <nconway_kernel@yahoo.co.uk>,
	Hans Kristian Rosbach <hk@isphuset.no>,
	Mark Watts <m.watts@eris.qinetiq.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3TB disk hassles
Date: Thu, 16 Dec 2004 18:40:15 +0100	[thread overview]
Message-ID: <41C1C87F.6050900@dbservice.com> (raw)
In-Reply-To: <41C1C2AD.90902@dbservice.com>

Tomas Carnecky wrote:
> Neil Conway wrote:
>  > Right now, the only scheme I have vaguely concocted in my head that
> 
>> will make this work for us is to add another disk to become the boot
>> disk - this is actually a major PITA cos there's really no physical
>> space in the chassis - and then use a GPT/EFI (whatever?) partition
>> table on the big disk.  This means that BIOS won't understand the big
>> disk at all but that'll be OK since it isn't trying to boot from it.
>>
>> Anyone with a magic tip for how to do this is welcome to tell us all
>> ;-))
>>
> 
> I had a GUID partition table (GPT) on my system (x86, normal 
> mainboard/BIOS etc) and it worked fine. I didn't need a separate boot 
> disk. I used grub as the boot loader. I think if you enable GPT in the 
> kernel you should be able to boot stright from the big disk.
> 

However, the disk array was only 360GB and the boot partition was the
first one on the disk, maybe 60MB big (in the first 1024 sectors).

tom

  parent reply	other threads:[~2004-12-16 17:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 14:52 3TB disk hassles Neil Conway
2004-12-16 15:33 ` Michelle Konzack
2004-12-16 15:37 ` Mark Watts
2004-12-16 15:38   ` Hans Kristian Rosbach
2004-12-16 16:44     ` Neil Conway
2004-12-16 17:15       ` Tomas Carnecky
2004-12-16 17:38         ` Neil Conway
2004-12-16 18:05           ` Tomas Carnecky
2005-02-05  1:47             ` Neil Conway
2004-12-16 17:40         ` Tomas Carnecky [this message]
2004-12-16 15:52   ` Michelle Konzack
2004-12-16 16:03     ` Jan Engelhardt
2004-12-16 16:00       ` Alan Cox
2004-12-18  0:12         ` Andries Brouwer
2004-12-18  3:08           ` H. Peter Anvin
2004-12-18 12:15             ` Andries Brouwer
2004-12-18 23:32               ` H. Peter Anvin
2005-01-03 17:13                 ` Jeff V. Merkey
2005-01-03 17:32                   ` Jeff V. Merkey
2005-01-03 18:11                     ` linux-os
2004-12-16 17:10       ` Michelle Konzack
2004-12-16 19:52 ` Adam Heath
2004-12-16 23:28 ` Pedro Venda (SYSADM)
2005-02-05  1:51   ` Neil Conway
2004-12-16 22:21 Rico Tudor
     [not found] <fa.fng0mbi.10jm21g@ifi.uio.no>
     [not found] ` <fa.ls0rpqi.104a23q@ifi.uio.no>
2005-02-05  2:58   ` Bodo Eggert
2005-02-05 11:14     ` Neil Conway
2005-02-06 10:59 Neil Conway
2005-02-06 19:01 ` Bodo Eggert
2005-02-08 23:33 ` H. Peter Anvin
     [not found] <linux.kernel.20041216145229.29167.qmail@web26502.mail.ukl.yahoo.com>
2005-02-10  0:06 ` Jan Lindheim

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=41C1C87F.6050900@dbservice.com \
    --to=tom@dbservice.com \
    --cc=hk@isphuset.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.watts@eris.qinetiq.com \
    --cc=nconway_kernel@yahoo.co.uk \
    /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).