layout-functions.sh:¶

Labels: support / question, fixed / solved / done

techadmin7 opened issue at 2018-01-30 14:54:¶

Relax-and-Recover (ReaR) Issue Template¶

Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):

rear version (/usr/sbin/rear -V): Relax-and-Recover 2.00 / Git
OS version (cat /etc/rear/os.conf or lsb_release -a):
OS_VENDOR=RedHatEnterpriseServer
OS_VERSION=7
rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf):
default.conf.txt
Are you using legacy BIOS or UEFI boot? UEFI
Brief description of the issue:

ERROR: 
====================
BUG in /usr/share/rear/lib/layout-functions.sh:
'Could not determine size of disk sda/sda1, please file a bug.'
--------------------
Please report this issue at https://github.com/rear/rear/issues
and include the relevant parts from /var/log/rear/rear-huey.log.lockless
preferably with full debug information via 'rear -d -D checklayout'
====================
Aborting due to an error, check /var/log/rear/rear-huey.log.lockless for details
/bin/sh: line 1: 56687 Terminated              /usr/sbin/rear checklayout"

Work-around, if any: N/A

gozora commented at 2018-01-30 16:20:¶

HI,
Maybe you could upgrade to ReaR >= 2.2.
There was https://github.com/rear/rear/pull/1418 implemented which might solve your issue.

V.

techadmin7 commented at 2018-01-30 19:00:¶

I understand updating however I have two other servers same build model same everything that isn’t having this problem at all.

Sent from my iPhone

On Jan 30, 2018, at 8:22 AM, Vladimir Gozora notifications@github.com wrote:

HI,
Maybe you could upgrade to ReaR >= 2.2.
There was #1418 implemented which might solve your issue.

V.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

gozora commented at 2018-01-30 20:31:¶

This is a captious one, I had 8 machines and only 2 were affected (but not always).

V.

techadmin7 commented at 2018-01-30 21:40:¶

Ok. Is the best way to update to run “yum update pkgname” ??

Sent from my iPhone

On Jan 30, 2018, at 12:31 PM, Vladimir Gozora notifications@github.com wrote:

This is a captious one, I had 8 machines and only 2 were affected (but not always).

V.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

techadmin7 commented at 2018-01-30 22:10:¶

