Segmentation fault on updating initramfs

Will perform a test now.

Edit - Performed the test for 10 mins. No crash.

Code: 
System Details:

    Host OS: Proxmox VE 8.3.4
    Kernel: Linux 6.8.12-8-pve
    CPU: 6 x Intel(R) Core™ i5-9600K CPU @ 3.70GHz (1 Socket)
    Motherboard: ASRock H370M-HDV
    RAM: Corsair DDR4 Vengeance LPX 2x32GB 2666MHz (64GB total)
    HBA: LSI SAS 9207-8i
    HDD: 5 x WD DC HC520 12TB (RAIDZ2 in TrueNAS)
    Power Supply: Corsair SF750
    Network Adapter: Intel I226 NIC
    Virtualization: TrueNAS ElectricEel-24.10.2 running as a VM on Proxmox

Edit - Performing smartctl --long tests on all HDDs; next, I will perform a memtest.
 
Last edited:
Absolutely. Its been 16 hours now. But with TRUENAS vm, it doesn't go more than 1 hour.

Also, I see this errors in journalctl when there is segmentation faults while updating initramfs


Code: 
Mar 04 09:37:41 pve kernel: show_signal_msg: 5 callbacks suppressed
Mar 04 09:37:41 pve kernel: modinfo[1186293]: segfault at 714 ip 0000763b2e948947 sp 00007ffc3e726e80 error 4 in ld-linux-x86-64.so.2[763b2e940000+25000] likel>
Mar 04 09:37:41 pve kernel: Code: 00 00 00 41 57 41 56 41 55 49 89 f5 41 54 4d 89 c4 55 48 89 d5 53 48 89 fb 48 81 ec 88 00 00 00 48 89 4c 24 10 44 89 4c 24 38>
Mar 04 09:37:42 pve kernel: modinfo[1187907]: segfault at 318 ip 00007d4873481947 sp 00007fffc772d4e0 error 4 in ld-linux-x86-64.so.2[7d4873479000+25000] likel>
Mar 04 09:37:42 pve kernel: Code: 00 00 00 41 57 41 56 41 55 49 89 f5 41 54 4d 89 c4 55 48 89 d5 53 48 89 fb 48 81 ec 88 00 00 00 48 89 4c 24 10 44 89 4c 24 38>
Mar 04 09:37:42 pve kernel: modinfo[1188071]: segfault at 409835600000 ip 000075ba6e8d0d16 sp 00007ffecd78a798 error 14 in libcrypto.so.3[75ba6e8c5000+27c000] >
Mar 04 09:37:42 pve kernel: Code: 3a 00 66 90 ff 25 02 ef 3a 00 66 90 ff 25 2a ef 3a 00 66 90 ff 25 2a ef 3a 00 66 90 ff 25 2a ef 3a 00 66 90 ff 25 2a ef 3a 00>
Mar 04 09:37:42 pve kernel: modinfo[1188494]: segfault at 113ac ip 000074750ddbe947 sp 00007ffd8c095440 error 4 in ld-linux-x86-64.so.2[74750ddb6000+25000] lik>
Mar 04 09:37:42 pve kernel: Code: 00 00 00 41 57 41 56 41 55 49 89 f5 41 54 4d 89 c4 55 48 89 d5 53 48 89 fb 48 81 ec 88 00 00 00 48 89 4c 24 10 44 89 4c 24 38>
Mar 04 09:37:43 pve kernel: traps: modinfo[1189251] general protection fault ip:77a9c5a6bbed sp:7ffe2206f3b8 error:0 in ld-linux-x86-64.so.2[77a9c5a64000+25000]
Mar 04 09:37:44 pve kernel: modinfo[1191801]: segfault at 8 ip 000070c5c550669e sp 00007fffa4f49e10 error 4 in libcrypto.so.3[70c5c54c5000+27c000] likely on CP>
Mar 04 09:37:44 pve kernel: Code: eb cd 66 2e 0f 1f 84 00 00 00 00 00 48 8d 05 59 70 35 00 c3 0f 1f 84 00 00 00 00 00 55 48 8d 2d 8c fe 23 00 ba 36 00 00 00 bf>
Mar 04 09:37:45 pve kernel: traps: modinfo[1192933] general protection fault ip:7833f5c32bed sp:7ffc2e09fd18 error:0 in ld-linux-x86-64.so.2[7833f5c2b000+25000]
Mar 04 09:37:45 pve kernel: traps: modinfo[1193126] general protection fault ip:7f54d2eb1bed sp:7ffe56f7a8d8 error:0 in ld-linux-x86-64.so.2[7f54d2eaa000+25000]
Mar 04 09:37:48 pve kernel: BUG: unable to handle page fault for address: 00000000f9ff0020
Mar 04 09:37:48 pve kernel: #PF: supervisor write access in kernel mode
Mar 04 09:37:48 pve kernel: #PF: error_code(0x0002) - not-present page
Mar 04 09:37:48 pve kernel: PGD 0 P4D 0
Mar 04 09:37:48 pve kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Mar 04 09:37:48 pve kernel: CPU: 1 PID: 1197044 Comm: modinfo Tainted: P           O       6.8.12-8-pve #1
Mar 04 09:37:48 pve kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H370M-HDV, BIOS P1.20E 11/27/2023
Mar 04 09:37:48 pve kernel: RIP: 0010:mas_walk+0x2a3/0x3a0
Mar 04 09:37:48 pve kernel: Code: e0 03 eb ae c7 46 38 01 00 00 00 48 c7 46 18 00 00 00 00 e9 8e fd ff ff 88 56 3d 8b 56 38 44 88 46 3f 4c 89 56 08 48 89 4e 10>
Mar 04 09:37:48 pve kernel: RSP: 0000:ffffb0cd8ff3fe38 EFLAGS: 00010a87
Mar 04 09:37:48 pve kernel: RAX: 0000000052bcf941 RBX: ffff8f5c472d6700 RCX: 0000610475662fff
Mar 04 09:37:48 pve kernel: RDX: 0000000000000000 RSI: 00000000f9ff0000 RDI: ffff8f5c472d6a00
Mar 04 09:37:48 pve kernel: RBP: 00000000f9ff0000 R08: 0000000000000009 R09: 0000000000000001
Mar 04 09:37:48 pve kernel: R10: 0000000000000000 R11: ffff8f5c472d670c R12: 0000000000000000
Mar 04 09:37:48 pve kernel: R13: 00007c5138444fff R14: 0000000000000000 R15: 0000000000000001
Mar 04 09:37:48 pve kernel: FS:  00007c5138c0b040(0000) GS:ffff8f6aeee80000(0000) knlGS:0000000000000000
Mar 04 09:37:48 pve kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 04 09:37:48 pve kernel: CR2: 00000000f9ff0020 CR3: 00000002296f8001 CR4: 00000000003706f0
Mar 04 09:37:48 pve kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 04 09:37:48 pve kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Mar 04 09:37:48 pve kernel: Call Trace:
Mar 04 09:37:48 pve kernel:  <TASK>
Mar 04 09:37:48 pve kernel:  ? show_regs+0x6d/0x80
Mar 04 09:37:48 pve kernel:  ? __die+0x24/0x80
Mar 04 09:37:48 pve kernel:  ? page_fault_oops+0x176/0x500
Mar 04 09:37:48 pve kernel:  ? filemap_map_pages+0x4b8/0x5b0
Mar 04 09:37:48 pve kernel:  ? do_user_addr_fault+0x2f4/0x660
Mar 04 09:37:48 pve kernel:  ? exc_page_fault+0x83/0x1b0
Mar 04 09:37:48 pve kernel:  ? asm_exc_page_fault+0x27/0x30
Mar 04 09:37:48 pve kernel:  ? mas_walk+0x2a3/0x3a0
Mar 04 09:37:48 pve kernel:  ? lock_vma_under_rcu+0x71/0x150
Mar 04 09:37:48 pve kernel:  ? do_user_addr_fault+0x138/0x660
Mar 04 09:37:48 pve kernel:  ? exc_page_fault+0x83/0x1b0
Mar 04 09:37:48 pve kernel:  ? asm_exc_page_fault+0x27/0x30
Mar 04 09:37:48 pve kernel:  </TASK>
Mar 04 09:37:48 pve kernel: Modules linked in: uhid hid xxhash_generic wp512 streebog_generic nhpoly1305_avx2 sm3_generic sm3_avx_x86_64 sm3 userio rmd160 nhpo>
Mar 04 09:37:48 pve kernel:  nf_conntrack_netlink xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE xt_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag>
Mar 04 09:37:48 pve kernel:  vfio_pci vfio_pci_core irqbypass vfio_iommu_type1 vfio iommufd efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_gener>
Mar 04 09:37:48 pve kernel: CR2: 00000000f9ff0020
Mar 04 09:37:48 pve kernel: ---[ end trace 0000000000000000 ]---
Mar 04 09:37:48 pve kernel: RIP: 0010:mas_walk+0x2a3/0x3a0
Mar 04 09:37:48 pve kernel: Code: e0 03 eb ae c7 46 38 01 00 00 00 48 c7 46 18 00 00 00 00 e9 8e fd ff ff 88 56 3d 8b 56 38 44 88 46 3f 4c 89 56 08 48 89 4e 10>
Mar 04 09:37:48 pve kernel: RSP: 0000:ffffb0cd8ff3fe38 EFLAGS: 00010a87
Mar 04 09:37:48 pve kernel: RAX: 0000000052bcf941 RBX: ffff8f5c472d6700 RCX: 0000610475662fff
Mar 04 09:37:48 pve kernel: RDX: 0000000000000000 RSI: 00000000f9ff0000 RDI: ffff8f5c472d6a00
Mar 04 09:37:48 pve kernel: RBP: 00000000f9ff0000 R08: 0000000000000009 R09: 0000000000000001
Mar 04 09:37:48 pve kernel: R10: 0000000000000000 R11: ffff8f5c472d670c R12: 0000000000000000
Mar 04 09:37:48 pve kernel: R13: 00007c5138444fff R14: 0000000000000000 R15: 0000000000000001
Mar 04 09:37:48 pve kernel: FS:  00007c5138c0b040(0000) GS:ffff8f6aeee80000(0000) knlGS:0000000000000000
Mar 04 09:37:48 pve kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 04 09:37:48 pve kernel: CR2: 00000000f9ff0020 CR3: 00000002296f8001 CR4: 00000000003706f0
Mar 04 09:37:48 pve kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 04 09:37:48 pve kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Mar 04 09:37:48 pve kernel: note: modinfo[1197044] exited with irqs disabled
Mar 04 09:38:35 pve kernel: modinfo[1204781]: segfault at 1752d ip 00007fb1c33ca947 sp 00007ffe711b7f20 error 4 in ld-linux-x86-64.so.2[7fb1c33c2000+25000] lik>
Mar 04 09:38:35 pve kernel: Code: 00 00 00 41 57 41 56 41 55 49 89 f5 41 54 4d 89 c4 55 48 89 d5 53 48 89 fb 48 81 ec 88 00 00 00 48 89 4c 24 10 44 89 4c 24 38>
Mar 04 09:38:36 pve kernel: modinfo[1205727]: segfault at 0 ip 000070a46b797bc0 sp 00007ffe491088d0 error 6 in ld-linux-x86-64.so.2[70a46b790000+25000] likely >
Mar 04 09:38:36 pve kernel: Code: e1 0f 49 83 79 08 00 0f 84 0d 01 00 00 45 31 c0 66 85 c0 b8 98 fb ff ff 41 0f 94 c0 d3 f8 41 21 d0 83 e0 01 41 09 c0 0f 85 cd>
Mar 04 09:38:36 pve kernel: modinfo[1206876]: segfault at 1d ip 000000000000001d sp 00007fffc0efbb48 error 14 in kmod[5d092db55000+4000] likely on CPU 1 (core >
Mar 04 09:38:36 pve kernel: Code: Unable to access opcode bytes at 0xfffffffffffffff3.
Mar 04 09:38:37 pve kernel: modinfo[1208493]: segfault at 0 ip 00007961481114bf sp 00007ffd371c7f50 error 4 in libcrypto.so.3[7961480c5000+27c000] likely on CP>
Mar 04 09:38:37 pve kernel: Code: ff c3 66 0f 1f 84 00 00 00 00 00 53 48 89 f3 89 d6 c6 03 00 48 8b 57 40 48 89 df e8 7b 74 fb ff 48 85 c0 b8 00 00 00 00 74 0d>
Mar 04 09:38:39 pve kernel: modinfo[1210686]: segfault at 4f ip 000071148722d902 sp 00007ffdd669be48 error 4 in libcrypto.so.3[7114870c5000+27c000] likely on C>
Mar 04 09:38:39 pve kernel: Code: 43 38 8b 4b 18 48 83 e8 01 48 89 43 38 83 f9 10 77 2e 48 8b 44 24 08 64 48 2b 04 25 28 00 00 00 0f 85 db 00 00 00 48 83 c4 18>
Mar 04 09:38:41 pve kernel: modinfo[1214378]: segfault at 1 ip 000078fee72960b3 sp 00007ffe965611e0 error 6 in libc.so.6[78fee7245000+155000] likely on CPU 2 (>
Mar 04 09:38:41 pve kernel: Code: 1f 84 00 00 00 00 00 41 55 41 54 55 53 48 89 fb 48 83 ec 18 4c 8b 25 8c ae 15 00 49 8b 2c 24 8b 45 00 25 00 80 00 00 75 5e 64>
Mar 04 09:38:41 pve kernel: traps: modinfo[1214800] general protection fault ip:7eb4a27dbbed sp:7ffdc521c6a8 error:0 in ld-linux-x86-64.so.2[7eb4a27d4000+25000]
Mar 04 09:38:41 pve kernel: modinfo[1214836]: segfault at 0 ip 0000000000000000 sp 00007ffcf41777e0 error 14 in kmod[62fcbc0de000+4000] likely on CPU 1 (core 1>
Mar 04 09:38:41 pve kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Mar 04 09:38:41 pve kernel: modinfo[1214926]: segfault at 5f66499ca412 ip 000073bbca096010 sp 00007ffccaa6a4f0 error 6 in libc.so.6[73bbca045000+155000] likely>
Mar 04 09:38:41 pve kernel: Code: c0 78 0b 49 83 c0 01 83 f8 01 49 83 dc ff 4c 89 e2 4c 89 f6 48 89 ef 4c 89 44 24 08 e8 89 f2 fa ff 4c 8b 44 24 08 49 8d 04 1c>
Mar 04 09:39:21 pve kernel: modinfo[1223924]: segfault at 370f5720 ip 00000000370f5720 sp 00007fff46b93338 error 14 in kmod[5a9cb9b0c000+4000] likely on CPU 1 >
Mar 04 09:39:21 pve kernel: Code: Unable to access opcode bytes at 0x370f56f6.
Mar 04 09:39:22 pve kernel: traps: modinfo[1225018] general protection fault ip:749781e36bed sp:7ffcbfd7f318 error:0 in ld-linux-x86-64.so.2[749781e2f000+25000]
Mar 04 09:39:23 pve kernel: modinfo[1226971]: segfault at 20 ip 00007c8dc0b56d70 sp 00007ffda1ab7378 error 4 in libcrypto.so.3[7c8dc0ac5000+27c000] likely on C>
Mar 04 09:39:23 pve kernel: Code: 00 00 3c 74 ba 09 00 00 00 0f 44 c2 49 8b 74 24 08 48 63 d5 83 c5 01 88 04 16 0f b6 73 02 48 89 cb 49 8b 56 08 40 84 f6 79 85>
Mar 04 09:39:24 pve kernel: traps: modinfo[1228444] general protection fault ip:7c5e49f21bed sp:7ffe3a9844c8 error:0 in ld-linux-x86-64.so.2[7c5e49f1a000+25000]
Mar 04 09:39:25 pve kernel: modinfo[1230579]: segfault at 18 ip 0000733dee8b675b sp 00007ffe3d217540 error 4 in libc.so.6[733dee845000+155000] likely on CPU 1 >
Mar 04 09:39:25 pve kernel: Code: 0f 87 31 01 00 00 b8 80 00 00 00 41 bd 02 00 00 00 bb 20 00 00 00 48 01 e8 48 8b 48 08 48 8d 70 f0 48 39 ce 0f 84 10 fe ff ff
Mar 04 09:39:26 pve kernel: modinfo[1232496]: segfault at 2326463a0 ip 00000002326463a0 sp 00007ffdf851c8d8 error 14 in kmod[5c1bd1512000+4000] likely on CPU 2>
Mar 04 09:39:26 pve kernel: Code: Unable to access opcode bytes at 0x232646376.
Mar 04 09:39:26 pve kernel: modinfo[1232607]: segfault at 0 ip 0000000000000000 sp 00007ffd29f23f88 error 14 in kmod[60626e1ea000+4000] likely on CPU 3 (core 3>
Mar 04 09:39:26 pve kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Mar 04 09:39:27 pve kernel: modinfo[1232825]: segfault at 701 ip 000071ce851dc947 sp 00007ffc7a5858e0 error 4 in ld-linux-x86-64.so.2[71ce851d4000+25000] likel>
Mar 04 09:39:27 pve kernel: Code: 00 00 00 41 57 41 56 41 55 49 89 f5 41 54 4d 89 c4 55 48 89 d5 53 48 89 fb 48 81 ec 88 00 00 00 48 89 4c 24 10 44 89 4c 24 38>
Mar 04 09:39:28 pve kernel: modinfo[1236397]: segfault at 50 ip 0000797267c2d864 sp 00007fff6bcda720 error 6 in libcrypto.so.3[797267ac5000+27c000] likely on C>
Mar 04 09:39:28 pve kernel: Code: 14 00 bf 18 00 00 00 e8 aa 34 ea ff 48 85 c0 74 25 48 8b 14 24 4c 89 20 48 c7 40 08 00 00 00 00 48 89 50 10 31 d2 48 89 45 00>

This is my grub


Code: 
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


pveversion --verbose

Code: 
root@pve:~# pveversion --verbose
proxmox-ve: 8.3.0 (running kernel: 6.8.12-8-pve)
pve-manager: 8.3.4 (running version: 8.3.4/65224a0f9cd294a3)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
intel-microcode: 3.20241112.1~deb12u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.2.0
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.2
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.3-1
proxmox-backup-file-restore: 3.3.3-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.6
pve-cluster: 8.0.10
pve-container: 5.2.4
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.4.0
pve-qemu-kvm: 9.0.2-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1


I have not turned on any XMP profile and RAM is currently at 2166 MT/s.
 
Last edited:
Vasi said:
I have 6 hard disks that are set up in raidz2 using TRUENAS.

The strange thing is, when I boot up TRUENAS, I no longer see these disks in the PVE disks section. Is this how it is supposed to be?
Click to expand...
If you doing things properly like passing through the controller that hosts the disks directly to TrueNAS then you wont see the disks in proxmox, depends how it is all setup.
 
Yea, All my disks are connected to the HBA and I did the entire HBA passthrough to the truenas VM. That explains why I do not see the disks. Thank you.
 
You must log in or register to reply here.
Top Bottom