User:Mictlantecuhtle/redumpernotes - Revision history

Mictlantecuhtle: /* warning: lead-out ends with unavailable sector */

2023-11-16T14:19:27Z

warning: lead-out ends with unavailable sector

← Older revision		Revision as of 14:19, 16 November 2023
Line 71:		Line 71:
	# Use a trap disc to get more leadout		# Use a trap disc to get more leadout
	# If either solution above is unrealistic		# If either solution above is unrealistic
-	#* If the offset is already at 0, add to the database as is without Track A/AA,	+	#* If the offset is already at 0, add to the database as is without Track A/AA and Universal Hash, and with a note in the comments ("Lead-out contains nonzero data but could not be completely read")
-	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track A/AA and with a note in the comments ("Lead-out contains nonzero data but could not be completely read, used redumper option --force-offset=0"). Do not include Universal Hash in this case.	+	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track A/AA and Universal Hash and with a note in the comments ("Lead-out contains nonzero data but could not be completely read, used redumper option --force-offset=0"). Do not include Universal Hash in this case.

	=== Informational warnings ===		=== Informational warnings ===

Mictlantecuhtle: /* warning: lead-out ends with unavailable sector */

2023-11-15T16:45:45Z

warning: lead-out ends with unavailable sector

← Older revision		Revision as of 16:45, 15 November 2023
Line 72:		Line 72:
	# If either solution above is unrealistic		# If either solution above is unrealistic
	#* If the offset is already at 0, add to the database as is without Track A/AA,		#* If the offset is already at 0, add to the database as is without Track A/AA,
-	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track A/AA and with a note in the comments ("Lead-out contains nonzero data but could not be completely read, used redumper option --force-offset=0")	+	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track A/AA and with a note in the comments ("Lead-out contains nonzero data but could not be completely read, used redumper option --force-offset=0"). Do not include Universal Hash in this case.

	=== Informational warnings ===		=== Informational warnings ===

Mictlantecuhtle: /* warning: lead-in starts with unavailable sector */

2023-11-15T16:45:22Z

warning: lead-in starts with unavailable sector

← Older revision		Revision as of 16:45, 15 November 2023
Line 55:		Line 55:
	'''Process'''		'''Process'''

-	# Confirm which drive was used to dump the disc. If this was an ASUS or Plextor 4824 model, request a dump with another Plextor model. If the dumper does not have another drive available then ~~<span style="background~~:#~~ffff00">discard~~ the ~~submission???<~~/~~span>~~	+	# Confirm which drive was used to dump the disc. If this was an ASUS or Plextor 4824 model, request a dump with another Plextor model. If the dumper does not have another drive available then the disc can be added to the database as follows:
		+	## If anything other than 0 offset, ask the dumper to redump/split with --force-offset=0
		+	## Do not include Track 0 or Universal Hash information
		+	## Add a note that lead-in data is present but could not be captured due to use of a 4824 drive, and that a redump with another drive is required
	# If the disc was dumped with any other compatible Plextor, then request the dumper to redump the disc with the commands --force-offset=0 and --plextor-leadin-skip		# If the disc was dumped with any other compatible Plextor, then request the dumper to redump the disc with the commands --force-offset=0 and --plextor-leadin-skip

Mictlantecuhtle: /* warning: lead-out ends with unavailable sector */

2023-11-04T12:06:32Z

warning: lead-out ends with unavailable sector

← Older revision		Revision as of 12:06, 4 November 2023
Line 69:		Line 69:
	# If either solution above is unrealistic		# If either solution above is unrealistic
	#* If the offset is already at 0, add to the database as is without Track A/AA,		#* If the offset is already at 0, add to the database as is without Track A/AA,
-	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track A/AA and with a note in the comments	+	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track A/AA and with a note in the comments ("Lead-out contains nonzero data but could not be completely read, used redumper option --force-offset=0")

	=== Informational warnings ===		=== Informational warnings ===

Mictlantecuhtle: /* warning: lead-in starts with unavailable sector */

2023-10-06T15:31:28Z

warning: lead-in starts with unavailable sector

← Older revision		Revision as of 15:31, 6 October 2023
Line 56:		Line 56:

	# Confirm which drive was used to dump the disc. If this was an ASUS or Plextor 4824 model, request a dump with another Plextor model. If the dumper does not have another drive available then <span style="background:#ffff00">discard the submission???</span>		# Confirm which drive was used to dump the disc. If this was an ASUS or Plextor 4824 model, request a dump with another Plextor model. If the dumper does not have another drive available then <span style="background:#ffff00">discard the submission???</span>
