Testdisk finds single OnTrack DM DDO partition on Disk.
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
First I would use the file command on the ontrack container. It may give the offset to the start of the partitions.
Attach a loop device. Include an offset. Then check the loop device.
If the CHS addresses in your second link are absolute locations on the disk, I think you would use for the first partition,
sudo /sbin/losetup -fs /dev/sdc -o $(16*63*512)
assuming 512 bytes per sector in the fixdisk listing and that the disk contents are linear.
The command will return the lo device used. You can use file -s or mount with the loop device instead. E.g. sudo file -s /dev/loop1
I played with a computer like that back in 97 or so. I think you'd be better off trying to get a physical computer with an old bios and try to image the old system back to a disk where they tried this on. I remember trying linux on that deal too and never could figure out a way to access it. The disk doesn't end up being a normal structure as far as I can recall. Part of the bios and maybe parts of the first part of the disk were used together. As you can see, it didn't say with us for very long cause it sucked. It was real difficult to backup and image.