could you please quote the parmfile that you use for the installation here somewhere? One issue that is found in the logs is this one:
No filesystem could mount root, tried: iso9660 I guess that this actually should be a CPIO archive and nothing like iso9660 (I am not from redhat, thus I never tried). I also heard rumors, that the parmfile on redhat ISO images was sometimes corrupted, and thus it should be fixed before you can use it. The message like RAMDISK: incomplete write (40960000 != 65745920) also points to a broken parmfile. So, please show us the parmfile (this should actually only be a text file with maybe 2 lines, so no big deal for the list). Berthold On Mon, 25 Aug 2014 14:55:33 +0000 "Martin, Terry Contractor" <[email protected]> wrote: > Alan, > > If the theory is that the INITRD file is somehow corrupted and say > the source (ISO) is ok could it be that it is getting messed up when > transferring to our workstation first and then loading it from there > to the z/Linux guest? > > If so can I take it directly from the HTTP server where the source > files sit to the z/Linux guest skipping the load down to the > workstation? If so what is the best way to do this? I can put the > HTTP URL in the parmfile? > > Thanks Alan! > > Terry martin - Contractor > Cell - 443 854-2452 > Office (NCC) - 410 965-8682 > Email - [email protected] -- ---------------------------------------------------------------------- Berthold Gunreben Build Service Team http://www.suse.de/ Maxfeldstr. 5 SUSE LINUX Products GmbH D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
