Bug 135795
Summary: | mediacheck failed on FC3T3 discs except disc1 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jim Cornette <jim.cornette> |
Component: | kernel | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | gregory.douglas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-03 00:35:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jim Cornette
2004-10-15 02:34:03 UTC
nautilus-cd-burner just uses cdrecord. Do you get the same problem when you burn a disk using cdrecord? alexl, do you pass the -dao option to cdrecord? I have also had the same issue with CD's 2,3 & 4 of FC3T3. They were burned from a Sony Desktop PCV-RX755 running Windows XP, using Nero 6.3.1.6. I have redownloaded the iso images from other mirrored sites with the same results, not passing media check. rridler harald: No, we don't. I have this problem burning fc3t2 discs with k3b in fc1. Mediacheck consistently fails on disc 1 and disc 4, but the cds pass md5sum checks. I encountered the same problem with my upgrade. I created the CDs in FC2 using the latest kernel (2.6.8) with the latest version of cdrecord. I used the command cdrecord -v -eject speed=0 dev=ATA:1,0,0 file.iso. Disk one passed, disks 2, 3 and 4 failed. Manually inspected the other CDs and all looked well. Upgrade to FC3 went fine using all 4 CDs. I have an LG 52x32x52x burner. Hey Greg, I think the key is the -dao argument. Here's the command I used: cdrecord -v -dao -eject speed=16 dev=ATA:1,0,0 -pad <iso> Like you, I was on Core 2 and my burns of the Core 3 ISOs kept failing the media check (expect for disk 1). With that command all my CDs passed the check and I'm on a fresh installation of Core 3 as I write this. Hope this helps. I was tearing my hair out getting this to work. I also couldn't get disks 2 and 3 of Fedora Core 3 to pass the media check. Burning the cd's on RedHat 7.3, Fedora Core 2 with different writers and only passing the -pad all didn't help. Adding the -dao option (didn't test without -pad) to cdrecord helped my out. Another solution was to start the installation with "linux ide=nodma" See also: http://www.troubleshooters.com/linux/coasterless.htm http://fedoraforum.org/forum/showthread.php?p=125511#post125511 Since the problem is triggered by an underdeveloped portion of the kernel, the component has been changed to the kernel. The easiest solution to get the discs to verify is to add linux ide=nodma and test the discs. Rebooting and installing with these discs works for installation. Would this be an anaconda bug? Maybe dma mode for the cd readers can be disabled for the mediacheck and then dma re-enabled for the installation. The long haul solution would be to fix ide-cd. ide=nodma worked for my laptop upgrade from RH9 to FC3. Used xcdroast to burn cds. all disks passed medicheck. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you. I have only tried the mediacheck with the ide=nodma option since this problem. Closing the bug is OK |