Error unable to send data to asr sent 0 of 131092 bytes

I was trying to Update and back-up my iPhone 8 to my computer. Nothing unusual or fancy, just the simple procedure of connecting my perfectly good and functioning iPhone to the computer, starting iTunes and selecting "download and update". Everything was going fine and then it crashed part way though the iOS install! iTunes said some error message (error14 maybe?) and my iPhone has never started since. It just has the "support.apple.com/iphone/restore" words on top with a picture of a computer and a lightening cable pointing to it. I've tried EVERYTHING automated apple support recommends to fix this problem, watched MANY YouTube tutorial videos, I spent a long time with Apple support on the phone and I spent hours of research time looking online for answers. Nothing worked.

I was trying to Update and back-up my iPhone 8 to my computer. Nothing unusual or fancy, just the simple procedure of connecting my perfectly good and functioning iPhone to the computer, starting iTunes and selecting «download and update». Everything was going fine and then it crashed part way though the iOS install! iTunes said some error message (error14 maybe?) and my iPhone has never started since. It just has the «support.apple.com/iphone/restore» words on top with a picture of a computer and a lightening cable pointing to it. I’ve tried EVERYTHING automated apple support recommends to fix this problem, watched MANY YouTube tutorial videos, I spent a long time with Apple support on the phone and I spent hours of research time looking online for answers. Nothing worked.

Is there any way to fix this or is my iPhone a brick for good? If its a hardware issue, what is most likely causing the problem? Is it a common thing for a simple update to cause hardware issues?

Errors I think I found in the log:

</dict>

</plist>

Received 234 bytes:

idevicerestore_common.c:printing 234 bytes plist:

<?xml version=»1.0″ encoding=»UTF-8″?>

<!DOCTYPE plist PUBLIC «-//Apple//DTD PLIST 1.0//EN» «http://www.apple.com/DTDs/PropertyList-1.0.dtd»>

<plist version=»1.0″>

<dict>

<key>Command</key>

<string>Payload</string>

</dict>

</plist>

Filesystem validated

Sending filesystem now…

### Asr Validating the filesystem…[20]

### Asr Validating the filesystem…[21]

### Asr Validating the filesystem…[21]

FDR 038FCBD0 timeout waiting for command

FDR 038FCBD0 waiting for message…

### Asr Validating the filesystem…[22]

FDR 038FCBD0 timeout waiting for command

FDR 038FCBD0 waiting for message…

ERROR: Unable to send data to ASR. Sent 0 of 20 bytes.

ERROR: Unable to send chunk checksum

ERROR: Unable to send payload to ASR

ERROR: Unable to send filesystem

ERROR: Unable to successfully restore device

ERROR: Unable to receive message from FDR 038FCBD0 (-4). 0/2 bytes

FDR 038FCBD0 terminating…

No data to read,err = -256,retry=1

ERROR: Unable to restore device

repair FAIL !err=-2

Содержание

  1. Error unable to send filesystem payload
  2. Error in restore.sh sending files interrupt in 7% #46
  3. Comments
  4. Footer
  5. 3uTools-Forum
  6. Iphone 7 — Unable to send data to ASR
  7. Iphone 7 — Unable to send data to ASR
  8. Re: Iphone 7 — Unable to send data to ASR
  9. Re: Iphone 7 — Unable to send data to ASR
  10. iPhone 8 will not «restore» or «Update»
  11. ERROR: Unable to restore device #65
  12. Comments

Error unable to send filesystem payload

Добрый день, дорогие коллеги и пользователи форума.
Прошу разобрать и поделиться опытом решения ошибки -1110, возникающей на 3uTools после процесса индексирования данных пользователя на устройстве. Данная проблема была обнаружена мной на iPhone 11 Pro и является не свойственной для него, так как данный телефон успешно восстанавливается с сохранением всех данных в принципе всегда (исключая случаи, когда пользователь повреждает данные, пытаясь обновить устройство через iTunes и рекавери мод).

Вводные данные:
3u
Tools 2.58 последняя версия.
2 разных ноутбука под управлением Windows 10 и Widnows 8.1
3 разных кабеля, два из них заведомо исправные с помощью которых было восстановлено данных примерно с 20 телефонов.
Разные порты.
Пользователь не пользовался iTunes перед обращением.
После неуспешной прошивки во всех случая устройство не сваливается на режим шнурка и продолжает пребывать с горящим яблоком и перезагрузкой раз в несколько минут.
Аккумулятор предварительно заряжен.
Скорее всего исключаю попадание влаги в устройство и в шлейф FaceID. Проблема возникла после того как перестали корректно работать ватцап и сбер из-за отсутстви свободного времени и пользователь принудительно перезагрузил телефон.
Прошивки использовались IOS 15.1 и IOS 15.2 (на разных ноутах, оба Lenovo)
Блок питания определяется корректно, ток — ок!

Материальной заинтересованности в решении данной проблемы нет, а вот её возникновение впервые за 2 месяца — беспокоит. Данные важны, очень важны, ситуация как всегда с переполненной памятью и всей жизнью в телефоне. Другой нижний шлейф не подкидывал ещё.
Случай интересный, участников его решения обязательно упомяну в статье на своём ресурсе и отблагодарю.
Прикладываю скриншот!

В коллекции error 1110 еще два аппарата: 11 Pro и 11 Pro Max. Также туда улетел 11 обычный, но после перезагрузки ожил с несколькими гигами места свободного.
Добавлю логов подробнее.
Жалуются на отсутствие места в логах..
log_11pro_1110_15.2rc.txt ( 172.49 КБ )

log_11promax_15.2beta5044b.txt ( 178.95 КБ )

Сообщение отредактировал rushouse34 — 17.12.21, 02:56

Источник

Error in restore.sh sending files interrupt in 7% #46

Sending filesystem now. [==== ] 7.0%ERROR: Unable to send data to ASR. Sent 0 of 1450 bytes.
ERROR: Unable to send filesystem payload
ERROR: Unable to send payload to ASR
ERROR: Unable to send filesystem
ERROR: Unable to successfully restore device
Got status message
Status: FailASR: __decompressChunk() error: 1000XSTA
ASR: fail
ASR: Could not restore — error 1000
ASR STATUS: fail
restore_apfs_image : failed to restore an APFS image, error = 14
[13:04:40.0806-GMT]<5>7> CHECKPOINT FAILURE:(FAILURE:14) APFS_RELOAD:[0x0C05] restore_invert [0]D(failed to restore APFS image)
restore-step-results = <0x11070C05:<0:14>>
restore-step-codes = <0x11070C05:<0:14>>
restore-step-domains = <0x11070C05:<0:»AMRestoreErrorDomain»>>
restore-step-error = <0x11070C05:»[0]D(failed to restore APFS image)»>
restore-step-uptime = 139
restore-step-user-progress = 12
[13:04:40.0810-GMT]<5>7> CHECKPOINT NOTICE: (NVRAM set) restore-step-user-progress=12 [sync=true] (first failure)
[13:04:40.0810-GMT]<5>7> CHECKPOINT FAILURE:(FAILURE:14) RESTORED:[0x064F] check_apfs_format [0]D(failed to restore APFS image)
restore-step-results = <0x1107064F:<0:14>;0x11070C05:<0:14>>
restore-step-codes = <0x1107064F:<0:14>;0x11070C05:<0:14>>
restore-step-domains = <0x1107064F:<0:»AMRestoreErrorDomain»>;0x11070C05:<0:»AMRestoreErrorDomain»>>
restore-step-error = <0x1107064F:»[0]D(failed to restore APFS image)»>
restore-step-uptime = 139
restore-step-user-progress = 12
[13:04:40.0814-GMT]<5>7> CHECKPOINT BEGIN: RESTORED:[0x0647] cleanup_check_result
restore-step-ids = <0x1103064F:49;0x11030C05:54;0x11030647:55>
restore-step-names = <0x1103064F:check_apfs_format;0x11030C05:restore_invert;0x11030647:cleanup_check_result>
restore-step-uptime = 139
restore-step-user-progress = 12
[13:04:40.0817-GMT]<5>7> CHECKPOINT END: RESTORED:[0x0647] cleanup_check_result
restore-step-ids = <0x1103064F:49;0x11030C05:54>
restore-step-names = <0x1103064F:check_apfs_format;0x11030C05:restore_invert>
restore-step-uptime = 139
restore-step-user-progress = 12
[13:04:40.0819-GMT]<5>7> CHECKPOINT BEGIN: RESTORED:[0x0648] cleanup_send_final_status
restore-step-ids = <0x1103064F:49;0x11030C05:54;0x11030648:56>
restore-step-names = <0x1103064F:check_apfs_format;0x11030C05:restore_invert;0x11030648:cleanup_send_final_status>
restore-step-uptime = 139
restore-step-user-progress = 12

