Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
DVD burners have stopped writing
4 views
Skip to first unread message
Yousuf Khan
Feb 6, 2012, 9:22:25 PM2/6/12
to
I had a pair of DVD burners, both of which have stopped writing (they
can still read them though). They were IDE drives, and they were
connected to each other on the same cable. One of them had started to
spew out random errors in the event log, but the other one was fine.
Then all of a sudden I noticed that the random errors had stopped. This
would've been good if it meant that everything is working again. But
after I tried to burn a disk it didn't seem to work in either drive. I
tried removing the drive that had previously been shown as giving the
errors, but it didn't help, the other drive still won't write either.
Is it possible that one drive could've damaged the other drive by being
connected to the same wire as the other? The software I'm using ImgBurn,
shows a lot of diagnostics messages, and all it shows when I try to
start a burn on the drive is that there is no medium inserted, and the
drive is not ready. The drive can detect other types of disks just fine
though, just not blank disks.
Yousuf Khan
can still read them though). They were IDE drives, and they were
connected to each other on the same cable. One of them had started to
spew out random errors in the event log, but the other one was fine.
Then all of a sudden I noticed that the random errors had stopped. This
would've been good if it meant that everything is working again. But
after I tried to burn a disk it didn't seem to work in either drive. I
tried removing the drive that had previously been shown as giving the
errors, but it didn't help, the other drive still won't write either.
Is it possible that one drive could've damaged the other drive by being
connected to the same wire as the other? The software I'm using ImgBurn,
shows a lot of diagnostics messages, and all it shows when I try to
start a burn on the drive is that there is no medium inserted, and the
drive is not ready. The drive can detect other types of disks just fine
though, just not blank disks.
Yousuf Khan
Rod Speed
Feb 7, 2012, 12:14:39 AM2/7/12
to
Yousuf Khan wrote:
> I had a pair of DVD burners, both of which have stopped writing (they
> can still read them though). They were IDE drives, and they were
> connected to each other on the same cable. One of them had started to
> spew out random errors in the event log, but the other one was fine.
> Then all of a sudden I noticed that the random errors had stopped.
> This would've been good if it meant that everything is working again.
> But after I tried to burn a disk it didn't seem to work in either drive. I tried removing the drive that had
> previously been shown as giving the errors, but it didn't help, the other drive still won't write either.
> Is it possible that one drive could've damaged the other drive by being connected to the same wire as the other?
Not that so much as prevent the other drive from working properly.
> I had a pair of DVD burners, both of which have stopped writing (they
> can still read them though). They were IDE drives, and they were
> connected to each other on the same cable. One of them had started to
> spew out random errors in the event log, but the other one was fine.
> Then all of a sudden I noticed that the random errors had stopped.
> This would've been good if it meant that everything is working again.
> But after I tried to burn a disk it didn't seem to work in either drive. I tried removing the drive that had
> previously been shown as giving the errors, but it didn't help, the other drive still won't write either.
> Is it possible that one drive could've damaged the other drive by being connected to the same wire as the other?
The obvious test for that possibility is to have only one drive on
the cable at a time and see if you still cant burn with either drive.
If you cant, try a new cable.
If that doesnt help either, try a different IDE connector
on the motherboard if there is more than one. From
memory you do run pretty elderly systems, but maybe
that was Ant, not you.
> The software I'm using ImgBurn, shows a lot of diagnostics messages, and all it shows when I try to start a burn on
> the drive is that there is no medium inserted,
> and the drive is not ready.
Arno
Feb 7, 2012, 3:41:07 AM2/7/12
to
Yousuf Khan <bbb...@spammenot.yahoo.com> wrote:
> I had a pair of DVD burners, both of which have stopped writing (they
> can still read them though). They were IDE drives, and they were
> connected to each other on the same cable. One of them had started to
> spew out random errors in the event log, but the other one was fine.
> Then all of a sudden I noticed that the random errors had stopped. This
> would've been good if it meant that everything is working again. But
> after I tried to burn a disk it didn't seem to work in either drive. I
> tried removing the drive that had previously been shown as giving the
> errors, but it didn't help, the other drive still won't write either.
> Is it possible that one drive could've damaged the other drive by being
> connected to the same wire as the other?
Not really, at least not without killing it completely. IDE
> I had a pair of DVD burners, both of which have stopped writing (they
> can still read them though). They were IDE drives, and they were
> connected to each other on the same cable. One of them had started to
> spew out random errors in the event log, but the other one was fine.
> Then all of a sudden I noticed that the random errors had stopped. This
> would've been good if it meant that everything is working again. But
> after I tried to burn a disk it didn't seem to work in either drive. I
> tried removing the drive that had previously been shown as giving the
> errors, but it didn't help, the other drive still won't write either.
> Is it possible that one drive could've damaged the other drive by being
> connected to the same wire as the other?
bus buffers are pretty robust.
> The software I'm using ImgBurn,
> shows a lot of diagnostics messages, and all it shows when I try to
> start a burn on the drive is that there is no medium inserted, and the
> drive is not ready. The drive can detect other types of disks just fine
> though, just not blank disks.
that dust and time kills writing-lasers, these may just have
reached EOL. This may also be a software problem.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: ar...@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
Yousuf Khan
Feb 7, 2012, 9:18:00 AM2/7/12
to
On 07/02/2012 12:14 AM, Rod Speed wrote:
> Yousuf Khan wrote:
>
>> I had a pair of DVD burners, both of which have stopped writing (they
>> can still read them though). They were IDE drives, and they were
>> connected to each other on the same cable. One of them had started to
>> spew out random errors in the event log, but the other one was fine.
>> Then all of a sudden I noticed that the random errors had stopped.
>> This would've been good if it meant that everything is working again.
>> But after I tried to burn a disk it didn't seem to work in either drive. I tried removing the drive that had
>> previously been shown as giving the errors, but it didn't help, the other drive still won't write either.
>
>> Is it possible that one drive could've damaged the other drive by being connected to the same wire as the other?
>
> Not that so much as prevent the other drive from working properly.
>
> The obvious test for that possibility is to have only one drive on
> the cable at a time and see if you still cant burn with either drive.
As I said above, I've already removed the troublesome drive. It still
> Yousuf Khan wrote:
>
>> I had a pair of DVD burners, both of which have stopped writing (they
>> can still read them though). They were IDE drives, and they were
>> connected to each other on the same cable. One of them had started to
>> spew out random errors in the event log, but the other one was fine.
>> Then all of a sudden I noticed that the random errors had stopped.
>> This would've been good if it meant that everything is working again.
>> But after I tried to burn a disk it didn't seem to work in either drive. I tried removing the drive that had
>> previously been shown as giving the errors, but it didn't help, the other drive still won't write either.
>
>> Is it possible that one drive could've damaged the other drive by being connected to the same wire as the other?
>
> Not that so much as prevent the other drive from working properly.
>
> The obvious test for that possibility is to have only one drive on
> the cable at a time and see if you still cant burn with either drive.
made no difference.
>
> If you cant, try a new cable.
>
> If that doesnt help either, try a different IDE connector
> on the motherboard if there is more than one. From
> memory you do run pretty elderly systems, but maybe
> that was Ant, not you.
work with. I could try another cable, but I'd have to look around for
one, not much requirement for IDE cables anymore.
Yousuf Khan
Yousuf Khan
Feb 7, 2012, 9:23:42 AM2/7/12
to
On 07/02/2012 3:41 AM, Arno wrote:
> Have you tried these with a different computer? Also note
> that dust and time kills writing-lasers, these may just have
> reached EOL. This may also be a software problem.
Don't have another desktop to try it with. Could maybe ask a friend to
> Have you tried these with a different computer? Also note
> that dust and time kills writing-lasers, these may just have
> reached EOL. This may also be a software problem.
put it on their desktop, maybe.
The two drives are about a year apart in age, but they both went at the
exact same time. Can't see them both reaching EOL at the same time.
Yousuf Khan
Arno
Feb 7, 2012, 12:16:03 PM2/7/12
to
something like it that damaged them both.
I don't think one could have damaged the other. That would require
frying bus-drivers or the like, and these are permanently short-circuit
proof for IDE and something like that would also kill reading.
Rod Speed
Feb 7, 2012, 3:00:22 PM2/7/12
to
Yousuf Khan wrote
> Could maybe ask a friend to put it on their desktop, maybe.
> The two drives are about a year apart in age, but they both went at the exact same time. Can't see them both reaching
> EOL at the same time.
Yeah, much more likely to be a failure with something common to them.
Could very easily be the cable and thats cheap to try.
Could also be something like bad caps or power supply in the PC too.
In theory it could be just that the lense needs cleaning if you are a smoker,
but that wouldnt normally see both drive stop writing that the same time.
> Arno wrote
>> Have you tried these with a different computer? Also note
>> that dust and time kills writing-lasers, these may just have
>> reached EOL. This may also be a software problem.
> Don't have another desktop to try it with.
Do you dispose of your previous machines ?
>> Have you tried these with a different computer? Also note
>> that dust and time kills writing-lasers, these may just have
>> reached EOL. This may also be a software problem.
> Don't have another desktop to try it with.
> Could maybe ask a friend to put it on their desktop, maybe.
> The two drives are about a year apart in age, but they both went at the exact same time. Can't see them both reaching
> EOL at the same time.
Could very easily be the cable and thats cheap to try.
Could also be something like bad caps or power supply in the PC too.
In theory it could be just that the lense needs cleaning if you are a smoker,
but that wouldnt normally see both drive stop writing that the same time.
Message has been deleted
Rod Speed
Feb 7, 2012, 7:55:01 PM2/7/12
to
Frank Williams wrote
> Yousuf Khan <bbb...@spammenot.yahoo.com> wrote
> CD & DVD burners have a limited life..
You hardly ever see both fail to write simultaneously and still read fine tho.
> Yousuf Khan <bbb...@spammenot.yahoo.com> wrote
You hardly ever see both fail to write simultaneously and still read fine tho.
Yousuf Khan
Feb 9, 2012, 2:22:13 PM2/9/12
to
On 07/02/2012 3:00 PM, Rod Speed wrote:
> Yousuf Khan wrote
> Yousuf Khan wrote
>> Don't have another desktop to try it with.
>
> Do you dispose of your previous machines ?
No, my basic modus operandi is to keep upgrade an existing machine until
>
> Do you dispose of your previous machines ?
it's bleeding edge modern again. I do it piece by piece though,
disposing of individual pieces as needed.
> In theory it could be just that the lense needs cleaning if you are a smoker,
> but that wouldnt normally see both drive stop writing that the same time.
what you mean about things getting cloudy inside. Also if lens that
writes gets cloudy, you'd think that the read lens would too. There's
not a lot of scenarios where only one function goes, but not the other.
Yousuf Khan
Yousuf Khan
Feb 9, 2012, 2:23:50 PM2/9/12
to
On 07/02/2012 7:55 PM, Rod Speed wrote:
> Frank Williams wrote
>> CD& DVD burners have a limited life..
drives and displays their results back?
Yousuf Khan
> Frank Williams wrote
>> CD& DVD burners have a limited life..
>
> You hardly ever see both fail to write simultaneously and still read fine tho.
I'd like to know if there's a test utility that sends ATAPI commands the
> You hardly ever see both fail to write simultaneously and still read fine tho.
drives and displays their results back?
Yousuf Khan
Rod Speed
Feb 9, 2012, 4:32:08 PM2/9/12
to
Yousuf Khan wrote
and motherboards, I still end up with obsolete machines that can be
used to test something like the problem with CD/DVD drives.
> I do it piece by piece though,
Sometimes I do, sometimes I dont.
> disposing of individual pieces as needed.
I dont bother to dispose of them myself. Handy for testing like now in your case.
>> In theory it could be just that the lens needs cleaning if you are a smoker, but that wouldnt normally see both drive
> Also if lens that writes gets cloudy, you'd think that the read lens would too.
They are different lasers, so the write one is usually affected first.
> There's not a lot of scenarios where only one function goes, but not the other.
There is with those, the write laser is quite different to the read one.
But you'd be VERY unlikely to lose the write function
on both drives at the same time even with a smoker.
Bet the problem is the cable or what the cable plugs into at the motherboard end.
> Rod Speed wrote
>> Yousuf Khan wrote
>>> Don't have another desktop to try it with.
>> Do you dispose of your previous machines ?
> No, my basic modus operandi is to keep upgrade an existing machine until it's bleeding edge modern again.
I do too, but with the significant changes in cases and power supplys
>> Yousuf Khan wrote
>>> Don't have another desktop to try it with.
>> Do you dispose of your previous machines ?
> No, my basic modus operandi is to keep upgrade an existing machine until it's bleeding edge modern again.
and motherboards, I still end up with obsolete machines that can be
used to test something like the problem with CD/DVD drives.
> I do it piece by piece though,
> disposing of individual pieces as needed.
>> In theory it could be just that the lens needs cleaning if you are a smoker, but that wouldnt normally see both drive
>> stop writing that the same time.
> No, not a smoker, but I did have a friend who used to be, and I know what you mean about things getting cloudy inside.
And you can always pick a smokers PC when you open it, the stink alone is enough.
> No, not a smoker, but I did have a friend who used to be, and I know what you mean about things getting cloudy inside.
> Also if lens that writes gets cloudy, you'd think that the read lens would too.
> There's not a lot of scenarios where only one function goes, but not the other.
But you'd be VERY unlikely to lose the write function
on both drives at the same time even with a smoker.
Bet the problem is the cable or what the cable plugs into at the motherboard end.
Rod Speed
Feb 9, 2012, 4:34:36 PM2/9/12
to
Yousuf Khan wrote
with that sort of fault where you lose the write function
on two drives at the same time and not the read fuction
so its unlikely that the problem was that both drives were
over voltaged at the same time by a power supply fault etc.
> Rod Speed wrote
>> Frank Williams wrote
>>> CD& DVD burners have a limited life..
>> You hardly ever see both fail to write simultaneously and still read fine tho.
> I'd like to know if there's a test utility that sends ATAPI commands the drives and displays their results back?
Likely there is, I just use substitution myself, particularly
>> Frank Williams wrote
>>> CD& DVD burners have a limited life..
>> You hardly ever see both fail to write simultaneously and still read fine tho.
> I'd like to know if there's a test utility that sends ATAPI commands the drives and displays their results back?
with that sort of fault where you lose the write function
on two drives at the same time and not the read fuction
so its unlikely that the problem was that both drives were
over voltaged at the same time by a power supply fault etc.
GMAN
Feb 10, 2012, 12:44:16 AM2/10/12
to
In article <9pis9l...@mid.individual.net>, "Rod Speed" <rod.sp...@gmail.com> wrote:
>Yousuf Khan wrote
>> Rod Speed wrote
>>> Yousuf Khan wrote
>>>> Don't have another desktop to try it with.
>
>>> Do you dispose of your previous machines ?
>
>> No, my basic modus operandi is to keep upgrade an existing machine until it's
> bleeding edge modern again.
>
>I do too, but with the significant changes in cases and power supplys
>and motherboards, I still end up with obsolete machines that can be
>used to test something like the problem with CD/DVD drives.
>
>> I do it piece by piece though,
>
>Sometimes I do, sometimes I dont.
>
>> disposing of individual pieces as needed.
>
>I dont bother to dispose of them myself. Handy for testing like now in your
> case.
>
>>> In theory it could be just that the lens needs cleaning if you are a smoker,
> but that wouldnt normally see both drive
>>> stop writing that the same time.
>
>> No, not a smoker, but I did have a friend who used to be, and I know what you
> mean about things getting cloudy inside.
>
>And you can always pick a smokers PC when you open it, the stink alone is
> enough.
>
Usually , i can salvage the drives and stuff, but oh my god, the Power Supply
>Yousuf Khan wrote
>> Rod Speed wrote
>>> Yousuf Khan wrote
>>>> Don't have another desktop to try it with.
>
>>> Do you dispose of your previous machines ?
>
>> No, my basic modus operandi is to keep upgrade an existing machine until it's
> bleeding edge modern again.
>
>I do too, but with the significant changes in cases and power supplys
>and motherboards, I still end up with obsolete machines that can be
>used to test something like the problem with CD/DVD drives.
>
>> I do it piece by piece though,
>
>Sometimes I do, sometimes I dont.
>
>> disposing of individual pieces as needed.
>
>I dont bother to dispose of them myself. Handy for testing like now in your
> case.
>
>>> In theory it could be just that the lens needs cleaning if you are a smoker,
> but that wouldnt normally see both drive
>>> stop writing that the same time.
>
>> No, not a smoker, but I did have a friend who used to be, and I know what you
> mean about things getting cloudy inside.
>
>And you can always pick a smokers PC when you open it, the stink alone is
> enough.
>
is always the first to go.
Rod Speed
Feb 10, 2012, 1:07:16 AM2/10/12
to
GMAN wrote
I buy decent ones in the first place, so dont need to operate like that.
The format does change and the capacity does too over time and the power connectors too.
And I keep a spare on hand too.
The format does change and the capacity does too over time and the power connectors too.
And I keep a spare on hand too.
GMAN
Feb 10, 2012, 11:16:40 PM2/10/12
to
working on it with their power supply attached. I usually hook one up
temporarily while i repair their pc.
Franc Zabkar
Feb 11, 2012, 12:27:59 AM2/11/12
to
On Mon, 06 Feb 2012 21:22:25 -0500, Yousuf Khan
<bbb...@spammenot.yahoo.com> put finger to keyboard and composed:
>I had a pair of DVD burners, both of which have stopped writing (they
>can still read them though).
Have you tried different media, eg CD-R rather than DVD?
- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
<bbb...@spammenot.yahoo.com> put finger to keyboard and composed:
>I had a pair of DVD burners, both of which have stopped writing (they
>can still read them though).
- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
Rod Speed
Feb 11, 2012, 11:03:12 AM2/11/12
to
> I usually hook one up temporarily while i repair their pc.
GMAN
Feb 11, 2012, 12:33:19 PM2/11/12
to
>> I usually hook one up temporarily while i repair their pc.
>
>Mad.
>
>
smell permeatting the room for hours while i work on the pc. Maybe you like
the smell, i dont.
Yousuf Khan
Feb 15, 2012, 5:37:20 PM2/15/12
to
Well, here's an update on this problem. I've now had a chance to test it
out with different configurations. It's been suggested that I should
test it with different IDE cables, I've now tried 3 different IDE
cables, each one had the same problem with this drive. I then tested
whether it was the motherboard IDE connection that was the problem here,
so I remembered that my eSATA PCI-e adapter also had included its own
IDE connector, so I moved the connection over to that connector. Same
problem here as well, in fact, on this connector it can't even detect
the DVD drive's model name!
So I'm thinking I've done sufficient due diligence and I can declare
this drive dead. The only other thing I could possibly try is to put an
IDE-SATA converter adapter on it, and try to run it through SATA. I've
had success in the past with old IDE hard drives that looked like they
were dying under native IDE, but after the SATA conversion they ran much
better, but I think that may be getting little too pedantic at this point.
Yousuf Khan
out with different configurations. It's been suggested that I should
test it with different IDE cables, I've now tried 3 different IDE
cables, each one had the same problem with this drive. I then tested
whether it was the motherboard IDE connection that was the problem here,
so I remembered that my eSATA PCI-e adapter also had included its own
IDE connector, so I moved the connection over to that connector. Same
problem here as well, in fact, on this connector it can't even detect
the DVD drive's model name!
So I'm thinking I've done sufficient due diligence and I can declare
this drive dead. The only other thing I could possibly try is to put an
IDE-SATA converter adapter on it, and try to run it through SATA. I've
had success in the past with old IDE hard drives that looked like they
were dying under native IDE, but after the SATA conversion they ran much
better, but I think that may be getting little too pedantic at this point.
Yousuf Khan
Rod Speed
Feb 16, 2012, 12:01:27 AM2/16/12
to
Yousuf Khan wrote:
in a completely different system.
I guess the most likely explaination for the simultaneous write
failure with two separate drives is either just coincidence, or
that you got a spike from the mains or from a faulty power
supply that killed just that function in two separate drives.
> The only other thing I could possibly try is to put an IDE-SATA converter adapter on it, and try to run it through
> SATA. I've had success in the past with old IDE hard drives that looked like they were dying under native IDE, but
> after the SATA conversion they ran much better,
Problem with that approach is that some of the converters
dont support ATAPI very well.
> but I think that may be getting little too pedantic at this point.
I'd personally try the drive in a completely different
system instead if you want to be that pedantic.
> Yousuf Khan wrote:
> Well, here's an update on this problem. I've now had a chance to test
> it out with different configurations. It's been suggested that I should test it with different IDE cables, I've now
> tried 3 different IDE
> cables, each one had the same problem with this drive. I then tested
> whether it was the motherboard IDE connection that was the problem
> here, so I remembered that my eSATA PCI-e adapter also had included
> its own IDE connector, so I moved the connection over to that connector. Same problem here as well, in fact, on this
> connector it can't even detect
> the DVD drive's model name!
> So I'm thinking I've done sufficient due diligence and I can declare this drive dead.
Yes, thats pretty convincing, tho you should really try the drive
> Well, here's an update on this problem. I've now had a chance to test
> it out with different configurations. It's been suggested that I should test it with different IDE cables, I've now
> tried 3 different IDE
> cables, each one had the same problem with this drive. I then tested
> whether it was the motherboard IDE connection that was the problem
> here, so I remembered that my eSATA PCI-e adapter also had included
> its own IDE connector, so I moved the connection over to that connector. Same problem here as well, in fact, on this
> connector it can't even detect
> the DVD drive's model name!
> So I'm thinking I've done sufficient due diligence and I can declare this drive dead.
in a completely different system.
I guess the most likely explaination for the simultaneous write
failure with two separate drives is either just coincidence, or
that you got a spike from the mains or from a faulty power
supply that killed just that function in two separate drives.
> The only other thing I could possibly try is to put an IDE-SATA converter adapter on it, and try to run it through
> SATA. I've had success in the past with old IDE hard drives that looked like they were dying under native IDE, but
> after the SATA conversion they ran much better,
dont support ATAPI very well.
> but I think that may be getting little too pedantic at this point.
system instead if you want to be that pedantic.
0 new messages