[root@huey bin]# cat /var/log/rear/rear-huey.log.lockless
2018-01-30 01:30:01 Relax-and-Recover 2.00 / Git
2018-01-30 01:30:01 Command line options: /usr/sbin/rear checklayout
2018-01-30 01:30:01 Using log file: /var/log/rear/rear-huey.log.lockless
2018-01-30 01:30:01 Including /etc/rear/os.conf
2018-01-30 01:30:01 Including conf/Linux-i386.conf
2018-01-30 01:30:01 Including conf/GNU/Linux.conf
2018-01-30 01:30:01 Including /etc/rear/local.conf
2018-01-30 01:30:01 Running 'init' stage
2018-01-30 01:30:01 Including init/default/010_set_drlm_env.sh
2018-01-30 01:30:01 Including init/default/030_update_recovery_system.sh
2018-01-30 01:30:01 Including init/default/050_check_rear-recover_mode.sh
2018-01-30 01:30:01 Finished running 'init' stage in 0 seconds
2018-01-30 01:30:01 Using build area '/tmp/rear.zsH0etc0NUinzRI'
2018-01-30 01:30:01 Running checklayout workflow
2018-01-30 01:30:01 Running 'layout/precompare' stage
2018-01-30 01:30:01 Including layout/precompare/default/110_check_layout_file.sh
2018-01-30 01:30:01 Finished running 'layout/precompare' stage in 0 seconds
2018-01-30 01:30:01 Running 'layout/save' stage
2018-01-30 01:30:01 Including layout/save/GNU/Linux/100_create_layout_file.sh
2018-01-30 01:30:01 Creating disk layout
2018-01-30 01:30:01 Preparing layout directory.
2018-01-30 01:30:01 Including layout/save/GNU/Linux/150_save_diskbyid_mappings.sh
2018-01-30 01:30:01 Saved diskbyid_mappings
2018-01-30 01:30:01 Including layout/save/GNU/Linux/200_partition_layout.sh
2018-01-30 01:30:01 Saving disk partitions.
2018-01-30 01:30:01 ERROR:
====================
BUG in /usr/share/rear/lib/layout-functions.sh:
'Could not determine size of disk sda/sda1, please file a bug.'
--------------------
Please report this issue at https://github.com/rear/rear/issues
and include the relevant parts from /var/log/rear/rear-huey.log.lockless
preferably with full debug information via 'rear -d -D checklayout'
====================
==== Stack trace ====
Trace 0: /usr/sbin/rear:504 main
Trace 1: /usr/share/rear/lib/checklayout-workflow.sh:18 WORKFLOW_checklayout
Trace 2: /usr/share/rear/lib/framework-functions.sh:85 SourceStage
Trace 3: /usr/share/rear/lib/framework-functions.sh:45 Source
Trace 4: /usr/share/rear/layout/save/GNU/Linux/200_partition_layout.sh:269 source
Trace 5: /usr/share/rear/layout/save/GNU/Linux/200_partition_layout.sh:63 extract_partitions
Trace 6: /usr/share/rear/lib/layout-functions.sh:534 get_disk_size
Trace 7: /usr/share/rear/lib/_input-output-functions.sh:166 BugIfError
Trace 8: /usr/share/rear/lib/_input-output-functions.sh:160 BugError
Message:
====================
BUG in /usr/share/rear/lib/layout-functions.sh:
'Could not determine size of disk sda/sda1, please file a bug.'
--------------------
Please report this issue at https://github.com/rear/rear/issues
and include the relevant parts from /var/log/rear/rear-huey.log.lockless
preferably with full debug information via 'rear -d -D checklayout'
====================
== End stack trace ==
Error: /dev/sdc: unrecognised disk label
Error: /dev/sdd: unrecognised disk label
2018-01-30 01:30:02 Running exit tasks.
2018-01-30 01:30:02 Finished in 1 seconds
2018-01-30 01:30:02 Removing build area /tmp/rear.zsH0etc0NUinzRI
2018-01-30 01:30:02 End of program reached

gdha commented at 2018-01-31 08:10:¶

@techadmin7 Do you have a support contract with RedHat? If yes, please open an incident for this with RH so that they can fix their ReaR version too.
If you want to test the latest stable version of rear go to our Download page and select the proper OS -
http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/RHEL_7/x86_64/

jsmeix commented at 2018-01-31 08:21:¶

@techadmin7
we cannot tell you what the best way is how to upgrade
a particular software on your particular Linux distribution.
For such kind of Linux distribution specific questions
you may better ask at your particular Linux distribution.

In general regarding ReaR version upgrades see the section
"Version upgrades with Relax-and-Recover" at
https://en.opensuse.org/SDB:Disaster_Recovery

In general regarding debugging issues in ReaR see the section
"Debugging issues with Relax-and-Recover" at
https://en.opensuse.org/SDB:Disaster_Recovery

FYI
how you could test the current ReaR GitHub master code
without get things messed up with an already installed
ReaR software package:

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

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

# cd rear

# vi etc/rear/local.conf

# usr/sbin/rear -D mkbackup

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

When the issue still appears with the current ReaR GitHub master code
provide your complete etc/rear/local.conf and a "rear -D mkbackup" log file, cf.
https://en.opensuse.org/SDB:Disaster_Recovery#Debugging_issues_with_Relax-and-Recover

techadmin7 commented at 2018-01-31 14:41:¶

@gdha I do have a contract with Redhat. I have opened a case just waiting for there response. Thank you for your advise.

[Export of Github issue for rear/rear.]

#1717 Issue closed: ERROR BUG in /usr/share/rear/lib/layout-functions.sh:¶