dd command appears unresponsive when attempting to create bootable USB media in Debian?












0















I'm attempting to mount an Ubuntu .iso to a USB drive using the dd command in Debian, however I'm having trouble. Below is the process I've been using thus far:




  1. Format the disk I want to mount the .iso to (now the Device ID is /dev/sde)

  2. Enter su in a terminal to grant root access and enter password

  3. Enter umount /dev/sde (Just for good measure, I'm aware the disk is already unmounted)

  4. Enter dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde


Now, in the past when I've used this in other distros it's worked just fine and I could carry on to sync, and then boot up using the newly created media. However in Debian it seems to become totally unresponsive after entering the command in step 4, simply giving me a cursor on the next line down with no shell prompt. It will stay this way until I remove the USB drive from my system. After re-inserting the drive the 'Disks' application shows that partitions have been created and that Ubuntu has been written to the drive, however when attempting to boot from the drive I get taken straight to the gnome recovery terminal where it informs me that some executable is missing. I'm assuming here that the problem lies with Debian.






debian terminal dd







share|improve this question

























  • Any messages from dmesg or when you run strace on the dd process?

    – Raman Sailopal
    Sep 18 '17 at 15:15











  • Apologies, typo, I meant to say that it becomes unresponsive after step 4. I'll edit my post now.

    – Meta
    Sep 18 '17 at 15:18











  • @Raman - I've not actually ran those before? Give me a couple minutes and I'll post the result here.

    – Meta
    Sep 18 '17 at 15:19






  • 2





    Try running iostat 5 in another window before running the dd. The read and write rates should increase until they level off. Do you see the i/o stop at any point? What speeds do you see? Some flash drives have write rates of 3 or 4 MB/sec, so it may take 20 minutes or more to write a DVD image.

    – Mark Plotnick
    Sep 18 '17 at 15:22











  • @Mark - When attempting to run the iostat 5 command as suggested I get the following error: bash: iostat: command not found

    – Meta
    Sep 18 '17 at 15:26


















0















I'm attempting to mount an Ubuntu .iso to a USB drive using the dd command in Debian, however I'm having trouble. Below is the process I've been using thus far:




  1. Format the disk I want to mount the .iso to (now the Device ID is /dev/sde)

  2. Enter su in a terminal to grant root access and enter password

  3. Enter umount /dev/sde (Just for good measure, I'm aware the disk is already unmounted)

  4. Enter dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde


Now, in the past when I've used this in other distros it's worked just fine and I could carry on to sync, and then boot up using the newly created media. However in Debian it seems to become totally unresponsive after entering the command in step 4, simply giving me a cursor on the next line down with no shell prompt. It will stay this way until I remove the USB drive from my system. After re-inserting the drive the 'Disks' application shows that partitions have been created and that Ubuntu has been written to the drive, however when attempting to boot from the drive I get taken straight to the gnome recovery terminal where it informs me that some executable is missing. I'm assuming here that the problem lies with Debian.






debian terminal dd







share|improve this question

























  • Any messages from dmesg or when you run strace on the dd process?

    – Raman Sailopal
    Sep 18 '17 at 15:15











  • Apologies, typo, I meant to say that it becomes unresponsive after step 4. I'll edit my post now.

    – Meta
    Sep 18 '17 at 15:18











  • @Raman - I've not actually ran those before? Give me a couple minutes and I'll post the result here.

    – Meta
    Sep 18 '17 at 15:19






  • 2





    Try running iostat 5 in another window before running the dd. The read and write rates should increase until they level off. Do you see the i/o stop at any point? What speeds do you see? Some flash drives have write rates of 3 or 4 MB/sec, so it may take 20 minutes or more to write a DVD image.

    – Mark Plotnick
    Sep 18 '17 at 15:22











  • @Mark - When attempting to run the iostat 5 command as suggested I get the following error: bash: iostat: command not found

    – Meta
    Sep 18 '17 at 15:26
















0












0








0








I'm attempting to mount an Ubuntu .iso to a USB drive using the dd command in Debian, however I'm having trouble. Below is the process I've been using thus far:




  1. Format the disk I want to mount the .iso to (now the Device ID is /dev/sde)

  2. Enter su in a terminal to grant root access and enter password

  3. Enter umount /dev/sde (Just for good measure, I'm aware the disk is already unmounted)

  4. Enter dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde


Now, in the past when I've used this in other distros it's worked just fine and I could carry on to sync, and then boot up using the newly created media. However in Debian it seems to become totally unresponsive after entering the command in step 4, simply giving me a cursor on the next line down with no shell prompt. It will stay this way until I remove the USB drive from my system. After re-inserting the drive the 'Disks' application shows that partitions have been created and that Ubuntu has been written to the drive, however when attempting to boot from the drive I get taken straight to the gnome recovery terminal where it informs me that some executable is missing. I'm assuming here that the problem lies with Debian.






debian terminal dd







share|improve this question
















I'm attempting to mount an Ubuntu .iso to a USB drive using the dd command in Debian, however I'm having trouble. Below is the process I've been using thus far:




  1. Format the disk I want to mount the .iso to (now the Device ID is /dev/sde)

  2. Enter su in a terminal to grant root access and enter password

  3. Enter umount /dev/sde (Just for good measure, I'm aware the disk is already unmounted)

  4. Enter dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde


Now, in the past when I've used this in other distros it's worked just fine and I could carry on to sync, and then boot up using the newly created media. However in Debian it seems to become totally unresponsive after entering the command in step 4, simply giving me a cursor on the next line down with no shell prompt. It will stay this way until I remove the USB drive from my system. After re-inserting the drive the 'Disks' application shows that partitions have been created and that Ubuntu has been written to the drive, however when attempting to boot from the drive I get taken straight to the gnome recovery terminal where it informs me that some executable is missing. I'm assuming here that the problem lies with Debian.






debian terminal dd




debian terminal dd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago









Rui F Ribeiro

41.5k1483140




41.5k1483140










asked Sep 18 '17 at 15:05









MetaMeta

11




11













  • Any messages from dmesg or when you run strace on the dd process?

    – Raman Sailopal
    Sep 18 '17 at 15:15











  • Apologies, typo, I meant to say that it becomes unresponsive after step 4. I'll edit my post now.

    – Meta
    Sep 18 '17 at 15:18











  • @Raman - I've not actually ran those before? Give me a couple minutes and I'll post the result here.

    – Meta
    Sep 18 '17 at 15:19






  • 2





    Try running iostat 5 in another window before running the dd. The read and write rates should increase until they level off. Do you see the i/o stop at any point? What speeds do you see? Some flash drives have write rates of 3 or 4 MB/sec, so it may take 20 minutes or more to write a DVD image.

    – Mark Plotnick
    Sep 18 '17 at 15:22











  • @Mark - When attempting to run the iostat 5 command as suggested I get the following error: bash: iostat: command not found

    – Meta
    Sep 18 '17 at 15:26





















  • Any messages from dmesg or when you run strace on the dd process?

    – Raman Sailopal
    Sep 18 '17 at 15:15











  • Apologies, typo, I meant to say that it becomes unresponsive after step 4. I'll edit my post now.

    – Meta
    Sep 18 '17 at 15:18











  • @Raman - I've not actually ran those before? Give me a couple minutes and I'll post the result here.

    – Meta
    Sep 18 '17 at 15:19






  • 2





    Try running iostat 5 in another window before running the dd. The read and write rates should increase until they level off. Do you see the i/o stop at any point? What speeds do you see? Some flash drives have write rates of 3 or 4 MB/sec, so it may take 20 minutes or more to write a DVD image.

    – Mark Plotnick
    Sep 18 '17 at 15:22











  • @Mark - When attempting to run the iostat 5 command as suggested I get the following error: bash: iostat: command not found

    – Meta
    Sep 18 '17 at 15:26



















Any messages from dmesg or when you run strace on the dd process?

– Raman Sailopal
Sep 18 '17 at 15:15





Any messages from dmesg or when you run strace on the dd process?

– Raman Sailopal
Sep 18 '17 at 15:15













Apologies, typo, I meant to say that it becomes unresponsive after step 4. I'll edit my post now.

– Meta
Sep 18 '17 at 15:18





Apologies, typo, I meant to say that it becomes unresponsive after step 4. I'll edit my post now.

– Meta
Sep 18 '17 at 15:18













@Raman - I've not actually ran those before? Give me a couple minutes and I'll post the result here.

– Meta
Sep 18 '17 at 15:19





@Raman - I've not actually ran those before? Give me a couple minutes and I'll post the result here.

– Meta
Sep 18 '17 at 15:19




2




2





Try running iostat 5 in another window before running the dd. The read and write rates should increase until they level off. Do you see the i/o stop at any point? What speeds do you see? Some flash drives have write rates of 3 or 4 MB/sec, so it may take 20 minutes or more to write a DVD image.

– Mark Plotnick
Sep 18 '17 at 15:22





Try running iostat 5 in another window before running the dd. The read and write rates should increase until they level off. Do you see the i/o stop at any point? What speeds do you see? Some flash drives have write rates of 3 or 4 MB/sec, so it may take 20 minutes or more to write a DVD image.

– Mark Plotnick
Sep 18 '17 at 15:22













@Mark - When attempting to run the iostat 5 command as suggested I get the following error: bash: iostat: command not found

– Meta
Sep 18 '17 at 15:26







@Mark - When attempting to run the iostat 5 command as suggested I get the following error: bash: iostat: command not found

– Meta
Sep 18 '17 at 15:26












2 Answers
2






active

oldest

votes


















1














dd does not show progress, what happens after step 4 is normal. Just let it finish, it might take some time depending on your USB and PC.



Use pv to see if the copy is happening.



apt-get install pv

dd if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso | pv | dd of=/dev/sde bs=4M





share|improve this answer


























  • Hmm. I have let it run for over half an hour before now though, and in the past on other distros it's only taken a matter of minutes? I'll install and run the command as you suggested though and see what the result is.

    – Meta
    Sep 18 '17 at 15:29



















0














Try this:



dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde status=progress


dd now supports showing the progress.






share|improve this answer
























  • If your dd is older, you can still send an USR1 signal to have it print the info. From man dd: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.

    – Ferenc Wágner
    Sep 20 '17 at 7:37













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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f392975%2fdd-command-appears-unresponsive-when-attempting-to-create-bootable-usb-media-in%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









1














dd does not show progress, what happens after step 4 is normal. Just let it finish, it might take some time depending on your USB and PC.



Use pv to see if the copy is happening.



apt-get install pv

dd if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso | pv | dd of=/dev/sde bs=4M





share|improve this answer


























  • Hmm. I have let it run for over half an hour before now though, and in the past on other distros it's only taken a matter of minutes? I'll install and run the command as you suggested though and see what the result is.

    – Meta
    Sep 18 '17 at 15:29
















1














dd does not show progress, what happens after step 4 is normal. Just let it finish, it might take some time depending on your USB and PC.



Use pv to see if the copy is happening.



apt-get install pv

dd if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso | pv | dd of=/dev/sde bs=4M





share|improve this answer


























  • Hmm. I have let it run for over half an hour before now though, and in the past on other distros it's only taken a matter of minutes? I'll install and run the command as you suggested though and see what the result is.

    – Meta
    Sep 18 '17 at 15:29














1












1








1







dd does not show progress, what happens after step 4 is normal. Just let it finish, it might take some time depending on your USB and PC.



Use pv to see if the copy is happening.



apt-get install pv

dd if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso | pv | dd of=/dev/sde bs=4M





share|improve this answer















dd does not show progress, what happens after step 4 is normal. Just let it finish, it might take some time depending on your USB and PC.



Use pv to see if the copy is happening.



apt-get install pv

dd if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso | pv | dd of=/dev/sde bs=4M






share|improve this answer














share|improve this answer



share|improve this answer








edited Sep 20 '17 at 7:34









Ferenc Wágner

3,109920




3,109920










answered Sep 18 '17 at 15:26









Hunter.S.ThompsonHunter.S.Thompson

5,54551336




5,54551336













  • Hmm. I have let it run for over half an hour before now though, and in the past on other distros it's only taken a matter of minutes? I'll install and run the command as you suggested though and see what the result is.

    – Meta
    Sep 18 '17 at 15:29



















  • Hmm. I have let it run for over half an hour before now though, and in the past on other distros it's only taken a matter of minutes? I'll install and run the command as you suggested though and see what the result is.

    – Meta
    Sep 18 '17 at 15:29

















Hmm. I have let it run for over half an hour before now though, and in the past on other distros it's only taken a matter of minutes? I'll install and run the command as you suggested though and see what the result is.

– Meta
Sep 18 '17 at 15:29





Hmm. I have let it run for over half an hour before now though, and in the past on other distros it's only taken a matter of minutes? I'll install and run the command as you suggested though and see what the result is.

– Meta
Sep 18 '17 at 15:29













0














Try this:



dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde status=progress


dd now supports showing the progress.






share|improve this answer
























  • If your dd is older, you can still send an USR1 signal to have it print the info. From man dd: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.

    – Ferenc Wágner
    Sep 20 '17 at 7:37


















0














Try this:



dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde status=progress


dd now supports showing the progress.






share|improve this answer
























  • If your dd is older, you can still send an USR1 signal to have it print the info. From man dd: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.

    – Ferenc Wágner
    Sep 20 '17 at 7:37
















0












0








0







Try this:



dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde status=progress


dd now supports showing the progress.






share|improve this answer













Try this:



dd bs=4M if=/home/user/Downloads/ubuntu-gnome-16.04.3-desktop-amd64.iso of=/dev/sde status=progress


dd now supports showing the progress.







share|improve this answer












share|improve this answer



share|improve this answer










answered Sep 19 '17 at 4:41









rootbotnixrootbotnix

91




91













  • If your dd is older, you can still send an USR1 signal to have it print the info. From man dd: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.

    – Ferenc Wágner
    Sep 20 '17 at 7:37





















  • If your dd is older, you can still send an USR1 signal to have it print the info. From man dd: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.

    – Ferenc Wágner
    Sep 20 '17 at 7:37



















If your dd is older, you can still send an USR1 signal to have it print the info. From man dd: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.

– Ferenc Wágner
Sep 20 '17 at 7:37







If your dd is older, you can still send an USR1 signal to have it print the info. From man dd: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.

– Ferenc Wágner
Sep 20 '17 at 7:37




















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f392975%2fdd-command-appears-unresponsive-when-attempting-to-create-bootable-usb-media-in%23new-answer', 'question_page');
}
);

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







-

Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Image
4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel...
Read more

Can't connect RFCOMM socket: Host is down

Image
up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2 ...
Read more

Kernel panic - not syncing: Fatal Exception in Interrupt

Image
0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment ...
Read more