Bug 120600

Can you please attach the /var/log/YaST2 directory?
(http://www.opensuse.org/Bug_Reporting_FAQ#YaST)

At the time when the question pops up, is it possible to get shell access
somewhere? Then I'd like to see the output of:

fuser -u /dev/hdc
fuser -um /dev/hdc
dmesg

Thanks!

(In reply to comment #0)
> After installing the first CD of Suse, the system makes a reboot. Then the
> installation prozess asks me to insert the second install CD.
> After putting it into the drive, and pressing the "OK" Button, the question pops
> up again. Changing the installation path from /dev/hdc to any other devices
dosn´t  
> change the situation.
> 
> The only way for me to install the RC1 was over the network. That worked fine.

(In reply to comment #1)
> Can you please attach the /var/log/YaST2 directory?
> (http://www.opensuse.org/Bug_Reporting_FAQ#YaST)
> 
> At the time when the question pops up, is it possible to get shell access
> somewhere? Then I'd like to see the output of:
> 
> fuser -u /dev/hdc
> fuser -um /dev/hdc
> dmesg
> 
> Thanks!

I can´t get the informations, because the root password isn´t set at this time
and so I can´t log in. The next Problem is, that I cant´t try this again,
because I´ve got only one PC to test this. And if I try, there´s no possebility
to send you the information because my system isn´t working. :-(

Perhaps this will help you a little bit.

I´m working with a Fujitsu Siemens Amilo L7300 
The Path to the DVD-RW Burner /dev/hdc is korrect, under suse 9.3 it´s got the
same path. 
I tried the Installation within and without a pcmcia card-reader inside, because
I saw that the SD-Card was detected as /dev/hda* when it´s inserted on
Installation (should this be like that???).

If there´s no other way to find out what´s the problem is I´ll kill my Linux und
try to repeat the bug. But that´s not my first choice, because I have to work
with it.

Stefan, can you have a look if you have any idea how to continue? Or do you
perhaps know this bug?

No, i have never seen anything like that. We should check if the device node is
even there, it could be something with udev, but i really don't know.

Hello bugscreeners, can you please guide Florian into how to retrieve the log
files (/var/log/Yast2 + dmesg + perhaps /var/log/messages)? (e.g. by
init=/bin/bash while booting)? Then assign back to yast2-maintainers.

Florian: at the grub screen press F2 for other options and enter at the  
bootprompt init=/bin/bash. This will boot the system direct to a propmpt.  
root filesystem is readonly, so mount -o remount,rw / to have write access. 
  
You can also use the rescue system and mount the root partition. Do you have a  
usb-stick where you can copy the files to? If you need more help, please let  
us know.  

Until the required information can be provided, this bug will be closed. Once you recovered the logfiles, please attach them and reopen it.

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(