Creating a bug report/issue
Required Information
-
DietPi version |
cat /boot/dietpi/.version
-
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=0
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’ -
Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
-
bookworm 0
-
Kernel version |
uname -a
Linux MotioneyeBK 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux -
SBC model |
echo $G_HW_MODEL_NAME
or (EG: RPi3) -
Power supply used | (EG: 5V 1A RAVpower)
-
RPi 4 Model B (aarch64)
-
Stock RPi 4 branded power supply
-
SD card used | (EG: SanDisk ultra)
-
USB → NvMe Drive. 1TB Samsung SSD
Additional Information (if applicable)
- Software title | (EG: Nextcloud)
- MotionEye
- Was the software title installed freshly or updated/migrated?
- Fresh Install using dietpi software install tool
- Can this issue be replicated on a fresh installation of DietPi?
- Yes I have 2 dietpi’s on Pi4 4G and both have this same problem.
- Bug report ID |
echo $G_HW_UUID
Steps to reproduce
- Imaged SSD with Etcher
- Logged in as root. Did all recommended updates etc
- Installed MotionEye
- Install Cameras
- Reboot system
- Motion Eye is dead
Expected behaviour
- .MotionEye restarts after reboot or power cycle
Actual behaviour
- If I reboot BEFORE Camera installs MotionEye restarts normally
- If I reboot AFTER Camera installs MotionEye not only fails to restart, but requires a complete uninstall and reinstall to get the system back…
Extra details
- currently supporting 9 Cameras. 3 from Octoprint Servers, 6 others from rtsv security cameras around the house.
- All camera’s record (motion based) to the 1T SSD
- 4 of the camera’s report motion to HA via MQTT calls.
System works fine, right up till you need to boot the system…