problem when I add a second NVME disk

mmmmmmm · Apr 10, 2024

Hi all
I have a strange issue, when I add a second nvme, i can see it under disk, format it, create a lvm-thin on it, create an lxc inside it.
after a reboot, I can see the storage as nvme, I can browse it, under CT volume i can see my lxc volume, but when i try to start my lxc i have this error:

Code:

explicitly configured lxc.apparmor.profile overrides the following settings: features:nesting
run_buffer: 571 Script exited with status 20
lxc_init: 845 Failed to run lxc.hook.pre-start for container "112"
__lxc_start: 2034 Failed to initialize container "112"
TASK ERROR: startup for container '112' failed

if i mount the lxc lvm partition manually in cli i can browse it
if i reboot i have the same issue, if i remove the other nvme, it works again and my lxc will start
if i wipe the first nvme i can restore the vm and it work until the next reboot

Code:

CPU(s)
 16 x AMD Ryzen 7 5800X 8-Core Processor (1 Socket)
Kernel Version
Linux 6.5.13-5-pve (2024-04-05T11:03Z)
Boot Mode
pve-manager/8.1.10/4b06efb5db453f29

the is enought disk space and RAM
my proxmox is in cluster with 2 other nodes

Code:

root@proxmox3:~# smartctl -ac /dev/nvme1n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.13-5-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 1TB
Serial Number:                      S64ANG0R553488B
Firmware Version:                   3B4QFXO7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      5
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            952,782,979,072 [952 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 d511512f11
Local Time is:                      Tue Apr  9 21:18:20 2024 EDT
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0055):     Comp DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius
Namespace 1 Features (0x10):        NP_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     5.24W       -        -    0  0  0  0        0       0
 1 +     4.49W       -        -    1  1  1  1        0       0
 2 +     2.19W       -        -    2  2  2  2        0     500
 3 -   0.0500W       -        -    3  3  3  3      210    1200
 4 -   0.0050W       -        -    4  4  4  4     1000    9000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        49 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    236,450,428 [121 TB]
Data Units Written:                 18,315,463 [9.37 TB]
Host Read Commands:                 2,481,739,843
Host Write Commands:                176,905,532
Controller Busy Time:               1,132
Power Cycles:                       257
Power On Hours:                     283
Unsafe Shutdowns:                   18
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               49 Celsius
Temperature Sensor 2:               57 Celsius
Thermal Temp. 2 Transition Count:   123
Thermal Temp. 2 Total Time:         13

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

thanks for your help

silverstone · Nov 24, 2024

mmmmmmm said:

Hi all
I have a strange issue, when I add a second nvme, i can see it under disk, format it, create a lvm-thin on it, create an lxc inside it.
after a reboot, I can see the storage as nvme, I can browse it, under CT volume i can see my lxc volume, but when i try to start my lxc i have this error:

Code:

explicitly configured lxc.apparmor.profile overrides the following settings: features:nesting
run_buffer: 571 Script exited with status 20
lxc_init: 845 Failed to run lxc.hook.pre-start for container "112"
__lxc_start: 2034 Failed to initialize container "112"
TASK ERROR: startup for container '112' failed

if i mount the lxc lvm partition manually in cli i can browse it
if i reboot i have the same issue, if i remove the other nvme, it works again and my lxc will start
if i wipe the first nvme i can restore the vm and it work until the next reboot

Code:

CPU(s)
 16 x AMD Ryzen 7 5800X 8-Core Processor (1 Socket)
Kernel Version
Linux 6.5.13-5-pve (2024-04-05T11:03Z)
Boot Mode
pve-manager/8.1.10/4b06efb5db453f29

the is enought disk space and RAM
my proxmox is in cluster with 2 other nodes

Code:

root@proxmox3:~# smartctl -ac /dev/nvme1n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.13-5-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 1TB
Serial Number:                      S64ANG0R553488B
Firmware Version:                   3B4QFXO7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      5
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            952,782,979,072 [952 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 d511512f11
Local Time is:                      Tue Apr  9 21:18:20 2024 EDT
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0055):     Comp DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius
Namespace 1 Features (0x10):        NP_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     5.24W       -        -    0  0  0  0        0       0
 1 +     4.49W       -        -    1  1  1  1        0       0
 2 +     2.19W       -        -    2  2  2  2        0     500
 3 -   0.0500W       -        -    3  3  3  3      210    1200
 4 -   0.0050W       -        -    4  4  4  4     1000    9000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        49 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    236,450,428 [121 TB]
Data Units Written:                 18,315,463 [9.37 TB]
Host Read Commands:                 2,481,739,843
Host Write Commands:                176,905,532
Controller Busy Time:               1,132
Power Cycles:                       257
Power On Hours:                     283
Unsafe Shutdowns:                   18
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               49 Celsius
Temperature Sensor 2:               57 Celsius
Thermal Temp. 2 Transition Count:   123
Thermal Temp. 2 Total Time:         13

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

thanks for your help

Hi,

Old Post I know but I thought I'd throw in my 0.02$.

I got a similar Error Message, but it doesn't look to be caused by AppArmor:

Code:

run_buffer: 571 Script exited with status 1
lxc_init: 845 Failed to run lxc.hook.pre-start for container "121"
__lxc_start: 2034 Failed to initialize container "121"
TASK ERROR: startup for container '121' failed

Instead, it appeared that the Volume/Virtual Disk was Full:

Code:

root@pve13:/tools_nfs/Debian# zfs list | grep "subvol-121"
NAME                                                         USED  AVAIL  REFER  MOUNTPOINT
rpool/data/subvol-121-disk-0                                19.9G     0B    12G  /rpool/data/subvol-121-disk-0

Not sure if you solved the Issue in the Meantime, but maybe something worth checking out

.

Or possibly useful for other affected Users as well.

Hope that Helps !

mmmmmmm · Dec 12, 2024

Hey,
no i didn't get anything to solve it
i just put the nvme in another computer

Search

Search

problem when I add a second NVME disk

mmmmmmm

New Member

silverstone

Well-Known Member

mmmmmmm

New Member

We value your privacy