Jump to content

Lost a Drive - Searching for SCSI / ATAPI devices... - Device Removal Detected!


Recommended Posts

Posted

We have on a ASUS P6TD Deluxe (with Windows 7 64x) a new ASUS U3S6 - Controler with USB3.0 & SATA 6G. And a Plextor PX-880SA (SATA) internal DVD-Rewriter joined to this controler.

 

Windows and also Nero find the new Plextor-DVD-Writer as Drive R. Nero can read and write to the Plextor PX-880SA!

 

But ImgBurn hangs by the first start 10 or 11 minutes here:

 

I 09:56:31 ImgBurn Version 2.5.1.0 started!

I 09:56:31 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600)

I 09:56:31 Total Physical Memory: 6.282.344 KB - Available: 4.707.008 KB

I 09:56:31 Initialising SPTI...

I 09:56:31 Searching for SCSI / ATAPI devices...

I 09:56:31 -> Drive 1 - Info: HL-DT-ST DVD-RAM GH22LP20 2.00 (S:) (ATA)

.........

 

 

After 11 minutes we have this log:

 

I 10:15:58 ImgBurn Version 2.5.1.0 started!

I 10:15:59 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600)

I 10:15:59 Total Physical Memory: 6.282.344 KB - Available: 4.241.948 KB

I 10:15:59 Initialising SPTI...

I 10:15:59 Searching for SCSI / ATAPI devices...

I 10:15:59 -> Drive 1 - Info: HL-DT-ST DVD-RAM GH22LP20 2.00 (S:) (ATA)

I 10:26:01 -> Drive 2 - Info: PLEXTOR DVDR PX-880SA 1.12 (R:) (SATA)

I 10:26:01 -> Drive 3 - Info: VXDV BD-HD-DVDRAM S15 10.0 (T:) (SCSI)

I 10:26:01 -> Drive 4 - Info: VXDV BD-HD-DVDROM S10 10.0 (U:) (SCSI)

I 10:26:01 -> Drive 5 - Info: VXDV BD-HD-DVDROM S10 10.0 (W:) (SCSI)

I 10:26:01 -> Drive 6 - Info: VXDV BD-HD-DVDROM S10 10.0 (V:) (SCSI)

I 10:26:01 -> Drive 7 - Info: HL-DT-ST DVD-RAM GSA-E60L 1.00 (I:) (USB)

I 10:26:01 Found 3 DVD±RW/RAMs, 3 BD-ROMs and 1 BD-RE!

W 10:26:01 Device Removal Detected!

I 10:26:01 Searching for SCSI / ATAPI devices...

I 10:26:01 -> Drive 1 - Info: HL-DT-ST DVD-RAM GH22LP20 2.00 (S:) (ATA)

I 10:26:01 -> Drive 2 - Info: VXDV BD-HD-DVDRAM S15 10.0 (T:) (SCSI)

I 10:26:01 -> Drive 3 - Info: VXDV BD-HD-DVDROM S10 10.0 (U:) (SCSI)

I 10:26:02 -> Drive 4 - Info: VXDV BD-HD-DVDROM S10 10.0 (W:) (SCSI)

I 10:26:02 -> Drive 5 - Info: VXDV BD-HD-DVDROM S10 10.0 (V:) (SCSI)

I 10:26:02 -> Drive 6 - Info: HL-DT-ST DVD-RAM GSA-E60L 1.00 (I:) (USB)

I 10:26:02 Found 2 DVD±RW/RAMs, 3 BD-ROMs and 1 BD-RE!

 

 

At I 10:26:01 we see -> Drive 2 - Info: PLEXTOR DVDR PX-880SA 1.12 (R:) (SATA) but in the next step ImgBurn till our Plextor complete. There is no more drive R under Windows 7! And we must make a reboot to use the Plextor.

 

Any ideas?

 

Stefan

Posted
W 10:26:01 Device Removal Detected!

 

Something is going on with the connection between the drive and controller.

 

Could be a loose connecton data cable or not enough power to drive to function correctly

 

Make sure you have the latest drivers for the controller and the power supply can cope with your configuration.

 

You could try to switch things arround.

Posted
W 10:26:01 Device Removal Detected!

 

Something is going on with the connection between the drive and controller.

 

Could be a loose connecton data cable or not enough power to drive to function correctly

 

Make sure you have the latest drivers for the controller and the power supply can cope with your configuration.

 

You could try to switch things arround.

 

I have the newest driver! The data cable is OK and Nero works very fine with the Plextor. And I can also stream a DVD-Video with Cyberlink from the Plextor. In the meantime I have tested it with Roxio WinOnCD. And it is also right. I can burn a DVD without any problems. Only ImgBurn has a problem.

 

I have changed the Plextor-SATA-connection from the ASUS U3S6 - Controller to a SATA-connector on the Mainboard (ASUS P6TD Deluxe) [and the HD-boot-partition from the mainboard to the U3S6 - Controller] and now it works with ImgBurn.

 

Imgburn (and only ImgBurn !!) has a problem with the ASUS U3S6 - Controller!

 

Stefan

Posted

What you have to do here is start the program up in I/O debug mode (read the FAQ) and see which command your drive/controller is hanging on.

 

ImgBurn issues exactly the same commands all the time (the controller is irrelevant), so it's not ImgBurn that has the issue, it's just the only one running into the problem with your system as a whole.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.