I keep finding code related posts searching for subject message.

Was doing some ordinary things on banana pi pro when it kernel panic'd and won't boot.

see attached, this something to do with failing/failed sdcard, never had one fail.

Thanks

Attached Thumbnails

 

A quick way to check is to insert the sd card into another computer. If it can be mounted and dmesg does not report errors.. it's something else.

mralk3, thank you.

Yes that was one of my first thoughts, I'd say sdcard has a problem.


Going to look through my install notes to see if possible to recreate sdcard contents on a different one.

mralk3 or anyone else, ever lose your pi sdcard and is possible to recover?

looking for info, I see INSTALL_AllWinner_A20.TXT has been updated, this was document I used to install.

"2.5 Writing the U-Boot boot loader to the SD card", sounds promising and I did find what was probably last cmdline that was in use.

Now just gotta figure out how to get this altogether.

Something like, follow the above document "write the U-Boot image to the SD card", if cmdline lives there, use my last cmdline?

I do not have any 32bit ARM devices left because they were worn out from use over the years. But, last week I installed to a Orange Pi R1 (32 bit), and this week it is dead. The board became too hot and now it will not boot again. I did the installation by copying all the right files into the right locations on the boot disk, then installed via HTTP on my home LAN. This was because the installer requires more than the 256MB of RAM provided on the R1 board.

I followed the AllWinner H3 document. The A20 should be accurate and is not much different.

The SD card on the Banana Pi (if you follow the install docs) is only used to house U-Boot and its config, so you need to do dd the U-Boot SD image to a new SD card and boot the Banana Pi, as described in the installation doc.
Then step through the u-boot configuration lines. Do all of section 3.1's steps apart from last saveenv;reset one.
Move to step 5.0 and follow the u-boot configuration steps. If you followed the install docs exactly last time, you can paste in the lines directly from the doc; if not you can remember what you did or put the storage onto another machine to figure out the partition layout.
Once you're done, saveenv; reset and it should boot again.

You can back up the u-boot configuration file from the sdcard's fat partition once done.

drmozes, thank you for replying.

I was doing some backups via ssh and just when I got done ssh locked up. Turned on banana monitor and it was kernel panic'd.
Tried to reboot, kept finding nothing to boot???

As you indicated, I tried to step through the instructions. Still would not boot with what looked like, from my notes, last cmdline u-boot I was using.

I tried to reinstall os, got to where to install os and there was no /dev/sd anything, this was ssd connected to banana pi pro sata power and sata data. Tried another ssd same way, no /dev/sd. Tried combination usb sata data power, got os installation rolling.

Came back half hour or so later, banana pi pro was off, now it seems faulty power supply might be real issue? Can't find where I got it.

My BPi's PSU also broke causing boot issues. I powered it from a USB power plug in the end.

1 members found this post helpful.

T T T T, yes I saw those too.

Thanks for that, I was going to retire my banana pi, I'm NOT "going to do this at home", I'm going to look into other workarounds.

Will post back.

You can just plug a USB cable into a USB power adapter. I just wanted to chop it up as I like doing that sort of thing :-)

I did, worked fine. Went about reinstalling as the Instructions are slightly different as in:
I didn't know what to do about the following, educated guess.

This isn't in the instructions, as I think there's not many bananapi users to point it out
4.3.1 Partitioning your hard disk
I don't have screen shot, trying to remember what it said, asked about what to do with vfat/dos partition found, what to do with it and permissions, I said mount to /boot and have root only permissions.

Stuart, with rockpro you're doing
.
With bananapi there's just root=LABEL=SLKroot so I ASSUMED vfat/dos partition found might be ok to be mounted /boot.

5.15.21-armv7 #1 SMP Sun Feb 6 21:08:43 GMT 2022 armv7l Allwinner sun7i (A20) Family GNU/Linux

bananapipro booted, os is running, is this going to be ok? Thank you

no, it won't be ok

got online, upgraded system, now /boot looks like this
and
and there's
I obviously didn't read something, rockpro64 seems to be ok with newer slackwarearm stuffs.

The /boot partition is too tiny probably, so the kernel package couldn't be copied. What does lsblk and df -h report? It's worth checking.

Also I downloaded the package:
Your file listing says the kernel package is only 30KB in size. While the package I downloaded is a lot bigger.

Ignore the crossed out part!

Try using explodepkg and copy the files manually to the /boot media. Then when you can boot the board you can run the following when you are booted up.

EDIT: The crossed out part is misleading and incorrect. That's what I get for watching a movie and answering questions on LQ.

reinstalled, see attached, ALSO see attached what was not in install documentation

When I did slackpkg upgrade-all, kernel packages and all that got upgraded
nothing new was moved into /boot, I've slackpkg upgrade-all kernels thousands of times, new kernel packages get installed, /boot gets updated, I've never had to do anything additional.

My rockpro64 has been humming aarch64 kernel upgrades for decades.

Maybe there's a step I've missed with Slackware ARM 32bit version 15.0?

Attached Thumbnails

   

1 members found this post helpful.

Yes, I saw my mistake and the post was edited, doh!

1 members found this post helpful.