Megaraid disks not detected in MAAS 3.1.0 with Smartctl-validate

cadourian · 5 March 2022 03:30

Hi, I have an old Dell PowerEdge 1850 with a Megaraid controller and MAAS is unable to detect the storage as it is unable to handle the Megaraid controller? How can I get this to work?

This is the error messages from the script “smartctl-validate”

Unable to run ‘smartctl-validate’: ‘MAAS did not detect any storage devices during commissioning!’
Given parameters:
{‘storage’: {‘argument_format’: ‘{path}’, ‘type’: ‘storage’, ‘value’: ‘all’}}
Discovered storage devices:
[{‘NAME’: ‘sr0’, ‘MODEL’: ‘HL-DT-STCD-RW_DVD-ROM_GCC-4244N’, ‘SERIAL’: ‘’, ‘MAJ:MIN’: ‘11:0’, ‘MODEL_ENC’: ‘HL-DT-STCD-RW/DVD-ROM GCC-4244N’}]
Discovered interfaces:
{‘00:13:72:58:d6:d5’: ‘enp6s7’}

Thanks

billwear · 15 March 2022 21:56

Hi, @cadourian,

Can you give us a little more information?

Identify your version and build

We need to know the version and build (and packaging format) that you’re running. You mentioned 3.1, but we need a little more information.

If you’re using a snap

If you’re using a snap, execute snap listmaas at the command line, which will return some lines like this:

Name  Version                       Rev    Tracking     Publisher   Notes
maas  3.0.0~beta2-9796-g.2182ab55f  13292  latest/edge  canonical✓  -

Please add the output of that command to a comment on this post.

If you’re using a Debian package

If you’re using a deb, execute apt list maas at the command line, and enter whatever it returns into a comment to this post, as in the snap example above.

Using CLI, UI, or API?

Next, you’ll need to specify which interface you’re using, and generally what command(s) you were attempting.

Explain what happens

Being as concise and specific as you can, please explain a little more about what seemed to go wrong. You mentioned that commissioned machines don’t show any storage? Can you show us some screenshots of an 1850 that commissions with no storage, for example? Maybe it’s not getting past smartctl-validate?

Explain how to reproduce your issue

In addition to the explanation above, you should create a step-by-step list of what you did to reproduce the problem. Sounds like it’s pretty simple – just try to commission a machine – but we’d like to be sure.

Take relevant screenshots

If you think it will help – especially when using the UI – try and capture screenshots of any unexpected results or ambiguous actions. Your goal isn’t to document your experience in pictures, but to provide a visual reference where verbal descriptions fall short. Name these so you can sync them with your explanation (e.g., “screenshot-1”). You can just upload them into your comment.

Locate and capture logfiles

If at all possible, capture at least the following logfiles, for the time period surrounding your error situation:

maas.log
regiond.log
rackd.log
the rsyslog file of the affected machine(s), if it exists.

On snap, these files are located as follows:

/var/snap/maas/common/log/maas.log
/var/snap/maas/common/log/regiond.log
/var/snap/maas/common/log/rackd.log
/var/snap/maas/common/log/rsyslog/$MACHINE_NAME/$RELEVANT_DATE/messages

If you’re using packages, you’ll find the files in these locations:

/var/log/maas/maas.log
/var/log/maas/regiond.log
/var/log/maas/rackd.log
/var/log/maas/rsyslog/$MACHINE_NAME/$RELEVANT_DATE/messages

Ideally, you’d want to put these in a pastebin and link the pastebin location in your comment.

Thanks for this. We’ll need this additional information in order to try and figure out what’s going on.

cadourian · 15 March 2022 22:14

Hi,

I’ll try to provide all the info requested

MAAS Version:
Name Version Rev Tracking Publisher Notes
maas 3.1.0-10901-g.f1f8f1505 18199 3.1/stable canonical✓ -

I was doing the “Commission” of a Dell PowerEdge 1850 that uses a Megaraid Controller.
This machine has two disks in some RAID configuration. It boots its local Ubuntu successfully.
During the boot, the BIOS does not detect any Virtual drives - I guess RAID disks don’t show in that stage but then it boots into the OS as expected.

As you say, what’s failing is “smartctl-validate”. No disks are visible in Smartctl-validate. I’ll see if I have any logs I can provide for this machine.

I can’t send you all my logs, but I can try to send you portions of it as needed. Here’s for a start the maas.log.
Please let me know if you need more and I will provide it.
I can also re-hookup this machine and repeat the process.

The main message is “Unable to set any default storage layout because it has no writable disks.”

