End to end error linux

Bash syntax error: unexpected end of file

Whats the reason behind this problem? I usually work on Windows but need to transfer scripts to unix systems.

@KeesdeKooter I wouldn’t say just because something didn’t work for you that you should downvote it, clearly it worked for the 28 upvotes. A simple it didn’t work for me suffices. That’s why SO allowed multiple answers to a question because there can be multiple solutions to a problem.

Before installing maybe try (in vim) ‘:set fileformat=unix’. This worked for me in the Windows Subsystem for Linux (WSL).

Another thing to check (just occured to me):

I.e. this innocent-looking snippet will cause the same error:

To make the dumb parser happy:

+1 Also applies to code snippets with brackets like so: [[ «$#» == 1 ]] && [[ «$arg» == [1,2,3,4] ]] && printf «%s\n» «blah» || < printf "%s\n" "blahblah"; usage; >. Note that semicolon inside the squiggly brackets, just after calling some previously defined function ‘usage’. Forgetting that will get you the same syntax error: unexpected eof.

you nailed it. Actually the simple thing is the ; Every statement is being expected to end with ; so put that at the end eg: if [ -f ~/.git-completion.bash ]; then . ~/.git-completion.bash fi will produce that error, whereas if [ -f ~/.git-completion.bash ]; then . ~/.git-completion.bash; fi; will not. notice the little semi-colons at the end, ie: after .bash and fi .

I had this in a script shared with me from a zsh user. The former does work in zsh but not in sh nor bash . Wish I was 4 people so I could give this 4 upvotes

i also just got this error message by using the wrong syntax in an if clause

i debugged it by commenting bits out until it worked

an un-closed if => fi clause will raise this as well

tip: use trap to debug, if your script is huge.

I exactly forgot the «fi»! Thanks 🙂 If you could, for the benefit of everyone, elaborate a bit on your tip of using trap.

sorry for the delay, my friend. ‘the ‘trap’ command is a way to debug your scripts by esentially breaking after every line. a fuller discussion is here: stackoverflow.com/questions/9080431/…

That was useful thanks a lot. Note that the unexpected end of file error will occur as soon as the fi is hit.

Ah so, one should not write those set and trap commands into the actual script, as it says in that post you suggested might clarify your answer? You write it in the shell, and then call the script. Please do clarify, save everyone running round in circles.

Open the file in Vim and try

Convert eh line endings to unix endings and see if that solves the issue. If editing in Vim, enter the command :set fileformat=unix and save the file. Several other editors have the ability to convert line endings, such as Notepad++ or Atom

This was happening for me when I was trying to call a function using parens, e.g.

I had the problem when I wrote «if — fi» statement in one line:

if [ -f ~/.git-completion.bash ]; then . ~/.git-completion.bash fi 

Write multiline solved my problem:

if [ -f ~/.git-completion.bash ]; then . ~/.git-completion.bash fi 

You can also keep it as one line like this: if [ -f ~/.git-completion.bash ]; then . ~/.git-completion.bash; fi (note the ; near the end).

So I found this post and the answers did not help me but i was able to figure out why it gave me the error. I had a

The issue was that i copied the above code to be in a function and inadvertently tabbed the code. Need to make sure the last EOF is not tabbed.

This was exactly my case. I had EOF indented by four spaces and bash didn’t parse it because of that. Removing spaces fixed the issue.

 export SHELLOPTS set -o igncr 

in .bash_profile . This way I didn’t need to run unix2dos

FOR WINDOWS:

In my case, I was working on Windows OS and I got the same error while running autoconf.

• I simply open configure.ac file with my NOTEPAD++ IDE.
• Then I converted the File with EOL conversion into Windows (CR LF) as follows: EDIT -> EOL CONVERSION -> WINDOWS (CR LF)

Missing a closing brace on a function definition will cause this error as I just discovered.

Which of course should be like this.

I was able to cut and paste your code into a file and it ran correctly. If you execute it like this it should work:

#!/bin/bash # june 2011 if [ $# -lt 3 -o $# -gt 3 ]; then echo "Error. Usage: $0 host database username" exit 0 fi 

Note that «file.sh» must be executable:

You may be getting that error b/c of how you’re doing input (w/ a pipe, carrot, etc.). You could also try splitting the condition into two:

if [ $# -lt 3 ] || [ $# -gt 3 ]; then echo "Error. Usage: $0 host database username" exit 0 fi 

Or, since you’re using bash , you could use built-in syntax:

if [[ $# -lt 3 || $# -gt 3 ]]; then echo "Error. Usage: $0 host database username" exit 0 fi 

And, finally, you could of course just check if 3 arguments were given (clean, maintains POSIX shell compatibility):

if [ $# -ne 3 ]; then echo "Error. Usage: $0 host database username" exit 0 fi 

weird, i cut and pasted your code and it worked as expected. was there any more error output? a lot of time bash will list a line number. also, what system are you running? (Linux, MacOS, BSD, distro, etc)

In my case, there is a redundant \ in the like following:

There is NOT a \ at the end of DATA.PATH_PREFIX ./afs/kinetics400

Apparently, some versions of the shell can also emit this message when the final line of your script lacks a newline.

For those who don’t have dos2unix installed (and don’t want to install it):

Remove trailing \r character that causes this error:

Details from this StackOverflow answer. This was really helpful. https://stackoverflow.com/a/32912867/7286223

I just cut-and-pasted your example into a file; it ran fine under bash. I don’t see any problems with it.

For good measure you may want to ensure it ends with a newline, though bash shouldn’t care. (It runs for me both with and without the final newline.)

You’ll sometimes see strange errors if you’ve accidentally embedded a control character in the file. Since it’s a short script, try creating a new script by pasting it from your question here on StackOverflow, or by simply re-typing it.

What version of bash are you using? ( bash —version )

Источник

What does end-to-end disk error mean?

I have opened Disks program today and noticed that there is FAILING in the Assessment column for the SMART status. What does this error mean? Is it serious problem? I have Lenovo G50-45 laptop, disk is SEAGATE ST1000LM014-SSHD-8GB(LVD3) 1TB SSHD with 8GB NAND Flash (original disk in this latop). Update 2017-09-24: The disk has died yesterday. 1 year and 3 months have passed since 1st hint of problem. About 4 months ago I had few issues with it not booting, but I was able to make another clean install. Since yesterday the disk is non-responsive. As this was long expected I had backup of all important data.(!) The disk was about 2 years old, so that was quite premature death.

Note that if your HDD is pretty new (4 months power on time seems likely), it may be in warranty and this error may be enough to get a warranty replacement.

3 Answers 3

Hard drives, supporting this attribute

Samsung, Seagate, IBM (Hitachi), Fujitsu, Maxtor, Western Digital, Hewlett-Packard

End-to-End error S.M.A.R.T. parameter is a part of HP’s SMART IV technology and it means that after transferring through the cache RAM data buffer, the parity data between the host and the hard drive did not match. For detailed information see SMART IV Documentation from HP. Recommendations

This is a critical parameter. Degradation of this parameter may indicate imminent drive failure. Urgent data backup and hardware replacement is recommended.

I would suggest getting a replacement disk. But I have seen it also before and the disk could still have a few years of life in it.

The description of the error says that DATA IS BEING CORRUPTED. Even to extract the data you’d have to (at least) disable the cache. See my answer.

According to the description of the failing parameter, DATA IS BEING CORRUPTED when it goes through the drive’s cache. So if you plan to do ANYTHING with that disk, the first thing to do is disable that cache. Concretely: if you plan to even extract the data, first use hdparm (for example) to disable the cache. MAYBE that will allow you to extract non-corrupted data.

Another, more hackish option would be to extract say 3 full-disk images, and then compare them. Assuming that the corruption happens rarely (which must be the case, or you would have noticed without SMART), and in random points, then you might be able to find sectors with disagreements between the 3 images, and then you could choose the sector that is agreed on by 2 of the 3 images. This could be done with a short script.

About writing to the drive: if you decide that you trust the electronics even after this problem, MAYBE you could get some use from it by again disabling the cache. It would turn pretty slow, anyway, even if you dared to trust it. I wouldn’t.

Источник

syntax error: unexpected end of file

The syntax error at the unexpected end of the file line is caused due to mismatched structure of the code. The machine executes the code line by line, so the syntax needs to be correct, with proper use of quotes (“”), brackets (), and other formatting. Several code editors provide code formatting, like showing interactive colors, which can be helpful for the users. Vim shows different colors and code formatting, which removes the chances of bracket missing.

This code will discuss the following topic in this guide:

What is a Syntax Error an Unexpected End of File Error in Linux?

As the name indicated, this error is caused due to syntax error, which is a user’s side mistake. There are several types of syntax errors, for instance, the bracket is not closed, and others. When there is a syntax error in the code, the output displays the below error:

Reason: Incorrect Syntax

The below code is written to execute an if condition, which shows “Target Achieved” if the condition is satisfied else, shows the text “Target not Achieved.” However, the execution of code displays the following error message:

#!/bin/bash num1=15; num2=8; sum=$(($num1+$num2)); if [ $sum>20 ]; then echo "Target Achieved!" else echo "Target not Achieved."

Let’s check how it behaves once executed:

The error itself shows the syntax error.

Solution: Correct the Syntax (Close the if Condition)

The code shows that the “if” condition is opened but never closed. As for every “then” keyword of the if condition, the keyword “fi” is used to close that condition. The code shows that the if condition is open but not closed using the “fi” keyword, so the error can be removed after correcting the syntax error and putting the “fi” at the end of the if condition.

Let’s put the missing “fi” keyword and check its output:

#!/bin/bash num1=15; num2=8; sum=$(($num1+$num2)); if [ $sum>20 ]; then echo "Target Achieved!" else echo "Target not Achieved." fi

Run the script as follows:

The output shows the “if” condition result “Target Achieved!”, which verifies the error is removed.

Example Scenario: Bracket is Missing

Keeping the above code, now we have missed putting the bracket while calculating the sum of the two variables.

#!/bin/bash num1=15; num2=8; sum=$(($num1+$num2); if [ $sum>20 ]; then echo "Target Achieved!" else echo "Target not Achieved." fi

The error shows there is something wrong with the syntax.

Solution of Example Scenario: Insert the Missing Bracket

Let’s correct the error by putting the “)” and executing it. The below code is corrected by putting the missing “)”, let’s execute it:

#!/bin/bash num1=15; num2=8; sum=$(($num1+$num2)); if [ $sum>20 ]; then echo "Target Achieved!" else echo "Target not Achieved." fi

Now, the script is executed:

The error-free output shows the syntax error is removed.

Similarly, if you are getting this error, you must check the syntax you have followed in writing a program.

Conclusion

The error “syntax error: unexpected end of file” occurs due to the mismatched structure of the code (incorrect syntax). Examples of it are missing the bracket or not closing the condition (after which the file is terminated). To counter this, you need to look at the syntax and fix all the errors to solve “syntax error: unexpected end of file”.

Источник