cifs does not know about sparse files, so you could create a dummy/empty file:and transfer that. It would not put load on PCI-E/NVME/SSD/SD/MMC, so might give a hint where to look for the root cause.
btop (need installation first) gives you a bit more history.
Still, don't waste too much time on guessing. In 20+ years Linux I have seen many errors/failures/crashes that only are visible via console (and loglevel=7.) A serial cable console is best, especially for the Raspberries as various issues have to do with GUI/HDMI (Pi4 VC4 specifically). There is a reason for that connector on Pi5 between the 2 uHDMIs and standaard GPIO14/15 also still there.
Code:
truncate -s10G /mnt/RPi/sparsefile.testbtop (need installation first) gives you a bit more history.
Still, don't waste too much time on guessing. In 20+ years Linux I have seen many errors/failures/crashes that only are visible via console (and loglevel=7.) A serial cable console is best, especially for the Raspberries as various issues have to do with GUI/HDMI (Pi4 VC4 specifically). There is a reason for that connector on Pi5 between the 2 uHDMIs and standaard GPIO14/15 also still there.
Statistics: Posted by redvli — Wed Nov 13, 2024 11:01 am