No such file or directory

[johan.finn]

Installed veeam Lnux agent, get this error message when try to configure

No such file or directory
POSIX: Failed to open file [/sys/class/block/nvme3c33n1/dev
Anyone has a clue?

Best regards
Johan

[PTide]

Hi,

Would you describe at what step does the configuration fail exactly, please? Also, is it an NVMe SSD installed into a PCIe slot by any chance?

Thanks

[johan.finn]

Hi
Thank you for reply
Get the error message when choosing configure for the first time in veeam.
Its not PCI, but DELL nvme external/hotswap.
Maybe a solution if possible to somehow ignore nvme3c33n1 in config somehow, if possible?
Best regards
Johan

[PTide]

Yes, you can switch to the Volume level mode and specify devices manually, omitting the problematic one.

Regarding the issue - my guess that it has something to do with the drivers for the device and the agent not knowing how to access it properly. In order to check what's exactly gone wrong we definitely need to see the logs. Would you open a support case and post your case ID, please? That would help us a lot.

Thanks!

[johan.finn]

Hi
You are probably right, the disks/server is a new Dell server with these disks:
6 Dell 800GB, NVMe, Mixed Use Express Flash, 2.5 SFF Drive, U.2, PM1725a with Carrier. The disks seems to create two entries in /dev/block
/nvme4n1p1 and /nvme4n1, where the fisrt entry is the actual disk.
The logs are below.
Dont have any license/contract yet, so i dont think i can open any case?

Best regards
Johan

Code: Select all

[25.09.2018 09:15:37] <139740980438784>        | Thread started. Thread id: 139740980438784, parent id: 139740988831488, role: Client processor thread
[25.09.2018 09:15:37] <139740980438784> net    | Client connected...
[25.09.2018 09:15:37] <139740955260672>        | Thread started. Thread id: 139740955260672, parent id: 139740980438784, role: peer local sock peer
[25.09.2018 09:15:37] <139740980438784>        | Thread finished. Role: 'Client processor thread'.
[25.09.2018 09:15:37] <139740955260672> lpbcore| Starting proxystub protocol dispatch loop.
[25.09.2018 09:15:37] <139740963653376>        | Thread started. Thread id: 139740963653376, parent id: 139740988831488, role: Client processor thread
[25.09.2018 09:15:37] <139740963653376> net    | Client connected...
[25.09.2018 09:15:37] <139740980438784>        | Thread started. Thread id: 139740980438784, parent id: 139740963653376, role: peer local sock peer
[25.09.2018 09:15:37] <139740980438784> lpbcore| Starting proxystub protocol dispatch loop.
[25.09.2018 09:15:37] <139740963653376>        | Thread finished. Role: 'Client processor thread'.
[25.09.2018 09:15:37] <139740955260672> lpbcore| Starting proxystub protocol dispatch loop. ok.
[25.09.2018 09:15:37] <139740955260672>        | Closing socket device.
[25.09.2018 09:15:37] <139740955260672>        | Thread finished. Role: 'peer local sock peer'.
[25.09.2018 09:15:37] <139740972046080>        | Thread started. Thread id: 139740972046080, parent id: 139740988831488, role: Client processor thread
[25.09.2018 09:15:37] <139740972046080> net    | Client connected...
[25.09.2018 09:15:37] <139740972046080> lpbcore| Starting new LPB session.
[25.09.2018 09:15:37] <139740972046080>        |   Closing socket device.
[25.09.2018 09:15:37] <139740972046080> lpbcore| Starting new LPB session. ok.
[25.09.2018 09:15:37] <139740972046080>        | Thread finished. Role: 'Client processor thread'.
[25.09.2018 09:15:37] <139740963653376>        | Thread started. Thread id: 139740963653376, parent id: 139740972046080, role: (async) LPBConfig session 
[25.09.2018 09:15:37] <139740963653376> lpbcore| LpbCfgSession: Tcp loop.
[25.09.2018 09:15:55] <139740980438784> lpbcore| ERR |No such file or directory
[25.09.2018 09:15:55] <139740980438784> lpbcore| >>  |POSIX: Failed to open file [/sys/class/block/nvme3c33n1/dev].
[25.09.2018 09:15:55] <139740980438784> lpbcore| >>  |--tr:Failed to read file [/sys/class/block/nvme3c33n1/dev].
[25.09.2018 09:15:55] <139740980438784> lpbcore| >>  |--tr:Failed to obtain slaves list for device [/sys/class/block/nvme3c33n1] in sysfs.
[25.09.2018 09:15:55] <139740980438784> lpbcore| >>  |--tr:Failed to execute method [5] for class [lpbcorelib::interaction::proxystub::CLpbServiceStub].
[25.09.2018 09:15:55] <139740980438784> lpbcore| >>  |An exception was thrown from thread [139740980438784].
[25.09.2018 09:16:04] <139740980438784> lpbcore| Starting proxystub protocol dispatch loop. ok.
[25.09.2018 09:16:04] <139740980438784>        | Closing socket device.
[25.09.2018 09:16:04] <139740980438784>        | Thread finished. Role: 'peer local sock peer'.
[25.09.2018 09:16:04] <139740963653376> lpbcore| LpbCfgSession: Tcp loop. Failed.
[25.09.2018 09:16:04] <139740963653376> lpbcore| ERR |LpbCfgSession failed.
[25.09.2018 09:16:04] <139740963653376> lpbcore| >>  |No such file or directory
[25.09.2018 09:16:04] <139740963653376> lpbcore| >>  |--tr:Cannot read data from the socket. Requested data size: [4].
[25.09.2018 09:16:04] <139740963653376> lpbcore| >>  |An exception was thrown from thread [139740963653376].
[25.09.2018 09:16:04] <139740963653376>        | Closing socket device.
[25.09.2018 09:16:04] <139740963653376>        | Thread finished. Role: '(async) LPBConfig session '.

[PTide]

Provided that you're registered on veeam.com you should be able to open a case via online support portal.

Thanks