I see this email on the anaconda list ten days ago:

Date: Thu, 31 May 2012 16:39:22 +0200
From: Martin Gracik <mgracik>
Reply-To: Discussion of Development and Customization of the Red Hat Linux
    Installer <anaconda-devel-list>
To: anaconda-devel-list
Subject: anaconda-d] Don't remove sha256sum from the install image

---
 share/runtime-cleanup.tmpl |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/share/runtime-cleanup.tmpl b/share/runtime-cleanup.tmpl
index 5a08ab1..b454e67 100644
--- a/share/runtime-cleanup.tmpl
+++ b/share/runtime-cleanup.tmpl
@@ -154,7 +154,7 @@ removefrom coreutils /usr/bin/mkfifo /usr/bin/nl
/usr/bin/nohup /usr/bin/nproc
 removefrom coreutils /usr/bin/od /usr/bin/paste /usr/bin/pathchk
 removefrom coreutils /usr/bin/pinky /usr/bin/pr /usr/bin/printenv
 removefrom coreutils /usr/bin/printf /usr/bin/ptx /usr/bin/runcon
/usr/bin/seq
-removefrom coreutils /usr/bin/sha224sum /usr/bin/sha256sum
/usr/bin/sha384sum
+removefrom coreutils /usr/bin/sha224sum /usr/bin/sha384sum
 removefrom coreutils /usr/bin/sha512sum /usr/bin/shuf /usr/bin/stat


Is this in play here such that a respin of the test candidate is in order?

per a mailing list request, I reverted to:

[root@fedora17-64-kvm fedora]# rpm -q hercules
hercules-3.07-3.fc17.x86_64


I still get this cyclic error (error two)

dracut Warning: Unable to process initqueue
dracut Warning: /dev/root does not exist

Dropping to debug shell.

/lib/dracut-lib.sh: line 802: /dev/tty1: No such file or directory
   511.528226! dracut Warning: Unable to process initqueue
   511.544667! dracut Warning: /dev/root does not exist


dracut Warning: Unable to process initqueue
dracut Warning: /dev/root does not exist

Dropping to debug shell.                                                        


As to the error one

There was a different error set, not involving the shasum ... re-running so I can catch it

earlier errors include:

...
     3.375339! Initializing cgroup subsys perf_event
     3.376805! ftrace: allocating 15705 entries in 62 pages
HHCCP014I CPU0000: Specification exception CODE=0006 ILC=4
PSW=07040001 80000000 00000000001212FA INST=83220258     DIAG  2,2,600(0)
V:0000000000000258:K:06=00000000 00000000 00000000 00000159  ................
R0=0000000000000440 R1=0000000000B23008 R2=000000001FFA7E70 R3=0000000000B18CC8
R4=0000000000AB3816 R5=000000000000001A R6=0000000000000000 R7=0000000000000000
R8=0000000000B17000 R9=0000000000000000 RA=0000000000000000 RB=0000000000134D78
RC=0000000000AB37E8 RD=0000000000000000 RE=000000001FFA7E10 RF=000000001FFA7DD0
     3.693361! cpu: 1 configured CPUs, 0 standby CPUs
     3.700970! Brought up 1 CPUs
  ...

I am able to duplicate here.  Did any previous builds of F17 work for you?  Any build that used dracut at all?

Also can I see your prm file?

Is there a 'not' missing in comment 4  ?

I did not test prior candidates in the F17 s390x series

The config file is straight out of the fedora-17-RelNotes.txt, changing:

 1. the DASD to 0120, and removing locally un-used ones
 2. pointing to a local files:/// image path

[I have a local install mirror, but reverted that out before filing the bug, to follow the upstream example as closely as possible -- I'll amend the nameserver, and networking, once I get past this part]

fedora]# grep -v ^# generic.prm

ro ramdisk_size=40000 cio_ignore=all,!0.0.0009 vnc
rd.dasd=0.0.0120
ip=192.168.100.100::192.168.100.1:24:fedora.example.com:eth0:none
rd.znet=qeth,0.0.0800,0.0.0801,0.0.0802,layer2=0,portname=FOOBAR,portno=0
root=live:file:///etc/hercules/images/fedora/install.img
repo=http://s390.koji.fedoraproject.org/tree/test/20120605/s390x/os/
nameserver=10.20.30.40
[root@fedora17-64-kvm fedora]#

[root@fedora17-64-kvm fedora]# cat /etc/redhat-release ; rpm -q hercules
Fedora release 17 (Beefy Miracle)
hercules-3.07-3.fc17.x86_64
[root@fedora17-64-kvm fedora]#

The not is not missing.  I am able to reproduce.  I ask about other versions because I just recently took on responsibilities for s390 and have until this bug came in never used hercules before.  I was looking for a base line of "it worked here, and doesn't any more' to start the debugging from.

I suspect that dracut is new to the hercules environment and may need some tweaking, but that's really just a guess here.

got it -- I will test the prior versions and advise, as a bisection

Note that this bug also occurs with real IBM s390x hardware (LPAR and in a z/VM virtual machine). That would probably indicate that it's more general in scope.

(In reply to comment #9)
> Note that this bug also occurs with real IBM s390x hardware (LPAR and in a
> z/VM virtual machine). That would probably indicate that it's more general
> in scope.

David, do you see the problem also with pre F-18 composes (http://s390.koji.fedoraproject.org/tree/test/ and http://fedoraproject.org/wiki/Architectures/s390x/18)?

Haven't had an opportunity to test the pre-F18 composes, but have asked Neale and the test team to do so. Barring other required miracles, I should have an answer early next week.

I was not able successfully to install F18 on Hercules for what appears to be this same reason.

(In reply to Adam Goode from comment #13)
> I was not able successfully to install F18 on Hercules for what appears to
> be this same reason.

Adam, can you attach the Hercules log here? The installation of F-18 in hercules should crash much later. What version of Hercules do you have?

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

This happens with 19. I will attach the log soon.

Created attachment 806216 [details]
log file for fedora 19

(In reply to Adam Goode from comment #18)
> Created attachment 806216 [details]
> log file for fedora 19

Adam, I can't see anything about sha256_s390 in your output, so your problem is different than this bug. It looks to me like using the default parameters file in installation, but one set the correct values there, please see https://fedoraproject.org/wiki/Architectures/s390x/19 (and use links to the older releases) for more info.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.