[Error] ERROR: Unable to restore device
Done: restoring failed.
Failed with errorcode=-11
[Log] Futurerestoring complete

**************** Downgrade complete! Enjoy 10.3.3 =) ****************
**************** Follow me on twitter @mosk_i for help/updates ******
leaders-Mac:1033-OTA-Downgrader-master leader$

The text was updated successfully, but these errors were encountered:

My device is iPad4,4

My ipad air has been downgraded successfully, ipad mini2 has the same problem as you.

@Leadereric Please try again with the latest version of the script

first i have tried the lasted version , but it seems to interrupt in command line16 or somthing,just keep showing waiting 10 seconds to put device in dfu mode,but actually my device has been in dfu even pwn mode,yet the command did not start the restore

I’ve never seen this issue before. Could you run everything again and send the full output?

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Welcome to 3uTools forum. Here you can find all information about iOS and 3uTools.

Iphone 7 — Unable to send data to ASR

Iphone 7 — Unable to send data to ASR

Post by smash59 » 29 Oct 2020 20:45

Re: Iphone 7 — Unable to send data to ASR

Post by claudioml » 05 Nov 2020 20:34

Re: Iphone 7 — Unable to send data to ASR

Post by tojaert » 07 Nov 2020 17:01

hello guys,
ASR (Apple System Restore) is a part of Ramdisk inside IPSW file (which you use to restore). This tool writings a root_fs files into actual system drive. Next step should be a Verify (checksum file approve).
Here are two examples: your is second one I guess. through mathematical combinatorics, I think the problem is with the coherence of the Nand device. To be sure, I would need to review your log entry for this operation.

keep safe, regards,
-tojaert

1. pass
[size=85]__text:00014204 LDR R3, =(off_235E8 — 0x1420A)
__text:00014206 ADD R3, PC
__text:00014208 LDR R3, [R3]
__text:0001420A LDR R3, [R3]
__text:0001420C CMP R3, #0
__text:0001420E BEQ loc_1427A
__text:00014210 LDR R0, =(aImagePassedSig — 0x14216)
__text:00014212 ADD R0, PC ; «Image passed signature verification»
__text:00014214 BLX _warnx
__text:00014218 B loc_1427A
[/size]
2. fail:
__text:0001421A
__text:0001421A loc_1421A ; CODE XREF: sub_13AB4+622�j
__text:0001421A ; sub_13AB4+628�j .
__text:0001421A LDR.W R0, =(aImageFailedSig — 0x14222)
__text:0001421E ADD R0, PC ; «Image failed signature verification»
__text:00014220 BLX _warnx
__text:00014224 MOVS R2, #0x50
__text:00014226 B loc_1426E

Источник

iPhone 8 will not «restore» or «Update»

I was trying to Update and back-up my iPhone 8 to my computer. Nothing unusual or fancy, just the simple procedure of connecting my perfectly good and functioning iPhone to the computer, starting iTunes and selecting «download and update». Everything was going fine and then it crashed part way though the iOS install! iTunes said some error message (error14 maybe?) and my iPhone has never started since. It just has the «support.apple.com/iphone/restore» words on top with a picture of a computer and a lightening cable pointing to it. I’ve tried EVERYTHING automated apple support recommends to fix this problem, watched MANY YouTube tutorial videos, I spent a long time with Apple support on the phone and I spent hours of research time looking online for answers. Nothing worked.

Is there any way to fix this or is my iPhone a brick for good? If its a hardware issue, what is most likely causing the problem? Is it a common thing for a simple update to cause hardware issues?

Errors I think I found in the log:

Received 234 bytes:

idevicerestore_common.c:printing 234 bytes plist:

Sending filesystem now.

### Asr Validating the filesystem. [20]

### Asr Validating the filesystem. [21]

### Asr Validating the filesystem. [21]

FDR 038FCBD0 timeout waiting for command

FDR 038FCBD0 waiting for message.

### Asr Validating the filesystem. [22]

FDR 038FCBD0 timeout waiting for command

FDR 038FCBD0 waiting for message.

ERROR: Unable to send data to ASR. Sent 0 of 20 bytes.

ERROR: Unable to send chunk checksum

ERROR: Unable to send payload to ASR

ERROR: Unable to send filesystem

ERROR: Unable to successfully restore device

ERROR: Unable to receive message from FDR 038FCBD0 (-4). 0/2 bytes

Источник

ERROR: Unable to restore device #65

I have a problem:

