Red Hat Bugzilla – Bug 1292960
StorageError: DeviceFormat.majorminor: can not get majorminor for '/dev/mapper/vg1-snap'
Last modified: 2017-12-06 07:13:10 EST
Version-Release number of selected component:
libreport version: 2.0.9
cmdline: /usr/bin/python /usr/bin/anaconda
:The following was filed automatically by anaconda:
:anaconda 13.21.229 exception report
:Traceback (most recent call first):
: File "/usr/lib/anaconda/storage/formats/__init__.py", line 439, in majorminor
: "can not get majorminor for '%s'" % device)
: File "/usr/lib/anaconda/storage/devices.py", line 1934, in writeKS
: pvs.append("pv.%s" % pv.format.majorminor)
: File "/usr/lib/anaconda/storage/__init__.py", line 1233, in writeKS
: device.writeKS(f, preexisting=preexisting, noformat=noformat)
: File "/usr/lib/anaconda/instdata.py", line 294, in writeKS
: File "/usr/lib/anaconda/packages.py", line 66, in writeKSConfiguration
: File "/usr/lib/anaconda/dispatch.py", line 210, in moveStep
: rc = stepFunc(self.anaconda)
: File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
: File "/usr/lib/anaconda/gui.py", line 1370, in nextClicked
: File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback
: File "/usr/lib/anaconda/gui.py", line 1391, in handleRenderCallback
:StorageError: DeviceFormat.majorminor: can not get majorminor for '/dev/mapper/vg1-snap'
Created attachment 1107414 [details]
Created attachment 1107415 [details]
Created attachment 1107416 [details]
Created attachment 1107417 [details]
Created attachment 1107418 [details]
Created attachment 1107419 [details]
Created attachment 1107420 [details]
Created attachment 1107421 [details]
Created attachment 1107423 [details]
Are you sure your initrd+kernel and the repo match? The bug is set to 6.7, but the anaconda version and the repo is from 6.6 and the logs have this:
18:25:50,603 INFO : Running... ['modprobe', 'xfs']
18:25:50,608 ERROR : FATAL: Module xfs not found.
which usually means the kernel and the modules in install.img are not from matching versions. The install.img will be loaded from the repo unless stage2= is also set.
I used vmlinuz and initrd.img from RHEL 6.7 and by mistake I passed it repo argument that points to RHEL 6.6 repository.
But when I used vmlinuz and initrd.img from RHEL 6.6 and repository from RHEL 6.6, the same bug happens, so it is not caused by mismatch between kernel and repository.
When I used vmlinuz, initrd.img and repository from RHEL 6.7, anaconda crashed very early with a different bug (see bug 1295897), so I don't know if this bug is present in 6.7 or not.
Created attachment 1111920 [details]
ABRT report when using vmlinuz, initrd and repository from RHEL 6.6
This is the same bug report, when installing RHEL 6.6
This is the list of physical volumes, volume groups and logical volumes that are present on the machine - that is probably causing the crash:
PV VG Fmt Attr PSize PFree
/dev/sdb5 vg1 lvm2 a-- 9,32g 5,79g
/dev/vg1/orig Vg_org lvm2 a-- 124,00m 0
/dev/vg1/snap Vg_cow lvm2 a-- 124,00m 0
VG #PV #LV #SN Attr VSize VFree
Vg_cow 1 1 0 wz--n- 124,00m 0
Vg_org 1 1 0 wz--n- 124,00m 0
vg1 1 8 1 wz--n- 9,32g 5,79g
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
Lv_cow Vg_cow -wi------- 124,00m
Lv_org Vg_org -wi------- 124,00m
o vg1 owi-a-s--- 128,00m
orig vg1 -wi-a----- 128,00m
s1 vg1 swi-a-s--- 128,00m o 0,00
snap vg1 -wi-a----- 128,00m
stripe vg1 -wa-a----- 32,00m
switch-0 vg1 -wi-a----- 1,00g
switch-1 vg1 -wi-a----- 1,00g
switch-2 vg1 -wi-a----- 1,00g
I just realized that we don't support XFS on i686 systems:
It would be nice if we didn't crash, but if you want to use xfs you need to use the x86_64 installer.
Ok, now I see what's actually happening, it isn't related to the xfs modprobe errors. When anaconda writes out the final kickstart it is trying to include all the pvs, etc. even ones that were not used as part of the installation. Since it isn't active it can't get the major/minor and fails.
The fix is to exclude things from the kickstart if they are not used for the installation.
Regarding XFS - there is RHEL-7 XFS installation on that machine, but I didn't attempt to use XFS (or mount it) during RHEL 6.6 installation.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: