Bad file descriptor как исправить

но флешка не стартует, просто курсор мигает

а это не флешка виновата, просто образ на вашей машине не запускается. почему – отдельный вопрос

может стоит чем то другим записывать?

записывайте тем, где

запись проходит, вроде все ок

и нет ошибок, как выше (bad file descriptor)

а что это значит PhysicalDrive0

от интерфейса программы зависит. в Windows есть несколько вариантов открыть один и тот же диск. Самое простое – по букве, можно даже с правами пользователя. Но может отвалиться, как у вас на скриншоте выше. Более экзотический вариант – по имени типа PhysicalDrive%, такое умеет, например, WinHex и некоторые другие редакторы. Наверняка Rufus тоже так открывает, но для красоты показывает диск по букве. Ну и самый экзотический – по полному пути, включающему номер USB порта, серийник флешки и т.д. Вряд ли найдется программа, что покажет такой полный путь среди вариантов открытия диска, но из программного кода – один из наиболее надежных способов найти вообще все диски.

Can’t launch Jupyter Notebook
I tried to install tensorflow then the numpy doesn’t work. So I reinstalled numpy then jupyter notebook doesn’t work at all. Whenever I open or create a new ipynb file the service will be diconnected and such error pops out:
Bad file descriptor (D:bldzeromq_1605919615529worksrcepoll.cpp:100)
Then jupyter crashes 🙁

Attach a screen shot

To Reproduce

1. launch the jupyter notebook
2. go to the notebook page (so far everything seems good)
3. open a ipynb file
4. lose connection, error pops out in the powershell prompt shell

Expected behavior
Open an ipynb file normally.

Screenshots
This is the error from the prompt

Desktop (please complete the following information):

• Windows 10 Pro
• Anaconda Powershell Prompt (mini) 4.9.2
• Jupyter Notebook 6.1.6

Additional context
I uninstalled jupyter and conda and re-install them but it doesn’t work. I still get the same error.

Before jumping right into the content directly, it’s essential to analyze the topics by asking some What and How questions. What is a Bad file descriptor error in Python? How do they occur? What are the ways that can help in solving this kind of errors? When we answer these questions, we can eventually understand the essence of this content by the end of this article.

When you don’t allow the code to perform the functions related to the file descriptors and the methods used, a Bad File Descriptor Error arises in Python, indicating the wrong way of implementing the code.

Kicking start with the basics always helps in understanding the core of the subject and hence assists in finding solutions to the most complex problems ever.

Cause of Errors Python

It’s salient to know that only by encountering many errors in code will you be highly proficient in the specific programming language. When you come across a new error, you try to detect where that error appeared from. Eventually, you start researching how to rectify the mistake.

There are even high chances of you exploring more and achieving various easier ways to apply the code better. At last, you will end up observing that your skills in the concept and knowledge about the same had grown vast.

Errors ought to occur in any possible programming language. In Python, errors generally occur when a particular code segment is not in compliance with the advised usage. Various errors are commonly faced by programmers, which include indentation, syntax, etc.

Rectifying these errors is no big deal when you review your code thoroughly. Have a complete understanding of the concepts and know enough about the right syntax to be used in the code.

What are File Descriptors in Python?

In Python, file descriptors are integers(positive) that identify the kernel’s open files kept in a table of files. They are generally non-negative values.

If found to be negative, that indicates error or a “no value” condition. They assist in performing various functions related to files. Descriptors, in general, are a unique way that Python follows to manage attributes.

They mainly help in accessing files, other input/output devices like network sockets or pipes.

File descriptors do perform various operations. They include:

• close(fd) – closes a file descriptor
• dup(fd1) – duplicates file descriptor
• fstat(fd) – returns the status of a file descriptor

The procedures mentioned above are elementary, and it’s important to know that file descriptors perform many more significant operations following the concept.

Understanding [Errno 9] Bad File Descriptor Error in Python

Have you encountered the following error message when you run your Python code when defining file directories or similar ones?

IOError:[Errno 9] Bad file descriptor

When you don’t allow the code to perform the functions related to the file descriptors and the methods used, these kinds of issues arise, indicating the wrong way of implementing the code.

Let’s understand this with an example:

<em>>>>file1=open(".bashrc")
>>>os.close(file1.fileno())
>>>def file1
close failed in file object destructor
IOError:[Errno 9] Bad file descriptor</em>

The below image shows a code with a bad file descriptor error in the Python shell.

In the above code, the del file will delete the reference of the file object specified. Now, as per the code written, the close function was not called. This forces the destructor to close the file. As this resulted in closing a file that wasn’t open in the first place, OS throws an error – Bad file descriptor.

Best Ways to Solve from [Errno 9] Bad File Descriptor in Python

• Make sure you are using a valid file descriptor number. You will get a UNIX or Python Shell- Bad file descriptor error message when you fail using the right file descriptor number. This can cause issues when you open, close or use a file.
• Use the right modes while handling file descriptors. For example to read from the file you need to use the read mode. When you choose the wrong mode, that triggers an error.
• Analyse the concept and then implement the right functions at the right segments of your code.
• Make certain whether the function to be executed through your code was executed already or not.

[Errno 9] Bad File Descriptor in Python Socket Module

Another main area in which this error is seen is in the Python socket – Socket error Bad file descriptor. When dealing with this kind of program, you can notice that you will find a Bad file descriptor error message is seen along with some issues in opening/closing or accessing the socket.

You can tackle this error by finding the right method of executing the function through the prescribed way of performing the function in accordance with the file descriptor.

One common thing that you can notice while handling errors in Python in relevance to files and file descriptors is that many of us fail to follow and implement the proper functions of the file descriptors defined in the code to perform the operations.

In addition to the above-discussed problems, this issue occurs while executing simple print statements too. You should focus on knowing if your specific file descriptors are available in the console that you are running.

This might seem simple when phrased but can cause a huge trauma to the programmer who has invested hours in writing the code. First, make sure that the specifies file descriptors are available in the console in which you run your program.

How to solve Bad File Descriptor in Python Socket module?

One way of handling this error is to calmly ignore the print statements and use alternative segments of code that serve a similar purpose.

Consider the following code –

from time import sleep
import socket
mcip = "mau5ville.com"
port = 25565
magic = "xFE"
s = socket.socket()
while 1:
    # Determine whether the server is up or down
    try:
        s.connect((mcip, port))
        s.send(magic)
        data = s.recv(1024)
        s.close()
        print(data)
    except Exception as e:
        print(e)
    sleep(60)

This error is caused when you specify a function to get executed when it has already completed doing the job. For instance, you order your code to close a file through your long lines of code. It shows an error like:

OSError: [Errno 9] Bad file descriptor

It means that the file defined in the program is already closed automatically while running the code. There lies no use in defining a separate method to perform the same task again.

Conclusion

Bad file descriptor mainly arises due to many factors that were discussed in brief above. The main fact is that they occur when the right functions do not perform in association with the file descriptors.

With clear analysis and better knowledge of the concept, one can easily detect these errors and transform the code into a successful one.

References

• Python open() function: file is a path-like object giving the pathname (absolute or relative to the current working directory) of the file to open or an integer file descriptor of the file to wrap.
• socket.socket(): If fileno is specified, the values for family, type, and proto auto-detects from the specified file descriptor.