View Issue Details

IDProjectCategoryView StatusLast Update
0007429Kali Linux[All Projects] Kali Package Bugpublic2021-10-30 17:11
ReporterTerraminator Assigned Tosteev  
PriorityhighSeveritymajorReproducibilitysometimes
Status assignedResolutionopen 
Product Version2021.3 
Target VersionFixed in Version 
Summary0007429: Error in Haveged.service on Raspberry Pi 4
DescriptionThere are two lines in etc/systemd/system/multi-user.target.wants/haveged.service wich have to be commented!
Otherwise the rasperry will ran into emergency mode with error Failed to start entropy Daemon based on the haveged Algorithm.

These are the lines wich have to be commented:
# SystemCallFilter=@basic-io @file-system @io-event @network-io @signal
# SystemCallFilter=arch_prctl brk ioctl mprotect sysinfo

Further Information:
https://github.com/jirka-h/haveged/issues/63
Steps To ReproduceJust install kali linux on a raspberry pi 4 and you will get into emergency mode after reboot.

Activities

steev

2021-10-28 15:29

manager   ~0015386

That's very odd that you end up in emergency mode, haveged failing to start shouldn't be fatal to the boot. I have a pi4 with 8gb as well, let me see if I can reproduce the issue. I'll also comment on the github because this should be specific to the armhf edition of the raspberrypi, and not just raspberrypi because haveged works just fine on the arm64 edition.

steev

2021-10-28 15:36

manager   ~0015387

Going back in my chat history, someone else had reported a similar issue, but it ended up being that their power supply wasn't up to snuff, and they were trying to power too many things at the same time off the usb bus of the rpi. Do you happen to have a similar situation?

steev

2021-10-28 16:30

manager   ~0015388

I just tested here, grabbing a fresh sdcard, downloading 2021.3 armhf (32bit) for the pi, and booted it on my pi4. haveged was actually disabled on the first boot, so i enabled it and rebooted, and it still does not end up in recovery mode.

I'm re-reading the chat with the user (it was on the #kali-linux irc channel) - the issue for them ended up being that they had too many drives connected, and when they would disconnect them, because they were listed in /etc/fstab *without* the nofail option, the system would not boot because without the nofail option being set, it considers a mount point missing as a fatal error.

Terraminator

2021-10-28 16:40

reporter   ~0015389

My fstab file doesnt have the nofail option:
root@TERRAMINATOR:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot vfat defaults 0 2
/dev/mmcblk0p2 / ext4 defaults,noatime 0 1

It also isn't a power issue I allready checked this.

Terraminator

2021-10-28 16:48

reporter   ~0015390

Here is btw my hardware information:
root@TERRAMINATOR:~# lscpu
Architecture: armv7l
  Byte Order: Little Endian
CPU(s): 4
  On-line CPU(s) list: 0-3
Vendor ID: ARM
  Model name: Cortex-A72
    Model: 3
    Thread(s) per core: 1
    Core(s) per socket: 4
    Socket(s): 1
    Stepping: r0p3
    CPU max MHz: 1500.0000
    CPU min MHz: 600.0000
    BogoMIPS: 108.00
    Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva
                        idivt vfpd32 lpae evtstrm crc32

steev

2021-10-28 16:52

manager   ~0015391

What modifications did you make? Did you actually convert your system to ext4? Is this a custom built image from the build scripts? Because the release images are ext3 not ext4, and you can't just say to use ext4, there need to be changes made

Terraminator

2021-10-28 16:56

reporter   ~0015392

I transfered this system from my old sd to a new it could be that this changed the filesystem

steev

2021-10-29 16:52

manager   ~0015393

How old of an installation was it? We haven't used ext4 in a long time (though I do want to go back to it, and do plan to for 2021.4) but I really can't reproduce the issue that you had where it entered recovery mode. Working with upstream, both of the versions of the service file that failed for you work fine here, so I'm really trying to figure out what the difference is.

Terraminator

2021-10-29 18:32

reporter   ~0015394

This is my Version:
RETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2021.3"
VERSION_ID="2021.3"
VERSION_CODENAME="kali-rolling"
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
When I uncomment the two lines haveged crashs and I run into emergency mode this is all I can say
Thank you

steev

2021-10-29 18:34

manager   ~0015395

Can you please provide the contents of your /boot/config.txt , /boot/cmdline.txt and /etc/fstab ?

Terraminator

2021-10-30 17:11

reporter   ~0015398

root@TERRAMINATOR:~# cat /boot/config.txt
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

#[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
#max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d

# If you would like to enable USB booting on your Pi, uncomment the following line.
# Boot from microsd card with it, then reboot.
# Don't forget to comment this back out after using, especially if you plan to use
# sdcard with multiple machines!
# NOTE: This ONLY works with the Raspberry Pi 3+
#program_usb_boot_mode=1
root@TERRAMINATOR:~# cat /boot/cmdline.txt
dwc_otg.fiq_fix_enable=2 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0
root@TERRAMINATOR:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot vfat defaults 0 2
/dev/mmcblk0p2 / ext4 defaults,noatime 0 1

Issue History

Date Modified Username Field Change
2021-10-28 12:17 Terraminator New Issue
2021-10-28 15:29 steev Note Added: 0015386
2021-10-28 15:36 steev Note Added: 0015387
2021-10-28 15:37 steev Assigned To => steev
2021-10-28 15:37 steev Status new => assigned
2021-10-28 16:30 steev Note Added: 0015388
2021-10-28 16:40 Terraminator Note Added: 0015389
2021-10-28 16:48 Terraminator Note Added: 0015390
2021-10-28 16:52 steev Note Added: 0015391
2021-10-28 16:56 Terraminator Note Added: 0015392
2021-10-29 16:52 steev Note Added: 0015393
2021-10-29 18:32 Terraminator Note Added: 0015394
2021-10-29 18:34 steev Note Added: 0015395
2021-10-30 17:11 Terraminator Note Added: 0015398