From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; EMC IS 55; .NET CLR 1.0.3705; .NET CLR 1.1.4322; InfoPath.1) Description of problem: Began the installation of RHEL 4.0 U2 for s390x on a z800. When prompted to enter the DASD device numbers, the DASD range specified was 600,601. However, instead of formatting and installing to DASD devices 600 and 601, the installer selected DASD devices 500 and 501. Subsequently, the data on the 500 and 501 devices was overwritten by the dasdfmt command. This is has caused data loss. How and why did this happen? Thanks. Version-Release number of selected component (if applicable): kernel-2.6.9-22.EL How reproducible: Always Steps to Reproduce: Began the installation of RHEL 4.0 U2 for s390x on a z800. When prompted to enter the DASD device numbers, the DASD range specified was 600,601. Continue with the installation.... Actual Results: The installer should have used the devices specified, 600 and 601, but it used 500 and 501 instead. It should not select other devices for installation. Expected Results: The installer should have used the devices specified, 600 and 601, but it used 500 and 501 instead. It should not select other devices for installation. Additional info:
yikes not sure if this is a kernel or installer issues at this point.
*** Bug 181634 has been marked as a duplicate of this bug. ***
*** Bug 181635 has been marked as a duplicate of this bug. ***
Is the installer looking for the LUN/Unit Address to be 00? If so, will the installer use the first Unit Address 00 that is accessible? (Sorry about the duplicates.....I don't know how I managed that one.) Thanks.
We figured out the problem - closing the issue.