SLOW copy

[blakespot]

It turns out what I thought for the longest time was a PSU issue was to do with a SCSI drive in my A1200 tower with A1260. There is a drive here that, if I boot from, causes the Amiga to sit with a black screen for days. I can boot from a blank drive and access the other drive fine, but cannot boot from it.

I booted to blank, and accessed c/ on the "bad" drive fine to try and copy its contents to blank drive to try boot from it. Sadly, blank boot has libs too old to run Dopus. So, I did a CLI: COPY dh1: dh0: ALL on it, and the 1.5GB of data is taking HOURS to copy. Mods 200-300K in size are taking 20 secs.

Why?

How can COPY be that inefficient on a NO S-S boot? Still copying. Thanks.



bp

[Matt_H]

There are a number of reasons why it could be copying slowly...

-SCSI hardware settings (termination, parity, etc.). This might be why the drive isn't booting properly.
-Filesystem / MaxTransfer - what are the settings on the source and destination drives?
-Non-standard drivers. What hardware interface are the drives connected to? Maybe there's something in your startup-sequence or user-startup that loads in a better driver. The 2091 is one such board that benefits from this.

Suggest you cancel the copy (Ctrl+C) and find a solution for this first. Also, you should probably add the CLONE argument to your copy command to preserve filesystem protection bits, comments, and file dates.

[paul1981]

It turns out what I thought for the longest time was a PSU issue was to do with a SCSI drive in my A1200 tower with A1260. There is a drive here that, if I boot from, causes the Amiga to sit with a black screen for days. I can boot from a blank drive and access the other drive fine, but cannot boot from it.

I booted to blank, and accessed c/ on the "bad" drive fine to try and copy its contents to blank drive to try boot from it. Sadly, blank boot has libs too old to run Dopus. So, I did a CLI: COPY dh1: dh0: ALL on it, and the 1.5GB of data is taking HOURS to copy. Mods 200-300K in size are taking 20 secs.

Why?

How can COPY be that inefficient on a NO S-S boot? Still copying. Thanks.



bp

No S-S? All the 060 caches would have been disabled, hampering performance. Use the 060 cpu command to turn them on. Such as "cpu060 b or cpu60 best" or whatever option it is with your particular cpu command (I can't remember details I'm afraid).
Also, large amounts of copying will stall unless you have plenty of disk buffers. For example, addbuffers dh0: 1000, addbuffers dh1: 1000

[x303]

No S-S? All the 060 caches would have been disabled, hampering performance. Use the 060 cpu command to turn them on. Such as "cpu060 b or cpu60 best" or whatever option it is with your particular cpu command (I can't remember details I'm afraid).
Also, large amounts of copying will stall unless you have plenty of disk buffers. For example, addbuffers dh0: 1000, addbuffers dh1: 1000

Well, he could also try to run setpatch, which not only puts the caches on, but might also fix some of the devices, which could also speed up copying.