http://redump.org/disc/109294/
I can now dump complete leadout with a new BW-16D1HT Asus drive and ribshark's firmware. I'll be revisiting all my discs with known incomplete leadout (about 12), should be able to provide universal hash for many. I'll open a separate thread for each, as requested.
My procedure is to do the dump --overread-leadout with the Asus and, then refine with a Plextor PX-760A to get the complete leadin (as these discs tend to overflow on both ends). I can then get a complete universal hash with split hash. I repeat the procedure to ensure the leadout is correct, and also check that the leadin and tracks match the earlier Plextor dump (as currently in redump.)
On this disc I had to redo the Asus dump a few times to get enough of the leadout to capture all the non-zero data, about half the time it would stop early, thus why there are 6 sets of logs; 2 and 6 went all the way to 5491 sectors. After a few incomplete dumps, dump 5 is when I tried --lba-start for the sake of getting to the leadout faster, then refining on the Plextor to get most of the rest, but I decided to try the whole disc again for dump 6.
New info is:
<b>Universal Hash (SHA-1): 5ce7f67ac6b38bba89a70dca3e4f6e30f55201e0</b>
<xmp><rom name="leadout.bin" size="2509584" crc="a05362f9" md5="d4482f06e37629b566760ddff325a48d" sha1="fad120bb5bde25b9e0382482ce2a10e8c7ab49ea" /></xmp>Relevant log chunk:
non-zero TOC sample range: [ -88200 .. +93601956]
non-zero data sample range: [ -323544 .. +94228983]
Universal Hash (SHA-1): 5ce7f67ac6b38bba89a70dca3e4f6e30f55201e0
fallback offset 0 applied
disc write offset: +0
warning: lead-in contains non-zero data (session: 1, sectors: 551/551)
warning: lead-out contains non-zero data (session: 1, sectors: 1067/5491)