[Anaconda] something wrong with dmraid disk?

[Kun Huang]

Hi

I have a problem when running anaconda in system which has dm-raid device.
I used "clearpart --all" but still got the error windows "specified
unpartitioned sdc in partition command".

And I found a guy have nearly same case as mine:
http://bugs.centos.org/view.php?id=3637
When using "dmraid -r -E", I got ERROR message too. So I guess this is a
very old problem and is this a dmraid bug?

[Kun Huang]

I have already fixed this issue by using "nodmraid".

On Mon, Dec 2, 2013 at 6:45 PM, Kun Huang  wrote:
> Hi
>
> I have a problem when running anaconda in system which has dm-raid device.
> I used "clearpart --all" but still got the error windows "specified
> unpartitioned sdc in partition command".
>
> And I found a guy have nearly same case as mine:
> http://bugs.centos.org/view.php?id=3637
> When using "dmraid -r -E", I got ERROR message too. So I guess this is a
> very old problem and is this a dmraid bug?

[David Lehman]

On Tue, 2013-12-03 at 15:12 +0800, Kun Huang wrote:
> I have already fixed this issue by using "nodmraid".

If that fixed your problem then you must not have removed all of the
dmraid metadata from the disk. Presumably it is still there and will
continue to cause problems until you actually remove it.

[Kun Huang]

Thanks David, that is what I'm worried about too. I tried "dmraid -rE" and
failed in same errors in http://bugs.centos.org/view.php?id=3637. So I'm
working on deleting this device mapper data now.

On Wed, Dec 4, 2013 at 12:29 AM, David Lehman  wrote:
> On Tue, 2013-12-03 at 15:12 +0800, Kun Huang wrote:
> > I have already fixed this issue by using "nodmraid".
>
> If that fixed your problem then you must not have removed all of the
> dmraid metadata from the disk. Presumably it is still there and will
> continue to cause problems until you actually remove it.
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Adam Williamson]

On Wed, 2013-12-04 at 13:34 +0800, Kun Huang wrote:
> Thanks David, that is what I'm worried about too. I tried "dmraid -rE"
> and failed in same errors in http://bugs.centos.org/view.php?id=3637.
> So I'm working on deleting this device mapper data now.

I've found it can be hard to shift dmraid data indeed, when doing RAID
testing in the past. Unfortunately I don't quite recall all the details,
but it may help to go into the RAID controller BIOS and ask it to 'reset
the disks to non-RAID' or similar, if it has an option for that. Those
commands you can find by Googling around didn't seem to get the job done
- I do remember that.

[Karel Zak]

On Tue, Dec 03, 2013 at 10:29:44AM -0600, David Lehman wrote:
> On Tue, 2013-12-03 at 15:12 +0800, Kun Huang wrote:
> > I have already fixed this issue by using "nodmraid".
>
> If that fixed your problem then you must not have removed all of the
> dmraid metadata from the disk. Presumably it is still there and will
> continue to cause problems until you actually remove it.

yes, see wipefs(8)

Karel

[Chris Murphy]

On Dec 9, 2013, at 12:52 PM, Karel Zak  wrote:
> On Tue, Dec 03, 2013 at 10:29:44AM -0600, David Lehman wrote:
> > On Tue, 2013-12-03 at 15:12 +0800, Kun Huang wrote:
> > > I have already fixed this issue by using "nodmraid".
> >
> > If that fixed your problem then you must not have removed all of the
> > dmraid metadata from the disk. Presumably it is still there and will
> > continue to cause problems until you actually remove it.
>
> yes, see wipefs(8)

Yes. I'd expect either wipefs -a, or dmraid -Er should remove the (correct amount of) metadata causing either dmraid or blkid to recognize it as a dmraid volume, or it's a bug.

Chris Murphy