UEFI-installed Debian on a pendrive doesn't want to boot after being removed once2019 Community Moderator ElectionWrong iso file preventing from booting Debian dvd with uefiHow to install Debian GNU/Linux on HP Chromebook 14? USB boot doesn't works!Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmwareDebian live USB has no EFI boot driver and cannot be installed on an Acer laptopUEFI-support for Debian Live-buildsystem doesn't have any usb boot option ErrorUnable to boot on Debian after cloning dual-boot from HDD to SSDUsing UEFI boot mode for Gentoo Linux installation on OracleVM VirtualBox instance after April 20, 2017Mint UEFI partition suddenly not recognized by UEFI anymore - after booting Windows 7 onceSystem skips grub and loads to Windows (UEFI)

Can you reject a postdoc offer after the PI has paid a large sum for flights/accommodation for your visit?

How do you like my writing?

Grey hair or white hair

What's the "normal" opposite of flautando?

They call me Inspector Morse

Why doesn't this Google Translate ad use the word "Translation" instead of "Translate"?

Why don't MCU characters ever seem to have language issues?

Algorithm to convert a fixed-length string to the smallest possible collision-free representation?

Accountant/ lawyer will not return my call

PTIJ: How can I halachically kill a vampire?

Word-Letter Ladder

What wound would be of little consequence to a biped but terrible for a quadruped?

Why does Captain Marvel assume the people on this planet know this?

How did the power source of Mar-Vell's aircraft end up with her?

Space in array system equations

Could you please stop shuffling the deck and play already?

Single word request: Harming the benefactor

Good allowance savings plan?

Is it true that real estate prices mainly go up?

How strictly should I take "Candidates must be local"?

What does C-53 signify?

Examples of a statistic that is not independent of sample's distribution?

In the late 1940’s to early 1950’s what technology was available that could melt a LOT of ice?

Is "history" a male-biased word ("his+story")?



UEFI-installed Debian on a pendrive doesn't want to boot after being removed once



2019 Community Moderator ElectionWrong iso file preventing from booting Debian dvd with uefiHow to install Debian GNU/Linux on HP Chromebook 14? USB boot doesn't works!Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmwareDebian live USB has no EFI boot driver and cannot be installed on an Acer laptopUEFI-support for Debian Live-buildsystem doesn't have any usb boot option ErrorUnable to boot on Debian after cloning dual-boot from HDD to SSDUsing UEFI boot mode for Gentoo Linux installation on OracleVM VirtualBox instance after April 20, 2017Mint UEFI partition suddenly not recognized by UEFI anymore - after booting Windows 7 onceSystem skips grub and loads to Windows (UEFI)










1















I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled 'UEFI: debian' on the bios setup, but as soon as i removed the adapter, that option disappeared.



I don't want to lose the debian installation, I want it working again. Could someone help me getting it booting again?










share|improve this question







New contributor




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




















  • This might be implied but... are you saying that when you plug the USB back in, the UEFI: debian option doesn't reappear?

    – Philip Couling
    1 hour ago















1















I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled 'UEFI: debian' on the bios setup, but as soon as i removed the adapter, that option disappeared.



I don't want to lose the debian installation, I want it working again. Could someone help me getting it booting again?










share|improve this question







New contributor




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




















  • This might be implied but... are you saying that when you plug the USB back in, the UEFI: debian option doesn't reappear?

    – Philip Couling
    1 hour ago













1












1








1








I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled 'UEFI: debian' on the bios setup, but as soon as i removed the adapter, that option disappeared.



I don't want to lose the debian installation, I want it working again. Could someone help me getting it booting again?










share|improve this question







New contributor




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












I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled 'UEFI: debian' on the bios setup, but as soon as i removed the adapter, that option disappeared.



I don't want to lose the debian installation, I want it working again. Could someone help me getting it booting again?







debian uefi usb-drive






share|improve this question







New contributor




Debianoid 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




Debianoid 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




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









asked 2 hours ago









DebianoidDebianoid

61




61




New contributor




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





