The usual (or works for me) method for booting off an external disk with a pi 4 is:
Start with a SD based system and an empty external drive (probably /dev/sda)...
Run fdisk, delete all partitions on /dev/sda.
Create a new primary linux partition. Save and exit.
run sudo mkfs.ext4 /dev/sda1
sudo mkdir /media/disk
sudo mount /dev/sda1 /media/disk
sudo rsync -...
I don't know what tutorial do you follow. I don't had a look at it, tl;dr. But it cannot belong to Raspberry Pi 4B because that model does not support booting from other devices than an SD Card yet. At Raspberry Pi boot modes you can find:
Note: The Raspberry Pi 4B does not use the bootcode.bin file - instead the bootloader is located in an on-board ...
There is a chance that some connections in your rpi is shorted somehow.
It seems your board is not working again so I am leaving some suggestions for others. Always clean your raspberry pi with a brush. The main problem of unused raspberry pi is they have dust on them and conductor particles can easily burn everything if not cleaned properly.
i've had a further look at it. My RP3's SD card had popped and split in half. Turns out i'm not the only one. There's a lot of people online that have had the same issue as me. They take it down after months, turn it on. And within a minute its unbareable to touch
@Ingo has provided a good and correct answer. This answer is provided to augment Ingo's answer & provide details that may be helpful to your understanding.
Know that cron is useful, but to use it effectively, you should understand its limitations.
1. cron has no knowledge of the state of your system during the boot process.
This means that it is ...
In addition to what @ingo has stated, crontab can often start running your script before the Pi is able to do any networking, so it might be worth adding a sleep function to your code after your imports.
You tagged the question with python-3 but you call everywhere python that is calling python 2. Because you don't tell us how do you start the script after login it is unclear why it then unexpected runs. You should also use full path calls in crontab:
@reboot /usr/bin/python3 /home/pi/Coding/BellButton.py >> /home/pi/Coding/BellButton.log
I think the board is hardbricked, and needs to be replaced. Nothing I tried made it work. I do find it weird that the system still has power, including the GPIO, on which I've connected a small cooling fan. The fan still spins when connected, but the RPI doesn't even get to the point where it reads the ssh file on the boot partition.
For what it's worth (if anyone still wants to know). I was hit by this trojan last night. I newly installed it (my first pi). It was late, I was tired. I Hooked up my pi to the internet with the ssh-port open through my router. But I forgot to change the original password of pi. So they could walk right in. From the times I noticed that it was done within ...
I had the same problem, but because my dhcp server managed two interfaces, it didn't crash on error.
I add multiple After= in its unit file /lib/systemd/system/isc-dhcp-server.service:
So I am sure it starts when the services using my wifi card are done starting.
I could also add a ExecStartPre=sleep 10, for ...