[SOLVED] Lsdvd on Remastered CD Issue

[mellowmaroon]

I have Tiny Core Plus on a frugal install in a VM, and compiled libdvdcss, libdvdread, and lsdvd, to where "lsdvd" worked without problems on the VM installation.

I then ran the ezremaster program (supplying the Core iso instead of Core Plus), and included the three tcz files I created from the respective sources.

However, upon testing the CD in a couple computers (that is, running "lsdvd" from after replacing the live CD with a DVD), I seem to keep getting errors looking like:

end_request: I/O error, dev sr0, sector 401304
Buffer I/O error on device sr0, logical block 100326

followed by the normal "lsdvd" output.  Some Google research led me to believe that an unset region might be to blame, but then I don't understand why it was working without issue on my HD.  Mounting "/mnt/sr0" didn't affect it either, but it did speed the whole process up.

Additionally, when I try to operate on the dvd with handbrake from the live CD, it complains about being unable to crack the CSS, in contrast to the VM's frugal install where things were working as expected.  Is there something in Core Plus I should be including in my disc remaster that is causing this behavior?

Apologies in advance if this is under the wrong section, it didn't seem like a bug more than a misconfiguration on my part.

EDIT: I can't seem to get that output inside the code tags without it flagging me for linking externally, so I bolded it.

[curaga]

Those are almost always hardware errors, and I can't think of anything remastering extensions could have done to change that.

So your remaster is likely working well, but on the downside you should check the drive and cable. If it works fine in your host OS (Windows?), it's possible there's a kernel bug.


edit: Of course your remaster method should be one that allows for removing the disc.

[mellowmaroon]

Yes, the disc drive works fine under my Windows Host OS and within the Tiny Core VM (to the point where the errors I was getting were never seen until I tested the remaster).  So I believe problems with the drive can be ruled out.

Sorry for poorly clarifying in my original post, but I have attempted testing the remaster on 2 VM's and the physical laptop I was working on using a burned cd.

The first machine had no hard drive, and one virtual IDE connection going to the remaster at first which I would switch for the dvd (the host disc drive). Thinking the IDE connection sharing might be throwing things, i had the two discs going on seperate IDE connections to the VM, with no luck.

My next test was loading it from the Tiny Core VM, to rule out the hardware environment as the issue.  Sure enough, no luck.  So I burned it to a CD to make sure it wasn't a VirtualBox quirk I was experiencing, with no sucess.

Now, when you say I should make sure to remaster with a method that allows disc removal, is there anything special I should be doing in that regard? The TC website said it always runs in memory, which made me think that the disc-swapping wasn't an issue.  Additionally, the test with two IDE virtual drives gave me the same results.

My suspicion lies with libdvdcss, since libdvdread and lsdvd seem to be working ok, and the handbrake output mentioned a CSS error.

I will test the remaster with a TinyPlus iso and the installed VM's environment to see if there is something in Core that is missing, or if my installed environment has something being excluded.

[Rich]

Hi mellowmaroon

The TC website said it always runs in memory

The TC file system is by default in RAM. Any extensions, however, are loop mounted by default, which means
you can't remove the CD. To make your extensions reside in RAM instead, add a file called  copy2fs.lst  to
your  tce  directory. Place the names of all of your extensions in that file, one per line, including the  .tcz  part
of the name.

[gerald_clark]

Or use a copy2fs.flg file.

[mellowmaroon]

Thanks for the info and ideas!

I added the copy2fs.lst to the directory /tmp/ezremaster/extract_apps/tce, it looked like ezremaster's tce directory anyway.

Unfortunately, the errors persist.

Is it worth attempting to remaster using the Tiny Plus iso and my installed VM?  Is there any potential either might allow me to figure out where the errors are coming from?

[mellowmaroon]

Tried using the Tiny Plus iso as the foundation, and have different errors, this time with libdvdread.

First thing worth noting is that VirtualBox gave me a dialog when I attempted to switch to the Host Disc Drive, in which I had to "Force Unmount".  Although I did only include a few .tcz files (libdvdcss, libdvdread, lsdvd, and a few HandBrake dependencies), I wonder if it has to do with the extensions included in the iso (At least the names of the ones in regular Tiny Plus iso were shown in the loading dialog).  Even still, Core had no qualms with switching media when I didn't include the copy2fs.lst file.

Anyway, the error consists of these four lines:
libdvdread: Can't seek to block 100301
libdvdread: Can't seek to block 100301
libdvdread: Can't seek to block 4096128
libdvdread: Can't seek to block 4096128

So I figure it must be something exclusive to my frugal install's environment?

[Rich]

Hi mellowmaroon
You need to include all the files listed in  onboot.lst  in your  copy2fs.lst  file. Or you can do as gerald_clark
suggest, simply create an empty file called  copy2fs.flg  instead.

[mellowmaroon]

In the ezremaster program, there is a prompt to include all the extensions from onboot.lst in the remaster.  At this stage I only select libdvdcss.tcz, libdvdread.tcz, lsdvd.tcz, and the dependencies for handbrake.

In my copy2fs.lst file, I include all the files I had chosen from onboot.lst (from the extension selection stage of ezremaster) in the same order.  Are there extensions that come with Core that I am neglecting to include?

[Rich]

Hi mellowmaroon

Are there extensions that come with Core that I am neglecting to include?

I don't think so.

libdvdread: Can't seek to block 100301
libdvdread: Can't seek to block 100301
libdvdread: Can't seek to block 4096128
libdvdread: Can't seek to block 4096128

Maybe there is some read ahead buffering going on that is reading past the end of file?

[mellowmaroon]

I'm just clueless as to why I'm not getting any errors in my virtual machine though!

Maybe loading the tcz's manually in a Core environment might tell me if the extensions truly are blameless?

EDIT: Those libdvdread errors were exclusive to the remaster of Tiny Plus, and unlike the Core remaster, it didn't even print out the title table.  Truly mysterious, if it is a readahead fault, I wonder why it was only happening on the Tiny Plus remaster.

[coreplayer2]

If it were an issue with the extensions, then you'd be hearing a lot more here..  as it is libdvdread is working fine for me in all my machines

[mellowmaroon]

I encountered the same exact issue with remastering SliTaz...

One potential fix I encountered while researching was setting the region.  Is there a way to temporarily do that from within the live cd's environment?  I'm running out of avenues otherwise...

If there is anything else I could include that might assist in diagnosing what is wrong, I will gladly provide it.

Related to the SliTaz attempt, the error messages differ slightly.  Here are the ones that stand out (the ones that do not start with libdvdnav):

hdc: command error: status=0x41 { DriveReady Error }
hdc: command error: status=0x50 { LastFailedSense=0x05}
hdc: possibly failed opcode: 0xa0

I really hope someone might be able to steer me in the right direction with this.  It seems like I am doing everything to the letter, and similarly to my installed Tiny Core, all of the packages seemed to work from within the SliTaz virtual machine.

EDIT: My issue mainly involves getting the extensions to work, but would this thread have been better off in a better subcategory?  Is there any way I can change it, or does a moderator have to move it?

[Rich]

Hi mellowmaroon

Is there any way I can change it, or does a moderator have to move it?

I you feel this thread would be better somewhere else, a moderator will have to move it for you, assuming they
agree the new location would be better choice.

[mellowmaroon]

I actually FINALLY figured it out!

I believe it was somehow a combination of not copying the extensions to the RAM filesystem and some quirk with my laptop's CD drive.

In any case, the remaster seems to be working otherwise!  I appreciate the advice given!

Should I marked this [SOLVED]?