Sending filesystem now.
[========== ] 19.0%ERROR: Unable to send data to ASR. Sent 0 of 20 bytes.
ERROR: Unable to send chunk checksum
ERROR: Unable to send payload to ASR
ERROR: Unable to send filesystem
ERROR: Unable to successfully restore device
Got status message
Status: Fail
Log is available:
= 0x0
Scaler 0 enableDeviceClock(false,FULL_CLOCK_INDEX) = 0x0
void AppleRGBOUT::verify_swap_gated(IOMFBSwapIORequest _, bool *) failed fIsDPOut: 0 fDPDriver: 0 fTVOUTDelegate: 0
AppleRGBOUT verify_swap failed
void AppleRGBOUT::verify_swap_gated(IOMFBSwapIORequest *, bool *) failed fIsDPOut: 0 fDPDriver: 0 fTVOUTDelegate: 0
AppleRGBOUT verify_swap failed
AppleS5L8920XBasebandSPIController::loadConfiguration: NCLK Frequency 48857142, Prescaler 3
BasebandSPIDevice::exitLowPower: Invalid state inactive
AppleSerialMultiplexer: adap::start: Frame size is 2048, Rx Buffer count is 16
AppleSerialMultiplexer: mux::start: created new mux (17) for spi-baseband with adapter BasebandSPIDevice
AppleSerialMultiplexer: debugparams::init: Parsed flags «» ( 0 )
AppleSerialMultiplexer: !! mux::setPowerStateGated: Skipping power state change
AppleSamsungSerial: Identified Serial Port on ARM Device=uart1 at 0x82600000(0x8bf4e000)
AppleSamsungSerial: Identified Serial Port on ARM Device=uart2 at 0x82700000(0x8bf56000)
AppleSamsungSerial: Identified Serial Port on ARM Device=uart3 at 0x82800000(0x8ca26000)
AppleSamsungSerial: Identified Serial Port on ARM Device=uart6 at 0x82b00000(0x8ca28000)
[HPark] AUD10::start: 0x800f6000, highland-park mIISNub: 0x91932080, sampleRate = 44100, ol=10, oi=12
AppleCS42L61Audio: could not allocate control 395
AppleARMBacklight::start: _minDACLevel=456 _maxDACLevel=1971
AppleMultitouchN1SPI: successfully started
AppleRGBOUT: TVOUT device is detected
ApplePinotLCD: _lcdPanelID: 0xa5970dc8 _lcdPanelClass: 2
IOReturn AppleMobileCLCD::set_ditherTable_state(bool), mIsCLCDDitherFor8Bits is true, no dynamic dither table.
[HPark] AUD10::start: 0x800f6000, highland-park mIICNub: 0x8fb5d540, mIISNub: 0x91932080, mSerialNub: 0x918fb400, sampleRate = 44100, ol=10, oi=12
AppleD1815PMUPowerSource: AppleUSBCableDetect 1
AppleD1815PMUPowerSource: AppleUSBCableType USBHost
[HPark] AUD10 ATSc values: [ mic1: 0x00000010, mic2: 0x000000f7, mic3: 0x00000000, recv: 0x00000000, spk: 0x00000000 ]
[HPark] AUD10::setPowerState() function called whereas Start() is not finished
AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don’t have device configuration yet
AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don’t have device configuration yet
AppleMultitouchN1SPI: detected HBPP. driver will be kept alive
IOSDIOController::enumerateSlot(): Searching for SDIO device in slot: 0
IOSDIOController::enumerateSlot(): Found SDIO I/O device. Function count(1), memory(0)
IOSDIOIoCardDevice::parseFn0CISTuple(): Device manufacturer ID 0x2d0, Product ID 0x4329
IOSDIOIoCardDevice::parseFn0CISTuple(): Manufacturer: «»
IOSDIOIoCardDevice::parseFn0CISTuple(): Product: «»
IOSDIOIoCardDevice::parseFn0CISTuple(): ProductInfo0: «s=B1»
IOSDIOIoCardDevice::parseFn0CISTuple(): ProductInfo1: «P=N90 m=3.1 V=m»
AppleBCMWLANBusInterfaceSdio::start(): Started by: IOSDIOIoCardDevice, AppleBCMWLANV2-259 Jun 11 2014 20:13:01
AppleBCMWLANCore::init(): IO80211-46 Jun 11 2014 20:10:01
000060.775046 wlan.N[0] AppleBCMWLANCore::start(): Starting with MAC Address: 5c:59:48:0f:50:44
IO80211Peer::addPhyStatistics Phy stats started for addr 00:be:ef:ff:ff:ff
IO80211Peer::addPhyStatistics Tx Completion stats started for addr 00:be:ef:ff:ff:ff
IO80211PeerManager::initWithInterface cant add monitoring timer
Started logging for intf
IO80211PeerManager::initWithInterface: inited peer manager
IO80211Interface::init peerManager=0x919db000
start:156
start:156
000060.778701 wlan.N[1] AppleBCMWLANCore::setPowerStateGated(): powerState 1, fStateFlags 0x20, dev 0x802fd000 (this 1, provider 0)
000060.778744 wlan.N[2] AppleBCMWLANCore::setPowerStateGated(): Received power state change before driver has initialized, ignoring
AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don’t have device configuration yet
read new style signature 0x43313131 (line:389)
[FTL:MSG] VSVFL Register [OK]
[WMR:MSG] Metadata whitening is set in NAND signature
[FTL:MSG] VFL Init [OK]
display-scale = 2
display-rotation = 0
found applelogo at /usr/share/progressui/applelogo@2x.tga
[FTL:MSG] VFL_Open [OK]
[FTL:MSG] YAFTL Register [OK]
found display: primary
display: 640 x 960
found PTP interface
AppleSynopsysOTGDevice — Configuration: PTP
AppleSynopsysOTGDevice Interface: PTP
AppleSynopsysOTGDevice — Configuration: iPod USB Interface
AppleSynopsysOTGDevice Interface: USBAudioControl
AppleSynopsysOTGDevice Interface: USBAudioStreaming
AppleSynopsysOTGDevice Interface: IapOverUsbHid
AppleSynopsysOTGDevice — Configuration: PTP + Apple Mobile Device
AppleSynopsysOTGDevice Interface: PTP
AppleSynopsysOTGDevice Interface: AppleUSBMux
AppleSynopsysOTGDevice — Configuration: PTP + Apple Mobile Device + Apple USB Ethernet
AppleSynopsysOTGDevice Interface: PTP
AppleSynopsysOTGDevice Interface: AppleUSBMux
AppleSynopsysOTGDevice Interface: AppleUSBEthernet
AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioControl
AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioStreaming
IOAccessoryPortUSB::start
AppleSynopsysOTGDevice::gated_registerFunction Register function IapOverUsbHid
virtual bool AppleUSBDeviceMux::start(IOService *) build: Jun 11 2014 20:11:28
init_waste
AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBMux
AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBEthernet
AppleSynopsysOTGDevice::gated_registerFunction Register function PTP
AppleSynopsysOTGDevice::startUSBStack Starting usb stack
IOReturn AppleUSBDeviceMux::setPropertiesGated(OSObject *) setting debug level to 7
[FTL:MSG] FTL_Open [OK]
[NAND] publishServices:642 FTL capabilities: 0x00000000
[nand_part_core:INF@ 157] published partition 0
[nand_part_core:INF@ 157] published partition 1
[nand_part_core:INF@ 157] published partition 2
[nand_part_core:INF@ 157] published partition 3
[nand_part_core:INF@ 157] published partition 5
[nand_part_core:INF@ 157] published partition 6
AppleSynopsysOTGDevice::stallBadSetupRequest request: a2 81 0100 0081 0003
AppleSynopsysOTGDevice::stallBadSetupRequest request: 21 0a 0000 0002 0000
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0101 0002 0006
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0102 0002 000a
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0103 0002 000e
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0104 0002 0012
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0105 0002 001a
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0106 0002 0032
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0107 0002 0060
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0108 0002 00c2
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 0109 0002 0102
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 010a 0002 0182
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 010b 0002 0202
AppleSynopsysOTGDevice::stallBadSetupRequest request: a1 01 010c 0002 0300
[effaceable:INIT] found current generation, 49, in group 0
[effaceable:INIT] started
[effaceable:INIT] started
AppleUSBDeviceMux::handleConnectResult new session 0x93118630 established 62078 49152 62078 1
void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x93118630
AppleARMBacklight::start: No AAP function
AppleUSBDeviceMux::handleConnectResult new session 0x93118630 established 62078 49153 62078 2
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
AppleUSBDeviceMux::handleConnectResult new session 0x93118580 established 62078 49155 62078 4
unrecognized request ‘GetValue’
AppleUSBDeviceMux::handleConnectResult new session 0x93118528 established 62078 49156 62078 5
unrecognized request ‘GetValue’
AppleUSBDeviceMux::handleConnectResult new session 0x931184d0 established 62078 49157 62078 6
unrecognized request ‘GetValue’
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
unrecognized request ‘GetValue’
AppleUSBDeviceMux::sessionUpcall socket is closed, session 0x93118528 (62078 49156 62078 5)
AppleUSBDeviceMux::sessionUpcall socket is closed, session 0x931184d0 (62078 49157 62078 6)
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 1082 failed: 61
client protocol version 13
*
* UUID 2628C4C3-EF38-166E-8676-9A3584C8313B ***
Restore options:
UUID =>
MinimumSystemPartition =>
SystemPartitionSize =>
PersonalizedDuringPreflight =>
SystemPartitionPadding => entries =>
2 : =
3 : =
4 : =
5 : =
8 : =
>

