RPI4 + OMV6 reboot

    Hello and sorry for my English, I'm French


    I was using omv5 with an rpi4 model B 4g (with ssd for system and hard disk for data in a Raspberry Pi X825 SSD & HDD SATA Board

    ) since 2021, and I never had a problem. I was using docker with nextcloud, jellyfin.....


    As 32bit support on some Dockers was coming to an end, I wanted to switch to omv6 in 64bits, so I installed Raspberry Pi OS Lite Debian version: 11 (bullseye) and I installed omv6


    Everything went well, I re-configured everything but I have a reboot problem.

    When the processor is overused, for example with a borgbakup service or the deletion of heavy folders on the server. The rpi reboots several times by day.

    Before with omv5 I used it without problems for several weeks without reboot but now I don't understand what is happening.


    Has anyone had this type of problem?

    What cooler are you using? Just CPU or kind of integrated plate to cover more?

    There are lot of posts on raspi forum about such issue (i.e. temperature related) - could be RAM or PMIC. You have to check system logs as well to find the source of problems.

    Anyway overloaded RPi tend to reboot.

    P.

    hello, I use a Pi X825 SSD et HDD SATA case, the cooling is in the case and not on the processor, I have never had a cooling problem with omv5 and 32bit os.
    I just looked at my syslog and in fact I have a problem last night 12 the pi rebooted at 1:17 a.m. but the last log line dates from 8 at 11:28 a.m., where are all the log lines missing?


    Oct 8 11:38:17 NAS systemd[1]: Stopping LSB: Switch to ondemand cpu governor (unless shift key is pressed)...

    Oct 8 11:38:17 NAS bluetoothd[1309]: Exit

    Oct 8 11:38:17 NAS systemd[1]: Stopping LSB: rng-tools (Debian variant)...

    Oct 8 11:38:17 NAS systemd[1]: Condition check resulted in Turns off Raspberry Pi display backlight on shutdown/reboot being skipped.

    Oct 8 11:38:17 NAS systemd[1]: rpi-eeprom-update.service: Succeeded.

    Oct 8 11:38:17 NAS systemd[1]: Stopped Check for Raspberry Pi EEPROM updates.

    Oct 12 01:17:29 NAS systemd-modules-load[157]: Failed to find module 'softdog'

    Oct 12 01:17:29 NAS blkmapd[169]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory

    Oct 12 01:17:29 NAS systemd-sysctl[173]: Couldn't write '10000' to 'dev/raid/speed_limit_min', ignoring: No such file or directory

    Oct 12 01:17:29 NAS systemd[1]: Finished Set the console keyboard layout.

    Oct 12 01:17:29 NAS fake-hwclock[155]: Wed Oct 11 23:17:02 UTC 2023

    Oct 12 01:17:29 NAS kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]

    Well, you have a different (new) system (Debian) and new processing power (64) plus new version of software (OMV) - so all things changed except for hardware. Performance boost could leads to higher CPU / memory temp on RPi . X825 - I guess it is Geekworm one? Does it comes with heat-sinks as well or just fan? I'm not using RPi for NAS anymore, but even using for other purposes it is good to equip RPi with heatsinks and fan or combined plate with cooler.

    Is it only borgbackup running at night or some other jobs (rsync / dowloads etc)? You may try to split in time some of the heavy tasks and check performance - anyway I would start from good cooling solution. On my RockPi4 with NVMe drive I've used old AMD CPU cooler to keep SBC in good state :)

    P.

    Hello thanks

    I solved the problem, it came from a multitasking between borgbackup and jellyfin under Docker. It is a problem of saturation of load average >30 but not a problem of temperature of the proc which does not exceed 50°C
    Since then the system is more stable.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login