Jump to content

reserve track ... hangs imgburn and thus system need cold restart


tlochner

Recommended Posts

hi, never had problem before.

using imgburn to burn bd-r file is 13,042,450,432 bytes

small for a bd-r burn.

 

have made 2 .iso images tested them with mounting and powerdvd. they both work fine.

but when trying to burn with imgburn, it says reserving track and hangs.

to get burner back, must cold restart system, in others word shut down, restart.

other image files/ movies burn no problem.

the disk that hangs is never written to so you can use for the next image file/movie.

i have tried multiple disk, and multiple images.

imgburn just won't burn this one movie. i think maybe because it is a small file, just guessing.

 

i have burned hundreds of disks with no problems. system is stable no added programs lately, except some auto updates.

chrome, java, etc.window updates are off. 

 

running win 7 sp1 (exact) no updates, imgburn 2.5.6.0, using verbatim bd-r.

 

any ideas??  i think you have a real bug.

 

tony

 

btw no log file gets created, but i made it, this is what it says.

Edited by tlochner
Link to comment
Share on other sites

Can't be the size.  Earlier today, I burned a between 6 and 7 GB image file to a BD-R fine.

 

 

So, you say you've done other Blu-Ray movie image files to BD-R fine?  If it does this always on the one image file, regardless of the type of BD-R you use, then it must be the image file has a problem in it somewhere.  Other image files burn fine.

 

 

Without another drive to test it on, you can't rule out if it's the drive that's doing it.  Well, the drive is causing the problem, but what causes the drive to do this is the issue.  If your drive hangs and you have to cold boot the system, the drive is becoming unresponsive.  Why is the issue.

 

 

LUK will probably have to help you here.  Will probably tell you to turn on advanced logging, etc.

 

 

Also, try updating ImgBurn to 2.5.8.0.  You're using at least a 2 year out of date version of the software as 2.5.8.0 was released 2 years ago.  See if that helps.

Link to comment
Share on other sites

ok, tried a different system. win7 with 2.5.8.0

same exact image file across shared network.

hangs ... kill in win task manager.

still active in task manager even though your program window disappears.

that is why cold boot is necessary.

 

whoo ... 

now,   ...  you took down the main server. yes reboot.

 

ok. 2.5.8.0 is no different

reserve track ... hangs ... other image files, no problem.

what is going on????

i'm an engineer.

i can isolate problems pretty well.

seem like imgburn or this image file has a problem.

how can an image file file that is mountable and playable have an issue?

never seen one.

 

of course after 1600 disks with your 2.5.6.0, never seen anything like this before either.

what do you want me to do? 

let's fix this.

tony

Link to comment
Share on other sites

Could be any number of problems with the image itself.

 

 

Try isolating if it's the image file at fault.  You say it's a Blu-Ray movie image file right?  Try mounting the image and then drag and drop the virtual drive contents into a Build job.  Build should detect it's Blu-Ray video contents and set the appropriate settings for it.  Build a new image and try burning that.  See if you get the same results.

Link to comment
Share on other sites

ok new info. 

tried burnaware software. a competitor.

it hung too.

what in an image could cause it to stop and reserve tracks?

i tried generating an image that was cut in the beginning, same thing.

 

it plays fine even in powerdvd15 with just dropping it on the icon,

or powerdvd11 mounted first.

it appears fine, can tsmuxer it fine. resulting files always hang.

 

completely lost?

any ideas?

 

tony

Link to comment
Share on other sites

Reserve track is a single command sent to the drive with the size it needs to reserve. Basically, it's foolproof from a software point of view.

You must be running into a bug in the drives firmware or your system as a whole.

 

Commands should complete successfully or error out, not just get stuck and make the program look like it has hung.

Link to comment
Share on other sites

is the Reserve track command necessary on a bd-r?

 

btw, i tried other systems, so the drivers might be different, and the bluray drive is different and it still hangs.

no solution so far.

yes, i have ripped apart the tracks, video, audio, and subs, and rebuilt bluray image,

that hangs too.

 

