View Single Post
Old 12-03-2012, 04:50 PM   #29
knc1
Embedded Cheerleader
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,441
Karma: 5840130
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by ixtab View Post
This is indeed an unexpected failure. The relevant part is in line 332 of jailbreak.sh:

Code:
cp -f "$current" "$backup" && log "Backed up diags passwords to ${backup_relative} on diags partition" || fail "Failed to backup original diags passwords"
It seems like the cp command failed - but it really, really shouldn't, and I have no idea why it did. Does anybody have a clue?

@aceflor: do you keep getting this error every time? As said, you can re-install the jailbreak as many times as you want. Maybe the failure just miraculously goes away on the second attempt...
Two possibilities there -

Is the copy being made to a partition with limited space? (since you don't report the error return code, we can't say if it is -ENOSPC or not).

The "log" command might have failed -
Similar types of problems (-ENOSPC) plus those associated with giving syslog-ng a chance to run enough to keep up with the messages.

Note: Complicated shell expressions, any part of which might fail, can be hell to debug.
It would be better to capture the return code(s) and then either continue or report them.
knc1 is offline   Reply With Quote