

6:13 am
February 28, 2021

Hi all,
Was hoping for some help with booting an image (Wolfanoz 1 TB) from USB. Took forever to download, burned the image to my SSD with Balenca, validated, everything went smoothly.
Tried to boot the RaspberryPi 4 with just the USB drive (yes, eeprom was updated), but it kept looking for the SD card; went into Raspian and changed the boot order to go from USB. Wasn’t this supposed to be automatic? Not recall seeing anywhere that I need to change the boot order.
When I try to boot from the USB, I get a couple of screens that eventually send with an end kernel panic. If I try to boot a fresh Retropie image, it boots with no issues.
What’s the most likely culprit here? Corrupted image? The thought of having to re-write that image for another 6 hours isn’t very appealing, not sure what other options I might have?
Another option: I have a 1 TB microSD card, can you write the image to this? In the notes, Woflanoz says “you’ll have to expand the card on your own in raspi-config”. How do I get to that step, will the images at least boot into ES first, and if not, what are the steps?
Thanks for any help!
9:26 pm
February 28, 2021

Sorry, I should have clarified. I burned the image to the USB drive, did not have anything in the SD card slot…plugged in the USB, and…nothing. It literally wouldn’t boot past the first screen (the one with the QR code). This was after having updated the EEPROM.
So, I plugged in an SD card that had Raspian, so that I could get into raspi-config to change the boot order to look for the USB. Then, I removed the SD card and booted from the USB, which did then boot, just at least to that kernel panic screen.
I ended up reburning the image and I was able to get into the image now. Clearly just a bad burn from the first time.
Thanks for the help!
1 Guest(s)