entering load_sep_os
device has no sep
entering partition_nand_device
device supports boot-from-NAND
nand device is already partitioned
entering wait_for_storage_device
Searching for NAND service
Found NAND service: IOFlashStoragePartition
NAND initialized. Waiting for devnode.
entering clear_remap_variable
executing /usr/sbin/nvram
entering format_effaceable_storage
effaceable storage is formatted, clearing it
effaceable storaged cleared
entering ramrod_probe_media
device partitioning scheme is GPT
find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
executing /sbin/fsck_hfs
volumeType is 0
0000: 0000 0000 0000 0000 0000 0000 0000 0000 |. |
. . .
01f0: 0000 0000 0000 0000 0000 0000 0000 0000 |. |
Offset 1024 length 512:
0000: 0000 0000 0000 0000 0000 0000 0000 0000 |. |
. . .
01f0: 0000 0000 0000 0000 0000 0000 0000 0000 |. |
** /dev/rdisk0s1s1
Executing fsck_hfs (version hfs-277.10.5).
fsck failed on /dev/disk0s1s1
skipping check for restore log due to old host software
entering clean_NAND
NAND format complete
entering ramrod_probe_media
find_filesystem_partitions: storage=/dev/disk0 system= data=
entering format_storage_for_LwVM
entering ramrod_probe_media
device partitioning scheme is GPT
unexpected partition ‘LwVM’ — skipping
find_filesystem_partitions: storage=/dev/disk0s1 system= data=
entering create_filesystem_partitions
User specified system partition size, skipping firmware extras size.
system partition padding size is: 167772160 bytes
unable to open : No such file or directory
creating 2 partitions
creating encrypted data partition
entering ramrod_probe_media
device partitioning scheme is GPT
find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
wipe entire partition: 1 (old = 0 new = 1691)
block size for /dev/disk0s1s1: 8192
/sbin/newfs_hfs -s -v System -J -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1s1
executing /sbin/newfs_hfs -s -v System -J -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1s1
void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x93118580
Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
block size for /dev/disk0s1s2: 8192
/sbin/newfs_hfs -s -v Data -J -P -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1s2
executing /sbin/newfs_hfs -s -v Data -J -P -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1s2
AppleUSBDeviceMux::handleConnectResult new session 0x93118420 established 62078 49167 62078 16
unrecognized request ‘GetValue’
AppleUSBDeviceMux::handleConnectResult new session 0x931183c8 established 62078 49168 62078 17
unrecognized request ‘GetValue’
Initialized /dev/rdisk0s1s2 as a 13 GB case-sensitive HFS Plus volume with a 8192k journal
entering ramrod_probe_media
device partitioning scheme is GPT
find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
entering mount_filesystems
executing /sbin/fsck_hfs
** /dev/rdisk0s1s1
Executing fsck_hfs (version hfs-277.10.5).
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive volume.
The volume name is System
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attributes file.
** Checking volume bitmap.
** Checking volume information.
** Trimming unused blocks.
** The volume System appears to be OK.
executing /sbin/mount_hfs
mount_hfs: Could not create property for re-key environment check: No such file or directory
/dev/disk0s1s1 mounted on /mnt1
executing /sbin/fsck_hfs
** /dev/rdisk0s1s2
Executing fsck_hfs (version hfs-277.10.5).
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive volume.
The volume name is Data
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attributes file.
** Checking volume bitmap.
** Checking volume information.
** Trimming unused blocks.
** The volume Data appears to be OK.
executing /sbin/mount_hfs
mount_hfs: Could not create property for re-key environment check: No such file or directory
/dev/disk0s1s2 mounted on /mnt2
entering resize_system_partition_to_options
User specified system partition size, skipping firmware extras size.
Found SystemPartitionPadding value of 167772160 bytes
Erasing system partition prior to resize operation.
block size for /dev/disk0s1s1: 8192
/sbin/newfs_hfs -s -v System -J -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1s1
executing /sbin/newfs_hfs -s -v System -J -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1s1
Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
executing /sbin/fsck_hfs
** /dev/rdisk0s1s1
Executing fsck_hfs (version hfs-277.10.5).
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive volume.
The volume name is System
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attributes file.
** Checking volume bitmap.
** Checking volume information.
** Trimming unused blocks.
** The volume System appears to be OK.
executing /sbin/mount_hfs
mount_hfs: Could not create property for re-key environment check: No such file or directory
/dev/disk0s1s1 mounted on /mnt1
Trying to resize system partition to 1773142016 bytes aka 1691 MB
entering adjust_partition_preflight
partition:0 requiredSize=216448
no change in size
Successfully resized the system partition
entering maximize_data_partition
entering adjust_partition_preflight
partition:1 requiredSize=2251799813685248
maximizing data partition to 14181990399 bytes
entering adjust_partition_preflight
partition:1 requiredSize=1731200
no change in size
Successfully resized data partition to consume free blocks
The system partition now has a total HFS+ capacity of 1691 MB
entering ramrod_probe_media
device partitioning scheme is GPT
find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
entering unmount_filesystems
entering ramrod_ticket_update
looking up root ticket hash
device tree ticket-hash:
ticket_hash: FB5459EEE0B6B50B60763F43325A6026C03AB71D
received valid ticket (2741 bytes)
entering restore_images
Successfully marked device node /dev/rdisk0s1s1 as static data
executing /usr/sbin/asr -source asr://localhost:12345 -target /dev/disk0s1s1 -erase -noprompt —chunkchecksum —puppetstrings
void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 12345 failed: 61
ASR: asr: Unable to disable idle sleep — -536870199
ASR STATUS: start 241.1 multicast-client
ASR: Waiting for connection attempt from server
AppleUSBDeviceMux::handleConnectResult new session 0x931180b0 established 12345 49170 12345 19
ASR STATUS: setup
ASR: Validating target. done
ASR STATUS: metadata
ASR: Validating source.
void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x93118420
ASR: done
ASR: Retrieving scan information. done
ASR: Validating sizes. done
ASR STATUS: restore
unrecognized request ‘GetValue’
ASR RESTORE PROGRESS: 2%
ASR RESTORE PROGRESS: 4%
void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x931183c8
ASR RESTORE PROGRESS: 6%
ASR RESTORE PROGRESS: 8%
ASR RESTORE PROGRESS: 10%
ASR RESTORE PROGRESS: 12%
ASR RESTORE PROGRESS: 14%
ASR RESTORE PROGRESS: 16%
ASR RESTORE PROGRESS: 18%
void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x931180b0
ASR: asr:
ASR: Socket unexpectedly closed while trying to read() offset 0xDBB466C
ASR: __decompressChunk: backing store read at offset 228366682 length 230024 failed with error 5
ASR: asr:
ASR: __decompressChunk() error: 5
ASR: Failed to read the stream
ASR: :
ASR: Input/output error
ASR: __decompressChunk: backing store read at offset 227641219 length 235574 failed with error 5
ASR: __decompressChunk: backing store read at offset 226029867 length 244217 failed with error 5
ASR: __decompressChunk: backing store read at offset 226727922 length 210638 failed with error 5
ASR: __decompressChunk() error: 5
ASR: __decompressChunk() error: 5
ASR: __decompressChunk() error: 5
ASR STATUS: fail
ASR: newfs_hfs: MarkExtentUsed::pread(9, 0x27d5a610, 8192, 4096): Invalid argument
ASR: /sbin/newfs_hfs failed with error 256
ASR: Could not restore — Input/output error
ASR STATUS: fail

ERROR: Unable to restore device

The text was updated successfully, but these errors were encountered:

Источник

Adblock
detector

