[CGFX.us]

Which is curious, since it's loaded on the machine (I can find the videod executable in /usr/etc ). chkconfig reports videod is on, and even after a reboot, I still get the same error message.

I _did_ just clone the old SCA drive from this machine to one of the SCSI 2 SD (v6) boards, and it otherwise appears to work perfectly (no errors thrown in the process). Not sure if this could be a factor.

I also get a notification on boot that:

Code:

loadable module registration may not have been done (e.g. tpsc)
See mload(4) manual page for more information on auto registration

I don't know if that's related. (But is there a way to resolve this message? I've no idea what mload was until today; the referenced manpage doesn't seem to offer a solution I can understand.)

Oh, it's also been a while. I got real used to the Terminal app on OS X.

Am I missing something basic? inst shows that the dmedia tools are all installed.

[weblacky]

Not that I know anything about this, but after you cloned (but before you booted the clone on the SCSI2SD)...did you change the SCSI ID to match the original "Source" drive? My thinking being the device file references/entries are not the same now with the replacement storage. Perhaps this is one of those stupid things where the original install hard-codes the drive's device path and all that in some config file somewhere.

So to the best of your knowledge, do the dsk entries and LUNs and all that match the original drive? Also I assume it has the same partition layout because you cloned it? I mean you didn't just clone the root partition only right? You cloned the entire disk and layout as-is, correct?

Outside of there being a difference in the raw device reference, I can't think of a reason you'd see this if you're sure your clone was actually complete and not missing files due to permission issues or something like that.

[CGFX.us]

To the best of my knowledge, yes. I used xfsdump | xfsrestore to do the work, per this cloning procedure. I did monitor the procedure but don't recall any errors or anything out of the ordinary, and I've performed the cloning process with tons of real disks in the (distant) past.

The Indy would not boot without the root drive being set to SCSI ID 1 (not without further configuration), so after the clone, I set the SCSI2SD hardware to that. And it seems fine, but perhaps I should run xfs_repair on the SD unit just in case.

This machine also runs LightWave and Photoshop_sgi, and nothing else appears affected. Just videod, so far as I can tell.

(BTW, those SCSI2SD cards are really nice. It makes Helicoprion the quietest it has ever been. Not even a fan in the PSU spins. Prior to that, the SCA drive was mad noisy.)