Bugzilla – Bug 116409
Installation of SUSE 10.0 RC1 fails on CD2
Last modified: 2006-02-03 13:57:17 UTC
I am running an HP Special Edition L2000 notebook. I downloaded RC1 iso files for X86-64 and ran md5sum to compare checksums with those published in the md5sum file on the website. All of the sums matched. I burned the iso images to CD with K3b (under SUSE 9.3). K3b calculated the checksums and they matched those given on the website. I booted the computer with CD1 and performed a media check on all 5 CDs. The check reported OK for each of the 5 CDs. CD1 installs fine. When prompted for CD2, I place it in the drive and click OK. The box prompting for CD2 remains on the screen even after clicking OK multiple times. When I click Abort and ask it to Show Details, I get the following in an error window: Package dosbootdisk-1.1-40.i586 was not found on the medium Err:10250:ERROR(InstSrc:E_cancel_media) I have not had any installation problems with Betas 2 through 4. I have tried to install RC1 twice and the same error has occurred.
Attach YaST logs, please. http://www.opensuse.org/Bug_Reporting_FAQ#YaST Thanks
Created attachment 49656 [details] Output from hwinfo command
Created attachment 49657 [details] Output of save_y2logs command After placing CD2 in the drive, I clicked on the OK button three times to try to get the installation to continue.
Created attachment 49659 [details] Some YaST2 files found in the /tmp directory Existing in the /tmp directory were the directories YaST2-05636-4NTECm (which was empty) and YaST2-05636-4vgUDx which had files such as stderr and stdout plus others. I tar'd these files up in case they might be useful.
I seems that your CD/DVD had been unable to mount the second CD durig the installation after reboot - because of missing /dev/hdc special device file. See the 'y2log' file: PackageCallbacks.ycp:473 MediaChange `retry SlideShow.ycp:1561 SetCurrentCdNo() - src: 1 , CD: 2 InstSrc.cc(provideMedia):882 Looking for media 2 (SUSE LINUX Products GmbH | 20050907201450) MediaCD.cc(closeTray):134 Unable to open '/dev/hdc' (No such file or directory) Mount.cc(mount):100 stdout: mount: special device /dev/hdc does not exist Hwinfo says: Device: "DVDRW DVR-K15" Device File: /dev/hdc Neil: Could you, please, check whether the file /dev/hdc really doesn't exist? `ls -lh /dev/hdc` Thanks MA: Any other idea? Fehr: Could partitioner have anything about it? Sorry for bothering you, guys...
Now it looks more like a hotplug issue
While CD1 is extracting the software packages, I press Ctrl-Alt-F2 and type 'ls -lh /dev/hdc' (I didn't actually type the single quotes.) The response was: brw-r------ 1 root disk 22,0 2005-09-14 01:45 /dev/hdc I press Ctrl-Alt-F7 to return to the installation screen. After CD1 loads, I let the computer perform its reboot. After it reboots, it asks for CD2. Before answering, I press Ctrl-Alt-F2 and type 'ls -lh /dev/hdc'. The response was: /bin/ls: /dev/hdc: No such file or directory I press Ctrl-Alt-F7 and abort out of the installation. I did not have this problem with betas 2 through 4, each of these betas loaded the 5 CDs just like they should. I didn't get a chance to try beta 1. I originally created my hard drive partitions with beta 2 and have simply been importing from the existing /etc/fstab when creating the partitions/mount table for betas 3 and 4 and RC1. The following is something that I have not been able to reproduce and do not know how the machine got into this state. Maybe it's best not to mention it but I will anyway. After reading the bugzilla e-mail about performing the above test, I started the computer and inserted CD1; however, I got distracted and do not remember if I selected Installation or let it Boot from the Hard Drive or if it started booting off of the hard drive without even booting from the CD. Anyway, when I returned to the machine, I saw the installation window and it was asking for CD2; however, I don't remember whether the installation window showed any files pulled from CD1--I do not think it did, I believe it was blank. (At this point I was a bit surprised and just wasn't paying too much attention.) I took CD1 out and inserted CD2, clicked OK, and it installed! It didn't fail as before and the file dosbootdisk that it couldn't find before, it was able to find. I went through the remaining CDs as one normally would. I entered the root password, created a user account, etc. After all of the configuring the machine came up to runlevel 5. I logged in as the non-root user and received a crash window for Kpower (or something like that). After this I put CD1 back in and rebooted the machine to go through all of the steps I had gone through before to reach the error on CD2 so that I could perform the 'ls -lh' test. After I had done that I wished I had clicked Turn off the computer instead to see if RC1 had fixed my bug report 115328 (Shutdown actually causes reboot). Unfortunately, I can not get back to the point where CD2 would load so I cannot submit a bug report for the Kpower crash problem because I didn't do a backtrace or keep the logs.
Nice ;) Could you, please, try a new RC2 installation? Just the standard one :)?
I did not find RC2 but used RC1 instead. Is RC2 coming out? An install using all of the default settings for partitions and software selection and choosing KDE works. I have found that when I start to fiddle with the partitions, install fails on CD2. I've not tried every combination, of course, but have determined that I can have up to the maximum 4 primary partitions. The size of the partitions doesn't seem to be a problem. I have been limiting my "experiments" to ext3 and reiserfs. It seems that I can adjust the number and size of my partitions and the installation will work with reiserfs. If I reinstall but change the partitions to ext3 (while keeping them the same size), the install stops at CD2. Ext3 is the filesystem I was using for the original installs as it is the filesystem I have used before. Is there a more structured series of tests I should perform to help narrow down the problem?
Said in two words: "Just Strange" ;) arvin, fehr: have you had any experience with such problem? Using Ext3 finishing with failing CD2.... Neil: I'd appreciate YaST log from the simpliest test you can do: Install it on/with an Ext3 partition to reproduce the 'failing CD2' issue. It might be helpful to get the YaST log from your test in comment #9. Thanks
No we do not have any experience with this. But it is perfectly possible that nobody tested this so far. We do mostly small installations or via the network using reiserfs as root filesystem all these cases would prevent running into this bug.
Thanks, so waiting for the YaST logs...
I am attaching the YaST logs for ext2, ext3, and xfs which all fail on CD2. However, reiser works fine. I did try an experiment: I created a reiser partition for / to mount on and an ext2 partition for /home to mount on. This works. Perhaps / needs to mount onto a reiser partition or /dev/hda needs to be a reiser partition. A bit off topic, I've noticed that when I boot off of CD1 I'm usually presented with the menu screen for 'Boot off Hard Drive', 'Installation', 'Memory Test', etc. with the SUSE trademark chameleon's head. However, sometimes I am presented with the menu screen that has the same menu choices but a penguin walks across the top of the menu, another hangs around an igloo, and a third tumbles down the righthand side of the screen. Is this normal?
Created attachment 50123 [details] YaST2 logs for an ext2 partition and a swap partition
Created attachment 50124 [details] YaST2 logs for an ext3 partition and a swap partition This is what you wanted in your comment #14.
Oops! My comment #15 should have referenced your comment #10, not comment #14.
Created attachment 50125 [details] YaST2 logs for an xfs partition and a swap partition
mvidner, snwint: Unknown network controller type 2005-09-15 20:43:44 <3> linux(5617) [YCP] network/hardware.ycp:93 Unknown network controller type: $["bus":"PCI", "bus_hwcfg":"pci", "bus_id":5, "class_id":2, "device":"BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller", "device_id":82712, "model":"Hewlett-Packard Company BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller", "old_unique_key":"xK8l.+HoqxypXtRE", "resource":$["irq":[$["count":0, "enabled":true, "irq":3]], "mem":[$["active":true, "length":8192, "start":3223339008]]], "rev":"2", "slot_id":2, "sub_class_id":128, "sub_device_id":70485, "sub_vendor":"Hewlett-Packard Company", "sub_vendor_id":69692, "sysfs_bus_id":"0000:05:02.0", "udi":"/org/freedesktop/Hal/devices/pci_14e4_4318", "unique_key":"NrnX.+HoqxypXtRE", "vendor":"Broadcom", "vendor_id":70884] 2005-09-15 20:43:44 <3> linux(5617) [YCP] network/hardware.ycp:94 It's probably missing in hwinfo (NOT src/hd/hd.h:sc_net_if) 2005-09-15 20:43:44 <3> linux(5617) [YCP] network/hardware.ycp:319 Unknown controller: $["bus":"PCI", "bus_hwcfg":"pci", "bus_id":5, "class_id":2, "device":"BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller", "device_id":82712, "model":"Hewlett-Packard Company BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller", "old_unique_key":"xK8l.+HoqxypXtRE", "resource":$["irq":[$["count":0, "enabled":true, "irq":3]], "mem":[$["active":true, "length":8192, "start":3223339008]]], "rev":"2", "slot_id":2, "sub_class_id":128, "sub_device_id":70485, "sub_vendor":"Hewlett-Packard Company", "sub_vendor_id":69692, "sysfs_bus_id":"0000:05:02.0", "udi":"/org/freedesktop/Hal/devices/pci_14e4_4318", "unique_key":"NrnX.+HoqxypXtRE", "vendor":"Broadcom", "vendor_id":70884]
Neil, if you haven't filed a bug already about the unrecognized WiFi card, you can do so using the button Copy to New.
I just don't know what's wrong but is seems that the CD drive disappears after the reboot. Whence it follows that the hotplug might be wrong.
no idea why this got assigned to me - i have nothing to do with it - QA work has to be requested via PrjMgmt, and if it's going via bugzilla at least some comment indicating what we should do would be nice ;) reassigning to reporter if it still appears with 10.1. (setting to needinfo)
if this still exists, lukas please take care, if not we can close it i suppose.
Thomas, would you like to take care of it :)?
It as a bug against 10.0, General media handling is totally different for 10.1 Handling of optical drives is totally different for 10.1 Since we are not fixing such bugs in a released product anyway and the same bug cannot be in 10.1 (since udev/hotplug/YaST2 media handling changed fundmentally) I simply resolve this with WONTFIX.