-	# If the disc was dumped with any other compatible Plextor, ~~follow the steps below~~	+	# If the disc was dumped with any other compatible Plextor, then request the dumper to redump the disc with the commands --force-offset=0 and --plextor-leadin-skip
-	~~#* If the offset is already at 0, add to the database without Track 0 and with a note in the comments~~	+
-	~~#* If the offset is not 0,~~ request the dumper to ~~resplit or~~ redump with ''--force-offset=~~0'', add to the database without Track~~ 0 and ~~with a note in the comments~~	+

	==== warning: lead-out ends with unavailable sector ====		==== warning: lead-out ends with unavailable sector ====

Mictlantecuhtle at 15:22, 6 October 2023

2023-10-06T15:22:26Z

← Older revision		Revision as of 15:22, 6 October 2023
Line 1:		Line 1:
-	~~'''Warning: lead-in starts with unavailable sector'''~~	+	== redumper Warnings and Processes ==
-	~~# We get a dump that shows lead-in starts with unavailable sector. Either:~~	+
-	~~## It's done with ASUS or 4824, request a dump with another Plextor model, revert to (1) once complete~~	+
-	~~## It's done with any other Plextor, follow the steps below~~	+
-	~~# Request the dumper to resplit or redump with the commands ''--force-offset~~=~~0''~~ and ~~''--plextor-leadin-skip''~~	+
-	~~# If that is not possible or doesn't resolve the problem, do X~~	+

		+	redumper logs can contain a range of warnings of interest to moderators. Some of these will always require further action, while others will help to inform moderators of areas of interest or potential concern.

-	~~# If the offset is already at 0, add to the database without Track 0 and with a note in the comments~~	+	=== Warnings requiring further action ===
-	~~# If the offset is not 0, request the dumper to split or redump with ''--force-offset~~=~~0''~~	+

-	~~'''Warning: lead-out ends with unavailable sector'''~~	+	==== "Show stoppers" requiring discard of submission ====

-	~~We are usually able~~ to ~~get ~100 sectors~~ of ~~last session leadout with any good plextor, including 4824~~	+	The following four warnings effectively mean that the drive being used does not support some fundamental feature required for redump purposes. Submissions with these warnings should be discarded and the dumper directed to the [[Optical_Disc_Drive_Compatibility\|List of supported disc drives]]