“”"
2022-03-04T23:27:58.674381+00:00 atxds02 maas.node: [info] 21 (10.10.21.181:type=STICKY): Deleting BMC
2022-03-04T23:28:51.891454+00:00 atxds02 maas.node: [info] pe1850: Status transition from NEW to COMMISSIONING
2022-03-04T23:28:51.974022+00:00 atxds02 maas.power: [info] Changing power state (on) of node: pe1850 (66abr4)
2022-03-04T23:28:51.974392+00:00 atxds02 maas.node: [info] pe1850: Commissioning started
2022-03-04T23:28:59.294289+00:00 atxds02 maas.power: [info] Changed power state (on) of node: pe1850 (66abr4)
2022-03-04T23:29:14.700021+00:00 atxds02 maas.power: [info] Changing power state (off) of node: pe1850 (66abr4)
2022-03-04T23:29:14.712672+00:00 atxds02 maas.node: [info] pe1850: Status transition from COMMISSIONING to NEW
2022-03-04T23:29:14.730138+00:00 atxds02 maas.node: [info] pe1850: Commissioning aborted, stopping machine
2022-03-04T23:29:20.181194+00:00 atxds02 maas.power: [info] Changed power state (off) of node: pe1850 (66abr4)
2022-03-04T23:29:33.160143+00:00 atxds02 maas.node: [info] pe1850: Status transition from NEW to COMMISSIONING
2022-03-04T23:29:33.229262+00:00 atxds02 maas.power: [info] Changing power state (on) of node: pe1850 (66abr4)
2022-03-04T23:29:33.229668+00:00 atxds02 maas.node: [info] pe1850: Commissioning started
2022-03-04T23:29:41.317397+00:00 atxds02 maas.power: [info] Changed power state (on) of node: pe1850 (66abr4)
2022-03-04T23:36:44.570342+00:00 atxds02 maas.node: [error] pe1850: Unable to set any default storage layout because it has no writable disks.
2022-03-04T23:37:18.218022+00:00 atxds02 maas.node: [info] pe1850: Status transition from COMMISSIONING to TESTING
2022-03-04T23:37:30.115990+00:00 atxds02 maas.node: [info] pe1850: Status transition from TESTING to FAILED_TESTING
2022-03-04T23:40:38.741364+00:00 atxds02 maas.node: [info] pe1850: Status transition from FAILED_TESTING to BROKEN
2022-03-04T23:41:37.399723+00:00 atxds02 maas.node: [info] pe1850: Status transition from BROKEN to ENTERING_RESCUE_MODE
2022-03-04T23:41:37.452605+00:00 atxds02 maas.power: [info] Changing power state (cycle) of node: pe1850 (66abr4)
2022-03-04T23:41:37.452919+00:00 atxds02 maas.node: [info] pe1850: Rescue mode starting
2022-03-04T23:41:45.714188+00:00 atxds02 maas.power: [info] Changed power state (on) of node: pe1850 (66abr4)
2022-03-04T23:41:59.086728+00:00 atxds02 maas.node: [info] pe1850: Status transition from ENTERING_RESCUE_MODE to EXITING_RESCUE_MODE
2022-03-04T23:41:59.181420+00:00 atxds02 maas.power: [info] Changing power state (off) of node: pe1850 (66abr4)
2022-03-04T23:42:04.622940+00:00 atxds02 maas.node: [info] pe1850: Status transition from EXITING_RESCUE_MODE to BROKEN
2022-03-04T23:42:04.668220+00:00 atxds02 maas.power: [info] Changed power state (off) of node: pe1850 (66abr4)
2022-03-04T23:42:36.553867+00:00 atxds02 maas.interface: [info] enp6s7 (physical) on pe1850: IP address automatically unlinked: None:type=AUTO
2022-03-04T23:42:36.569418+00:00 atxds02 maas.node: [info] pe1850: Status transition from BROKEN to COMMISSIONING
2022-03-04T23:42:36.958500+00:00 atxds02 maas.power: [info] Changing power state (on) of node: pe1850 (66abr4)
2022-03-04T23:42:36.958847+00:00 atxds02 maas.node: [info] pe1850: Commissioning started
2022-03-04T23:42:44.338650+00:00 atxds02 maas.power: [info] Changed power state (on) of node: pe1850 (66abr4)
2022-03-04T23:49:44.948577+00:00 atxds02 maas.node: [error] pe1850: Unable to set any default storage layout because it has no writable disks.
“”"

Cheers

Chahe’

billwear · 15 March 2022 22:22

thanks, @cadourian! this is enough to start looking at this. will keep you posted.

billwear · 17 March 2022 20:32

hey, @cadourian,

What do you see if you do the following?

/opt/MegaRAID/MegaCli/MegaCli64 -adpgetpciinfo -a0 | grep Bus
ls /sys/bus/pci/devices/0000\:0${BUS_ID}\:00.0/  | grep host
ls /sys/bus/pci/devices/0000\:0${BUS_ID}\:00.0/${HOST_ID}/

# check if previous ID is in:
lsscsi

cadourian · 18 March 2022 00:00

Hey, @billwear,

I wasn’t able to boot into the system. Something may be broken with the machine.
I had another PowerEdge 1850 and I was able to commission it.

The two 1850 machines may be configured differently.

the one that was failing, at boot, it would say “0 virtual disks detected”
the one that is working detects virtual disks at boot.

I thank you for you getting back to me. If this is important, I will compare the BIOS settings, particularly RAID config etc and try to boot into the “failing” machine’s OS to get you your answers. I myself am not going to use the PowerEdge 1850 as it’s too old.

Cheers

dweeks75080 · 18 March 2022 12:37

I had a similar issue with brand new Dell X740xd and the fix for it was creating a virtual disk. Even though in my case, we should be able to configure the Perc 750 for HBA mode.

billwear · 18 March 2022 14:25

@cadourian, we’ll wait for your ping on this. we’ll be here if you decide to brave those waters again.

system · 20 March 2022 14:25

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.