Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Apr 2000 10:41:33 -0400
From:      Rod Taylor <rbt@zort.on.ca>
To:        Jean-Francois Dockes <jean-francois.dockes@wanadoo.fr>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: BurnCD
Message-ID:  <20000416104133.B3353@peon.zort.on.ca>

next in thread | raw e-mail | index | archive | help
The drive worked before with the v3 burning stuff.  (The 3 or 4 
utilities that did the job in a script).   But this was all userland, no 
kernel stuff.

However, I did the upgrade to v4 shortly after moving, so perhaps the 
drive got knocked around during that time.

On Sun, 16 Apr 2000 02:53:30 Jean-Francois Dockes wrote:
> Rod Taylor writes:
>  > Problems fixating with BurnCD.  dmesg below...
>  > 
>  > ...
>  > acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04
> 
> This would happen for READ_TOC on a blank disk. May be normal,
> depending on what burncd is doing
> 
>  > acd0: WRITE_BIG - MEDIUM ERROR asc=0c ascq=09 error=04
> 
> Medium error normally means just this: bad spot on the disk. Some
> drives sometimes mistakenly report medium error for what is actually a
> loss of streaming. Also, it is impossible to discriminate a bad drive
> from a bad disk in most cases (other than statistically: retry with a
> disk from another batch, etc...)
> 
> The following are just uninteresting consequences:
> 
>  > acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=24 ascq=00 error=04
> 
> burncd tries to finalize, but the drive is in no mood to do this after 
> the previous error.
> 
> All the rest signals internal inconsistencies in burncd and acd0
> states: I think you just have to reboot...
> 
>  > acd0: WRITE_BIG - MEDIUM ERROR asc=0c ascq=09 error=04
>  > acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=24 ascq=00 error=04
>  > pid 810 (burncd), uid 0: exited on signal 3 (core dumped)
>  > acd0: sequence error (disk already open)
>  > acd0: sequence error (disk already open)
>  > ...
> 
> If you've tried this several times on different (several brands or
> different batches) disks, the most probable cause is a bad drive, but
> these problems are extremely hard to diagnose. At musicmaker, we'd
> just replace the drive after a few problems of this kind.
> 
> 
> Jean-Francois Dockes - musicmaker.com
> 





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000416104133.B3353>