Jump to content

gmitch64

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by gmitch64

  1. Installed the JMB driver as suggested. The driver installed fine, no errors or warnings from device manager, but it couldn't find any of the drives attached to the controller. Went to the Gigabyte site and downloaded the latest driver for the GIGABYTE SATA2 Driver (V1.17.50.2, dated 2008/09/29). It also installed fine, and I am able to see the drives. It shows up as a GIGABYTE GBB36X Controller, and installs a driver from JMicron Technology Corp (hmmm... lol). Anyways, I have burned a couple of BluRays, and successfully verified them, so it looks like it is working fine now. I'm not sure why the original Microsoft drivers were having issues with the BluRay drive, and not with the DVD ones, but we're up and running now. Thanks very much for your help. G
  2. Yeah, I have one of them on my SAN box in the basement I'm using for my VM cluster. I have a couple of those spare. I'm using them on 2 main media servers - with port multipliers, so I can get all 20 disk spinning on them. I have 2 or 3 Gigabyte boards with the jmicron on it working fine - but mainly for disks, rather than DVSs. I'll have a go at getting the driver done later today. If that makes no difference, then I'll put in one of the SiL cards and see where we go from there. G
  3. Yeah, I am out of ports on the mobo... 6 on the ICH10, 2 used for boot, 4 for RAID5. I'll try the driver in the morning and see if it makes a differece. If not, I can probably steal a 2 port SATA PCIe card from another box for a bit and do some tests. G
  4. Motherboard is a Gigabyte EP45-UD3R with the F12 BIOS. The BD Writer is connected to the 'Gigabyte SATA 2 chip' on the motherboard (which I believe is a rebranded JMicron device). Both my DVD burner and BD burner are connected to this via SATA. The HD-DVD drive is connected to the same chip via PATA (it's a PATA drive). Windows updates are up to date as far as this evening. Windows is showing the devices to be connected to a standard AHCI 1.0 Serial ATA Controller (BD on channel 0, DVD on channel 1). There are no third party drivers installed. G
  5. Sorry.. Posted file info instead of uploading it. Here's the upload. G ImgBurnF8.log
  6. Yup, with every one - I've not had a good verify on one yet. I've got some more stuff I need to burn off, so will post the log once I'm done. G
  7. And write mode info for a blank disk HL-DT-ST BD-RE WH10LS30 1.00 (SATA) Current Profile: BD-R Disc Information: Status: Empty State of Last Session: Empty Erasable: No Supported Write Speeds: 2x, 4x, 6x, 8x BD Disc Information: Disc ID: PHILIP-R04-00 Disc Type: BD-R Disc Size: 120mm Disc Class: 0 Disc Version: 1 Number of Layers: 1 Layer Type: Writable DVD Layer Present: No CD Layer Present: No Channel Bit Length: 74.5nm (25GB Per Layer) Push-Pull Polarity: Positive Recorded Mark Polarity: HTL BCA Present: Yes Maximum Transfer Rate: Not Specified Last User Data PSN for Disc: 0 First PAA of Data Zone: 131,072 Last PAA of Data Zone: 1,658,494 Performance (Write Speed): Descriptor 1... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 8,991 KB/s (2x) Descriptor 2... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 17,982 KB/s (4x) Descriptor 3... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 26,973 KB/s (6x) Descriptor 4... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 35,964 KB/s (8x)
  8. Read Mode info as requested for burned disk (which failed verify) HL-DT-ST BD-RE WH10LS30 1.00 (SATA) Current Profile: BD-R Disc Information: Status: Complete State of Last Session: Complete Erasable: No Sessions: 1 Sectors: 11,915,552 Size: 24,403,050,496 bytes Time: 2647:56:02 (MM:SS:FF) TOC Information: Session 1... (LBA: 0) -> Track 01 (Mode 1, LBA: 0 - 11915551) -> LeadOut (LBA: 11915552) BD Disc Information: Disc ID: PHILIP-R04-00 Disc Type: BD-R Disc Size: 120mm Disc Class: 0 Disc Version: 1 Number of Layers: 1 Layer Type: Writable DVD Layer Present: No CD Layer Present: No Channel Bit Length: 74.5nm (25GB Per Layer) Push-Pull Polarity: Positive Recorded Mark Polarity: HTL BCA Present: Yes Maximum Transfer Rate: Not Specified Last User Data PSN for Disc: 0 First PAA of Data Zone: 131,072 Last PAA of Data Zone: 1,658,494
  9. I've been having issues since I installed my BD burner a couple of weeks ago. DVDs burn fine on my other DVD drives, and on the BD burner too, but when I burn a BluRay data disk, the burn seems to go without error, but I always get the Verify Failed! - Reason: Layouts do not match When the verify process runs. From what I csn tell, the data on the disk is fine, and can be read, but how do I get the verify process to complete? I'm currently using 2.5.2.0 (had the same issue on 2.5.1.0 too). Is there some setting I need to change somewhere? I 08:20:28 ImgBurn Version 2.5.2.0 started! I 08:20:28 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 08:20:28 Total Physical Memory: 8,387,032 KB - Available: 3,370,588 KB I 08:20:29 Initialising SPTI... I 08:20:29 Searching for SCSI / ATAPI devices... I 08:20:29 -> Drive 1 - Info: HL-DT-ST BD-RE WH10LS30 1.00 (S:) (SATA) I 08:20:29 -> Drive 2 - Info: HL-DT-ST DVDRAM GH20NS15 IL00 (T:) (SATA) I 08:20:29 -> Drive 3 - Info: TOSHIBA DVD/HD SD-H802A HP10 (U:) (ATA) I 08:20:29 -> Drive 4 - Info: MATSHITA DVD-RAM SW-9584 B104 (D:) (1394) I 08:20:29 -> Drive 5 - Info: MagicISO Virtual DVD-ROM 1.0A (E:) (Unknown) I 08:20:29 Found 1 DVD-ROM, 2 DVD±RW/RAMs, 1 BD-RE and 1 HD DVD-ROM! <snipped adding files to image> I 08:38:42 Calculating Totals... I 08:38:43 Preparing Image... I 08:38:43 Contents: 119 Files, 6 Folders I 08:38:43 Content Type: Data I 08:38:43 Data Type: MODE1/2048 I 08:38:43 File System(s): UDF (2.00) I 08:38:43 Volume Label: 0618 I 08:38:43 Size: 24,401,999,292 bytes I 08:38:43 Sectors: 11,915,129 I 08:38:43 Image Size: 24,403,050,496 bytes I 08:38:43 Image Sectors: 11,915,552 I 08:38:43 Operation Successfully Completed! - Duration: 00:00:06 I 08:38:43 Operation Started! I 08:38:43 Source File: -==/\/[bUILD IMAGE]\/\==- I 08:38:43 Source File Sectors: 11,915,552 (MODE1/2048) I 08:38:43 Source File Size: 24,403,050,496 bytes I 08:38:43 Source File Volume Identifier: 0618 I 08:38:43 Source File Application Identifier: ImgBurn v2.5.2.0 I 08:38:43 Source File Implementation Identifier: ImgBurn I 08:38:43 Source File File System(s): UDF (2.00) I 08:38:43 Destination Device: [4:0:0] HL-DT-ST BD-RE WH10LS30 1.00 (S:) (SATA) I 08:38:43 Destination Media Type: BD-R (Disc ID: PHILIP-R04-00) (Speeds: 2x, 4x, 6x, 8x) I 08:38:43 Write Mode: BD I 08:38:43 Write Type: DAO I 08:38:43 Write Speed: 4x I 08:38:43 BD-R Verify Not Required: Yes I 08:38:43 Link Size: Auto I 08:38:43 Lock Volume: Yes I 08:38:43 Test Mode: No I 08:38:43 OPC: No I 08:38:43 BURN-Proof: Enabled I 08:38:43 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 08:39:01 Filling Buffer... (128 MB) I 08:39:04 Writing LeadIn... I 08:39:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 11915551) I 08:39:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11915551) I 09:01:48 Synchronising Cache... I 09:01:52 Closing Track... I 09:01:53 Finalising Disc... I 09:02:04 Exporting Graph Data... I 09:02:04 Graph Data File: C:\Users\gmitch\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH10LS30_1.00_THURSDAY-NOVEMBER-04-2010_8-38_AM_PHILIP-R04-00_4x.ibg I 09:02:04 Export Successfully Completed! I 09:02:04 Operation Successfully Completed! - Duration: 00:23:21 I 09:02:04 Average Write Rate: 17,497 KB/s (3.9x) - Maximum Write Rate: 18,091 KB/s (4.0x) I 09:02:04 Cycling Tray before Verify... W 09:02:14 Waiting for device to become ready... I 09:02:26 Device Ready! E 09:02:26 Verify Failed! - Reason: Layouts do not match. I 09:11:44 Close Request Acknowledged I 09:11:45 Closing Down... I 09:11:45 Shutting down SPTI... I 09:11:45 ImgBurn closed!
×
×
  • Create New...

Important Information

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