Bug 156902 - installation hangs when pressing next (weiter) at the media check (Media Prüfung) screen (media errors driveready seekcomplete)
Summary: installation hangs when pressing next (weiter) at the media check (Media Prüf...
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 6
Hardware: x86-64 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 02:30 UTC by Markus Ebenhoeh
Modified: 2006-03-14 12:49 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
messages-log (44.86 KB, text/plain)
2006-03-10 02:34 UTC, Markus Ebenhoeh
Details
hwinfo (49.10 KB, application/x-gzip)
2006-03-10 02:35 UTC, Markus Ebenhoeh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Ebenhoeh 2006-03-10 02:30:27 UTC
I guess this problem probably only occurs with my Samsung DVD-RW drive and my ABit-KV8 Pro mainboard and maybe my CD.

.) downloaded and burned SUSE-Linux-10.1-beta6-x86_64-CD1.iso on my laptop
.) booted with CD1 and selected (normal) install
.) selected German as language
.) clicked "check media" and check finished OK or I skipped checking 
.) clicked "Next" (weiter)
.) waiting clock cursor is shown for at least 7 minutes but probably forever.

I repeated the steps and restarted syslogd with a logfile on a local hd before selecting language.
The installation is continued, though, if either a) the cd is ejected and put back in or b) hwinfo is called on the console.

This or very similar is written to messages-log every ~7 seconds
Mar  9 11:52:15 linux kernel: hdd: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
Mar  9 11:52:15 linux kernel: hdd: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
Mar  9 11:52:15 linux kernel: ide: failed opcode was: unknown
Mar  9 11:52:15 linux kernel: end_request: I/O error, dev hdd, sector 1388232
Mar  9 11:52:15 linux kernel: Buffer I/O error on device hdd, logical block 347058


In the attached messages file I clicked next at 11:52:15 and waited until about 11:59:38 to execute hwinfo (attached).
.) at about 12:23:16, after reading the license screen, I clicked "back" (to the media screen) 
.) and clicked "next" on the media check screen for a second time.
.) again the installation hangs. 
.) this time I ejected the CD at about 12:25:35 and put it back in. And again, the installation continues.

checking the media finishes OK.

mainboard: Abit "KV8 Pro (VIA K8T800P-8237)"
ide controller:
  pci.subsys_vendor = 'ABIT Computer Corp.'
  info.product = 'VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE'
DVD :  Model: "TSSTcorpCD/DVDW TS-H552B"

where is the attach button?
Comment 1 Markus Ebenhoeh 2006-03-10 02:34:27 UTC
Created attachment 72141 [details]
messages-log
Comment 2 Markus Ebenhoeh 2006-03-10 02:35:24 UTC
Created attachment 72143 [details]
hwinfo
Comment 3 Michael Gross 2006-03-13 15:45:41 UTC
Are you sure this is not a problem with your hardware? Does this drive work fine with other systems or installations? Have you tried using another CD or reducing the write speed for this media?
Comment 4 Markus Ebenhoeh 2006-03-14 12:49:32 UTC
Yes, its the DVD drive....
The "lock" just only happend with the OpenSuSE.10.1B6 installation.

I installed SuSE 9.2 and 9.3 on the same hardware and used it for a 14 months. But I almost never used the Samsung DVD-RW drive.
But yes, it seems to be a problem with my hardware and CDs that are > 640MB or so.
I tested it before, but only with smaller CDs.
And even though burning the iso works fine with the drive, the same media gives the mentioned errors on a dd if=/dev/hhd of=somefile as with all CDs > 640 or something. All media worked fine on my laptops DVD drive.
And the same 700MB CDRW media works fine with less data on it.
Well, I guess I forget about it for now or look for a firmware update.

Sorry for the noise.