On Tue, Mar 26, 2019 at 10:45:40PM +0100, J??r??me FRGACIC wrote:
> Thanks for all your replies.
>
> > it means the optcode does alllow or prevent media removal it depends on
> > the prevent bits in the cdb but you basically just have a 00 for allow
> > or a 01 for prevent in the cdb. Anyway since sense already told you the
> > request is illegal you have to figure out what came befor the removal
> > request so you might get a clue in what state the hardware is still.
>
> Thanks for those informations. Unfortunetly, I don't have more
> informations or error than those for the moment to determine what happen
> exactly.
>
> > Have you tried cdrecord from ports? I haven't burnt a CD in awhile but last
> > time I did I couldn't get cdio to work but cdrecord would.
>
> I've tried cdrecord too, but I have the same problem. More precisely, it
> quits because it encounters an error, but the CD is still spining forever.
>
> I put the output of cdrecord at the end, just in case it can help, but
> since it seems to be a hardware problem, I suppose there is no easy
> solutions (except changing it, of course). ^^"
>
> Kind regards,
>
>
> J??r??me
>
hi. i don;t think it's a hardware error - i have a cd/dvd writer that
behaves in a similar fashion:
cd0 at scsibus1 targ 1 lun 0: <TSSTcorp, DVD+-RW TS-U633J, D400> ATAPI
5/cdrom removable
i can reproduce the errors you get if i try to write a cd on it. it's
not something i really do, so i never bothered (though i also suspected
a hardware error ;)
jmc
