[Bug 1878596] Comment bridged from LTC Bugzilla

2020-11-11 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2020-11-11 10:36 EDT--- IBM Bugzilla status->closed, documented within the BZ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878596 Title:

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-09-18 Thread bugproxy
--- Comment From tkc...@us.ibm.com 2020-09-17 14:59 EDT--- I used the Ubuntu 20.04 focal image mentioned below because the live-server version did not prompt for installation information during install. http://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/ The focal version

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-09-11 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2020-09-11 05:49 EDT--- (In reply to comment #38) > I did an CPFMTXA format on the DASD device and it did not solve the problem. After a CPFMTXA or any other method to destroy a Linux DASD formatting a DASD will be reported as not formatted

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-09-11 Thread bugproxy
--- Comment From tkc...@us.ibm.com 2020-09-10 13:04 EDT--- I did an CPFMTXA format on the DASD device and it did not solve the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878596

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-05-28 Thread bugproxy
--- Comment From tkc...@us.ibm.com 2020-05-28 10:46 EDT--- This is a newly created device so that was no formatting, but later on it was CPFMTXA formatted under z/VM but the result under Ubuntu installer was the same indicating 0B. -- You received this bug notification because you are

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-05-28 Thread bugproxy
--- Comment From peter.oberparlei...@de.ibm.com 2020-05-28 09:52 EDT--- Not sure if this is related, but from the crash install logs: mkfs /dev/dasda It appears that an attempt is made to create a file system on the full block device, instead of a partition. Note that this will fails

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-05-27 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2020-05-27 04:05 EDT--- (In reply to comment #23) > First of all thanks for sharing the additional information. > I would assume that things worked for you on such a special disk by > coincidence - such DASDs are not tested nor supported by

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-05-26 Thread bugproxy
--- Comment From tkc...@us.ibm.com 2020-05-26 20:05 EDT--- This is strange that you're saying you only support the traditional 3390 Mod9, Mod27, and Mod54 because on Ubuntu 18.04, we're able to install the OS on a 100GB DASD without any problems. RHEL 8.1 and SLES 15 SP1 doesn't have a

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-05-22 Thread bugproxy
--- Comment From tkc...@us.ibm.com 2020-05-22 10:29 EDT--- I have attached the crash install logs and a screen shot of the Storage Configuration panel. As you can see the "Add VTOC Partition" is not highlighted and cannot be selected. Going back to the DASD storage. You can configure

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-05-20 Thread bugproxy
--- Comment From tkc...@us.ibm.com 2020-05-20 13:40 EDT--- I said I was using DASD. FBA is defined using EDEV of an FCP disk. DASD was dedicated to the guest so it's not a minidisk either. I wrote on my last note with Heinz that the for the DASD, VTOC is not highlighted as a possible

[Bug 1878596] Comment bridged from LTC Bugzilla

2020-05-20 Thread bugproxy
--- Comment From tkc...@us.ibm.com 2020-05-20 09:30 EDT--- The document on Ubuntu 20.04 doesn't mention changes in the installer to subiquity installer. It doesn't mention updates to parmfile to include the ip definitions and ftp to the Ubuntu 20.04. After having done the parmfile