Bugzilla – Bug 156914
Inserting blank CDR messes up installation
Last modified: 2006-04-13 06:40:08 UTC
As CD3 I inserted a blank CD instead of a written one Result of this misstep was that installation asked for CD4??? When using Eject in window it changed its mind and wanted CD5??? I had not written CD5 yet, so I tried with CD4. This resulted in what first looked like a hang (related to bug #137525 ?) but it did continue after a while. I even think it said it downloaded some packages - but it did not install any. After that it was finished and got to "Test Internet Connection"...
Created attachment 72157 [details] tar cjf of /var/log/YaST2
Does this also happen if you insert a wrong CD, like CD5 for CD3, or only with a blank media.
As it happened I did both insert a blank and wrong. Install did not complain in either case (this must be wrong!) The computer in question is too slow to retry on (CD1 takes several hours) [I will probably try to install beta7 sooner or later]
I'll reassign this now - Klaus: Can you reproduce this?
*** Bug 157416 has been marked as a duplicate of this bug. ***
OK, tried with beta8 CD1 and CD2 worked well (I planned to insert wrong CD at CD5) But... After CD2 the installation requested CD4 (it still says 40 packages for CD3) I clicked the checkbox to get info - something did not work out right because instead of getting info the installation skipped CD4 (I think CD2 was still in the CD ROM drive at this point). So now it requested CD5! Tried to insert CD3 [in expected order] - failed. Inserting CD5 continued the installation... There are some disk errors in the F10 console "hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } hdc: packet command error: status=0x54 { AbortedCommand LastFailedSense=0x05 } ide: failed opcode was: unknown [repeated once more]" raising Severity...
please attach fresh ;-) y2logs from beta8 installation.
Created attachment 75023 [details] tar cjf of /var/log/YaST2
Created attachment 75024 [details] dump_rpm done before upgrade attempt to beta8 Note that several upgrades before this one failed. RPM database might be unstable/unconsistent state.
media handling -> stano
Much better with Beta9, but... When requested to insert CD5 I inserted a blank CD instead. Detected, got a new request for CD5 Inserted CD4 Detected, got a new request for CD5 Inserted CD5 Upgrade failed to detect that it was CD5... Retested lots of times... Did not work. Opened a virtual terminal, could mount it on /mnt checked the files media.5 did exist... Skip did go on - my 3 packages from CD5 did not install...
What about attaching fresh y2logs? ;-)
Created attachment 77404 [details] Requested YaST2 log files
2006-04-08 20:24:30 <3> thinkpad(3362) [zypp] ExternalProgram.cc(start_program):262 Cannot fork Cannot allocate memory 2006-04-08 20:24:30 <0> thinkpad(3362) [media] Mount.cc(Status):247 exit code: 0 We can hardly do much more anything about it :(
If it is OK for you that this only happens after error handling. Then I guess it is OK for me too. If it had been me investigating this report I would search for memory leaks in error handling code...