Best bet with these kind of issues is to get the privileged helper binary (daos_admin) log file which can be enabled by setting the server config helper_log_file parameter to a given path.
This will give us more information as to what’s happening when the privileged helper binary is performing NVMe SPDK setup.
Regards,
Tom Nabarro – DCG/ESAD
M: +44 (0)7786 260986
Skype: tom.nabarro
From: daos@daos.groups.io <daos@daos.groups.io>
On Behalf Of Colin Ngam
Sent: Friday, April 10, 2020 7:07 PM
To: daos@daos.groups.io
Subject: [daos] daos_server.yml bdev_include list
Greetings,
If I include the following:
bdev_include: ["0000:3b:00.0", "0000:3c:00.0", "0000:3d:00.0", "0000:3e:00.0", "0000:af:00.0", "0000:b0:00.0", "0000:b1:00.0", "0000:b2:00.0"]
I get an error during daos_server start:
ERROR: setup control service: server: code = 637 description = "NVMe SSDs [0000:3b:00.0 0000:3c:00.0 0000:3d:00.0 0000:3e:00.0 0000:af:00.0 0000:b0:00.0 0000:b1:00.0 0000:b2:00.0] not found"
ERROR: server: code = 637 resolution = "check SSDs [0000:3b:00.0 0000:3c:00.0 0000:3d:00.0 0000:3e:00.0 0000:af:00.0 0000:b0:00.0 0000:b1:00.0 0000:b2:00.0] that are specified in server config exist"
Even though I have the following later:
bdev_list: ["0000:3b:00.0", "0000:3c:00.0", "0000:3d:00.0", "0000:3e:00.0"]
Is the bdev_include list should only include NVMe that has not been “prepared” via dmg command? Does this also mean that we do not need to use dmg storage prepare for NVMe SSDs?
Thanks.
Colin