so far anything to do with this movie/iso's/modified isos/shortened isos/ all hang, on multiple systems,

with different bluray writers, and even with other burning software too.

 

i think i have burned disks with about 12g before, they had no issues of course, but they are rare, mostly 18-24gigs on a bd-r.

 

the only thing left for me to try is to reencode the video, and leave the audio untouched.

unless you have some ideas?????

 

tony

Link to comment
Share on other sites

Which drives have you tried it with? Specific model numbers and firmware versions please.

 

In fact, it's probably better if you just copy + paste everything from the log window at the point where the reserve track command is issued and never completes.

 

It's definitely nothing to do with the image itself... or rather its content. The command purely sends a size (number of sectors).

 

In theory, it would also get stuck if you used Discovery mode and set the size to the same value as the size of the image. Discovery mode just burns zeros.

Link to comment
Share on other sites

ok, been busy, ran avchd, took 6hrs,

regenerated a new image, video processed, audio untouched, subs untouched, chapters untouched.

it works, or it is burning now, no hangs.

this is the log so far, it shows the drive / firmware etc.

 

I 00:05:55 ImgBurn Version 2.5.6.0 started!
I 00:05:55 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 00:05:55 Total Physical Memory: 16,657,560 KB  -  Available: 14,064,304 KB
W 00:05:55 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.
I 00:05:55 Initialising SPTI...
I 00:05:55 Searching for SCSI / ATAPI devices...
I 00:05:55 -> Drive 1 - Info: PIONEER BD-RW   BDR-207D 1.21 (N:) (SATA)
I 00:05:56 -> Drive 2 - Info: TSSTcorp CDDVDW SH-S223C SB06 (O:) (SATA)
I 00:05:56 -> Drive 3 - Info: Alcohol Drive 3.5Z (R:) (SCSI)
I 00:05:56 -> Drive 4 - Info: Alcohol Drive 3.5Z (S:) (SCSI)
I 00:05:56 -> Drive 5 - Info: DVDFab Virtual Drive 1.1 (Q:) (SCSI)
I 00:05:56 -> Drive 6 - Info: DVDFab Virtual Drive 1.1 (P:) (SCSI)
I 00:05:56 Found 1 DVD±RW/RAM, 2 BD-ROMs, 2 BD-ROM/HD DVD-ROMs and 1 BD-RE!
I 00:06:05 Operation Started!
I 00:06:05 Source File: F:\All Videos\Ready To Burn\new Ice Age (2002) (BD25).iso
I 00:06:05 Source File Sectors: 12,027,616 (MODE1/2048)
I 00:06:05 Source File Size: 24,632,557,568 bytes
I 00:06:05 Source File Volume Identifier: Ice Age (2002)
I 00:06:05 Source File Volume Set Identifier: 4741BEB600B78663
I 00:06:05 Source File Application Identifier: ImgBurn v2.5.8.0
I 00:06:05 Source File Implementation Identifier: ImgBurn
I 00:06:05 Source File File System(s): UDF (2.50)
I 00:06:05 Destination Device: [2:0:0] PIONEER BD-RW   BDR-207D 1.21 (N:) (SATA)
I 00:06:05 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000)
I 00:06:05 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x
I 00:06:05 Destination Media Sectors: 12,219,392
I 00:06:05 Write Mode: BD
I 00:06:05 Write Type: DAO
I 00:06:05 Write Speed: 4x
I 00:06:05 BD-R Verify Not Required: Yes
I 00:06:05 Link Size: Auto
I 00:06:05 Lock Volume: Yes
I 00:06:05 Test Mode: No
I 00:06:05 OPC: No
I 00:06:05 BURN-Proof: Enabled
I 00:06:05 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x)
I 00:06:05 Advanced Settings - Optimal Writing Speed: No
I 00:06:05 Filling Buffer... (40 MB)
I 00:06:07 Writing LeadIn...
 
i don't know where it dies, when it hangs, but i'd rather not hang it up. the system needs cold restart to get drive back.
i still to take down this server to get it back.
that's next.
 
thoughts?
Edited by tlochner
Link to comment
Share on other sites

similar

