Since it apparently doesn't boot you're going to need to do a bit of detective work.
The best way to figure out what's going on is to look at the system journal. This is easy to do when the system has booted and you can login, but you have to do a bit more work if it's not booting.
Do you have an x64 Linux system? If so, you can use the attached script to enter the device container and have a look at it. Assuming you do, you canwhere /dev/sdX is the device name of your problematic disk.
If you don't, you can always build another RasPiOS disk, boot it, and run mini-nspawn from that.
In either case, if the logs don't give you sufficient information, post the last 100-200 lines of the log here.
The best way to figure out what's going on is to look at the system journal. This is easy to do when the system has booted and you can login, but you have to do a bit more work if it's not booting.
Do you have an x64 Linux system? If so, you can use the attached script to enter the device container and have a look at it. Assuming you do, you can
Code:
sudo /path/to/mini-nspawn /dev/sdX<some garp will print>root@sdm:~# journalctl -D /var/log/journal | less# And then have a look at the tail end of the log to see what's going onIf you don't, you can always build another RasPiOS disk, boot it, and run mini-nspawn from that.
In either case, if the logs don't give you sufficient information, post the last 100-200 lines of the log here.
Statistics: Posted by bls — Thu Dec 21, 2023 11:23 pm