I have a Raspberry Pi 5 8GB connected to internet only through WiFi and placed very closed to the router in my house. It runs Debian 12 64bit, ARM architecture. It's not easy to connect through a real monitor using mouse and keyboard so the best way to access it it's using RealVNC. I use it to install and run some home automation things and working as server. It has two hard disks through a NVMe board The full hardware of it it's the following:
userServer01
description: Computer
product: Raspberry Pi 5 Model B Rev 1.0
serial: d2a4fcaa930ec6e1
width: 64 bits
capabilities: smp cp15_barrier setend swp tagged_addr_disabled
*-core
description: Motherboard
physical id: 0
*-cpu:0
description: CPU
product: cpu
physical id: 0
bus info: cpu@0
size: 2400MHz
capacity: 2400MHz
capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp cpufreq
*-cache
description: L1 Cache
physical id: 0
size: 64KiB
*-cpu:1
description: CPU
product: cpu
physical id: 1
bus info: cpu@1
size: 2400MHz
capacity: 2400MHz
capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp cpufreq
*-cache
description: L1 Cache
physical id: 0
size: 64KiB
*-cpu:2
description: CPU
product: cpu
physical id: 2
bus info: cpu@2
size: 2400MHz
capacity: 2400MHz
capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp cpufreq
*-cache
description: L1 Cache
physical id: 0
size: 64KiB
*-cpu:3
description: CPU
product: cpu
physical id: 3
bus info: cpu@3
size: 2400MHz
capacity: 2400MHz
capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp cpufreq
*-cache
description: L1 Cache
physical id: 0
size: 64KiB
*-cpu:4 DISABLED
description: CPU
product: l2-cache-l0
physical id: 4
bus info: cpu@4
*-cpu:5 DISABLED
description: CPU
product: l2-cache-l1
physical id: 5
bus info: cpu@5
*-cpu:6 DISABLED
description: CPU
product: l2-cache-l2
physical id: 6
bus info: cpu@6
*-cpu:7 DISABLED
description: CPU
product: l2-cache-l3
physical id: 7
bus info: cpu@7
*-cpu:8 DISABLED
description: CPU
product: l3-cache
physical id: 8
bus info: cpu@8
*-memory
description: System memory
physical id: 9
size: 8052MiB
*-pci:0
description: PCI bridge
product: Broadcom Inc. and subsidiaries
vendor: Broadcom Inc. and subsidiaries
physical id: 100
bus info: pci@0000:00:00.0
version: 21
width: 32 bits
clock: 33MHz
capabilities: pci pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:38 memory:1b80000000-1b801fffff
*-pci
description: PCI bridge
product: ASM1182e 2-Port PCIe x1 Gen2 Packet Switch
vendor: ASMedia Technology Inc.
physical id: 0
bus info: pci@0000:01:00.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci msi pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:38 memory:1b80000000-1b801fffff
*-pci:0
description: PCI bridge
product: ASM1182e 2-Port PCIe x1 Gen2 Packet Switch
vendor: ASMedia Technology Inc.
physical id: 3
bus info: pci@0000:02:03.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci msi pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:40 memory:1b80000000-1b800fffff
*-nvme
description: NVMe device
product: Patriot M.2 P300 128GB
physical id: 0
bus info: pci@0000:03:00.0
logical name: /dev/nvme0
version: APF1M3R1
serial: P300HHBB240911007947
width: 64 bits
clock: 33MHz
capabilities: nvme pciexpress msix msi pm nvm_express bus_master cap_list rom
configuration: driver=nvme latency=0 nqn=nqn.2018-12.com.hg:nvme:nvm-subsystem-sn:P300HHBB240911007947 state=live
resources: irq:39 memory:1b80010000-1b80013fff memory:1b80000000-1b8000ffff
*-namespace:0
description: NVMe disk
physical id: 0
logical name: hwmon1
*-namespace:1
description: NVMe disk
physical id: 2
logical name: /dev/ng0n1
*-namespace:2
description: NVMe disk
physical id: 1
bus info: nvme@0:1
logical name: /dev/nvme0n1
size: 119GiB (128GB)
capabilities: partitioned partitioned:dos
configuration: logicalsectorsize=512 sectorsize=512 signature=574bc368 wwid=eui.2c3ebf30373934370000000000000000
*-volume
description: EXT4 volume
vendor: Linux
physical id: 1
bus info: nvme@0:1,1
logical name: /dev/nvme0n1p1
logical name: /mnt/drive128GB-1
version: 1.0
serial: c26d8e38-ba06-41e8-a372-0767c3f68a81
size: 119GiB
capacity: 119GiB
capabilities: primary journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized
configuration: created=2024-11-30 17:45:12 filesystem=ext4 lastmountpoint=/mnt/drive128GB-1 modified=2025-01-26 13:17:31 mount.fstype=ext4 mount.options=rw,relatime mounted=2025-01-26 11:34:53 state=mounted
*-pci:1
description: PCI bridge
product: ASM1182e 2-Port PCIe x1 Gen2 Packet Switch
vendor: ASMedia Technology Inc.
physical id: 7
bus info: pci@0000:02:07.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci msi pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:41 memory:1b80100000-1b801fffff
*-nvme
description: NVMe device
product: Patriot M.2 P300 128GB
physical id: 0
bus info: pci@0000:04:00.0
logical name: /dev/nvme1
version: APF1M3R1
serial: P300HHBB240911007997
width: 64 bits
clock: 33MHz
capabilities: nvme pciexpress msix msi pm nvm_express bus_master cap_list rom
configuration: driver=nvme latency=0 nqn=nqn.2018-12.com.hg:nvme:nvm-subsystem-sn:P300HHBB240911007997 state=live
resources: irq:39 memory:1b80110000-1b80113fff memory:1b80100000-1b8010ffff
*-namespace:0
description: NVMe disk
physical id: 0
logical name: hwmon2
*-namespace:1
description: NVMe disk
physical id: 2
logical name: /dev/ng1n1
*-namespace:2
description: NVMe disk
physical id: 1
bus info: nvme@1:1
logical name: /dev/nvme1n1
size: 119GiB (128GB)
capabilities: partitioned partitioned:dos
configuration: logicalsectorsize=512 sectorsize=512 signature=eb085e5d wwid=eui.2c3ebf30373939370000000000000000
*-volume
description: EXT4 volume
vendor: Linux
physical id: 1
bus info: nvme@1:1,1
logical name: /dev/nvme1n1p1
logical name: /mnt/drive128GB-2
version: 1.0
serial: 59e79f3e-9e43-4fdb-8c6c-211f9009d0a1
size: 119GiB
capacity: 119GiB
capabilities: primary journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized
configuration: created=2024-11-30 17:45:13 filesystem=ext4 lastmountpoint=/mnt/drive128GB-2 modified=2025-01-26 11:34:53 mount.fstype=ext4 mount.options=rw,relatime mounted=2025-01-26 11:34:53 state=mounted
*-pci:1
description: PCI bridge
product: Broadcom Inc. and subsidiaries
vendor: Broadcom Inc. and subsidiaries
physical id: 101
bus info: pci@0001:00:00.0
version: 21
width: 32 bits
clock: 33MHz
capabilities: pci pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:48 memory:1f00000000-1f005fffff
*-network
description: Ethernet controller
physical id: 0
bus info: pci@0001:01:00.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msix bus_master cap_list
configuration: driver=rp1 latency=0
resources: irq:48 memory:1f00410000-1f00413fff memory:1f00000000-1f003fffff memory:1f00400000-1f0040ffff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 6.6.62+rpt-rpi-2712 xhci-hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 6.06
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 6.6.62+rpt-rpi-2712 xhci-hcd
physical id: 2
bus info: usb@2
logical name: usb2
version: 6.06
capabilities: usb-3.00
configuration: driver=hub slots=1 speed=5000Mbit/s
*-usbhost:2
product: xHCI Host Controller
vendor: Linux 6.6.62+rpt-rpi-2712 xhci-hcd
physical id: 3
bus info: usb@3
logical name: usb3
version: 6.06
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usbhost:3
product: xHCI Host Controller
vendor: Linux 6.6.62+rpt-rpi-2712 xhci-hcd
physical id: 4
bus info: usb@4
logical name: usb4
version: 6.06
capabilities: usb-3.00
configuration: driver=hub slots=1 speed=5000Mbit/s
*-mmc0
description: MMC Host
physical id: 5
logical name: mmc0
*-device
description: SD Card
product: SDU1
physical id: 59b4
logical name: /dev/mmcblk0
version: 1.0
date: 08/2024
serial: 346110000
size: 58GiB (62GB)
capabilities: sd partitioned partitioned:dos
configuration: logicalsectorsize=512 sectorsize=512 signature=9ce2bf84
*-volume:0
description: Windows FAT volume
vendor: mkfs.fat
physical id: 1
logical name: /dev/mmcblk0p1
logical name: /boot/firmware
version: FAT32
serial: 5dc7-f115
size: 507MiB
capacity: 512MiB
capabilities: primary fat initialized
configuration: FATs=2 filesystem=fat label=bootfs mount.fstype=vfat mount.options=rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro state=mounted
*-volume:1
description: EXT4 volume
vendor: Linux
physical id: 2
logical name: /dev/mmcblk0p2
logical name: /
version: 1.0
serial: a36be96c-66be-4487-a7a6-0481bca99d89
size: 58GiB
capacity: 58GiB
capabilities: primary journaled extended_attributes large_files dir_nlink recover extents ext4 ext2 initialized
configuration: created=2024-11-19 14:42:52 filesystem=ext4 label=rootfs lastmountpoint=/ modified=2025-01-26 14:35:05 mount.fstype=ext4 mount.options=rw,noatime mounted=2025-01-26 11:34:52 state=mounted
*-mmc1
description: MMC Host
physical id: 6
logical name: mmc1
*-device
description: SDIO Device
physical id: 1
bus info: mmc@1:0001
serial: 0
capabilities: sdio
*-interface:0
description: Wireless interface
product: 4345
vendor: Broadcom
physical id: 1
bus info: mmc@1:0001:1
logical name: mmc1:0001:1
logical name: wlan0
serial: 2c:cf:67:75:9f:b2
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=brcmfmac driverversion=7.45.16.144 firmware=01-b677b91b ip=192.168.1.104 multicast=yes wireless=IEEE 802.11
*-interface:1
product: 4345
vendor: Broadcom
physical id: 2
bus info: mmc@1:0001:2
logical name: mmc1:0001:2
*-bt
description: BlueTooth interface
product: 4345
vendor: Broadcom
physical id: 3
bus info: mmc@1:0001:3
logical name: mmc1:0001:3
capabilities: wireless bluetooth
configuration: wireless=BlueTooth
*-sound:0
description: vc4hdmi0
physical id: 7
logical name: card0
logical name: /dev/snd/controlC0
logical name: /dev/snd/pcmC0D0p
*-sound:1
description: vc4hdmi1
physical id: 8
logical name: card1
logical name: /dev/snd/controlC1
logical name: /dev/snd/pcmC1D0p
*-input:0
product: pwr_button
physical id: 9
logical name: input0
logical name: /dev/input/event0
capabilities: platform
*-input:1
product: vc4-hdmi-0
physical id: a
logical name: input1
logical name: /dev/input/event1
capabilities: cec
*-input:2
product: vc4-hdmi-0 HDMI Jack
physical id: b
logical name: input2
logical name: /dev/input/event2
*-input:3
product: vc4-hdmi-1
physical id: c
logical name: input3
logical name: /dev/input/event3
capabilities: cec
*-input:4
product: vc4-hdmi-1 HDMI Jack
physical id: d
logical name: input4
logical name: /dev/input/event4
*-network
description: Ethernet interface
physical id: e
logical name: eth0
serial: 2c:cf:67:75:9f:b0
capacity: 1Gbit/s
capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=macb driverversion=6.6.62+rpt-rpi-2712 link=no multicast=yes port=twisted pair
The problem is that since around a week I'm encountering many problems like loosing wifi connection, blocking system so I need to reboot continuously. I tried to read and understand the logs of the system trying to understand what's happening but this sometimes becomes difficult because the system is freezing also during this reading. I'm reporting here some extracts about the logs when exactly the freezing/blocking/losing connection happens. I'm not expert in reading the logs but I tried to report the parts around the time when I encountered the problem. This is the first:
For instance at 11:26:22 there is a "wlan0: CTRL-EVENT-DISCONNECTED" that seems something that makes the wifi connection down. I've found through some searches that is a known issue but I don't have understood how is it solved, as reported here and also here. Please consider that this error is not periodically as reported somewhere (like every 12hrs)
I've encountered another error that should be considered, and please see at 4:00:32 in this extract, regarding the rebooting operations, where sometimes it does not solve the issue anyway (Raspberry remains not connected): READ HERE It seems there is an error related one of the hard disk related to the NVMe board: "nvme nvme1: Disabling device after reset failure: -19 Jan 26 04:00:32 userServer01 kernel: I/O error, dev nvme1n1, sector 0 op 0x1:(WRITE) flags" What exactly is it about? I read here that's something about the disk but not sure how to investigate better. Somewhere I also find this error: "I/O error, dev nvme1n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2" or "watchdog: watchdog0: watchdog did not stop!". Also the beginning message is about a network error but I cannot say more: "brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52"
I tried to check the wifi network configurations and they seem to be correctly set on IT (the place where I'm in).
The Raspberry is new and operating since few weeks, and even if the specific issues are happening in the last week, I did not find a stand stability since the beginning.
My first point is: how to solve the connection issue through WiFi? This is of extremely importance about the general server application
The second point is: is it important the error about the NMVe I/O error?
Jan 26 11:35:06 userServer01 containerd[777]: time="2025-01-26T11:35:06.120793583+01:00" level=warning msg="error from *cgroupsv2.Manager.EventChan" error="failed to add inotify watch for `Indicates that there isn't enough with inodes. Check askubuntu.com/questions/1088272/…