Drive 1 - Info: PIONEER BD-RW   BDR-206D 1.56-ID61 (N:) (SATA)

 

btw, i forgot to mention that i create the iso image using imgburn, even the one that locks up.

i load bluray files and create iso image first. that works. that's is the image i try to burn.

in looking at the log(s), i think this is it ... for the creation of the image

 

; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Wednesday, 30 September 2015, 22:14:32
; \\****************************************//
;
;
I 22:12:18 ImgBurn Version 2.5.8.0 started!
I 22:12:18 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 22:12:18 Total Physical Memory: 16,679,244 KiB  -  Available: 13,651,036 KiB
W 22:12:18 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.
I 22:12:18 Initialising SPTI...
I 22:12:18 Searching for SCSI / ATAPI devices...
I 22:12:19 -> Drive 1 - Info: PIONEER BD-RW   BDR-206D 1.56-ID61 (N:) (SATA)
I 22:12:19 -> Drive 2 - Info: TSSTcorp CDDVDW SH-S223C SB06 (O:) (SATA)
I 22:12:19 -> Drive 3 - Info: Alcohol Drive 3.5Z (R:) (SCSI)
I 22:12:19 -> Drive 4 - Info: Alcohol Drive 3.5Z (S:) (SCSI)
I 22:12:19 -> Drive 5 - Info: Alcohol Drive 3.5Z (T:) (SCSI)
I 22:12:19 -> Drive 6 - Info: DVDFab Virtual Drive 1.1 (P:) (SCSI)
I 22:12:19 -> Drive 7 - Info: DVDFab Virtual Drive 1.1 (Q:) (SCSI)
I 22:12:19 Found 1 DVD±RW/RAM, 3 BD-ROMs, 2 BD-ROM/HD DVD-ROMs and 1 BD-RE!
I 22:12:37 Operation Started!
I 22:12:37 Building Image Tree...
W 22:12:37 Skipped Hidden File: L:\Video_FV1\2nd Level Processing\temp\BDMV\META\DL\Thumbs.db
I 22:12:37 Calculating Totals...
I 22:12:37 Preparing Image...
I 22:12:37 Contents: 12 Files, 16 Folders
I 22:12:37 Content Type: BD Video
I 22:12:37 Data Type: MODE1/2048
I 22:12:37 File System(s): UDF (2.50)
I 22:12:37 Volume Label: Ice Age (2002)
I 22:12:37 Size: 13,040,914,487 bytes
I 22:12:37 Sectors: 6,367,642
I 22:12:37 Image Size: 13,041,926,144 bytes
I 22:12:37 Image Sectors: 6,368,128
I 22:12:37 Operation Successfully Completed! - Duration: 00:00:00
I 22:12:38 Operation Started!
I 22:12:38 Building Image Tree...
W 22:12:39 Skipped Hidden File: L:\Video_FV1\2nd Level Processing\temp\BDMV\META\DL\Thumbs.db
I 22:12:39 Calculating Totals...
I 22:12:39 Preparing Image...
I 22:12:39 Contents: 12 Files, 16 Folders
I 22:12:39 Content Type: BD Video
I 22:12:39 Data Type: MODE1/2048
I 22:12:39 File System(s): UDF (2.50)
I 22:12:39 Volume Label: Ice Age (2002)
I 22:12:39 Size: 13,040,914,487 bytes
I 22:12:39 Sectors: 6,367,642
I 22:12:39 Image Size: 13,041,926,144 bytes
I 22:12:39 Image Sectors: 6,368,128
I 22:12:40 Operation Successfully Completed! - Duration: 00:00:01
I 22:12:40 Operation Started!
I 22:12:40 Image Contents: 12 Files, 16 Folders
I 22:12:40 Image Sectors: 6,368,128 (MODE1/2048)
I 22:12:40 Image Size: 13,041,926,144 bytes
I 22:12:40 Image Volume Identifier: Ice Age (2002)
I 22:12:40 Image Volume Set Identifier: 473EB19300612B1A
I 22:12:40 Image Application Identifier: ImgBurn v2.5.8.0
I 22:12:40 Image Implementation Identifier: ImgBurn
I 22:12:40 Image File System(s): UDF (2.50)
I 22:12:40 Destination File: J:\Video_BD1\Ready To Burn\Ice Age (2002) (BD25).iso
I 22:12:40 Destination Free Space: 762,291,503,104 Bytes (744,425,296.00 KiB) (726,977.83 MiB) (709.94 GiB)
I 22:12:40 Destination File System: NTFS
I 22:12:40 File Splitting: Auto
I 22:12:40 Writing Image...
I 22:13:58 Operation Successfully Completed! - Duration: 00:01:17
I 22:13:58 Average Write Rate: 165,405 KiB/s (37.7x) - Maximum Write Rate: 275,427 KiB/s (62.7x)
I 22:14:32 Close Request Acknowledged
I 22:14:32 Closing Down...
I 22:14:32 Shutting down SPTI...
I 22:14:32 ImgBurn closed!
 
