dd doesn't overwrite the disk2019 Community Moderator ElectionWhy is dd not protected against writing on the active disk ?How to inspect the contents of /dev/sdt?Overwritten superblock and dd backup files recoveryBroken disk size after incomplete dd operationAccidentally ejected sd card physically while ddCan't mount disksErrors on cloning disk with catZero Disk SpaceI have a dedicated with 2 SSDs, how to I group them to behave as 1?Can recover data from disk but not from image of same disk?
Pre-mixing cryogenic fuels and using only one fuel tank
How could a planet have erratic days?
Why can Carol Danvers change her suit colours in the first place?
It grows, but water kills it
creating a ":KeepCursor" command
What should you do if you miss a job interview (deliberately)?
What if a revenant (monster) gains fire resistance?
Add big quotation marks inside my colorbox
How do apertures which seem too large to physically fit work?
Quoting Keynes in a lecture
Limits and Infinite Integration by Parts
What are the advantages of simplicial model categories over non-simplicial ones?
What is the highest possible scrabble score for placing a single tile
Does the UK parliament need to pass secondary legislation to accept the Article 50 extension
How to explain what's wrong with this application of the chain rule?
Biological Blimps: Propulsion
How to hide some fields of struct in C?
Mixing PEX brands
What to do when eye contact makes your subordinate uncomfortable?
Calculating total slots
This is why we puzzle
How can mimic phobia be cured?
What are some good ways to treat frozen vegetables such that they behave like fresh vegetables when stir frying them?
Is there a RAID 0 Equivalent for RAM?
dd doesn't overwrite the disk
2019 Community Moderator ElectionWhy is dd not protected against writing on the active disk ?How to inspect the contents of /dev/sdt?Overwritten superblock and dd backup files recoveryBroken disk size after incomplete dd operationAccidentally ejected sd card physically while ddCan't mount disksErrors on cloning disk with catZero Disk SpaceI have a dedicated with 2 SSDs, how to I group them to behave as 1?Can recover data from disk but not from image of same disk?
I am running Ubuntu 18.04.1 in a Virtual Machine (VMWare) on a Windows host. I am trying to zero out an entire SD card using dd. This is part of the process I use to release embedded Linux to the software group (SD card images compress much better when the empty FS data is all 0).
The command I am using is: sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress and it completes successfully; I get the printout of records transferred, and a message saying no space left on device. If I then do a sudo cat /dev/sdc | hexdump to look at the disk contents though, the disk is still full of data and isn't zeroes (and not just at the end).
Do I have to specify the number of bytes of the SD card for it to work consistently? I don't have this issue every time I zero out an SD card.
Complete console output:
gen-ccm-root@ubuntu:~$ sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress
15929966592 bytes (16 GB, 15 GiB) copied, 1274 s, 12.5 MB/s
dd: error writing '/dev/sdc': No space left on device
3799+0 records in
3798+0 records out
15931539456 bytes (16 GB, 15 GiB) copied, 1274.19 s, 12.5 MB/s
gen-ccm-root@ubuntu:~$ sudo cat /dev/sdc | hexdump
[sudo] password for gen-ccm-root:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0101000 2004 0000 6004 0000 0000 0000 0000 0000
0101010 0000 0000 0000 0000 0000 0000 0000 0000
*
0101400 2005 0000 6005 0000 0000 0000 0000 0000
...
dd disk
|
show 1 more comment
I am running Ubuntu 18.04.1 in a Virtual Machine (VMWare) on a Windows host. I am trying to zero out an entire SD card using dd. This is part of the process I use to release embedded Linux to the software group (SD card images compress much better when the empty FS data is all 0).
The command I am using is: sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress and it completes successfully; I get the printout of records transferred, and a message saying no space left on device. If I then do a sudo cat /dev/sdc | hexdump to look at the disk contents though, the disk is still full of data and isn't zeroes (and not just at the end).
Do I have to specify the number of bytes of the SD card for it to work consistently? I don't have this issue every time I zero out an SD card.
Complete console output:
gen-ccm-root@ubuntu:~$ sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress
15929966592 bytes (16 GB, 15 GiB) copied, 1274 s, 12.5 MB/s
dd: error writing '/dev/sdc': No space left on device
3799+0 records in
3798+0 records out
15931539456 bytes (16 GB, 15 GiB) copied, 1274.19 s, 12.5 MB/s
gen-ccm-root@ubuntu:~$ sudo cat /dev/sdc | hexdump
[sudo] password for gen-ccm-root:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0101000 2004 0000 6004 0000 0000 0000 0000 0000
0101010 0000 0000 0000 0000 0000 0000 0000 0000
*
0101400 2005 0000 6005 0000 0000 0000 0000 0000
...
dd disk
2
Can you try the same with badblocks -t 0x0000 -sw /dev/sdc (dangerous, it will write zero data too)
– Luciano Andress Martini
yesterday
Your question makes sense until “I don't have this issue every time I zero out an SD card.” I then wonder if I miss-read the start. Do you mean “I don't have this problem every time”?
– ctrl-alt-delor
yesterday
2
I didn't actually know badblocks existed, which is a good thing to learn. Correct I don't have this issue every time. Today was the first time that it has been consistent. badblocks is slow, but if I am reading the output correctly (7234624 done, 39:10 elapsed. (0/0/2417408 errors)) it looks like my SD card might be toast (A different question implies the last number is corruptions), which is unfortunate since it was new less than a week ago. I guess I just got lucky since I have been burning new kernels on it for the past week and they all worked fine.
– Eskimoalva
yesterday
1
Yes it is probably lost, but before saying this try with another sd card or in another machine. RAM errors can cause this too, because it will compare a value stored in RAM with a value found in the sdcard. It may run almost eternally depending on the damage you are experiencing the command dmesg will show important informations too.
– Luciano Andress Martini
yesterday
1
I jsut got another new SD card and it appears to be working fine.
– Eskimoalva
yesterday
|
show 1 more comment
I am running Ubuntu 18.04.1 in a Virtual Machine (VMWare) on a Windows host. I am trying to zero out an entire SD card using dd. This is part of the process I use to release embedded Linux to the software group (SD card images compress much better when the empty FS data is all 0).
The command I am using is: sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress and it completes successfully; I get the printout of records transferred, and a message saying no space left on device. If I then do a sudo cat /dev/sdc | hexdump to look at the disk contents though, the disk is still full of data and isn't zeroes (and not just at the end).
Do I have to specify the number of bytes of the SD card for it to work consistently? I don't have this issue every time I zero out an SD card.
Complete console output:
gen-ccm-root@ubuntu:~$ sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress
15929966592 bytes (16 GB, 15 GiB) copied, 1274 s, 12.5 MB/s
dd: error writing '/dev/sdc': No space left on device
3799+0 records in
3798+0 records out
15931539456 bytes (16 GB, 15 GiB) copied, 1274.19 s, 12.5 MB/s
gen-ccm-root@ubuntu:~$ sudo cat /dev/sdc | hexdump
[sudo] password for gen-ccm-root:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0101000 2004 0000 6004 0000 0000 0000 0000 0000
0101010 0000 0000 0000 0000 0000 0000 0000 0000
*
0101400 2005 0000 6005 0000 0000 0000 0000 0000
...
dd disk
I am running Ubuntu 18.04.1 in a Virtual Machine (VMWare) on a Windows host. I am trying to zero out an entire SD card using dd. This is part of the process I use to release embedded Linux to the software group (SD card images compress much better when the empty FS data is all 0).
The command I am using is: sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress and it completes successfully; I get the printout of records transferred, and a message saying no space left on device. If I then do a sudo cat /dev/sdc | hexdump to look at the disk contents though, the disk is still full of data and isn't zeroes (and not just at the end).
Do I have to specify the number of bytes of the SD card for it to work consistently? I don't have this issue every time I zero out an SD card.
Complete console output:
gen-ccm-root@ubuntu:~$ sudo dd if=/dev/zero of=/dev/sdc bs=4M status=progress
15929966592 bytes (16 GB, 15 GiB) copied, 1274 s, 12.5 MB/s
dd: error writing '/dev/sdc': No space left on device
3799+0 records in
3798+0 records out
15931539456 bytes (16 GB, 15 GiB) copied, 1274.19 s, 12.5 MB/s
gen-ccm-root@ubuntu:~$ sudo cat /dev/sdc | hexdump
[sudo] password for gen-ccm-root:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0101000 2004 0000 6004 0000 0000 0000 0000 0000
0101010 0000 0000 0000 0000 0000 0000 0000 0000
*
0101400 2005 0000 6005 0000 0000 0000 0000 0000
...
dd disk
dd disk
asked yesterday
EskimoalvaEskimoalva
284
284
2
Can you try the same with badblocks -t 0x0000 -sw /dev/sdc (dangerous, it will write zero data too)
– Luciano Andress Martini
yesterday
Your question makes sense until “I don't have this issue every time I zero out an SD card.” I then wonder if I miss-read the start. Do you mean “I don't have this problem every time”?
– ctrl-alt-delor
yesterday
2
I didn't actually know badblocks existed, which is a good thing to learn. Correct I don't have this issue every time. Today was the first time that it has been consistent. badblocks is slow, but if I am reading the output correctly (7234624 done, 39:10 elapsed. (0/0/2417408 errors)) it looks like my SD card might be toast (A different question implies the last number is corruptions), which is unfortunate since it was new less than a week ago. I guess I just got lucky since I have been burning new kernels on it for the past week and they all worked fine.
– Eskimoalva
yesterday
1
Yes it is probably lost, but before saying this try with another sd card or in another machine. RAM errors can cause this too, because it will compare a value stored in RAM with a value found in the sdcard. It may run almost eternally depending on the damage you are experiencing the command dmesg will show important informations too.
– Luciano Andress Martini
yesterday
1
I jsut got another new SD card and it appears to be working fine.
– Eskimoalva
yesterday
|
show 1 more comment
2
Can you try the same with badblocks -t 0x0000 -sw /dev/sdc (dangerous, it will write zero data too)
– Luciano Andress Martini
yesterday
Your question makes sense until “I don't have this issue every time I zero out an SD card.” I then wonder if I miss-read the start. Do you mean “I don't have this problem every time”?
– ctrl-alt-delor
yesterday
2
I didn't actually know badblocks existed, which is a good thing to learn. Correct I don't have this issue every time. Today was the first time that it has been consistent. badblocks is slow, but if I am reading the output correctly (7234624 done, 39:10 elapsed. (0/0/2417408 errors)) it looks like my SD card might be toast (A different question implies the last number is corruptions), which is unfortunate since it was new less than a week ago. I guess I just got lucky since I have been burning new kernels on it for the past week and they all worked fine.
– Eskimoalva
yesterday
1
Yes it is probably lost, but before saying this try with another sd card or in another machine. RAM errors can cause this too, because it will compare a value stored in RAM with a value found in the sdcard. It may run almost eternally depending on the damage you are experiencing the command dmesg will show important informations too.
– Luciano Andress Martini
yesterday
1
I jsut got another new SD card and it appears to be working fine.
– Eskimoalva
yesterday
2
2
Can you try the same with badblocks -t 0x0000 -sw /dev/sdc (dangerous, it will write zero data too)
– Luciano Andress Martini
yesterday
Can you try the same with badblocks -t 0x0000 -sw /dev/sdc (dangerous, it will write zero data too)
– Luciano Andress Martini
yesterday
Your question makes sense until “I don't have this issue every time I zero out an SD card.” I then wonder if I miss-read the start. Do you mean “I don't have this problem every time”?
– ctrl-alt-delor
yesterday
Your question makes sense until “I don't have this issue every time I zero out an SD card.” I then wonder if I miss-read the start. Do you mean “I don't have this problem every time”?
– ctrl-alt-delor
yesterday
2
2
I didn't actually know badblocks existed, which is a good thing to learn. Correct I don't have this issue every time. Today was the first time that it has been consistent. badblocks is slow, but if I am reading the output correctly (
7234624 done, 39:10 elapsed. (0/0/2417408 errors)) it looks like my SD card might be toast (A different question implies the last number is corruptions), which is unfortunate since it was new less than a week ago. I guess I just got lucky since I have been burning new kernels on it for the past week and they all worked fine.– Eskimoalva
yesterday
I didn't actually know badblocks existed, which is a good thing to learn. Correct I don't have this issue every time. Today was the first time that it has been consistent. badblocks is slow, but if I am reading the output correctly (
7234624 done, 39:10 elapsed. (0/0/2417408 errors)) it looks like my SD card might be toast (A different question implies the last number is corruptions), which is unfortunate since it was new less than a week ago. I guess I just got lucky since I have been burning new kernels on it for the past week and they all worked fine.– Eskimoalva
yesterday
1
1
Yes it is probably lost, but before saying this try with another sd card or in another machine. RAM errors can cause this too, because it will compare a value stored in RAM with a value found in the sdcard. It may run almost eternally depending on the damage you are experiencing the command dmesg will show important informations too.
– Luciano Andress Martini
yesterday
Yes it is probably lost, but before saying this try with another sd card or in another machine. RAM errors can cause this too, because it will compare a value stored in RAM with a value found in the sdcard. It may run almost eternally depending on the damage you are experiencing the command dmesg will show important informations too.
– Luciano Andress Martini
yesterday
1
1
I jsut got another new SD card and it appears to be working fine.
– Eskimoalva
yesterday
I jsut got another new SD card and it appears to be working fine.
– Eskimoalva
yesterday
|
show 1 more comment
2 Answers
2
active
oldest
votes
As said in the comments, the sdcard was with badblocks.
The solution I proposed was to run:
badblocks -t 0x0000 -sw /dev/sdc
CAUTION: this is data destructive like dd if=/dev/zero.
And the user received something like:
7234624 done, 39:10 elapsed. (0/0/2417408 errors)
Showing the sdcard was damaged.
The sdcard was replaced and the problem was solved.
looking for errors is a decent idea, but fwiw this is a bit of a tautology. The last figure apparently shows when badblocks reads a sector and it does not match the value that badblocks just wrote to it.
– sourcejedi
yesterday
@sourcejedi I did not understand what you say, my first language is Portuguese. What do you mean?
– Luciano Andress Martini
yesterday
0/0/2417408means no write errors, no read errors, but the data returned by 2417408 reads did not match the data that was written. But, that's what we already saw in the question :-).
– sourcejedi
22 hours ago
1
By that logic we did not need to runbadblocks. It was just another way to run the same test. But apart from that, the principle is good, I agree with the conclusion you reached.
– sourcejedi
22 hours ago
add a comment |
use
sudo fdsik -l
and see result for example:
/dev/mmcblk0
/dev/mmcblk01
/dev/mmcblk02
it's maybe different in your output!
now you should use:
sudo dd bs=4M if=exmple.img of=**/dev/mmcblk0** conv=fsync status=progress
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why are you reading from what looks like a filesystem image? What difference does theconvsetting do? Why do you think they're using the wrong device to write to?
– Kusalananda
yesterday
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507740%2fdd-doesnt-overwrite-the-disk%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
As said in the comments, the sdcard was with badblocks.
The solution I proposed was to run:
badblocks -t 0x0000 -sw /dev/sdc
CAUTION: this is data destructive like dd if=/dev/zero.
And the user received something like:
7234624 done, 39:10 elapsed. (0/0/2417408 errors)
Showing the sdcard was damaged.
The sdcard was replaced and the problem was solved.
looking for errors is a decent idea, but fwiw this is a bit of a tautology. The last figure apparently shows when badblocks reads a sector and it does not match the value that badblocks just wrote to it.
– sourcejedi
yesterday
@sourcejedi I did not understand what you say, my first language is Portuguese. What do you mean?
– Luciano Andress Martini
yesterday
0/0/2417408means no write errors, no read errors, but the data returned by 2417408 reads did not match the data that was written. But, that's what we already saw in the question :-).
– sourcejedi
22 hours ago
1
By that logic we did not need to runbadblocks. It was just another way to run the same test. But apart from that, the principle is good, I agree with the conclusion you reached.
– sourcejedi
22 hours ago
add a comment |
As said in the comments, the sdcard was with badblocks.
The solution I proposed was to run:
badblocks -t 0x0000 -sw /dev/sdc
CAUTION: this is data destructive like dd if=/dev/zero.
And the user received something like:
7234624 done, 39:10 elapsed. (0/0/2417408 errors)
Showing the sdcard was damaged.
The sdcard was replaced and the problem was solved.
looking for errors is a decent idea, but fwiw this is a bit of a tautology. The last figure apparently shows when badblocks reads a sector and it does not match the value that badblocks just wrote to it.
– sourcejedi
yesterday
@sourcejedi I did not understand what you say, my first language is Portuguese. What do you mean?
– Luciano Andress Martini
yesterday
0/0/2417408means no write errors, no read errors, but the data returned by 2417408 reads did not match the data that was written. But, that's what we already saw in the question :-).
– sourcejedi
22 hours ago
1
By that logic we did not need to runbadblocks. It was just another way to run the same test. But apart from that, the principle is good, I agree with the conclusion you reached.
– sourcejedi
22 hours ago
add a comment |
As said in the comments, the sdcard was with badblocks.
The solution I proposed was to run:
badblocks -t 0x0000 -sw /dev/sdc
CAUTION: this is data destructive like dd if=/dev/zero.
And the user received something like:
7234624 done, 39:10 elapsed. (0/0/2417408 errors)
Showing the sdcard was damaged.
The sdcard was replaced and the problem was solved.
As said in the comments, the sdcard was with badblocks.
The solution I proposed was to run:
badblocks -t 0x0000 -sw /dev/sdc
CAUTION: this is data destructive like dd if=/dev/zero.
And the user received something like:
7234624 done, 39:10 elapsed. (0/0/2417408 errors)
Showing the sdcard was damaged.
The sdcard was replaced and the problem was solved.
edited yesterday
answered yesterday
Luciano Andress MartiniLuciano Andress Martini
4,0951136
4,0951136
looking for errors is a decent idea, but fwiw this is a bit of a tautology. The last figure apparently shows when badblocks reads a sector and it does not match the value that badblocks just wrote to it.
– sourcejedi
yesterday
@sourcejedi I did not understand what you say, my first language is Portuguese. What do you mean?
– Luciano Andress Martini
yesterday
0/0/2417408means no write errors, no read errors, but the data returned by 2417408 reads did not match the data that was written. But, that's what we already saw in the question :-).
– sourcejedi
22 hours ago
1
By that logic we did not need to runbadblocks. It was just another way to run the same test. But apart from that, the principle is good, I agree with the conclusion you reached.
– sourcejedi
22 hours ago
add a comment |
looking for errors is a decent idea, but fwiw this is a bit of a tautology. The last figure apparently shows when badblocks reads a sector and it does not match the value that badblocks just wrote to it.
– sourcejedi
yesterday
@sourcejedi I did not understand what you say, my first language is Portuguese. What do you mean?
– Luciano Andress Martini
yesterday
0/0/2417408means no write errors, no read errors, but the data returned by 2417408 reads did not match the data that was written. But, that's what we already saw in the question :-).
– sourcejedi
22 hours ago
1
By that logic we did not need to runbadblocks. It was just another way to run the same test. But apart from that, the principle is good, I agree with the conclusion you reached.
– sourcejedi
22 hours ago
looking for errors is a decent idea, but fwiw this is a bit of a tautology. The last figure apparently shows when badblocks reads a sector and it does not match the value that badblocks just wrote to it.
– sourcejedi
yesterday
looking for errors is a decent idea, but fwiw this is a bit of a tautology. The last figure apparently shows when badblocks reads a sector and it does not match the value that badblocks just wrote to it.
– sourcejedi
yesterday
@sourcejedi I did not understand what you say, my first language is Portuguese. What do you mean?
– Luciano Andress Martini
yesterday
@sourcejedi I did not understand what you say, my first language is Portuguese. What do you mean?
– Luciano Andress Martini
yesterday
0/0/2417408 means no write errors, no read errors, but the data returned by 2417408 reads did not match the data that was written. But, that's what we already saw in the question :-).– sourcejedi
22 hours ago
0/0/2417408 means no write errors, no read errors, but the data returned by 2417408 reads did not match the data that was written. But, that's what we already saw in the question :-).– sourcejedi
22 hours ago
1
1
By that logic we did not need to run
badblocks. It was just another way to run the same test. But apart from that, the principle is good, I agree with the conclusion you reached.– sourcejedi
22 hours ago
By that logic we did not need to run
badblocks. It was just another way to run the same test. But apart from that, the principle is good, I agree with the conclusion you reached.– sourcejedi
22 hours ago
add a comment |
use
sudo fdsik -l
and see result for example:
/dev/mmcblk0
/dev/mmcblk01
/dev/mmcblk02
it's maybe different in your output!
now you should use:
sudo dd bs=4M if=exmple.img of=**/dev/mmcblk0** conv=fsync status=progress
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why are you reading from what looks like a filesystem image? What difference does theconvsetting do? Why do you think they're using the wrong device to write to?
– Kusalananda
yesterday
add a comment |
use
sudo fdsik -l
and see result for example:
/dev/mmcblk0
/dev/mmcblk01
/dev/mmcblk02
it's maybe different in your output!
now you should use:
sudo dd bs=4M if=exmple.img of=**/dev/mmcblk0** conv=fsync status=progress
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why are you reading from what looks like a filesystem image? What difference does theconvsetting do? Why do you think they're using the wrong device to write to?
– Kusalananda
yesterday
add a comment |
use
sudo fdsik -l
and see result for example:
/dev/mmcblk0
/dev/mmcblk01
/dev/mmcblk02
it's maybe different in your output!
now you should use:
sudo dd bs=4M if=exmple.img of=**/dev/mmcblk0** conv=fsync status=progress
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
use
sudo fdsik -l
and see result for example:
/dev/mmcblk0
/dev/mmcblk01
/dev/mmcblk02
it's maybe different in your output!
now you should use:
sudo dd bs=4M if=exmple.img of=**/dev/mmcblk0** conv=fsync status=progress
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
farhad azimifarhad azimi
312
312
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
farhad azimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Why are you reading from what looks like a filesystem image? What difference does theconvsetting do? Why do you think they're using the wrong device to write to?
– Kusalananda
yesterday
add a comment |
Why are you reading from what looks like a filesystem image? What difference does theconvsetting do? Why do you think they're using the wrong device to write to?
– Kusalananda
yesterday
Why are you reading from what looks like a filesystem image? What difference does the
conv setting do? Why do you think they're using the wrong device to write to?– Kusalananda
yesterday
Why are you reading from what looks like a filesystem image? What difference does the
conv setting do? Why do you think they're using the wrong device to write to?– Kusalananda
yesterday
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507740%2fdd-doesnt-overwrite-the-disk%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Can you try the same with badblocks -t 0x0000 -sw /dev/sdc (dangerous, it will write zero data too)
– Luciano Andress Martini
yesterday
Your question makes sense until “I don't have this issue every time I zero out an SD card.” I then wonder if I miss-read the start. Do you mean “I don't have this problem every time”?
– ctrl-alt-delor
yesterday
2
I didn't actually know badblocks existed, which is a good thing to learn. Correct I don't have this issue every time. Today was the first time that it has been consistent. badblocks is slow, but if I am reading the output correctly (
7234624 done, 39:10 elapsed. (0/0/2417408 errors)) it looks like my SD card might be toast (A different question implies the last number is corruptions), which is unfortunate since it was new less than a week ago. I guess I just got lucky since I have been burning new kernels on it for the past week and they all worked fine.– Eskimoalva
yesterday
1
Yes it is probably lost, but before saying this try with another sd card or in another machine. RAM errors can cause this too, because it will compare a value stored in RAM with a value found in the sdcard. It may run almost eternally depending on the damage you are experiencing the command dmesg will show important informations too.
– Luciano Andress Martini
yesterday
1
I jsut got another new SD card and it appears to be working fine.
– Eskimoalva
yesterday