2014-01-01 16:35:30.595 [520:17bc]: restore library built Aug 8 2013 at 02:24:58
2014-01-01 16:35:30.595 [520:17bc]: iTunes: iTunes 11.1.3.8
2014-01-01 16:35:30.595 [520:17bc]: iTunes: Software payload version: 11B554a
2014-01-01 16:35:30.595 [520:17bc]: iTunes: Using MobileRestore state machine
[14:35:48,0435] Changing state from ‘Idle’ to ‘Restoring’
[14:35:48,0435] requested restore behavior: Erase
[14:35:48,0436] requested variant: Erase
[14:35:48,0438] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[14:35:48,0647] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
[14:35:48,0648] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «RestoreLogo» Digest = «<CFData 068CD3F8 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0649] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «RestoreDeviceTree» Digest = «<CFData 068CD248 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0649] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «RestoreKernelCache» Digest = «<CFData 068CD320 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0650] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «RestoreRamDisk» Digest = «<CFData 068CD560 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0651] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «iBEC» Digest = «<CFData 068CD3B0 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0652] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «iBSS» Digest = «<CFData 068CD290 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0652] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «KernelCache» Digest = «<CFData 068CD440 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0653] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «Diags» not part of manifest, skipping
[14:35:48,0653] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «CFELoader» not part of manifest, skipping
[14:35:48,0654] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «RBM» not part of manifest, skipping
[14:35:48,0655] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PHLEET» not part of manifest, skipping
[14:35:48,0655] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PERTOS» not part of manifest, skipping
[14:35:48,0656] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PEHammer» not part of manifest, skipping
[14:35:48,0656] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «BatteryLow1» Digest = «<CFData 068CD518 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0657] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «BatteryLow0» Digest = «<CFData 068CD5A8 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0658] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «LLB» Digest = «<CFData 068CD2D8 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0658] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «iBoot» Digest = «<CFData 068CD488 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0659] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «DeviceTree» Digest = «<CFData 05983240 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0660] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «SEP» Digest = «<CFData 05983288 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0661] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «BatteryCharging1» Digest = «<CFData 05983318 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0661] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «RestoreSEP» Digest = «<CFData 05983360 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0662] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «AppleLogo» Digest = «<CFData 05983510 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0663] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «BatteryPlugin» Digest = «<CFData 059834C8 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0664] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «BatteryFull» Digest = «<CFData 059833A8 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0664] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «BatteryCharging0» Digest = «<CFData 059831B0 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0665] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing «RecoveryMode» Digest = «<CFData 059831F8 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}»
[14:35:48,0666] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 02AC98A0 [748B8078]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[14:35:48,0667] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[14:35:48,0667] amai: AMAuthInstallDebugWriteObject: debug object written: C:UsersZAVAppDataLocalTempPer8CA6.tmpamaidebugtss-request.plist
[14:35:48,0945] amai: tss_submit_job: HttpQueryInfo returned 200
[14:35:49,0088] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[14:35:49,0088] amai: AMAuthInstallDebugWriteObject: debug object written: C:UsersZAVAppDataLocalTempPer8CA6.tmpamaidebugtss-response.plist
[14:35:49,0331] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for «Diags»
[14:35:49,0332] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for «CFELoader»
[14:35:49,0333] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for «RBM»
[14:35:49,0334] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for «PHLEET»
[14:35:49,0334] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for «PERTOS»
[14:35:49,0335] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for «PEHammer»
[14:35:49,0446] iBoot build-version = iBoot-1940.3.5
[14:35:49,0447] iBoot build-style = RELEASE
[14:35:49,0447] requested restore behavior: Erase
[14:35:49,0449] requested restore behavior: Erase
[14:35:49,0451] unable to open device_map.txt: No such file or directory
[14:35:49,0452] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[14:35:49,0453] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[14:35:49,0453] AMDeviceIoControl: GetOverlappedResult failed
[14:35:49,0454] AMDeviceIoControl: pipe stall
[14:35:49,0454] USBControlTransfer: error 31, usbd status c0000004
[14:35:49,0455] command device request for ‘getenv radio-error’ failed: 2008
[14:35:49,0456] radio-error not set
[14:35:49,0456] unable to open device_map.txt: No such file or directory
[14:35:49,0457] <Recovery Mode Device 02ACDCB8>: production fused device
[14:35:49,0457] requested restore behavior: Erase
[14:35:49,0458] requested restore behavior: Erase
[14:35:49,0458] interface has 1 endpoints, file pipe = 1
[14:35:49,0458]
[14:35:49,0459] <Recovery Mode Device 02ACDCB8>: operation 4 progress -1
[14:35:49,0460] bootstrapping restore with iBEC
[14:35:49,0460] requested restore behavior: Erase
[14:35:49,0472] <Recovery Mode Device 02ACDCB8>: operation 31 progress -1
[14:35:50,0473] <Recovery Mode Device 02ACDCB8>: Recovery mode succeeded
[14:35:50,0477] Finished Recovery Restore Phase: Successful
[14:35:50,0540] Recovery mode device disconnected
[14:35:50,0541] Device removed when in state Restoring, moving device to transition state
[14:35:50,0541] Changing state from ‘Restoring’ to ‘Transitioning’
[14:35:50,0542] Creating timer to monitor transition
[14:35:52,0812] Recovery mode device connected
[14:35:52,0813] Transitioning device returned, continuing restore.
[14:35:52,0813] Canceling timer
[14:35:52,0814] Changing state from ‘Transitioning’ to ‘Restoring’
[14:35:52,0814] requested restore behavior: Erase
[14:35:52,0815] requested variant: Erase
[14:35:52,0815] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[14:35:53,0024] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[14:35:53,0024] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreLogo»
[14:35:53,0025] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreDeviceTree»
[14:35:53,0026] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreKernelCache»
[14:35:53,0026] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreRamDisk»
[14:35:53,0027] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «iBEC»
[14:35:53,0028] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «iBSS»
[14:35:53,0028] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «KernelCache»
[14:35:53,0029] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «Diags» not part of manifest, skipping
[14:35:53,0029] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «CFELoader» not part of manifest, skipping
[14:35:53,0030] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «RBM» not part of manifest, skipping
[14:35:53,0031] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PHLEET» not part of manifest, skipping
[14:35:53,0031] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PERTOS» not part of manifest, skipping
[14:35:53,0032] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PEHammer» not part of manifest, skipping
[14:35:53,0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryLow1»
[14:35:53,0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryLow0»
[14:35:53,0034] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «LLB»
[14:35:53,0035] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «iBoot»
[14:35:53,0035] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «DeviceTree»
[14:35:53,0036] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «SEP»
[14:35:53,0037] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryCharging1»
[14:35:53,0038] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreSEP»
[14:35:53,0038] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «AppleLogo»
[14:35:53,0039] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryPlugin»
[14:35:53,0039] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryFull»
[14:35:53,0040] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryCharging0»
[14:35:53,0041] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RecoveryMode»
[14:35:53,0041] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[14:35:53,0043] iBoot build-version = iBoot-1940.3.5
[14:35:53,0043] iBoot build-style = RELEASE
[14:35:53,0044] requested restore behavior: Erase
[14:35:53,0044] requested restore behavior: Erase
[14:35:53,0045] unable to open device_map.txt: No such file or directory
[14:35:53,0046] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[14:35:53,0046] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[14:35:53,0047] AMDeviceIoControl: GetOverlappedResult failed
[14:35:53,0047] AMDeviceIoControl: pipe stall
[14:35:53,0048] USBControlTransfer: error 31, usbd status c0000004
[14:35:53,0048] command device request for ‘getenv radio-error’ failed: 2008
[14:35:53,0049] radio-error not set
[14:35:53,0050] unable to open device_map.txt: No such file or directory
[14:35:53,0050] <Recovery Mode Device 05A20DA8>: production fused device
[14:35:53,0051] requested restore behavior: Erase
[14:35:53,0051] requested restore behavior: Erase
[14:35:53,0052] interface has 1 endpoints, file pipe = 1
[14:35:53,0052]
[14:35:53,0052] <Recovery Mode Device 05A20DA8>: operation 4 progress -1
[14:35:53,0053] unable to open device_map.txt: No such file or directory
[14:35:53,0054] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[14:35:53,0054] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[14:35:53,0055] requested restore behavior: Erase
[14:35:53,0056] requested restore behavior: Erase
[14:35:53,0056] <Recovery Mode Device 05A20DA8>: operation 42 progress -1
[14:35:53,0057] requested restore behavior: Erase
[14:35:54,0072] <Recovery Mode Device 05A20DA8>: operation 5 progress -1
[14:35:54,0312] unable to open device_map.txt: No such file or directory
[14:35:54,0313] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[14:35:54,0314] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[14:35:54,0314] AMDeviceIoControl: GetOverlappedResult failed
[14:35:54,0315] AMDeviceIoControl: pipe stall
[14:35:54,0315] USBControlTransfer: error 31, usbd status c0000004
[14:35:54,0316] command device request for ‘getenv ramdisk-delay’ failed: 2008
[14:35:55,0436] <Recovery Mode Device 05A20DA8>: operation 6 progress -1
[14:35:56,0459] <Recovery Mode Device 05A20DA8>: operation 7 progress -1
[14:35:56,0659] <Recovery Mode Device 05A20DA8>: operation 8 progress -1
[14:35:56,0660] unable to open device_map.txt: No such file or directory
[14:35:56,0660] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[14:35:56,0661] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[14:35:56,0661] <Recovery Mode Device 05A20DA8>: operation 9 progress -1
[14:35:56,0662] <Recovery Mode Device 05A20DA8>: Recovery mode succeeded
[14:35:56,0662] Finished Recovery Restore Phase: Successful
[14:35:57,0346] Recovery mode device disconnected
[14:35:57,0346] Device removed when in state Restoring, moving device to transition state
[14:35:57,0347] Changing state from ‘Restoring’ to ‘Transitioning’
[14:35:57,0349] Creating timer to monitor transition
[14:36:01,0788] RestoreOS mode device connected
[14:36:01,0788] Transitioning device returned, continuing restore.
[14:36:01,0789] Canceling timer
[14:36:01,0790] Changing state from ‘Transitioning’ to ‘Restoring’
[14:36:01,0794] <Restore Device 02AFFC08>: operation 44 progress -1
[14:36:01,0795] requested restore behavior: Erase
[14:36:01,0795] requested variant: Erase
[14:36:01,0797] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[14:36:02,0024] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[14:36:02,0025] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreLogo»
[14:36:02,0026] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreDeviceTree»
[14:36:02,0027] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreKernelCache»
[14:36:02,0027] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreRamDisk»
[14:36:02,0028] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «iBEC»
[14:36:02,0029] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «iBSS»
[14:36:02,0029] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «KernelCache»
[14:36:02,0030] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «Diags» not part of manifest, skipping
[14:36:02,0030] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «CFELoader» not part of manifest, skipping
[14:36:02,0031] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «RBM» not part of manifest, skipping
[14:36:02,0032] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PHLEET» not part of manifest, skipping
[14:36:02,0032] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PERTOS» not part of manifest, skipping
[14:36:02,0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry «PEHammer» not part of manifest, skipping
[14:36:02,0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryLow1»
[14:36:02,0034] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryLow0»
[14:36:02,0035] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «LLB»
[14:36:02,0035] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «iBoot»
[14:36:02,0036] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «DeviceTree»
[14:36:02,0036] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «SEP»
[14:36:02,0037] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryCharging1»
[14:36:02,0037] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RestoreSEP»
[14:36:02,0038] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «AppleLogo»
[14:36:02,0038] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryPlugin»
[14:36:02,0039] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryFull»
[14:36:02,0040] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «BatteryCharging0»
[14:36:02,0040] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing «RecoveryMode»
[14:36:02,0041] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[14:36:02,0041] requested restore behavior: Erase
[14:36:02,0042] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[14:36:02,0044] device did not return saved USB log
[14:36:02,0045] device had saved panic logs: panic(cpu 0 caller 0x<<<<<MEID>>>>>dc): «Timeout on ART_LOAD»

[info] Using LOCAL IPSW C:Watch5,2_8.0_19R346_Restore.ipsw
[info] Updated version data.
[info] Found device in Recovery mode
[info] Gettting dfu mode device …
[info] Identified device as Apple Watch S5, n144bap, Watch5,2
[info] Extracting BuildManifest from ipsw
[data] Product Version: 8.0
[data] Product Build: 19R346 Major: 19
[info] device serial number is G9CCW1R0MLTQ
[data] Device supports Image4: true
[info] Variant: Customer Erase Install (IPSW)
[info] This restore will erase your device data.
[info] Checking IPSW for required components…
[info] All required components found in IPSW
[info] Found ECID 00150b0e0a0b802e
[info] Getting ApNonce in recovery mode… [data] 5EDF8D9F68824B138BD2AB4A3C697D209FD4B30B3F4255AC06 E884C6F9388713
[info] tts>Trying to fetch new SHSH blob
[info] Getting SepNonce in recovery mode… [data] 49091D30A798754ED226261E16F9991216563105
[note] Unable to find BbChipID node
[note] Unable to find BbProvisioningManifestKeyHash node
[note] Unable to find BbActivationManifestKeyHash node
[note] Unable to find BbCalibrationManifestKeyHash node
[note] Unable to find BbFactoryActivationManifestKeyHash node
[note] Unable to find BbFDRSecurityKeyHash node
[note] Unable to find BbSkeyId node
[info] Request URL set to https://gs.apple.com/TSS/controller?action=2
[info] Sending TSS request attempt 1…
[info] response successfully received
[info] tts>Received SHSH blobs
[info] Using cached filesystem from ‘iDeviceTools/Watch5,2_8.0_19R346_Restore/018-78404-002.dmg’
[info] Found ECID 00150b0e0a0b802e
[info] Getting ApNonce in recovery mode… [data] 5EDF8D9F68824B138BD2AB4A3C697D209FD4B30B3F4255AC06 E884C6F9388713
[info] tts>Trying to fetch new SHSH blob
[info] Getting SepNonce in recovery mode… [data] 49091D30A798754ED226261E16F9991216563105
[note] Unable to find BbChipID node
[note] Unable to find BbProvisioningManifestKeyHash node
[note] Unable to find BbActivationManifestKeyHash node
[note] Unable to find BbCalibrationManifestKeyHash node
[note] Unable to find BbFactoryActivationManifestKeyHash node
[note] Unable to find BbFDRSecurityKeyHash node
[note] Unable to find BbSkeyId node
[info] Request URL set to https://gs.apple.com/TSS/controller?action=2
[info] Sending TSS request attempt 1…
[info] response successfully received
[info] tts>Received SHSH blobs
[warn] No path for component iBEC in TSS, will fetch from build_identity
[info] Extracting iBEC.n144b.RELEASE.im4p…
[info] Personalizing IMG4 component iBEC…
[info] Sending iBEC (1118744 bytes)…
[info] Device ecid 00150b0e0a0b802e disconnect detected!
[info] Recovery Mode Environment:
[info] iBoot build-version=iBoot-7429.10.23.0.2
[info] iBoot build-style=RELEASE

[info] Sending AppleLogo…
[warn] No path for component AppleLogo in TSS, will fetch from build_identity
[info] Extracting [email protected]~watch.im4p…
[info] Personalizing IMG4 component AppleLogo…
[info] Sending AppleLogo (10947 bytes)…
[warn] No path for component ACIBT in TSS, will fetch from build_identity
[info] Extracting BT_FW_m9.im4p…
[info] Personalizing IMG4 component ACIBT…
[info] Sending ACIBT (1845625 bytes)…
[warn] No path for component ACIWIFI in TSS, will fetch from build_identity
[info] Extracting wifi_armv7r_m9_rtkit_image.im4p…
[info] Personalizing IMG4 component ACIWIFI…
[info] Sending ACIWIFI (1905205 bytes)…
[warn] No path for component ANE in TSS, will fetch from build_identity
[info] Extracting h11_ane_fw_mercury.im4p…
[info] Personalizing IMG4 component ANE…
[info] Sending ANE (1731589 bytes)…
[warn] No path for component AOP in TSS, will fetch from build_identity
[info] Extracting aopfw-watch5aop.im4p…
[info] Personalizing IMG4 component AOP…
[info] Sending AOP (2006165 bytes)…
[warn] No path for component GFX in TSS, will fetch from build_identity
[info] Extracting armfw_g11m.im4p…
[info] Personalizing IMG4 component GFX…
[info] Sending GFX (881133 bytes)…
[warn] No path for component RestoreTrustCache in TSS, will fetch from build_identity
[info] Extracting 018-78678-002.dmg.trustcache…
[info] Personalizing IMG4 component RestoreTrustCache…
[info] Sending RestoreTrustCache (16710 bytes)…
[warn] No path for component SCE in TSS, will fetch from build_identity
[info] Extracting scefw.im4p…
[info] Personalizing IMG4 component SCE…
[info] Sending SCE (20345 bytes)…
[warn] No path for component SIO in TSS, will fetch from build_identity
[info] Extracting SmartIOFirmware_ASCv2.im4p…
[info] Personalizing IMG4 component SIO…
[info] Sending SIO (1176673 bytes)…
[warn] No path for component WCHFirmwareUpdater in TSS, will fetch from build_identity
[info] Extracting WirelessPower.watch4.im4p…
[info] Personalizing IMG4 component WCHFirmwareUpdater…
[info] Sending WCHFirmwareUpdater (31828 bytes)…
[warn] No path for component RestoreRamDisk in TSS, will fetch from build_identity
[info] Extracting 018-78678-002.dmg…
[info] Personalizing IMG4 component RestoreRamDisk…
[info] Sending RestoreRamDisk (87495832 bytes)…
[warn] No path for component RestoreDeviceTree in TSS, will fetch from build_identity
[info] Extracting DeviceTree.n144bap.im4p…
[info] Personalizing IMG4 component RestoreDeviceTree…
[info] Sending RestoreDeviceTree (42876 bytes)…
[warn] No path for component RestoreSEP in TSS, will fetch from build_identity
[info] Extracting sep-firmware.n144b.RELEASE.im4p…
[info] Personalizing IMG4 component RestoreSEP…
[info] Sending RestoreSEP (5463422 bytes)…
[warn] No path for component RestoreKernelCache in TSS, will fetch from build_identity
[info] Extracting kernelcache.release.watch5…
[info] Personalizing IMG4 component RestoreKernelCache…
[info] Sending RestoreKernelCache (13105161 bytes)…
[info] Device ecid 00150b0e0a0b802e disconnect detected!
[info] About to restore device…
[info] Waiting for device…
[info] Device is now connected in restore mode…
[info] Connecting now…
[info] Connected to com.apple.mobile.restored, version 15
[info] Device 00008006-00150B0E0A0B802E has successfully entered restore mode
[info] Hardware Information:
[info] BoardID: 18
[info] ChipID: 32774
[info] UniqueChipID: 5923129436897326
[info] ProductionMode: true
[sett] Previous restore exit status: 0x100
[info] Starting FDR listener thread
[info] Connecting to FDR client at port 1082
[warn] About to do ctrl handshake
[done] Ctrl handshake done (ConnPort = 49158)
[warn] Requesting NOT TO Update Baseband
[info] Checkpoint 1621 complete with code 0
[info] Checkpoint 1540 complete with code 0
[info] Checkpoint 1679 complete with code 0
[info] About to send RootTicket…
[info] Sending RootTicket now…
[info] Done sending RootTicket
[info] Checkpoint 1547 complete with code 0
[info] Waiting for NAND (28)
[info] Checkpoint 1549 complete with code 0
[info] Updating NAND Firmware (58)
[info] Checkpoint 1550 complete with code 0
[info] Checkpoint 1551 complete with code 0
[info] Checkpoint 1628 complete with code 0
[info] Checkpoint 1552 complete with code 0
[info] Checkpoint 1555 complete with code 0
[info] Checkpoint 1662 complete with code 0
[info] Sending NORData…
[info] Found firmware path Firmware/all_flash
[erro] zip_name_locate: Firmware/all_flash/manifest
[info] Getting firmware manifest from build identity
[info] Extracting LLB.n144b.RELEASE.im4p…
[info] Personalizing IMG4 component LLB…
[info] Extracting [email protected]~watch.im4p…
[info] Personalizing IMG4 component AppleLogo…
[info] Extracting dali-ui.n144b.release.im4p…
[info] Personalizing IMG4 component Dali…
[info] Extracting DeviceTree.n144bap.im4p…
[info] Personalizing IMG4 component DeviceTree…
[info] Extracting [email protected]~watch.im4p…
[info] Personalizing IMG4 component RecoveryMode…
[info] Extracting WirelessPower.watch4.im4p…
[info] Personalizing IMG4 component WCHFirmwareUpdater…
[info] Extracting iBoot.n144b.RELEASE.im4p…
[info] Personalizing IMG4 component iBoot…
[info] Extracting sep-firmware.n144b.RELEASE.im4p…
[info] Personalizing IMG4 component RestoreSEP…
[info] Extracting sep-firmware.n144b.RELEASE.im4p…
[info] Personalizing IMG4 component SEP…
[info] Sending NORData now…
[info] Done sending NORData
[info] Checkpoint 1545 complete with code 0
[info] Checkpoint 1683 complete with code 0
[info] Unmounting filesystems (29)
[info] Checkpoint 1637 complete with code 0
[info] Checkpoint 1556 complete with code 0
[info] Checkpoint 1686 complete with code 0
[info] Checkpoint 1697 complete with code 0
[info] Checkpoint 1695 complete with code 0
[info] Checkpoint 1620 complete with code 0
[info] Checkpoint 1687 complete with code 0
[info] Checkpoint 1557 complete with code 0
[info] About to send FDR Trust data…
[info] Sending FDR Trust data now…
[done] sending FDR Trust Data
[info] Checkpoint 1558 complete with code 0
[info] Checkpoint 1559 complete with code 0
[info] Checkpoint 1560 complete with code 0
[info] Checking for uncollected logs (44)
[info] Checkpoint 1561 complete with code 0
[info] Checkpoint 1562 complete with code 0
[info] Checkpoint 1563 complete with code 0
[info] Checkpoint 1633 complete with code 0
[info] Unmounting filesystems (29)
[info] Checkpoint 1565 complete with code 0
[info] Checkpoint 1614 complete with code 0
[info] Checkpoint 1567 complete with code 0
[info] Checkpoint 1674 complete with code 0
[info] Creating partition map (11)
[info] Checkpoint 1569 complete with code 0
[info] Checkpoint 1632 complete with code 0
[info] Checkpoint 1570 complete with code 0
[info] Checkpoint 1629 complete with code 0
[info] Checkpoint 5645 complete with code 0
[info] Creating filesystem (12)
[info] Checkpoint 1624 complete with code 0
[info] Checkpoint 1625 complete with code 0
[info] Checkpoint 1626 complete with code 0
[info] About to send filesystem…
[info] Connected to ASR
[info] Validating the filesystem
[info] Filesystem validated
[info] Sending filesystem now…
[erro] Unable to send data to ASR.Sent 0 of 20 bytes.
[erro] Unable to send chunk checksum
[erro] Unable to send payload to ASR
[erro] Unable to send filesystem
[erro] Unable to successfully restore device
[info] Checkpoint 1627 complete with code 1100
[erro] Unable to restore device
[done] Operation finished!
[info] Removing USBVID_05AC&PID_12AF

phil31

Posts: 43
Joined: Thu Nov 13, 2014 3:40 pm

right procedure to send data ?

Dear,

again, my application is a web server embedded in my host CPU.
I manage to configure the ESP8266 as expected.
my AT firmware is 0020000903 and I use the hardware handshake feature.

when I send data, after the AT+CIPSEND=..,.. command, sometime I receive «SEND OK» as expected,
but others time, some strange message as «busy s…», «busy p….», «ERROR», «Fail» and some others !!

Anybody know what are the required action to do for each messages ?…
by example,
— if «busy ..» message then wait ?? what !..?
— if «ERROR» message then retry AT+CIPSEND then send again same data ?

what are the differences between «busy s» and «busy p» message ..?

thanks for any help, have nice holidays, regards
Phil


ESP_Faye

Posts: 1646
Joined: Mon Oct 27, 2014 11:08 am

Re: right procedure to send data ?

Postby ESP_Faye » Wed Dec 31, 2014 9:29 am

Hi, there are some documents about how to test AT commands might help you http://bbs.espressif.com/viewtopic.php?f=21&t=93

«busy» means the previous AT command is not finished yet, so we cannot accept the next AT command ..
«busy p» means command is doing; «busy s» means sending data is doing ..
«ERROR» means you may input an incorrect AT command..

Notice that in normal mode every time you want to send some data ,you need a «AT+SEND» command ..

Example in single connection:
AT+CIPSEND=3 // we want to send 3 bytes

>QWE // the 3 bytes data

SEND OK
AT+CIPSEND=6 // then we want to send 6 bytes

>DGFYRW // the 6 bytes data

SEND OK


phil31

Posts: 43
Joined: Thu Nov 13, 2014 3:40 pm

Re: right procedure to send data ?

Postby phil31 » Wed Dec 31, 2014 7:33 pm

Hello Faye,

thanks for your details, but it’s ever not clear in my mind !.. please :
my application use multiple connections only, so help me with such example please.

if «busy s…» : what we need to do ? pooling with «AT» then wait until «OK» by example ?
when «OK», then we can continue to send next packet ?

if «busy p…» … what to do ?

«ERROR» appear sometime only .. i can’t imagine that my host send not the right format of the command !

to send by example 6KB of data :

Code: Select all

loop 3 times
   send "AT+SIPSEND=0, 2048"
   wait for ">" which is not rn ended 
   what to do in case of others messages ?
   send 2048 bytes
   wait for "SEND OK"
   what to do in case of others messages ?
end loop

i check the WIKI, explanation are not clear :

https://github.com/espressif/esp8266_at/wiki/CIPSEND

Wrap return “>” after execute command. Enters unvarnished transmission, 20ms interval between each packet, maximum 2048 bytes per packet. When single packet containing “+++” is received, it returns to command mode.

we need to wait 20ms between each packets .. then what is the purpose of the «busy ..» message if it is too simple !?
it is not specified any chronogram or procedure..

thanks for your help

regards


ESP_Faye

Posts: 1646
Joined: Mon Oct 27, 2014 11:08 am

Re: right procedure to send data ?

Postby ESP_Faye » Sun Jan 04, 2015 9:57 am

Hi, when it shows «busy» , you can do nothing but wait till «OK»..
We need to finish the previous AT command, then accept the next one.
Thanks for your interest in ESP8266 !


phil31

Posts: 43
Joined: Thu Nov 13, 2014 3:40 pm

Re: right procedure to send data ?

Postby phil31 » Sun Jan 04, 2015 9:31 pm

Faye,

please,

when «busy» ==> wait until «OKrn»
when «busy s…» ==> what to do ?
when «busy p…» ==> what to do ?

thanks


ESP_Faye

Posts: 1646
Joined: Mon Oct 27, 2014 11:08 am

Re: right procedure to send data ?

Postby ESP_Faye » Mon Jan 05, 2015 9:54 am

Hi,

when «busy s…» ==> wait until «OKrn»
when «busy p…» ==> wait until «OKrn»

Thanks for your interest in ESP8266 !


Who is online

Users browsing this forum: No registered users and 4 guests

Problem

Attempts to export packets using IBM Rational ClearCase Multisite fail with «Error: unable to send data:»

Symptom

Generating packet works, but shipping fails.

WINDOWS

shipping_server.exe(15152): Error: unable to send data: [WINSOCK] Connection reset by peer

UNIX and Linux

shipping_server(31794)_C(3031): Error: shp_forward_request_V1: RPC: Unable to receive; errno = Connection reset by peer

  • WINDOWS

    C:temp>mkorder -data y.txt -fship <destination_server>
    Shipping order "C:tempsh_o_y.txt" generated.
    Attempting to forward/deliver generated packets...
    ---- NOTE: consult the NT event log for errors.
    mkorder(18112): Error: Store-and-forward server "C:Program Files (x86)IBMRationalSDLCClearCasebinshipping_server" failed with status 1
    mkorder(18112): Warning: Unable to send packet C:tempy.txt (see store-and-forward log)

    This corresponding error is generated in the application log of Windows Event Viewer:
    shipping_server.exe(15152): Error: unable to send data: [WINSOCK] Connection reset by peer

  • UNIX and Linux

    $ mkorder -data <file> -fship <destination_server>
    Shipping order "/var/adm/rational/clearcase/shipping/ms_ship/outgoing/sh_o_<file>_2" generated.
    Attempting to forward/deliver generated packets...

    ---- NOTE: consult log file (/var/adm/rational/clearcase/log/shipping_server_log) for errors.
    mkorder(25125): Error: Store-and-forward server "/opt/rational/clearcase/etc/shipping_server" failed with status 1
    mkorder(25125): Warning: Unable to send packet /var/adm/rational/clearcase/shipping/ms_ship/outgoing/<file> (see store-and-forward log)

    $ tail /var/adm/atria/log/shipping_server_log
    2015-11-19T02:19:49+11:00 shipping_server(25126)_C(25127): Error: unable to deliver/forward order /var/adm/rational/clearcase/shipping/ms_ship/outgoing/sh_o_sync_<file>_2
    see shipping_server_log on host '<source_server>' for more info
    2015-11-19T02:20:08+11:00 shipping_server(25470): Error: timeout waiting for transfer RPC request

Cause

If shipping worked before but does not anymore, the cause could be WAN optimization or WAN acceleration.

Environment

  • ClearCase Multisite 8.x
  • WAN network between two sites

Diagnosing The Problem

  1. Collect a network trace during the shipping operation (mkorder …).
  2. Look at the TCP OPTIONS in the trace and check whether they have Riverbed probe options.

    Note: Riverbed is a WAN optimization product.

Resolving The Problem

There are two possible solutions.

  • Exclude the source and destination servers from Riverbed configuration.
  • Accelerate multisite traffic at TCP level only and with de-duplication enabled.

[{«Product»:{«code»:»SSSH27″,»label»:»Rational ClearCase»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»Synchronization»,»Platform»:[{«code»:»PF016″,»label»:»Linux»},{«code»:»PF033″,»label»:»Windows»}],»Version»:»8.0;8.0.1″,»Edition»:»»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]

Понравилась статья? Поделить с друзьями:
  • Error unable to initialize the unity engine как исправить
  • Error unable to initialize steam api please make sure steam is running and
  • Error unable to initialize smbios library
  • Error unable to initialize main class
  • Error unable to initialize gtk is display set properly