I wanted to clone a RevPi onto another. the first is a 16GB RevPi Core3+, the second is a 16GB RevPi Core 3. I connected in rpiboot mode to device 1 and used win32DiskImager to copy the revPi boot drive to a USB Flash drive, which was successful.
I then connected to device 2 through rpiboot and although I may have started writing to the "USB Drive F:" presented by the revPi before it fell over, I then successfully wrote the image back to the boot partition (it had complained there wasn't enough space, which I don't understand given the source and target are the same size), but succeeded regardless after approx. 45mins.
When I rebooted device 2 (after removing the USB cable), it wouldn't boot into Linux. it gets as far as loading the kernel (I believe) and hangs. See attached image. Should I have copied both the boot and USB drive images, or perhaps was there something in the USB drive that may have been corrupted by my initial attempt to flash?
I double checked; the first working Core3+ has a boot and another partition, the cloned Core3 now only shows a boot partition when booted from a USB cable. Perhaps that's why it can't load the kernel?
Thanks!
Sophie
rPi not booting
- Attachments
-
- 20211206_151800.jpg (99.93 KiB) Viewed 5987 times
-
- BootFail.jpg (287.99 KiB) Viewed 5992 times
Hi Sophie,
please check the model of the seconds device as there isn't a Core 3 (without +) with 16 GB.
Nicolai
please check the model of the seconds device as there isn't a Core 3 (without +) with 16 GB.
Nicolai
Please see attached -
Hmm, I may have assumed it's 16GB...interesting...
Hmm, I may have assumed it's 16GB...interesting...
- Attachments
-
- 20211206_161029.jpg (34.02 KiB) Viewed 5973 times
-
- 20211206_161005.jpg (34.38 KiB) Viewed 5973 times
Last edited by Sophie on 06 Dec 2021, 17:32, edited 1 time in total.
Hi Sophie,
No, the Core3 is 4 GB only. This explains why your image was not flashed correctly (insufficient space).
Nicolai
No, the Core3 is 4 GB only. This explains why your image was not flashed correctly (insufficient space).
Nicolai
Yep, confirmed in the purchase order...bother.
What's the quickest way to revert its image to the factory default?
(edit: I'm flashing the Core 3 Buster image now)
(Annnndd, it's working again.)
Thank you!
Sophie
What's the quickest way to revert its image to the factory default?
(edit: I'm flashing the Core 3 Buster image now)
(Annnndd, it's working again.)
Thank you!
Sophie
Last edited by Sophie on 06 Dec 2021, 18:17, edited 2 times in total.
Hi Sophie,
quickest way to restore the Core 3:
1) Download the current buster image from our website
2) Flash it to your device
3) Start & run the initial configuration uppon first boot
Nicolai
quickest way to restore the Core 3:
1) Download the current buster image from our website
2) Flash it to your device
3) Start & run the initial configuration uppon first boot
Nicolai
Yep, all done. Successfully downloaded and installed. Set up the serial number and MAC address, booted to GUI via raspi-config and completed the graphical setup routine. Prompted to restart...
Restarted, blank screen. No OS... Green power light is lit, Red A1 light is lit but dim.
Aaa...
Sophie
Restarted, blank screen. No OS... Green power light is lit, Red A1 light is lit but dim.
Aaa...
Sophie
Last edited by Sophie on 08 Dec 2021, 12:37, edited 1 time in total.
Hi Sophie,
did any error message occured during the graphical setup (for example a failed update)? If yes this can be the issue as there might be kernel updates too, which unfortunately can't completed when another packages fails.
To prevent a broken system after the graphical setup, please do not click the restart button if any error occurs. Click the later button and proceed with the following steps:
1) Open a terminal
2) Run the update again: sudo apt upgrade
3) Follow the instructions and check for any error messages
Nicolai
did any error message occured during the graphical setup (for example a failed update)? If yes this can be the issue as there might be kernel updates too, which unfortunately can't completed when another packages fails.
To prevent a broken system after the graphical setup, please do not click the restart button if any error occurs. Click the later button and proceed with the following steps:
1) Open a terminal
2) Run the update again: sudo apt upgrade
3) Follow the instructions and check for any error messages
Nicolai
Yep, "sudo apt upgrade" resolved it after whatever caused the GUI upgrade process to fall over; it's usually the simplest things...
I've since rebooted it a few times so fingers crossed, that was the last of my issues for now.
Thanks!
Soph
I've since rebooted it a few times so fingers crossed, that was the last of my issues for now.
Thanks!
Soph
Yes, see my answer above.
Nicolai
Nicolai
