Bug 1252905
Summary: | intermittent guest install problem (image mount error) with f23 ppc64 alpha1 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Menanteau Guy <menantea> | ||||
Component: | distribution | Assignee: | Peter Robinson <pbrobinson> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 23 | CC: | anaconda-maint-list, dan, dennis, gansalmon, g.kaviyarasu, itamar, jcajka, jonathan, kernel-maint, madhu.chinakonda, mchehab, notting, than, vanmeeuwen+fedora | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | ppc64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-08-23 15:17:21 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1071880, 1251887 | ||||||
Attachments: |
|
Description
Menanteau Guy
2015-08-12 13:31:17 UTC
[ 10.494035] dracut-initqueue[555]: cp: error reading './proc/144/task/144/mem': Input/output error Looks like either a kernel or a hardware failure, and since the hardware is fake assigning to kernel. [ 10.424359] dracut-initqueue[555]: anaconda using disk root at /dev/sr0 [ 10.441160] dracut-initqueue[555]: mount: /dev/sr0 is write-protected, mounting read-only [ 10.446709] dracut-initqueue[555]: anaconda: found /run/install/repo//images/install.img [ 10.469821] loop: module loaded [ 10.465425] dracut-initqueue[555]: mount: wrong fs type, bad option, bad superblock on /dev/loop0, [ 10.466225] dracut-initqueue[555]: missing codepage or helper program, or other error [ 10.467742] dracut-initqueue[555]: In some cases useful info is found in syslog - try [ 10.468415] dracut-initqueue[555]: dmesg | tail or so. [ 10.470521] dracut-initqueue[555]: Warning: can't unpack filesystem image! [ 10.472326] dracut-initqueue[555]: /lib/dracut-lib.sh: line 679: cd: /tmp/product.img.684: No such file or directory [ 10.494035] dracut-initqueue[555]: cp: error reading './proc/144/task/144/mem': Input/output error Other explanation might be zero length product.img caused by an issue in xz (too many CPUs and not enough memory) when preparing the compose. i got the same installation issue. After changing the memory from 16384MB to 32000MB it works. Menanteau Guy, could you please try to change the memory and test again if it works for you? For the record, the same issue also affects bare-metal P8 installation. Seems similar to BZ#1215669 (bug for issue mentioned in comment #2). Ngo Than, not sure of what memory you are talking about. In "qemu guest create command" indicated in comment 1, you can see that the guest is done with -m 6G . I also tried with 8G memory without better result. Keep in mind it is a transient problem. I do agree with comment 2 of Dan and I suggest to wait a better compose with a product.img not empty to see if this problem is still alive. (In reply to Menanteau Guy from comment #5) > Ngo Than, not sure of what memory you are talking about. > In "qemu guest create command" indicated in comment 1, you can see that the > guest is done with -m 6G . I also tried with 8G memory without better result. > Keep in mind it is a transient problem. > i created the VM with the kimchi, there's a option memory where the user can change. I changed it to 3200MB and it works for me. Afterthat I tried to create new VM again with memory 32000MB and it failed this time. It seems this problem is randomly. I have investigated but still haven't found the cause. > I do agree with comment 2 of Dan and I suggest to wait a better compose with > a product.img not empty to see if this problem is still alive. i do agree too. From my testing it seems that with F23 Alpha RC2 this problem went away, but please recheck too before we will close this bug. Fixed in Alpha RC2 Problem not reproductible after several tries with Alpha_RC2. http://ppc.koji.fedoraproject.org/compose/23_Alpha_RC2/23/Server/ppc64le/iso/Fedora-Server-DVD-ppc64le-23.iso i can comfirm that the bug is fixed in alpha rc2. http://ppc.koji.fedoraproject.org/compose/23_Alpha_RC2/23/Server/ppc64/iso/Fedora-Server-DVD-ppc64-23.iso it's fixed in ppc64le-rc2 too. http://ppc.koji.fedoraproject.org/compose/23_Alpha_RC2/23/Server/ppc64le/iso/Fedora-Server-DVD-ppc64le-23.iso |