--------
i think this is the log, when it is attempting to burn, when it hangs
 
; //****************************************\\
;   ImgBurn Version 2.5.8.0 - Log
;   Wednesday, 30 September 2015, 22:14:44
; \\****************************************//
;
;
I 22:14:35 ImgBurn Version 2.5.8.0 started!
I 22:14:35 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 22:14:35 Total Physical Memory: 16,679,244 KiB  -  Available: 13,917,320 KiB
W 22:14:35 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.
I 22:14:35 Initialising SPTI...
I 22:14:35 Searching for SCSI / ATAPI devices...
I 22:14:35 -> Drive 1 - Info: PIONEER BD-RW   BDR-206D 1.56-ID61 (N:) (SATA)
I 22:14:36 -> Drive 2 - Info: TSSTcorp CDDVDW SH-S223C SB06 (O:) (SATA)
I 22:14:36 -> Drive 3 - Info: Alcohol Drive 3.5Z (R:) (SCSI)
I 22:14:36 -> Drive 4 - Info: Alcohol Drive 3.5Z (S:) (SCSI)
I 22:14:36 -> Drive 5 - Info: Alcohol Drive 3.5Z (T:) (SCSI)
I 22:14:36 -> Drive 6 - Info: DVDFab Virtual Drive 1.1 (P:) (SCSI)
I 22:14:36 -> Drive 7 - Info: DVDFab Virtual Drive 1.1 (Q:) (SCSI)
I 22:14:36 Found 1 DVD±RW/RAM, 3 BD-ROMs, 2 BD-ROM/HD DVD-ROMs and 1 BD-RE!
I 22:14:44 Close Request Acknowledged
I 22:14:44 Closing Down...
I 22:14:44 Shutting down SPTI...
I 22:14:44 ImgBurn closed!
;
 
i think it closes ImgBurn when i kill it after it hangs, not sure, maybe it write no log at all when it hangs and this something else i did.
it doesn't give any meaningful log info ... it just says reserving track in lower left hand corner while imgburn window is up.
Edited by tlochner
Link to comment
Share on other sites

i personally think there is something in the setting pages that is causing this.

so i write the image, maybe it is not written correctly, but other programs can still mount and powerdvd can still play.

or maybe it is written correctly but the burning setting are wrong. (less likely)

Link to comment
Share on other sites

the kids watched the avchd version today. it is ok. 24.5g

if i get another disk problem like this, then i will update firmware.

right now everything is good. 1 hang in a 1000 with a workaround tolerable.

 

the reason i said that it could be settings is that maybe it's not being set in the .iso

as a bd or something when it is 12-13g.

maybe powerdvd doesn't care, but burning that .iso does care.

 

maybe your right a small bd .iso is making the burner with old firmware hang.

i will shy away from 12g bds.

 

thanks for your help.

Link to comment
Share on other sites

It's nothing to do with what's in the image or how it was made.

 

It's purely a size thing. You take the size of the file in bytes, convert it to a numbers of sectors and ask the drive to reserve a track of that size.

 

You should update the firmware regardless of this issue. They release them to fix problems and improve burn quality.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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