#1197 Issue `closed`: ReaR on Raspberry Pi: Rear package for ARM¶

Labels: enhancement, fixed / solved / done, sponsored

ArnoutVerbeken opened issue at 2017-02-10 20:28:¶

Hello,

I want to install REAR on an Raspberry3 on Debian Jessie (Raspbian actually), but I can't find suitable package for ARM (for v2.0)

Is it available anywhere? Or how should I install?

Thanks

gozora commented at 2017-02-12 17:55:¶

Hi @ArnoutVerbeken ,

I don't know if there are some packages for RPI.
But ReaR is pure bash script, all you need is to download ReaR e.g. from https://github.com/rear/rear/releases, untar it and run make install.

This should do the trick.

V.

gdha commented at 2017-02-13 13:40:¶

@ArnoutVerbeken How do you plan to boot from the rescue image?

ArnoutVerbeken commented at 2017-02-14 19:24:¶

@gdha I was thinking about a bootable USB stick and then restore to SDcard..?

didacog commented at 2017-02-15 11:59:¶

@gdha

I have plans to do some testings on ARM platforms in near future, I cannot assign me any issue, but I can update this issue when I finish those tests with my results if you are agree.

Also I cannot guarantee any dates to finish my tests :-P

Anyway I can say now that if the SDcard is detected as mmc device, ReaR cannot recreate layout for it because this:

/usr/share/rear/layout/save/GNU/Linux/200_partition_layout.sh

    for disk in /sys/block/* ; do
        blockd=${disk#/sys/block/}
        if [[ $blockd = hd* || $blockd = sd* || $blockd = cciss* || $blockd = vd* || $blockd = xvd* || $blockd = dasd* || $blockd = nvme* ]]

Kind regards,

gdha commented at 2017-02-15 12:20:¶

Indeed, new architectures require new pre-requisites. Looking forward to pull requests.

ArnoutVerbeken commented at 2017-02-15 21:00:¶

So if I understand it right, not much I can do right now, except being patient and being a tester if needed?

jsmeix commented at 2018-02-13 08:46:¶

Since https://github.com/rear/rear/pull/1662 is merged
I consider this issue to be at least initially solved.

Now since @Lukey3332 implemented the basics for ARM support
it should be relatively easy for other ARM users to further
enhance and adapt that to support more ARM devices
in particular Raspberry Pi.

jsmeix commented at 2018-02-13 08:52:¶

@ArnoutVerbeken

FYI:

How you could test the current ReaR GitHub master code:

Basically "git clone" it into a separated directory and then
configure and run ReaR from within that directory like:

# git clone https://github.com/rear/rear.git

# mv rear rear.github.master

# cd rear.github.master

# vi etc/rear/local.conf

# usr/sbin/rear -D mkbackup

Note the relative paths "etc/rear/" and "usr/sbin/".

In general regarding how to work on issues in ReaR
see the sections
"Debugging issues with Relax-and-Recover"
"How to adapt and enhance Relax-and-Recover"
"How to contribute to Relax-and-Recover"
at
https://en.opensuse.org/SDB:Disaster_Recovery

Danrancan commented at 2022-05-25 19:28:¶

Has anyone been able to solve this issue? Why was this closed? OUTPUT=PXE is the only support for ARM. Can we develop a full raspberry pi implementation of this?

gdha commented at 2022-05-26 07:57:¶

@Danrancan Unfortuntely, no-one contributed any ARM64 code for ReaR as far as I know except for the message around PXE booting. However, the PXE booting itself is not the biggest hurdle, but recovering the PI itself:

the rescue image creation
the different disk types are tricky
make the target PI bootable again
and other unkowns

The question these days is who is willing to spent time on this for free? Via a team of persons it might be possible...

[Export of Github issue for rear/rear.]

#1197 Issue closed: ReaR on Raspberry Pi: Rear package for ARM¶