From: Mike Berger <lists@mike01.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Filesystem on RAID5 missing or corrupted after reboot (bad superblock error)
Date: Fri, 23 Jan 2009 16:34:05 -0600 [thread overview]
Message-ID: <497A45DD.4020107@mike01.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0901231639290.1866@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Fri, 23 Jan 2009, Mike Berger wrote:
>
>> Justin Piszcz wrote:
>>>
>>> Hi,
>>>
>>> If you are using GPT partitions, the kernel will not recognize them
>>> after stop/start or a reboot unless you have this option enabled in the
>>> kernel:
>>>
>>> CONFIG_EFI_PARTITION=y
>>>
>>> Also, why use a GPT partition, do you have individual HDDs over 2TiB?
>>> If not, just make a regular partition on each HDD with fdisk and make
>>> it type
>>> 'fd'?
>>>
>>> Justin.
>> This seems likely to be the problem.
>> CONFIG_LBD=y
>> CONFIG_EFI=y
>> CONFIG_FB_EFI=y
>> CONFIG_PARTITION_ADVANCED=y
>> # CONFIG_EFI_VARS is not set
>> # CONFIG_EFI_PARTITION is not set
>>
>>
>> I've got a kernel building now with CONFIG_EFI_PARTITION=y so I will
>> know shortly.
>>
>> My thinking with the GPT partition table was to be more future proof.
>> I'm already using 1.5 TiB drives, so it seems likely I would transition
>> to 2 TiB or larger drives whenever I replaced these or added to the
>> array. Do you know if using a traditional/msdos partition table now
>> would be an issue if I wanted to migrate to larger disks in the future?
>>
>> Thanks,
>> Mike
>>
>
> In that case, use GPT. Who knows, maybe next year there will be > 2T
> disks
> and in that case you need GPT I believe..
>
> Justin.
Just wanted to say thanks (and leave a trail for those who may google
with similar problems and find the archives). After setting
CONFIG_EFI_PARTITION=y and building a new kernel the filesystem showed
up again on reboot and things are working great.
Mike
prev parent reply other threads:[~2009-01-23 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 20:02 Filesystem on RAID5 missing or corrupted after reboot (bad superblock error) Mike Berger
2009-01-23 21:23 ` Justin Piszcz
2009-01-23 21:36 ` Mike Berger
2009-01-23 21:39 ` Justin Piszcz
2009-01-23 22:34 ` Mike Berger [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=497A45DD.4020107@mike01.com \
--to=lists@mike01.com \
--cc=jpiszcz@lucidpixels.com \
--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).