USB drive not useable right after Debian installation












0















I have encountered an interesting scenario. I have some Debian Live CD images (I have tried debian-8.11.0-amd64-netinst.iso, debian-9.6.0-amd64-netinst.iso and some custom images I built using live-build) and dd the image onto an USB drive. I boot the computer with the USB drive and install Debian onto hard drive. When the installation finishes, the computer reboots. At this time, after I login, I find I am not able to use the USB drive, which is still plugged in. I can see it being /dev/sdb, but /dev does not show any partitions of the USB drive. I tried fdisk -l /dev/sdb but gets fdisk: cannot open /dev/sdb: No medium found. In dmesg the only two lines I see related are



sd 2:0:0:0: Attached scsi generic sg1 type0
sd 2:0:0:0: [sdb] Attached SCSI removable disk


Here's the interesting part. If I unplug the drive and plug back in, it gets detected and works fine. If I reboot the box (either reboot or poweroff and then power on), it doesn't work. However, if after the box is powered off, I unplug the drive and plug in back it, upon the next boot it works. I wondered if there's some mechanism in Debian Installer that prevents the USB drive from working to avoid reboot-install loop. I looked into some of the files and in /bin/live-medium-eject I find it's not doing anything to usb devices and has the following comment:



# ignoring usb mass storage devices
# (they need coldreboot to recover)


What could be the cause of this behavior?










share|improve this question







New contributor




user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    I have encountered an interesting scenario. I have some Debian Live CD images (I have tried debian-8.11.0-amd64-netinst.iso, debian-9.6.0-amd64-netinst.iso and some custom images I built using live-build) and dd the image onto an USB drive. I boot the computer with the USB drive and install Debian onto hard drive. When the installation finishes, the computer reboots. At this time, after I login, I find I am not able to use the USB drive, which is still plugged in. I can see it being /dev/sdb, but /dev does not show any partitions of the USB drive. I tried fdisk -l /dev/sdb but gets fdisk: cannot open /dev/sdb: No medium found. In dmesg the only two lines I see related are



    sd 2:0:0:0: Attached scsi generic sg1 type0
    sd 2:0:0:0: [sdb] Attached SCSI removable disk


    Here's the interesting part. If I unplug the drive and plug back in, it gets detected and works fine. If I reboot the box (either reboot or poweroff and then power on), it doesn't work. However, if after the box is powered off, I unplug the drive and plug in back it, upon the next boot it works. I wondered if there's some mechanism in Debian Installer that prevents the USB drive from working to avoid reboot-install loop. I looked into some of the files and in /bin/live-medium-eject I find it's not doing anything to usb devices and has the following comment:



    # ignoring usb mass storage devices
    # (they need coldreboot to recover)


    What could be the cause of this behavior?










    share|improve this question







    New contributor




    user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I have encountered an interesting scenario. I have some Debian Live CD images (I have tried debian-8.11.0-amd64-netinst.iso, debian-9.6.0-amd64-netinst.iso and some custom images I built using live-build) and dd the image onto an USB drive. I boot the computer with the USB drive and install Debian onto hard drive. When the installation finishes, the computer reboots. At this time, after I login, I find I am not able to use the USB drive, which is still plugged in. I can see it being /dev/sdb, but /dev does not show any partitions of the USB drive. I tried fdisk -l /dev/sdb but gets fdisk: cannot open /dev/sdb: No medium found. In dmesg the only two lines I see related are



      sd 2:0:0:0: Attached scsi generic sg1 type0
      sd 2:0:0:0: [sdb] Attached SCSI removable disk


      Here's the interesting part. If I unplug the drive and plug back in, it gets detected and works fine. If I reboot the box (either reboot or poweroff and then power on), it doesn't work. However, if after the box is powered off, I unplug the drive and plug in back it, upon the next boot it works. I wondered if there's some mechanism in Debian Installer that prevents the USB drive from working to avoid reboot-install loop. I looked into some of the files and in /bin/live-medium-eject I find it's not doing anything to usb devices and has the following comment:



      # ignoring usb mass storage devices
      # (they need coldreboot to recover)


      What could be the cause of this behavior?










      share|improve this question







      New contributor




      user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I have encountered an interesting scenario. I have some Debian Live CD images (I have tried debian-8.11.0-amd64-netinst.iso, debian-9.6.0-amd64-netinst.iso and some custom images I built using live-build) and dd the image onto an USB drive. I boot the computer with the USB drive and install Debian onto hard drive. When the installation finishes, the computer reboots. At this time, after I login, I find I am not able to use the USB drive, which is still plugged in. I can see it being /dev/sdb, but /dev does not show any partitions of the USB drive. I tried fdisk -l /dev/sdb but gets fdisk: cannot open /dev/sdb: No medium found. In dmesg the only two lines I see related are



      sd 2:0:0:0: Attached scsi generic sg1 type0
      sd 2:0:0:0: [sdb] Attached SCSI removable disk


      Here's the interesting part. If I unplug the drive and plug back in, it gets detected and works fine. If I reboot the box (either reboot or poweroff and then power on), it doesn't work. However, if after the box is powered off, I unplug the drive and plug in back it, upon the next boot it works. I wondered if there's some mechanism in Debian Installer that prevents the USB drive from working to avoid reboot-install loop. I looked into some of the files and in /bin/live-medium-eject I find it's not doing anything to usb devices and has the following comment:



      # ignoring usb mass storage devices
      # (they need coldreboot to recover)


      What could be the cause of this behavior?







      debian boot usb live-usb bios






      share|improve this question







      New contributor




      user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 1 hour ago









      user274602user274602

      1




      1




      New contributor




      user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      user274602 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











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


          }
          });






          user274602 is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496093%2fusb-drive-not-useable-right-after-debian-installation%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          user274602 is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          user274602 is a new contributor. Be nice, and check out our Code of Conduct.













          user274602 is a new contributor. Be nice, and check out our Code of Conduct.












          user274602 is a new contributor. Be nice, and check out our Code of Conduct.
















          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%2f496093%2fusb-drive-not-useable-right-after-debian-installation%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

          Entries order in /etc/network/interfaces

          新発田市

          Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)