New contributor





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






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












  • This might be implied but... are you saying that when you plug the USB back in, the UEFI: debian option doesn't reappear?

    – Philip Couling
    1 hour ago

















  • This might be implied but... are you saying that when you plug the USB back in, the UEFI: debian option doesn't reappear?

    – Philip Couling
    1 hour ago
















This might be implied but... are you saying that when you plug the USB back in, the UEFI: debian option doesn't reappear?

– Philip Couling
1 hour ago





This might be implied but... are you saying that when you plug the USB back in, the UEFI: debian option doesn't reappear?

– Philip Couling
1 hour ago










2 Answers
2






active

oldest

votes


















0














This smells like a BIOS problem. You've missed some information out of your question so I'm going to assume somethings:




  • UEFI: debian appears in a BIOS menu after install (not a grub menu)

  • When you unplug and re-plug the USB drive, the BIOS no-longer shows UEFI: debian even after reboot

  • Your main hard disk uses EFI to boot your other operating system (Windows?)


It would be very difficult to give a direct solution without knowing a lot more about your BIOS. However the problem might be something to do with you having two EFI partitions; one on your internal HDD and one on your USB disk.



It may be possible to manually remind your BIOS about the USB EFI entries when you plug back in, but I couldn't tell you how.



A possible work around might be to copy your EFI entry from your USB drive onto your internal hard drive. This will be easier from Debian (if you can get back into it) but it can be done on windows.



EFI entries are basically just a few files in a directory on your EFI partition. So all you would need to do is to mount your internal HDD's EFI partition and copy the one from your USB drive (usually mounted to /boot/efi/EFI/debian)






