Tweet
I have a couple of severely damaged discs that take a very very long time to rip. After about an hour using the above releases to rip them (and other discs) in ultrasecure mode using four plextor 24/10/40A models on a firewire chain, something goes haywire. The symptoms are:
- anything that requires showing the top level drive letters hangs (e.g. my computer).
- i can choose to save files (e.g. from notepad), and the save as dialog opens up...but as soon as I hit save, it freezes.
- I can't launch most programs.
That seems to point to anything that tries to "stat" the optical drives gets stuck there.
Ejecting the problem discs doesn't help (at least, nothing useful 30 minutes after the ejct). It's not possible to get the Safely Remove Hardware dialog box to show up. The only solution is to pull the firewire cable...after a minute the system starts operating normally. After that:
1. Connecting the firewire cable back up showed two of the four plextor drives as working, and two as unresponsive.
2. Pulling the cable again, powering down the four drives, powering them up and reconnecting the cable, all four become operational.
So, it's pretty clear that at some point the plextor drives go a bit loopy trying to rip severely damaged discs.
More info:
The messages in the system event log are all the same:
They start appearing every minute or two early in the rip of the damaged discs...and by the time the system is really problematic, they are happening every few seconds, as the drives have gone off into lala land.
Is this something the the dbpa ripper could notice and try to work around? Are there reset commands it could send the drive when things start acting up? Could dbpa notice and ask the operator to power cycle the drive?
-brendan
- anything that requires showing the top level drive letters hangs (e.g. my computer).
- i can choose to save files (e.g. from notepad), and the save as dialog opens up...but as soon as I hit save, it freezes.
- I can't launch most programs.
That seems to point to anything that tries to "stat" the optical drives gets stuck there.
Ejecting the problem discs doesn't help (at least, nothing useful 30 minutes after the ejct). It's not possible to get the Safely Remove Hardware dialog box to show up. The only solution is to pull the firewire cable...after a minute the system starts operating normally. After that:
1. Connecting the firewire cable back up showed two of the four plextor drives as working, and two as unresponsive.
2. Pulling the cable again, powering down the four drives, powering them up and reconnecting the cable, all four become operational.
So, it's pretty clear that at some point the plextor drives go a bit loopy trying to rip severely damaged discs.
More info:
The messages in the system event log are all the same:
Code:
Source: sbp2port Evenit ID: 9 Description: The device, , did not respond within the timeout period.
Is this something the the dbpa ripper could notice and try to work around? Are there reset commands it could send the drive when things start acting up? Could dbpa notice and ask the operator to power cycle the drive?
-brendan
Comment