Errors 36/60 and 35/59: Disk read and write failed



Errors 36 and 60 refer to disk write problems while transferring, and errors 35 and 59 refer to disk read problems while transferring.

The disk is essentially where transfers are being made to or from. This error can occur, for example, when transferring files directly to an external drive and the drive becomes suddenly disconnected or unreadable during the transfer.

Examples of this error

This error can manifest itself in several ways, including in the GUI application for your server, the command line if you’re transferring with ascp, and in the transfer log file.

GUI and ascp

When transferring files from a disk that becomes unreadable during a transfer, you will see the following error message:

Disk read failed

When transferring files to a disk that becomes unwriteable during a transfer, you will see the following error message:

Disk write failed

Log file

Below is an example of these errors as they can be recorded in the logs. The aspera-scp-transfer.log file records helpful information for each attempted transfer, labelled by the date and time attempted. For a reference of the location of this log file on your system, please see this article (Where are the Client or Server logs located?).

2015-09-18 14:12:56 [23f8-000027bc] ERR FASP sender had error, errcode 19 errstr [Disk write failed (server)]
2015-09-18 14:12:56 [23f8-000027bc] ERR Peer FASP receiver had error, errcode 60 errstr [Disk write failed]
2015-09-18 14:12:56 [23f8-0000264c] LOG FASP Session Stop uuid=e535259c-aefc-47a8-bf60-4f58cf0cc41a op=send
status=failed errcode=39 errstr="Peer aborted session" [peer errcode=36 errstr="Disk write error"]

These errors in the logs are sometimes accompanied by the 39/19 error codes, which occur when the client terminates the transfer session. A client terminates a session when data is not being written to the disk on the server, as in the above example.


Ensure that the disk on the server is writeable and readable.

Powered by Zendesk