Again, your boot log shows the Rpi trying to load the OS from the 1st partition (PINN). Here, there is no start.elf as it is renamed to recovery.elf (but it's the same thing).
It is reading autoboot.txt which tells it to reboot into partition 6, but it is not doing so. Instead it is just booting partition 1 again, endlessly.
By using autoboot.txt we have established this is nothing to do with NOOBS/PINN, as this boot process is all part of the RPI firmware boot process.
I can only imagine something is wrong with your backup, but I'm at a loss to explain it at the moment. How did you replace the Raspbian Full boot files from a fresh image? Was it a file-by file copy from the command shell, or some other method using Paragon Disk Manager?
The message from paragon hard disk manager probably relates more to a PC installation, where the boot loader is stored on the disk in unmarked sectors, so I don't think that is relevant as that method is not used by the RPi boot loader.
Would you mind doing another test? Try installing PINN from the RPi imaging tool (from under the Misc Utility category). This will wipe your SD card so we know we are starting from scratch.
Then use PINN to install an OS, like say Raspios_armhf_lite (from the minimal category) - I chose the Lite version just because it is smaller and will take less time to install, but you can chose the "Raspbian full" version if you like. Then just check that this OS can be booted. (This is subtly different to your previous test and tries to eliminate some other causes).
The only times I've seen a similar boot-loop issue where it won't boot from another partition is 1) on certain Pi4 revisions due to an error in the SD card power supply/clock circuit and 2) on early Pi5s where there was an error in the firmware in the Eeprom, but both of these issues have been resolved.
Do you have other storage devices at your disposal? e.g. other SD cards, USB SD card adaptor, USB memory sticks, USB HDDs etc? (Just in case we need to do other tests)
It is reading autoboot.txt which tells it to reboot into partition 6, but it is not doing so. Instead it is just booting partition 1 again, endlessly.
By using autoboot.txt we have established this is nothing to do with NOOBS/PINN, as this boot process is all part of the RPI firmware boot process.
I can only imagine something is wrong with your backup, but I'm at a loss to explain it at the moment. How did you replace the Raspbian Full boot files from a fresh image? Was it a file-by file copy from the command shell, or some other method using Paragon Disk Manager?
The message from paragon hard disk manager probably relates more to a PC installation, where the boot loader is stored on the disk in unmarked sectors, so I don't think that is relevant as that method is not used by the RPi boot loader.
Would you mind doing another test? Try installing PINN from the RPi imaging tool (from under the Misc Utility category). This will wipe your SD card so we know we are starting from scratch.
Then use PINN to install an OS, like say Raspios_armhf_lite (from the minimal category) - I chose the Lite version just because it is smaller and will take less time to install, but you can chose the "Raspbian full" version if you like. Then just check that this OS can be booted. (This is subtly different to your previous test and tries to eliminate some other causes).
The only times I've seen a similar boot-loop issue where it won't boot from another partition is 1) on certain Pi4 revisions due to an error in the SD card power supply/clock circuit and 2) on early Pi5s where there was an error in the firmware in the Eeprom, but both of these issues have been resolved.
Do you have other storage devices at your disposal? e.g. other SD cards, USB SD card adaptor, USB memory sticks, USB HDDs etc? (Just in case we need to do other tests)
Statistics: Posted by procount — Thu Apr 11, 2024 10:50 am