You are not logged in.
Pages: 1
Hello
Do not be tired.
I'm really busy for two days trying to solve the problem of formatting the flash!
Let me tell you the whole story to see if my flash memory is burned or repaired?
In Linux, I formatted the flash with FAT format, and I played two gigs of music and put it in the car recorder, but it did not open and gave an error! I came and upgraded my Windows 10 and cleaned it from the command prompt environment and format the flash memory and it was formatted! Then I wanted to transfer the songs to flash memory again, which was almost in the middle of copying the songs, when the copy speed dropped sharply and I canceled the copy and reconnected the flash memory to the computer in Windows, but it didn't work! I could not format or even open my flash drive at all!
Now I entered my Linux manjar and then connected the flash memory here and opened the terminal and ran the following commands:
sudo dd if = / dev / zero of = / dev / sdb bs = 4MAnd then the quick ctrl + c that I press comes out and then I type the following command:
[spy @ Linux Desktop] $ sudo fdisk / dev / sdb
Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
fdisk: cannot open / dev / sdb: No such file or directoryCan my flash drive be repaired or burned?
Only progress!
Offline
Why are there spaces in all those paths? From the output I suspect you just added that when posting to the forums - but WHY? Post the ACTUAL commands and output, unmodified. And why would you enter a dd command then use Ctrl-C to break it part way through?
But perhaps more relevant:
Now I entered my Linux manjar
You mean manjaro? That is not supported here.
Last edited by Trilby (2020-12-02 15:47:40)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I am leaving this open -- for now -- as I want to find out about the spaces in the paths. How did you install Arch Linux? On the surface, you seem to not understand pathnames.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Hello
Do not be tired.
I'm really busy for two days trying to solve the problem of formatting the flash!
Let me tell you the whole story to see if my flash memory is burned or repaired?
In Linux, I formatted the flash with FAT format, and I played two gigs of music and put it in the car recorder, but it did not open and gave an error! I came and upgraded my Windows 10 and cleaned it from the command prompt environment and format the flash memory and it was formatted! Then I wanted to transfer the songs to flash memory again, which was almost in the middle of copying the songs, when the copy speed dropped sharply and I canceled the copy and reconnected the flash memory to the computer in Windows, but it didn't work! I could not format or even open my flash drive at all!
Now I entered my Linux manjar and then connected the flash memory here and opened the terminal and ran the following commands:sudo dd if = / dev / zero of = / dev / sdb bs = 4MAnd then the quick ctrl + c that I press comes out and then I type the following command:
[spy @ Linux Desktop] $ sudo fdisk / dev / sdb Welcome to fdisk (util-linux 2.36.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open / dev / sdb: No such file or directoryCan my flash drive be repaired or burned?
Have you tried removing spaces in your commands ? spaces are making your paths invalid !
sudo dd if=/dev/zero of=/dev/sdb bs=4M
sudo fdisk /dev/sdbFilesystem paths in GNU/Linux have tree hierarchy (eg: /one/two/three/...), they are usually perceeded with "/" and there is no space between them with slash
Offline
A literal "fdisk / dev / sdb" would get you a different error (bad usage) - it's probably because of some translation service…
@SPYAM, run "dmesg -w" and when it's done printing stuff, inject the usb key.
Watch the following output (if any)
Online
Pages: 1