Re: Avoid wedges from certain devices

[Dima Veselov <kab00m%lich.phys.spbu.ru@localhost>]

01.03.2020 0:10, Martin Husemann пишет:

> > it may be very dumb to ask, but I have installed 9.0 on UEFI server with
> > soft-RAID and now I have ld0, wd0 and wd1 having same wedges. When
> > booting NetBSD find wedges on wd0, then complain about same wedges
> > on wd1 and ld0. It won't boot, I think this happens because first wedges
> > are found on wd0 which is blocked at the moment of finding root.
>
> Usually the colliding wedges just show up with their guid as name.
> Do you have wedges where even the guid collides?

Yes, thats the point. Every new device (wd0,wd1 and ld0) discover same
guids

This is wd0

[     3.751005] wd0 at atabus0 drive 0
[     3.751005] wd0: <ST2000DM006-2DM164>
[     3.761014] wd0: drive supports 16-sector PIO transfers, LBA48 
addressing
[     3.761014] wd0: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 
bytes/sect x 3907029168 sectors
[     3.791045] wd0: GPT GUID: f8b60d10-7efa-4611-87e9-6522ef835436
[     3.791045] dk0 at wd0: "91fbe1b5-1140-4ad3-b5b5-1b2c6ab625f1", 
262144 blocks at 2048, type: msdos
[     3.805917] dk1 at wd0: "be8fc31e-8450-484b-ad73-5eb6db77e873", 
2097152 blocks at 266240, type: ffs
[     3.814930] dk2 at wd0: "d8a5e09e-24a8-497c-b132-bb3763465886", 
16777216 blocks at 2365440, type: swap
[     3.824203] dk3 at wd0: "153d7f95-c49a-4dda-940a-ff3440b1ce4f", 
33554432 blocks at 19144704, type: ffs
[     3.833477] dk4 at wd0: "52896b2b-9bdc-4351-a623-3af1facc479d", 
33554432 blocks at 52701184, type: ffs

This is his pair

[     3.871123] wd1 at atabus1 drive 0
[     3.881133] wd1: <ST2000VX000-1CU164>
[     3.881133] wd1: drive supports 16-sector PIO transfers, LBA48 
addressing
[     3.881133] wd1: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 
bytes/sect x 3907029168 sectors
[     3.911162] wd1: GPT GUID: f8b60d10-7efa-4611-87e9-6522ef835436
[     3.911162] autoconfiguration error: wd1: wedge named 
'91fbe1b5-1140-4ad3-b5b5-1b2c6ab625f1' already exists, manual 
intervention required
[     3.921172] autoconfiguration error: wd1: wedge named 
'be8fc31e-8450-484b-ad73-5eb6db77e873' already exists, manual 
intervention required
[     3.931182] autoconfiguration error: wd1: wedge named 
'd8a5e09e-24a8-497c-b132-bb3763465886' already exists, manual 
intervention required
[     3.941191] autoconfiguration error: wd1: wedge named 
'153d7f95-c49a-4dda-940a-ff3440b1ce4f' already exists, manual 
intervention required
[     3.951201] autoconfiguration error: wd1: wedge named 
'52896b2b-9bdc-4351-a623-3af1facc479d' already exists, manual 
intervention required

And this is array

[     5.282509] ld0 at ataraid0 vendtype 5 unit 0: Intel MatrixRAID ATA 
RAID-1 array
[     5.294214] ld0: 1769 GB, 231045 cyl, 255 head, 63 sec, 512 
bytes/sect x 3711741952 sectors
[     5.307811] ld0: GPT GUID: f8b60d10-7efa-4611-87e9-6522ef835436
[     5.307811] autoconfiguration error: ld0: wedge named 
'91fbe1b5-1140-4ad3-b5b5-1b2c6ab625f1' already exists, manual 
intervention required
[     5.317491] autoconfiguration error: ld0: wedge named 
'be8fc31e-8450-484b-ad73-5eb6db77e873' already exists, manual 
intervention required
[     5.326331] autoconfiguration error: ld0: wedge named 
'd8a5e09e-24a8-497c-b132-bb3763465886' already exists, manual 
intervention required
[     5.335171] autoconfiguration error: ld0: wedge named 
'153d7f95-c49a-4dda-940a-ff3440b1ce4f' already exists, manual 
intervention required
[     5.344010] autoconfiguration error: ld0: wedge named 
'52896b2b-9bdc-4351-a623-3af1facc479d' already exists, manual 
intervention required


--
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University