Description of problem: Following dd imaging for media on OS X, the system automounts the media, thereby altering it in a manner that causes rd.live.check to fail. Version-Release number of selected component (if applicable): 1.0.12-3.fc21.x86_64 but applies to any version How reproducible: Always Steps to Reproduce: 1. On OS X, dd any Fedora ISO installation media to a USB stick upon completion, the USB stick automounts rw, this cannot be avoided 2. diskutil unmount the volume cleanly 3. Remove media 4. Boot any computer with this USB stick, choosing media check option in boot menu Actual results: Media check fails. Expected results: Media check succeeds if the payloads are all good. Additional info: This may be unfixable in isomd5sum itself, and maybe should be switched to distribution component if the fix is to use a different method to check media, e.g. check initramfs and the payload, rather than the way it's currently done. In the meantime, we just have to tolerate the fact all OS X produced USB media will always fail media checks, which is not ideal.
Another way to reproduce: 1. On any Fedora system, use dd to create Fedora USB install media. 2. Boot a computer using that USB media, choosing the option to test the media. Result: pass 3. Repeat step 2 as desire to prove the media continues to pass the test. 4. Insert media into a Mac running OS X, it will automount, cleanly eject it, and then repeat step 2. Result: Fail A possible alternative is testing /run/initramfs/live/LiveOS/squashfs.img. The sha256sum of this file remains identical between live environment and the original ISO, even when isomd5sum fails.
Switching this to distribution since it's pretty clear isomd5sum is working exactly as it should since the media has in fact changed.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Still a problem. blkid shows the dd'd stick as: /dev/sdb1: UUID="2015-10-29-21-39-35-00" LABEL="Fedora-Live-WS-x86_64-23-10" TYPE="iso9660" PTUUID="6b8b4567" PTTYPE="dos" PARTUUID="6b8b4567-01" /dev/sdb2: SEC_TYPE="msdos" LABEL="EFI" UUID="FAB8-48CD" TYPE="vfat" PARTUUID="6b8b4567-02" /dev/sdb3: UUID="b09a2592-cc1f-325f-9f1c-5d8b975d214f" LABEL="Fedora Live" TYPE="hfsplus" PARTUUID="6b8b4567-03" And on OS X it's automounting the HFS+ volume we depend on to boot Macs: $ mount [...snip...] /dev/disk2s3 on /Volumes/Fedora Live (hfs, local, nodev, nosuid, noowners) [ 9.900171] localhost systemd[1]: Received SIGCHLD from PID 651 (checkisomd5). [ 9.900613] localhost systemd[1]: Child 651 (checkisomd5) died (code=exited, status=1/FAILURE) [ 9.901029] localhost systemd[1]: checkisomd5@dev-disk-by\x2dlabel-Fedora\x2dLive\x2dWS\x2dx86_64\x2d23\x2d10.service: Child 651 belongs to checkisomd5@dev-disk-by\x2dlabel-Fedora\x2dLive\x2dWS\x2dx86_64\x2d23\x2d10.service [ 9.901447] localhost systemd[1]: checkisomd5@dev-disk-by\x2dlabel-Fedora\x2dLive\x2dWS\x2dx86_64\x2d23\x2d10.service: Main process exited, code=exited, status=1/FAILURE [ 9.901847] localhost systemd[1]: checkisomd5@dev-disk-by\x2dlabel-Fedora\x2dLive\x2dWS\x2dx86_64\x2d23\x2d10.service: Changed start -> failed [ 9.902258] localhost systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13 reply_cookie=0 error=n/a [ 9.902664] localhost systemd[1]: checkisomd5@dev-disk-by\x2dlabel-Fedora\x2dLive\x2dWS\x2dx86_64\x2d23\x2d10.service: Job checkisomd5@dev-disk-by\x2dlabel-Fedora\x2dLive\x2dWS\x2dx86_64\x2d23\x2d10.service/start finished, result=failed [ 9.961241] localhost dracut-initqueue[511]: Got message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13 reply_cookie=0 error=n/a [ 9.941439] localhost kernel: audit_printk_skb: 6 callbacks suppressed [ 9.941446] localhost kernel: audit: type=1130 audit(1453757578.346:13): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=checkisomd5@dev-disk-by\x2dlabel-Fedora\x2dLive\x2dWS\x2dx86_64\x2d23\x2d10 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' [ 9.945272] localhost dracut: FATAL: CD check failed! [ 9.945339] localhost dracut: Refusing to continue
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.