share|improve this answer






























    0














    My guess is that the root file system (with the Debian operating system) is damaged.



    This can happen



    • if the drive is unplugged before the operating system is fully shutdown or


    • if connected when another operating system is running, you unplugged it without unmounting all partitions on the drive.



    You can connect the drive to a computer running linux and try to repair the file system(s).



    • Make sure that all partitions on the SD card are unmounted


    • Repair the root file system on the SD card (and other file systems, that belong to Debian, for example home, if there is a separate home partition.



    • Run the following command line for each of these file systems (I assume ext4 here, modify if you use another file system),



      sudo e2fsck -f /dev/sdxn


      where x is the device letter for the SD card and n is the partition number, so for example /dev/sdb2




    It is also possible, that Windows damaged the boot system for the SD card via USB. This can happen, if the card was connected, when you booted Windows or when Windows was running some update/upgrade process.



    If this is the case, you can find methods to 'repair grub' or 'repair boot' via the internet. I know methods for Ubuntu, and I think but am not sure that the same methods work for Debian.




    Please notice that the first part about damaged file systems and the second part about Windows damaging the boot system are describing independent problems. I don't know enough about your particular problem to be able to tell which of the problems that is affecting your Debian system on the SD card.






    share|improve this answer




















    • 1





      EFI partitions are unlikely to corrupt through failing to unmount. If the OP successfully booted from the USB drive once then the EFI partition was successfully written once. Very few things touch data on EFI so its very unlikely to be in an unstable state even if yanked out. Note that EFI can't be fixed with e2fsck as it must be a FAT based file system.

      – Philip Couling
      56 mins ago












    • @PhilipCouling, I can state more clearly that the part about corruption of file systems is independent of the part about Windows tampering with the boot system.

      – sudodus
      6 mins ago










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



    );






    Debianoid 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%2f505907%2fuefi-installed-debian-on-a-pendrive-doesnt-want-to-boot-after-being-removed-onc%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









    0














    This smells like a BIOS problem. You've missed some information out of your question so I'm going to assume somethings:




    • UEFI: debian appears in a BIOS menu after install (not a grub menu)

    • When you unplug and re-plug the USB drive, the BIOS no-longer shows UEFI: debian even after reboot

    • Your main hard disk uses EFI to boot your other operating system (Windows?)


    It would be very difficult to give a direct solution without knowing a lot more about your BIOS. However the problem might be something to do with you having two EFI partitions; one on your internal HDD and one on your USB disk.



    It may be possible to manually remind your BIOS about the USB EFI entries when you plug back in, but I couldn't tell you how.



    A possible work around might be to copy your EFI entry from your USB drive onto your internal hard drive. This will be easier from Debian (if you can get back into it) but it can be done on windows.



    EFI entries are basically just a few files in a directory on your EFI partition. So all you would need to do is to mount your internal HDD's EFI partition and copy the one from your USB drive (usually mounted to /boot/efi/EFI/debian)






    share|improve this answer



























      0














      This smells like a BIOS problem. You've missed some information out of your question so I'm going to assume somethings:




      • UEFI: debian appears in a BIOS menu after install (not a grub menu)

      • When you unplug and re-plug the USB drive, the BIOS no-longer shows UEFI: debian even after reboot

      • Your main hard disk uses EFI to boot your other operating system (Windows?)


      It would be very difficult to give a direct solution without knowing a lot more about your BIOS. However the problem might be something to do with you having two EFI partitions; one on your internal HDD and one on your USB disk.



      It may be possible to manually remind your BIOS about the USB EFI entries when you plug back in, but I couldn't tell you how.



      A possible work around might be to copy your EFI entry from your USB drive onto your internal hard drive. This will be easier from Debian (if you can get back into it) but it can be done on windows.



      EFI entries are basically just a few files in a directory on your EFI partition. So all you would need to do is to mount your internal HDD's EFI partition and copy the one from your USB drive (usually mounted to /boot/efi/EFI/debian)






      share|improve this answer

























        0












        0








        0







        This smells like a BIOS problem. You've missed some information out of your question so I'm going to assume somethings:




        • UEFI: debian appears in a BIOS menu after install (not a grub menu)

        • When you unplug and re-plug the USB drive, the BIOS no-longer shows UEFI: debian even after reboot

        • Your main hard disk uses EFI to boot your other operating system (Windows?)


        It would be very difficult to give a direct solution without knowing a lot more about your BIOS. However the problem might be something to do with you having two EFI partitions; one on your internal HDD and one on your USB disk.



        It may be possible to manually remind your BIOS about the USB EFI entries when you plug back in, but I couldn't tell you how.



        A possible work around might be to copy your EFI entry from your USB drive onto your internal hard drive. This will be easier from Debian (if you can get back into it) but it can be done on windows.



        EFI entries are basically just a few files in a directory on your EFI partition. So all you would need to do is to mount your internal HDD's EFI partition and copy the one from your USB drive (usually mounted to /boot/efi/EFI/debian)






        share|improve this answer













        This smells like a BIOS problem. You've missed some information out of your question so I'm going to assume somethings:




        • UEFI: debian appears in a BIOS menu after install (not a grub menu)

        • When you unplug and re-plug the USB drive, the BIOS no-longer shows UEFI: debian even after reboot

        • Your main hard disk uses EFI to boot your other operating system (Windows?)


        It would be very difficult to give a direct solution without knowing a lot more about your BIOS. However the problem might be something to do with you having two EFI partitions; one on your internal HDD and one on your USB disk.



        It may be possible to manually remind your BIOS about the USB EFI entries when you plug back in, but I couldn't tell you how.



        A possible work around might be to copy your EFI entry from your USB drive onto your internal hard drive. This will be easier from Debian (if you can get back into it) but it can be done on windows.



        EFI entries are basically just a few files in a directory on your EFI partition. So all you would need to do is to mount your internal HDD's EFI partition and copy the one from your USB drive (usually mounted to /boot/efi/EFI/debian)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 50 mins ago









        Philip CoulingPhilip Couling

        1,802920




        1,802920























            0














            My guess is that the root file system (with the Debian operating system) is damaged.



            This can happen



            • if the drive is unplugged before the operating system is fully shutdown or


            • if connected when another operating system is running, you unplugged it without unmounting all partitions on the drive.



            You can connect the drive to a computer running linux and try to repair the file system(s).



            • Make sure that all partitions on the SD card are unmounted


            • Repair the root file system on the SD card (and other file systems, that belong to Debian, for example home, if there is a separate home partition.



            • Run the following command line for each of these file systems (I assume ext4 here, modify if you use another file system),



              sudo e2fsck -f /dev/sdxn


              where x is the device letter for the SD card and n is the partition number, so for example /dev/sdb2




            It is also possible, that Windows damaged the boot system for the SD card via USB. This can happen, if the card was connected, when you booted Windows or when Windows was running some update/upgrade process.



            If this is the case, you can find methods to 'repair grub' or 'repair boot' via the internet. I know methods for Ubuntu, and I think but am not sure that the same methods work for Debian.




            Please notice that the first part about damaged file systems and the second part about Windows damaging the boot system are describing independent problems. I don't know enough about your particular problem to be able to tell which of the problems that is affecting your Debian system on the SD card.






            share|improve this answer




















            • 1





              EFI partitions are unlikely to corrupt through failing to unmount. If the OP successfully booted from the USB drive once then the EFI partition was successfully written once. Very few things touch data on EFI so its very unlikely to be in an unstable state even if yanked out. Note that EFI can't be fixed with e2fsck as it must be a FAT based file system.

              – Philip Couling
              56 mins ago












            • @PhilipCouling, I can state more clearly that the part about corruption of file systems is independent of the part about Windows tampering with the boot system.

              – sudodus
              6 mins ago















            0














            My guess is that the root file system (with the Debian operating system) is damaged.



            This can happen



            • if the drive is unplugged before the operating system is fully shutdown or


            • if connected when another operating system is running, you unplugged it without unmounting all partitions on the drive.



            You can connect the drive to a computer running linux and try to repair the file system(s).



            • Make sure that all partitions on the SD card are unmounted


            • Repair the root file system on the SD card (and other file systems, that belong to Debian, for example home, if there is a separate home partition.



            • Run the following command line for each of these file systems (I assume ext4 here, modify if you use another file system),



              sudo e2fsck -f /dev/sdxn


              where x is the device letter for the SD card and n is the partition number, so for example /dev/sdb2




            It is also possible, that Windows damaged the boot system for the SD card via USB. This can happen, if the card was connected, when you booted Windows or when Windows was running some update/upgrade process.



            If this is the case, you can find methods to 'repair grub' or 'repair boot' via the internet. I know methods for Ubuntu, and I think but am not sure that the same methods work for Debian.




            Please notice that the first part about damaged file systems and the second part about Windows damaging the boot system are describing independent problems. I don't know enough about your particular problem to be able to tell which of the problems that is affecting your Debian system on the SD card.






            share|improve this answer




















            • 1





              EFI partitions are unlikely to corrupt through failing to unmount. If the OP successfully booted from the USB drive once then the EFI partition was successfully written once. Very few things touch data on EFI so its very unlikely to be in an unstable state even if yanked out. Note that EFI can't be fixed with e2fsck as it must be a FAT based file system.

              – Philip Couling
              56 mins ago












            • @PhilipCouling, I can state more clearly that the part about corruption of file systems is independent of the part about Windows tampering with the boot system.

              – sudodus
              6 mins ago













            0












            0








            0







            My guess is that the root file system (with the Debian operating system) is damaged.



            This can happen



            • if the drive is unplugged before the operating system is fully shutdown or


            • if connected when another operating system is running, you unplugged it without unmounting all partitions on the drive.



            You can connect the drive to a computer running linux and try to repair the file system(s).



            • Make sure that all partitions on the SD card are unmounted


            • Repair the root file system on the SD card (and other file systems, that belong to Debian, for example home, if there is a separate home partition.



            • Run the following command line for each of these file systems (I assume ext4 here, modify if you use another file system),



              sudo e2fsck -f /dev/sdxn


              where x is the device letter for the SD card and n is the partition number, so for example /dev/sdb2




            It is also possible, that Windows damaged the boot system for the SD card via USB. This can happen, if the card was connected, when you booted Windows or when Windows was running some update/upgrade process.



            If this is the case, you can find methods to 'repair grub' or 'repair boot' via the internet. I know methods for Ubuntu, and I think but am not sure that the same methods work for Debian.




            Please notice that the first part about damaged file systems and the second part about Windows damaging the boot system are describing independent problems. I don't know enough about your particular problem to be able to tell which of the problems that is affecting your Debian system on the SD card.






            share|improve this answer















            My guess is that the root file system (with the Debian operating system) is damaged.



            This can happen



            • if the drive is unplugged before the operating system is fully shutdown or


            • if connected when another operating system is running, you unplugged it without unmounting all partitions on the drive.



            You can connect the drive to a computer running linux and try to repair the file system(s).



            • Make sure that all partitions on the SD card are unmounted


            • Repair the root file system on the SD card (and other file systems, that belong to Debian, for example home, if there is a separate home partition.



            • Run the following command line for each of these file systems (I assume ext4 here, modify if you use another file system),



              sudo e2fsck -f /dev/sdxn


              where x is the device letter for the SD card and n is the partition number, so for example /dev/sdb2




            It is also possible, that Windows damaged the boot system for the SD card via USB. This can happen, if the card was connected, when you booted Windows or when Windows was running some update/upgrade process.



            If this is the case, you can find methods to 'repair grub' or 'repair boot' via the internet. I know methods for Ubuntu, and I think but am not sure that the same methods work for Debian.




            Please notice that the first part about damaged file systems and the second part about Windows damaging the boot system are describing independent problems. I don't know enough about your particular problem to be able to tell which of the problems that is affecting your Debian system on the SD card.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 2 mins ago

























            answered 1 hour ago









            sudodussudodus

            1,68339




            1,68339







            • 1





              EFI partitions are unlikely to corrupt through failing to unmount. If the OP successfully booted from the USB drive once then the EFI partition was successfully written once. Very few things touch data on EFI so its very unlikely to be in an unstable state even if yanked out. Note that EFI can't be fixed with e2fsck as it must be a FAT based file system.

              – Philip Couling
              56 mins ago












            • @PhilipCouling, I can state more clearly that the part about corruption of file systems is independent of the part about Windows tampering with the boot system.

              – sudodus
              6 mins ago












            • 1





              EFI partitions are unlikely to corrupt through failing to unmount. If the OP successfully booted from the USB drive once then the EFI partition was successfully written once. Very few things touch data on EFI so its very unlikely to be in an unstable state even if yanked out. Note that EFI can't be fixed with e2fsck as it must be a FAT based file system.

              – Philip Couling
              56 mins ago












            • @PhilipCouling, I can state more clearly that the part about corruption of file systems is independent of the part about Windows tampering with the boot system.

              – sudodus
              6 mins ago







            1




            1





            EFI partitions are unlikely to corrupt through failing to unmount. If the OP successfully booted from the USB drive once then the EFI partition was successfully written once. Very few things touch data on EFI so its very unlikely to be in an unstable state even if yanked out. Note that EFI can't be fixed with e2fsck as it must be a FAT based file system.

            – Philip Couling
            56 mins ago






            EFI partitions are unlikely to corrupt through failing to unmount. If the OP successfully booted from the USB drive once then the EFI partition was successfully written once. Very few things touch data on EFI so its very unlikely to be in an unstable state even if yanked out. Note that EFI can't be fixed with e2fsck as it must be a FAT based file system.

            – Philip Couling
            56 mins ago














            @PhilipCouling, I can state more clearly that the part about corruption of file systems is independent of the part about Windows tampering with the boot system.

            – sudodus
            6 mins ago





            @PhilipCouling, I can state more clearly that the part about corruption of file systems is independent of the part about Windows tampering with the boot system.

            – sudodus
            6 mins ago










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









            draft saved

            draft discarded


















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












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











            Debianoid 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%2f505907%2fuefi-installed-debian-on-a-pendrive-doesnt-want-to-boot-after-being-removed-onc%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







            -debian, uefi, usb-drive

            Popular posts from this blog

            Frič See also Navigation menuinternal link

            Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

            fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox