In general dd is much better from a performance point of view.ģ) Get back to us. The AFF file format has some serious performance issues (by this I mean all implementations of it, not just with OSF). Was it an NTFS file system to start with? Did it have any partitions that you know about? Might be worth doing to see if it is a general AFF image mounting problem, or a problem just with this particular image. Using the afinfo tool you can check the hash value and dump out a lot of other data about the AFF image.Īlso in both the OSFmount and afflib tools, you should be able to covert the image back to a straight dd raw image. There is a pre-compiled Windows Executable available. What you can do however is to go to the site and get the afinfo tool. Because there is compression of the image, taking a hash of the AFF image file will not match the internal MD5 value that corresponds to the MD5 of the unpacked data. For AFF images the MD5 is stored in internal meta data. Was it an NTFS file system to start with? Did it have any partitions that you know about? After mounting it (and it not finding a NTFS file system), can you use the raw disk viewer in OSF to view to first few sectors, and see what data is in the image. Does the AFF file look about the right size? You should be able to check the hash from the INFO file. We suspect it might be part of the Linux operating system that was incorrectly included.Īs for why the image doesn't mount. It certainly isn't required in order to use the image. The file content normally looks something like this,Ĭhecksum source( /dev/sdc ): 21b30b7d241985c3510124fdc0deded7Ĭhecksum image ( iou.img ): 21b30b7d241985c3510124fdc0deded7Īs for the drivers folder, we aren't sure. This is a text file with details of the image. My guess would be that the image was made with OSFClone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |