5.3 Release CD ROM Time out Issues

Lowell Gilbert freebsd-questions-local at be-well.ilk.org
Tue Nov 9 14:34:35 PST 2004


<admin at unixdaemon.org> writes:

> I have a fresh install of 5.3 Release my dvd burner drive conitunes to
> timeout and yes the drive is set as slave...heres my dmesg
> 
> acd0: DVDROM <JLMS DVD-ROM LTD-166S/DS08> at ata1-master UDMA33
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - MODE_SENSE_BIG timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - MODE_SENSE_BIG timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - MODE_SENSE_BIG timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - MODE_SENSE_BIG timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - MODE_SENSE_BIG timed out
> acd1: CDROM <TDK DVDRW420N/1.39> at ata1-slave UDMA33
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - TEST_UNIT_READY timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - PREVENT_ALLOW timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - TEST_UNIT_READY timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - TEST_UNIT_READY timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - PREVENT_ALLOW timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - TEST_UNIT_READY timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - PREVENT_ALLOW timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - TEST_UNIT_READY timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - TEST_UNIT_READY timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - PREVENT_ALLOW timed out
> acd0: DMA limited to UDMA33, non-ATA66 cable or device
> acd1: FAILURE - TEST_UNIT_READY timed out
> 
> 
> It goes on for awhile before booting its TDK 420NBurner has been working
> perfectly since 5.x with no errors. The hardware is fine sometimes the
> machine boots without errors but thats a rarity, so i am not sure why
> exactly its behaving this way.

Sounds like a marginal drive cable (or possibly controller or the
drive itself, but much more likely the cable)...


More information about the freebsd-questions mailing list