Bug 157239

Summary:	Network-install stops if there is no floppydrive: end_request: I/O error, dev fd0, sector 0
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Azerion Fagonda <azerion>
Component:	Installation	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P5 - None	CC:	suse-beta
Version:	Beta 6
Target Milestone:	---
Hardware:	i586
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	kmsg output (aka log)

Description Azerion Fagonda 2006-03-10 18:53:45 UTC

I am running 10.1 beta6 at the moment. So it can be installed. However, searching for rough edges I tried to re-install using the factory-ftp (I know, I know).

Before we reach YaST-install the computer is set-up. SUSE cannot find the floppy-drive (cause is is not connected) and after finding the networkcard and setting up DHCP it give the error:

end_request: I/O error, dev fd0, sector 0

*since nobody at IRC/mailinglist can tell me how to copy a log in that stage I need to wait for an answer about that before I can post one (boot.msg is not saying that much...). Then I can try to find the 'only-VESA-install-works'-problem and search for it in bugzilla (and report it if there is no report yet)

Comment 1 Christian Boltz 2006-03-10 23:55:28 UTC

To save the logs:
- switch to a terminal (Ctrl-Alt-F2)
- mount any media (hard disk partition, usb stick, NFS mount, ...)
- copy the logs there (hint: save_y2logs /mountpoint/y2logs.tar.gz)
- umount the manually mounted media again

Comment 2 Azerion Fagonda 2006-03-11 00:12:21 UTC

Well, even console2 did not work. 9 did work and I was able to log /proc/kmsg. Notice that /var/log/YaST is empty all the time. But this log will hopefully give some answers (the answer is that there is no answer in the log then only the error)

Comment 3 Azerion Fagonda 2006-03-11 00:14:20 UTC

Created attachment 72388 [details]
kmsg output (aka log)

Comment 4 Azerion Fagonda 2006-03-13 12:30:21 UTC

ps. after the error nothing happens anymore. System does NOT freeze but install hangs.

Comment 5 Michael Gross 2006-03-13 13:01:03 UTC

Why does console #2 not work? What do you mean by this? At which point (exactly) does the error occurr? Can you fetch the state of the screen, maby by taking a picture? Did you disconnect your floppy-drive during the installation?

Comment 6 Azerion Fagonda 2006-03-13 13:13:10 UTC

1.) I have no idea. Just a blank screen. But let that point not be a big point, it's all about that floppy-error. Cause console2 does work when everything goes fine so I do not think it is a bug at it's own. Maybe the error occurs before console2 is setup?

2.) Tell me how, I can tell that the last line is about DHCP setting up. But as you can see in the log that does work and the problem comes after that. Remind: this is all before X is started.

3.) No, if I would do that I would not dare to report the bug cause it would not be a bug but a stupid user-action ;-)

Comment 7 Azerion Fagonda 2006-03-13 14:06:17 UTC

NEW and IMPORTANT information:

Console2 cannot be reached cause when I press CTRL-ALT-F2 nothing happens. So Console2 does not exist yet I think.

Okey, you can cut everything about the floppydrive, maybe an edit of the subject is also recomment. The error about the floppy does not effect anything..... I have arranged an floppydrive and it prints out the same thing, but not the floppy error. So the floppy-error wil probably not hang the setup when the rest goed fine. Some other thing hangs te install.

Last line is about the fact that eth0 is set up.

Comment 8 Michael Gross 2006-03-14 11:34:13 UTC

Please try to fetch all kernel messages until this error happens.

Comment 9 Michael Gross 2006-03-20 12:52:56 UTC

Please reopen this report once you can provide the information.

Comment 10 Azerion Fagonda 2006-03-24 00:06:42 UTC

You may close this one. Still don't know what was the problem but do know it does not occur anymore in beta8 :-). Closed.

Comment 11 Bugzilla Account Maintenance 2008-09-02 18:08:10 UTC

Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from REMIND to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."