To ensure disk integrity when copying from one disk to another, we suggest the following:
1) Do a "fsck" on the source disk to make sure the original disk file system is good.
2) Use bs= multiple of k (1024 bytes) or b (512 bytes block) rather than the number of bytes on the "dd" command. The bs=24576 is actually bs=24k or bs=48b, which is fine because it is a multiple of 512 bytes.
Are you sure you gave this number? If the number is not a multiple of 512, it could create a corrupted A/UX disk, because the A/UX file system requires a 512-byte block or 1024-byte boundary.
3) Do a "fsck" on the newly-created disk to ensure that the target disk file system is good.
We don't think that there is a way you can correct the corrupted file system, if the created or "dd" file system's block size was not a multiple of 512 bytes.
It is not clear how the error messages "Unable to read the required table from the selected" or "Fail to read the table" was generated. Which step of HD Setup ("Initialization", "Update", or "Partition") encountered these messages?
It is unusual to mount the entire disk /dev/dsk/cXd0s31 on a directory. If you do a "mount -v /dev/dsk/c0d0s31 /tmp", you will get the error message:
mount: /dev/dsk/c0d0s31 on /tmp: Invalid file system
Just a reminder, by default:
/dev/[r]dsk/cXd0s0 is for Root&Usr file system
/dev/[r]dsk/cXd0s1 is for Swap file system
/dev/[r]dsk/cXd0s2 is for Usr file system
/dev/[r]dsk/cXd0s31 is for entire disk
We don't mount Swap file system and entire disk.
Can you see the internal disk partition map using "dp" under A/UX?
Last, we suggest that you use HD Setup to "Initialize" the internal hard disk, and follow the above suggestions to clone the disk.
Article Change History:
24 Aug 1994 - Reviewed and updated.
Support Information Services