I did the steps provided in the first post. Made an img-file from the sd-card, flashed that to the SSD drive. Then followed the instructions from
sudo apt update && sudo apt upgrade && sudo reboot
echo program_usb_boot_mode=1 | sudo tee -a /boot/config.txt
vcgencmd otp_dump | grep 17:
The OTP seems to have been programmed correctly
When restarting the PI nothing happend
I’m afraid that something didn’t quite work in the original instructions on the first post
Do you have a pen steck? Would it be possible to flash a fresh copy of DietPi on that stick and try to boot from it? Just to check of USB boot is working.
It’s not a stick, it’s a ‘normal’ SSD drive.
Will try to flash a new Dietpi install tomorrow.
I guess we misunderstood. For testing, you could try using a pen stick instead of your SSD to see how it behave.
Tried with USB stick I had lying around. Didn’t want to startup either. So I flashed some other SD-card with the img I created earlier in the hope that will work again., but that also fails now.
Btw. I can see that the PI is up (at least in the DHCP table of my router it shows up.
does it boot with the original SD card? How does it behave if you flash a complete new/fresh image to SD/ pen stick?
Just flashed the newest Bullseye to a stick, and it seems that one is booting. At least I could login and start the dietpi install. So, waiting to see what happens next.
Seems to be working so far.
ok means USB boot is working well. Probably there is an issue with the *.img file you create because it was not working as well on another SD card if I understood correctly? How did you created the image?
I cloned the card with Win32 diskimager.
Usually this should be fine. Strange that it was not working on another SD card as well.
Even found another problem.
Armv8 (64bit) doesn’t work, but the 32bit version does. Problem is that a WordPress backup (Backupguard) needs 64 bits to restorre the bakups…
usually there shouldn’t be any difference. How long did you wait on the 64bit version to boot?
February 22, 2022, 6:13pm
Make sure everything is up to date, rpi-eeprom etc, make a backup of your SDcard system with dietpi-backup
Install the stick in the enclosure
(Optional) Verify the drive works well. Connect to your RPi4 running and booted off of the SD card. Drive should be visible in
dietpi-drive_manager. Mount the drive, format the drive, then run benchmarks with dietpi-config just to make sure everything is playing nicely. You don’t have to do this, but then if something is screwed up you may be backtracking here. Copy over the system files: Power down the Pi. Pop out the microSD card, connect to another computer (I used alaptop running Windows and clone the microSD card as an .img on another computer. I used Win32 Disk Imager to create the .img, then connected the SSD to my other computer and flashed the .img using Balena Etcher. I got errors the first two times but succeeded without errors the third time.
Plug the SSD into the pi and boot without a microSD card. If all went well the system should boot basically just the same.
(Optional) Resize the drive. After flashing a 32GB microSD card, the 256GB nvme stick was only recognized as a 32GB partition. Open
dietpi-drive_manager and select the partion and resize it. dietpi-drive_manager hung for what felt like a few minutes the first time. Benchmark and enjoy.
Wow - this went really smooth and worked perfectly! Thanks so much for posting!
I haven’t resized yet (step 5) - will do that tomorrow
in meantime we created a small blog post for this kind of activity
February 23, 2022, 9:18am
bookmarked for the future - thanks!!
the blog is describing as well how to move from a lager SD card to a way smaller device
Just in case some has started with a too large device first.
February 23, 2022, 9:25am
yep - I think you just described me
Will existing files be preserved on the external boot drive if I follow the guide on the blog?