Sony 40x12x48x Problems - Willing to help debug
Greetings - A few days ago I purchased a Sony CRX195E1 (labeled as CRX195A1, but I think they're basically the same drive), which is a 40x12x48x Powerburn-enabled CD-RW. Although I have been able to get packet-writing to work in Linux, I haven't been able to get it to work in an entirely error-free manner. Examples are: -If I delete a directory on the CD-RW (say, dir1) in Windows, I am unable to create a directory of that name in Linux (mkdir claims that a directory of that name already exists). -For some reason, at least one file (possibly more) gives me 'access denied' errors, despite the utter lack of restrictions put on the thing. For instance, if I were to do 'ls *.jpg' it would stick in the middle of the output 'myfile.jpg - Access Denied'. Furthering this problem, after deleting and replacing this file in Windows, I not only did not regain access, but I got TWO of these errors on the SAME filename. -The CD-RW's drive light is almost ALWAYS on when I have the CD-RW mounted. -On one disc, the drive writing time was exceedingly slow when writing lots of little files. However, I suspect that the disc may have been bad. I have attempted using both SCSI emulation mode and plain IDE, but the problems seem to persist equally between these two modes. I am rather at a loss as to what to do. Is there a possibility of the drive being damaged? I have my suspicions, but it seems to work alright in Windows. I am currently using Linux 2.4.18 on a Slackware installation, with the (I believe) latest version of the packet-writing patch. In Windows, I'm using B's Clip 3.24 (which was what came with the drive). Although my skills in kernel programming are lacking, I -am- willing to try to help debug it, albiet I don't know what can be done - I turned on the logging/debug function at it seemed to produce no errors. Any help anyone can give me would be GREATLY appreciated. I have about nine days to determine whether or not this drive is suitable for use before I can't take it back. Thank you for any help you can give me. __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com
Fritz Lnes wrote:
-If I delete a directory on the CD-RW (say, dir1) in Windows, I am unable to create a directory of that name in Linux (mkdir claims that a directory of that name already exists).
I see that I am not alone. The same goes for the window$-deleted files. Regards; O. Sezer
On Mon, Jul 22, 2002 at 11:40:38AM -0700, Fritz Lnes wrote:
Greetings -
A few days ago I purchased a Sony CRX195E1 (labeled as CRX195A1, but I think they're basically the same drive), which is a 40x12x48x Powerburn-enabled CD-RW. Although I have been able to get packet-writing to work in Linux, I haven't been able to get it to work in an entirely error-free manner. Examples are:
-If I delete a directory on the CD-RW (say, dir1) in Windows, I am unable to create a directory of that name in Linux (mkdir claims that a directory of that name already exists). -For some reason, at least one file (possibly more) gives me 'access denied' errors, despite the utter lack of restrictions put on the thing. For instance, if I were to do 'ls *.jpg' it would stick in the middle of the output 'myfile.jpg - Access Denied'. Furthering this problem, after deleting and replacing this file in Windows, I not only did not regain access, but I got TWO of these errors on the SAME filename. -The CD-RW's drive light is almost ALWAYS on when I have the CD-RW mounted. -On one disc, the drive writing time was exceedingly slow when writing lots of little files. However, I suspect that the disc may have been bad.
If your not using the patch I posted to the list friday-ish (or whatever day it was), every file create causes a read which really kills performance on a CDRW.
latest version of the packet-writing patch. In Windows, I'm using B's Clip 3.24 (which was what came with the drive).
Is anything showing up in the kernel log? (run dmesg to check). I've never used B's Clip 3.2 so I don't know what its doing when it deletes a file. You could try recreating the problem with as small a sample set as possible, pull only the used data off the disc, compress it, and send it too me and I can take a look and see if I can figure out what's going wrong. You could also run the UDF verifier on the disc and see what it has to say. Ben
participants (3)
-
Ben Fennema -
Fritz Lnes -
O.Sezer