-	# We get a ~~dump~~ where non zero leadout data exceeds these 100 sectors~~, either~~:	+	# warning: drive doesn't support reading of subchannel data
-	#~~# use~~ RibShark's 3.10 ASUS drive firmware and dump with --overread-leadout option to get more leadout	+	# warning: drive doesn't support C2 Error pointers
-	#~~# use~~ trap disc to get more leadout	+	# warning: unsupported drive read method
-	# If either solution above is unrealistic~~, make sure audio dump~~ is ~~either~~ already at offset 0, ~~otherwise ask~~ dumper ~~split~~ or redump with ''--force-offset=0'' ~~and~~ add ~~as is~~ without Track A/AA	+	# warning: subchannel data is not available, generating TOC index 0 entries
		+
		+	=== Additional action required to check/process ===
		+
		+	==== warning: unable to read CD-TEXT, SCSI ({}) ====
		+
		+	Drive failed to read CD-TEXT, questionable and this shouldn't pop up on compatible drives.
		+
		+	<span style="background:#ffff00">Not sure what the process is here</span>
		+
		+	==== warning: descramble failed (LBA: {} .. {}) ====
		+
		+	An indication of CD-ROM standard deviation and potential mastering issues, including, but not limited to, disc write offset shift
		+
		+	<span style="background:#ffff00">Not sure what the process is here</span>
		+
		+	==== warning: TOC / QTOC mismatch ====
		+
		+	TOC and subchannel desync that might affect track split or CUE-sheet flags and track type, redump.org favors TOC based split but the decision has to be made which variant is preferable for a given disc
		+
		+	<span style="background:#ffff00">Not sure what the process is here</span>
		+
		+	==== warning: incomplete dump detected, using available dump size ====
		+
		+	Dump is incomplete with regard to TOC lead-out entry, safe to ignore for dumps with TOC lead-out entry that spans beyond physical media size, such as unlicensed early [PS2] Datel discs, such discs can be dumped either with --stop-lba=<value> or Ctrl+C redumper interruption and split has to be performed with --iso9660-trim option, this is advanced use and will be covered later
		+
		+	<span style="background:#ffff00">Not sure what the process is here</span>
		+
		+	==== warning: split is performed by QTOC ====
		+
		+	Indicates the use of --force-qtoc option which instructs redumper to perform a subchannel based track split
		+
		+	'''Process'''
		+	# If there has been prior agreement with the dumper to submit on the basis described above then
		+	#* Process and add the dump according to usual rules, otherwise;
		+	# Discuss with the dumper and discard the submission if required
		+
		+	==== warning: lead-in starts with unavailable sector ====
		+
		+	For some discs, it is not always possible to capture all of the lead-in data present, resulting in this error.
		+
		+	'''Process'''
		+
		+	# Confirm which drive was used to dump the disc. If this was an ASUS or Plextor 4824 model, request a dump with another Plextor model. If the dumper does not have another drive available then <span style="background:#ffff00">discard the submission???</span>
		+	# If the disc was dumped with any other compatible Plextor, follow the steps below
		+	#* If the offset is already at 0, add to the database without Track 0 and with a note in the comments
		+	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track 0 and with a note in the comments
		+
		+	==== warning: lead-out ends with unavailable sector ====
		+
		+	We are usually able to get ~100 sectors of last session leadout with any good Plextor, including 4824. In some circumstances, we will get a submission where the non-zero leadout data exceeds these 100 sectors.
		+
		+	'''Process'''
		+
		+	Either:
		+	# Use RibShark's 3.10 ASUS drive firmware and dump with --overread-leadout option to get more leadout
		+	# Use a trap disc to get more leadout
		+	# If either solution above is unrealistic
		+	#* If the offset is already at 0, add to the database as is without Track A/AA,
		+	#* If the offset is not 0, request the dumper to resplit or redump with ''--force-offset=0'', add to the database without Track A/AA and with a note in the comments
		+
		+	=== Informational warnings ===
		+
		+	The following warnings either indicate some useful information about the dump, or can be safely ignored.
		+
		+	==== warning: fake TOC detected, using default 74min disc size ====
		+
		+	Indicates invalid TOC entries, the only known disc that generates such a warning is [PSX] Breaker Pro [http://redump.org/disc/71787/ NTSC] [http://redump.org/disc/72708/ PAL]
		+
		+	==== warning: incomplete pre-gap (session: ..., unavailable: {}/{}) ====
		+
		+	This is an indication that drive didn't manage to get full 2 seconds of pre-gap, at the time of writing, this is expected (<span style="background:#ffff00">in certain circumstances???</span>) and can be ignored, unless either of the lead-in/out warnings above obtain.
		+
		+	==== warning: lead-in contains non-zero data (session: {}, sectors: {}/{}) ====
		+
		+	Informational, guarantees that Track 0 will be generated
		+
		+	==== warning: lead-out contains non-zero data ====
		+
		+	Informational, guarantees that Track A/AA will be generated

Sadikyo at 14:15, 6 October 2023

2023-10-06T14:15:46Z

← Older revision		Revision as of 14:15, 6 October 2023
Line 2:		Line 2:
	# We get a dump that shows lead-in starts with unavailable sector. Either:		# We get a dump that shows lead-in starts with unavailable sector. Either:
	## It's done with ASUS or 4824, request a dump with another Plextor model, revert to (1) once complete		## It's done with ASUS or 4824, request a dump with another Plextor model, revert to (1) once complete
-	## It's done with any other Plextor, ~~move to (2)~~ below	+	## It's done with any other Plextor, follow the steps below
		+	# Request the dumper to resplit or redump with the commands ''--force-offset=0'' and ''--plextor-leadin-skip''
		+	# If that is not possible or doesn't resolve the problem, do X
		+
		+
	# If the offset is already at 0, add to the database without Track 0 and with a note in the comments		# If the offset is already at 0, add to the database without Track 0 and with a note in the comments
	# If the offset is not 0, request the dumper to split or redump with ''--force-offset=0''		# If the offset is not 0, request the dumper to split or redump with ''--force-offset=0''

Mictlantecuhtle: personal notes for future guidance

2023-10-06T13:59:52Z

personal notes for future guidance

New page

'''Warning: lead-in starts with unavailable sector'''
# We get a dump that shows lead-in starts with unavailable sector. Either:
## It's done with ASUS or 4824, request a dump with another Plextor model, revert to (1) once complete
## It's done with any other Plextor, move to (2) below
# If the offset is already at 0, add to the database without Track 0 and with a note in the comments
# If the offset is not 0, request the dumper to split or redump with ''--force-offset=0''

'''Warning: lead-out ends with unavailable sector'''

We are usually able to get ~100 sectors of last session leadout with any good plextor, including 4824

# We get a dump where non zero leadout data exceeds these 100 sectors, either:
## use RibShark's 3.10 ASUS drive firmware and dump with --overread-leadout option to get more leadout
## use trap disc to get more leadout
# If either solution above is unrealistic, make sure audio dump is either already at offset 0, otherwise ask dumper split or redump with ''--force-offset=0'' and add as is without Track A/AA