I have encountered a rather interesting issue trying to install rc1. The system boots and then says there is no disk in the CD drive. The rc1 disk1 downloaded fine and the checksums matched. The CD will mount fine in other systems and can easily be read. I then let 7.0 boot on the test system and mounted the 7.2 cd. It mounts fine and I can read all the files ( well a few that I tested). Looking through the 7.0 dmesg I find some rather unexpected entries for the CD drive. acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 1 lun 0 cd0: <ATAPI CD ROM 1.5> Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: cd present [287216 x 2048 byte records] ... acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retries Exhausted (cd0:ata0:0:1:0): cddone: got error 0x5 back The drive works under 7.0, although with error messages. I also am hearing some rather unusual clicks and whines occasionally from the computer. I can't tell if they are from the CD drive but I suspect so. Many of them stop temporarily when I read a file from the CD. Taking the CD out seems to have stopped the noise. It would appear that I have some kind of CD drive failure. I don't understand why 7.0 can read the drive and 7.2 doesn't even see the disk in it.
On Apr 18, 2009, at 14:05, Doug Hardie wrote:> I have encountered a rather interesting issue trying to install > rc1. The system boots and then says there is no disk in the CD > drive. The rc1 disk1 downloaded fine and the checksums matched. > The CD will mount fine in other systems and can easily be read. I > then let 7.0 boot on the test system and mounted the 7.2 cd. It > mounts fine and I can read all the files ( well a few that I > tested). Looking through the 7.0 dmesg I find some rather > unexpected entries for the CD drive.... Since I can't boot the CD, I did a source update. Unfortunately I seem to have downloaded one of the kernel modules while it was being updated since it would not compile. Since it was for hardware I don't have, I just commented it out and everything then built just fine. #device ath # Atheros pci/cardbus NIC's #device ath_hal # Atheros HAL (Hardware Access Layer) #device ath_rate_sample # SampleRate tx rate control for ath I usually run a stress test on new releases. Basically I open a ftp to a server (local LAN) and download gigs of data - more than the available free space on the drive. With 7.1, the download would hang about 50% of the time. There was free space remaining on the drive. The NIC was basically useless at that point. The only way to restore it was to reboot. The particular machine I am using right now only has an old decrepit rl NIC: rl0: <RealTek 8139 10/100BaseTX> port 0xe000-0xe0ff mem 0xdd104000-0xdd1040ff irq 12 at device 13.0 on pci0 rlphy0: <RealTek internal media interface> PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:d0:09:d8:8f:ff rl0: [ITHREAD] When running this test with 7.2-rc1 it always managed to make it to disk full and then terminate gracefully. Looks like the rl NICs are going to be usable. I had eliminated them from my production servers a long time ago. The only real issue I encountered was that the number of files you have to respond to in mergemaster continues to grow (perhaps exponentially). For my machine I maintain the source on thats no big issue. However, it does cause a lot of additional down time for the servers. I am going to have to dig through mergemaster to see if there is some way to tell it to automatically install the updates to specific directories (e.g., periodic, security, rc.d etc.). I never touch them and they contribute the majority of manual entries.