Hi,
I have MAAS 3.1 deployed and I just booted my first server through MAAS and PXE. When I look at the storage configuration of the server I can see that MAAS didn’t recognize the Intel VROC RAID Configuration. Also, I have an storage LUN mapped to the server and MAAS doesn’t show any type of mapper for multipath.
Is there any way I can either create a custom script or make MAAS recognize the Multipath device and the VROC RAID Configuration? I’ll be using Ubuntu 20.04
@carlosbravo, this is an interesting one.
can you use this guide to get us some logs? (no need to file a bug, yet, tho it might come to that later). we’d like to see what’s happening underneath when this fails. tia.
Hi,
sorry about the super long time it took me to reply and I’m not sure if I should be replying to this topic at all (it has been almost 1 month) but I had a lot of different things to deal with while we transition from our current Openstack Cloud to a Charmed one. This is the paste bin file with the log of the node.
From those logs, I can see that curtin sees the RAID virtual drive, however it isn’t listed onto maas.
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.252516] md/raid1:md126: not clean -- starting background reconstruction
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.253939] mlx5_core 0000:4b:00.1 enp75s0f1: renamed from eth1
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.257115] usbcore: registered new interface driver usbhid
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.257116] usbhid: USB HID core driver
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.258598] md/raid1:md126: active with 2 out of 2 mirrors
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.258884] md126: detected capacity change from 0 to 456088616960
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.259124] mlx5_ib: Mellanox Connect-IB Infiniband driver v5.0-0
2022-06-11T16:44:26+00:00 maas-enlisting-node kernel: [ 4.278933] md: resync of RAID array md126okay, got it. please go ahead and file a bug. it may not be a bug, but that’s what it looks like to me at this moment.
@carlosbravo, saw your bug and triaged it into the buglist. i’m going to close this entry as “bug filed,” but if we need to come back here and document the solution, we can.
@billwear I feel like an idiot. I changed the status to fix released as I was reading the different options and accidentally clicked on it. Sorry about that 
I can put it back, np. 
you’re not an idiot, just a normal person!