Hide Forgot
Created attachment 499294 [details] anaconda crash report Description of problem: During installation, after selecting Basic Storage Devices| Type of installation ( Use All Space) Write changes to disk. Then a small dialogue pops up saying formatting ext3 and then Unhandled exception from Anaconda. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.cpfmtxa disk from z/VM 2.Attach disk form z/VM to the linux guest. 2.ipl REDHAT EXEC | follow instructions and 3.start VNC 4.select Basic Storage Devices 5. Type of installation as (Use All Space) [I have tied all the methods, all of them fails] Actual results: Installation aborts Expected results: Installation to proceed Additional info:
Hm, doesn't look like as an anaconda issue, the /dev/dasda1 device node is created and then the mkfs process fails with an I/O error when accessing the device.
ok I found a work around to proceed with the installation. 1. cpfmtxa disks form z/VM 2. logoff FEDORA guest form z/VM 3. Log on to another Linux guest say TESTLIN running on the same z/VM 4. link cpfmtxa disks to the second guest Log on to TESTLIN # vmcp link FEDORA 100 1001 mr # chccwdev -e 1001 //say the dasd name assigned in dasde # dasdfmt -b 4096 -y -f /dev/dasde # fdasd -a /dev/dasde # chccwdev -d 1001 # vmcp det 1001 5. log on to the FEDORA guest, and rerun the installation, and everything works fine, and the mkfs error is no more since the disks are already prepared. Thanks sharkcz for the tip!
I have asked a colleague to look at the error messages and this is his opinion: From the messages in anaconda-tb-g3vuXp6UlB0Z.xml I take, that device 0.0.0100 has been recognized as formatted, but later on you get a lot of the following messages: dasd-eckd 0.0.0100: The specified record was not found which indicates that the devices was indeed not properly formatted. Old data on a device can cause the DASD device driver to believe that a DASD is formatted. This is usually no problem as dasdfmt ignores any old format and always applies the specified new format. However, my guess is, that this situation caused anaconda to not call dasdfmt at all. I cannot tell for sure, as I have no detailed knowledge of anaconda, but I recommend that someone who does, has a look at this step of the installation. A device of unknown origins should always be formatted before you use it, even if it seems to be properly formatted.
> > dasd-eckd 0.0.0100: The specified record was not found > > which indicates that the devices was indeed not properly formatted. > Old data on a device can cause the DASD device driver to believe that a DASD is > formatted. This is usually no problem as dasdfmt ignores any old format and > always applies the specified new format. > Well, not properly formatted I am not sure how. because before I started to install, I ran 'cpfmtxa' from z/VM which will format the dasd. (I did not see any errors while I ran cpfmtxa.) -- jsr
(In reply to comment #3) > However, my guess is, that this situation caused anaconda to not call dasdfmt > at all. I cannot tell for sure, as I have no detailed knowledge of anaconda, > but I recommend that someone who does, has a look at this step of the > installation. > > A device of unknown origins should always be formatted before you use it, even > if it seems to be properly formatted. Reassigning to anaconda.
Your syslog is full of I/O errors. This is naturally going to lead to some pretty weird tracebacks. We can't really do anything about that.