[lintweaker]

I followed the the guide:
http://www.sgidepot.co.uk/disksfiles.html#CLONE
to clone my O2 root disk. All content cloned fine but I cannot get the system to boot from the cloned disk.
Verifying the partitions and labels seem to look okay.

in the PROM monitor the a 'ls' on the normal root disk gives:

Code:

ls pci(0)scsi(0)disk(1)rdisk(0)partition(8)/:
sash

While 'ls' on the cloned disk gives:

Code:

ls pci(0)scsi(0)disk(2)rdisk(0)partition(8)/:
dks0d2s8: Abort command: Message reject error
pci(0)scsi(0)disk(2)rdisk(0)partition(8)/: IO error

I can mount the cloned disk just fine. Did I miss a step?

[jirka]

While 'ls' on the cloned disk gives:

Code:

ls pci(0)scsi(0)disk(2)rdisk(0)partition(8)/:
dks0d2s8: Abort command: Message reject error
pci(0)scsi(0)disk(2)rdisk(0)partition(8)/: IO error

I can mount the cloned disk just fine. Did I miss a step?

Why there is disk(2) in the second command and disk(1) in the first (the working one)?

It might be unrelated but I ended with non-booting disk when I last cloned mu O2 drive: I "finished the guide" but forgot to umount the drive. The /etc/fstab (on the clone disk) was thus incorrect. Maybe you have similar problem?

[lintweaker]

While 'ls' on the cloned disk gives:

Code:

ls pci(0)scsi(0)disk(2)rdisk(0)partition(8)/:
dks0d2s8: Abort command: Message reject error
pci(0)scsi(0)disk(2)rdisk(0)partition(8)/: IO error

I can mount the cloned disk just fine. Did I miss a step?

Why there is disk(2) in the second command and disk(1) in the first (the working one)?

It might be unrelated but I ended with non-booting disk when I last cloned mu O2 drive: I "finished the guide" but forgot to umount the drive. The /etc/fstab (on the clone disk) was thus incorrect. Maybe you have similar problem?

AFAIK disk(1) refers to SCSI ID 1 and disk(2) to SCSI ID 2.
I'll check the /etc/fstab on the cloned disk. Not sure if is read/needed for loading the kernel, I would think it is needed/read af booting the kernel (which does not work on my cloned disk).

EDIT: I checked the /etc/fstab on both the original and cloned disk, they are identical and only contain the / mount

[jpstewart]

Did you perhaps skip the dvhtool commands (after 'cd /stand') as described in the cloning guide you mentioned in the first post? The I/O error might be related to missing file(s) in the volume header.

If you did install the correct files to the volume header, then the error could also indicate a hardware problem with that area of the disk.

[lintweaker]

Did you perhaps skip the dvhtool commands (after 'cd /stand') as described in the cloning guide you mentioned in the first post? The I/O error might be related to missing file(s) in the volume header.

If you did install the correct files to the volume header, then the error could also indicate a hardware problem with that area of the disk.

It was an issue with the clone disk. I put in another disk to use as clone disk. This one booted up just fine.
The original clone disk happily took all files only the volume header was troublesome. Luckily I have plenty of spare disks lying around.