Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Currently only OUTPUT=PXE is supported on ARM #2657

Closed
qiulg opened this issue Jul 13, 2021 · 4 comments
Closed

Currently only OUTPUT=PXE is supported on ARM #2657

qiulg opened this issue Jul 13, 2021 · 4 comments
Labels
enhancement Adaptions and new features needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. no-issue-activity
Milestone

Comments

@qiulg
Copy link

qiulg commented Jul 13, 2021

  • ReaR version ("/usr/sbin/rear -V"):
    Relax-and-Recover 2.6, compile from source.

  • OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
    VERSION="V10 (Tercel)"
    ID="kylin"
    VERSION_ID="V10"
    PRETTY_NAME="Kylin Linux Advanced Server V10 (Tercel)"

Not in os list, and no lsb_release command available. It's simaliar with centos7, so in /etc/rear/os.conf I wrote:
OS_VENDOR=RedHatEnterpriseServer
OS_VERSION=7

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
    OUTPUT=ISO
    BACKUP=NETFS
    OUTPUT_URL=nfs://10.0.90.60/database/nfs/
    BACKUP_URL=nfs://10.0.90.60/database/nfs/

  • Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
    KVM guest on aarch64(ARM64)

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
    aarch64, Vendor ID: HiSilicon, Model name: Kunpeng-920

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
    Don't know.

  • Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT" or "lsblk" as makeshift):
    Only /dev/sda, it's a kvm virtual scsi disk

  • Description of the issue (ideally so that others can reproduce it):

# rear mkrescue
ERROR: Currently only OUTPUT=PXE is supported on ARM
Some latest log messages since the last called script 060_check_config.sh:
  2021-07-13 19:12:57.124692180 Including prep/Linux-arm/060_check_config.sh
Aborting due to an error, check /var/log/rear/rear-kylin10sp1a.log for details
Terminated

/var/log/rear/rear-kylin10sp1a.log shows:

......
2021-07-13 19:12:57.061890400 Finished running 'init' stage in 0 seconds
2021-07-13 19:12:57.067528330 Using build area '/tmp/rear.GllFHK2k49F4ZyO'
2021-07-13 19:12:57.070519290 Running mkrescue workflow
2021-07-13 19:12:57.071559800 ======================
2021-07-13 19:12:57.072485020 Running 'prep' stage
2021-07-13 19:12:57.073898660 ======================
2021-07-13 19:12:57.081478810 Including prep/default/005_remove_workflow_conf.sh
2021-07-13 19:12:57.087046430 Including prep/default/020_translate_url.sh
2021-07-13 19:12:57.090367500 Including prep/default/030_translate_tape.sh
2021-07-13 19:12:57.096112110 Including prep/default/035_valid_backup_methods.sh
2021-07-13 19:12:57.099223580 Including prep/default/040_check_backup_and_output_scheme.sh
2021-07-13 19:12:57.107939610 Including prep/NETFS/default/040_inspect_configuration_files.sh
2021-07-13 19:12:57.111099850 Including prep/NETFS/default/050_check_NETFS_requirements.sh
2021-07-13 19:12:57.116203240 Skipping 'ping' test for host '10.0.90.60' in BACKUP_URL 'nfs://10.0.90.60/database/nfs/'
2021-07-13 19:12:57.121207970 Including prep/default/050_check_keep_old_output_copy_var.sh
2021-07-13 19:12:57.124692180 Including prep/Linux-arm/060_check_config.sh
2021-07-13 19:12:57.133532650 ERROR: Currently only OUTPUT=PXE is supported on ARM
===== Stack trace =====
Trace 0: /usr/sbin/rear:541 main
Trace 1: /usr/share/rear/lib/mkrescue-workflow.sh:12 WORKFLOW_mkrescue
Trace 2: /usr/share/rear/lib/framework-functions.sh:116 SourceStage
Trace 3: /usr/share/rear/lib/framework-functions.sh:56 Source
Trace 4: /usr/share/rear/prep/Linux-arm/060_check_config.sh:2 source
=== End stack trace ===
2021-07-13 19:12:57.140821950 Exiting rear mkrescue (PID 141230) and its descendant processes ...
2021-07-13 19:13:00.157448040 rear,141230 /usr/sbin/rear mkrescue
  `-rear,141457 /usr/sbin/rear mkrescue
      `-pstree,141458 -Aplau 141230
/usr/share/rear/lib/_input-output-functions.sh: line 151: kill: (141461) - No such process
2021-07-13 19:13:00.175114490 Running exit tasks
2021-07-13 19:13:00.176825580 Finished in 4 seconds
2021-07-13 19:13:00.178242010 Removing build area /tmp/rear.GllFHK2k49F4ZyO
2021-07-13 19:13:00.185432940 End of program reached

I saw rear2.4 release note begin to support arm, now 2.6 can mkbackuponly my machine, but can't make ISO. Any workaround for this? Thanks.

Ligong

@jsmeix jsmeix added enhancement Adaptions and new features needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. labels Jul 13, 2021
@jsmeix jsmeix added this to the ReaR future milestone Jul 13, 2021
@jsmeix
Copy link
Member

jsmeix commented Jul 13, 2021

The Currently only OUTPUT=PXE is supported on ARM
comes from usr/share/rear/prep/Linux-arm/060_check_config.sh
which was contributed via #1662
in relation to #1197

As far as I see according to the git log output nothing was contributed
regarding further ARM support enhancements since that time.

@jsmeix jsmeix changed the title Still can't support Currently only OUTPUT=PXE is supported on ARM Jul 13, 2021
@qiulg
Copy link
Author

qiulg commented Jul 13, 2021

@jsmeix Thanks a lot. Got it.

@jsmeix
Copy link
Member

jsmeix commented Jul 13, 2021

@qiulg
if you like to contribute enhancements for ARM support
you may have a look at generic information like
http://relax-and-recover.org/development/
see also the section "How to contribute to Relax-and-Recover" in
https://en.opensuse.org/SDB:Disaster_Recovery

FYI:
I do not have ARM hardware so I myself cannot actually help with ARM issues.

@github-actions
Copy link

Stale issue message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. no-issue-activity
Projects
None yet
Development

No branches or pull requests

2 participants