Re: RHEL 7.x installation

"Mike Stramba [email protected] [hercules-390]" <[email protected]>
Newsgroups gmane.comp.emulators.hercules390.general
Message-ID <CAA5vqSaXrwXMpzRhgUEA2pz0gCPLXsFNFt+xLyzUeBq_ZqxgeQ@mail.gmail.com>
I don't remember the problem, but seem to remember a post here that it
won't run on Hercules...  (maybe the newer Hyperion 4.xx versions
*might* work ???)

What Hercules version are you trying to use?

Mike

On 6/5/19, [email protected] [hercules-390] <[email protected]> wrote:
> (Originally posted at Hercules-Linux but there hasn't been any action there
> since 2016)
>  I have successfully installed RH 4.7 & 6.0 in previous years. When I
> attempt to IPL the RHEL 7.0 images, I eventually get an error
>
>
>  17:00:21    948.194028! localhost dracut-initqueue 579!: Warning: Could not
> boot.
> 17:00:21    948.302948! localhost dracut-initqueue 579!: Warning: /dev/root
> does not exis
> 17:00:21 t
>
>
>  I am using the same conf file as my older installations (obviously
> different directories):
>
>
>  CPUSERIAL 000611
> CPUMODEL 3090
> MAINSIZE 3072
> XPNDSIZE 0
> CNSLPORT 3270
> HTTPPORT 8081
> NUMCPU 4
> LOADPARM 0120....
> SYSEPOCH 1900
> TODDRAG 1
> ARCHMODE Z/Arch
> PANRATE FAST
> OSTAILOR LINUX
> 000C 3505 images/kernel.img images/generic.prm images/initrd.img autopad eof
>
> 000E 1403 print00e.txt crlf
> 0120 3390 /usr4/hercules/rh7.0_390x/dasd/linux.120
> 0121 3390 /usr4/hercules/rh7.0_390x/dasd/linux.121
> 0122 3390 /usr4/hercules/rh7.0_390x/dasd/linux.122
> 0E20.2 LCS 192.0.2.26 -m 00:11:22:33:44:55
>
>
>
>  generic.prm:
>
>
>  ro ramdisk_size=40000 cio_ignore=all,!condev
>
>
>  and I IPL 000C. Has anyone been successful at installing 7.x or know what
> is the problem? I know that RHEL 7.x switched to this Dracut stuff from what
> they did pre-7.x. Reading about it, it seems that perhaps udev is failing to
> create symbolic links? I can post the entire Hercules log however it all
> looks fine until that point.
>  Paul
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.