On Thu, May 18, 2017 at 10:03 AM, Sachidananda URS <surs(a)redhat.com> wrote:
Hi,
On Thu, May 18, 2017 at 7:08 PM, Sahina Bose <sabose(a)redhat.com> wrote:
>
>
> On Thu, May 18, 2017 at 3:20 PM, Mike DePaulo <mikedep333(a)gmail.com>
> wrote:
>
>> Well, I tried both of the following:
>> 1. Having only a boot partition and a PV for the OS that does not take
>> up the entire disk, and then specifying "sda" in Hosted Engine Setup.
>> 2. Having not only a boot partition and a PV for the OS, but also an
>> empty (and not formatted) /dev/sda3 PV that I created with fdisk.
>> Then, specfying "sda3" in Hosted Engine Setup.
>>
>> Both attempts resulted in errors like this:
>> failed: [
centerpoint.ad.depaulo.org] (item=/dev/sda3) => {"failed":
>> true, "failed_when_result": true, "item":
"/dev/sda3", "msg": "
>> Device /dev/sda3 not found (or ignored by filtering).\n", "rc":
5}
>>
>
> Can you provide gdeploy logs? I think, it's at ~/.gdeploy/gdeploy.log
>
>
>>
>> It seems like having gluster bricks on the same disk as the OS doesn't
>> work at all.
>>
>>
Hi, /dev/sda3 should work, the error here is possibly due to filesystem
signature.
Can you please set wipefs=yes? For example
[pv]
action=create
wipefs=yes
devices=/dev/sda3
-sac
Sorry for the long delay.
This worked. Thank you very much.
-Mike