Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #219986 > unrolled thread

failure to install debian

Started bykaye n <guikaye@gmail.com>
First post2020-03-09 04:50 +0100
Last post2020-03-19 18:30 +0100
Articles 11 — 7 participants

Back to article view | Back to linux.debian.user

Contents

  failure to install debian kaye n <guikaye@gmail.com> - 2020-03-09 04:50 +0100
    Re: failure to install debian David Christensen <dpchrist@holgerdanske.com> - 2020-03-09 05:40 +0100
    Re: failure to install debian Curt <curty@free.fr> - 2020-03-09 09:40 +0100
      Re: failure to install debian kaye n <guikaye@gmail.com> - 2020-03-09 19:40 +0100
        Re: failure to install debian kaye n <guikaye@gmail.com> - 2020-03-09 19:50 +0100
          Re: failure to install debian Gene Heskett <gheskett@shentel.net> - 2020-03-09 20:00 +0100
          Re: failure to install debian David Christensen <dpchrist@holgerdanske.com> - 2020-03-09 20:30 +0100
    Re: failure to install debian David Wright <deblis@lionunicorn.co.uk> - 2020-03-09 19:20 +0100
      Re: failure to install debian kaye n <guikaye@gmail.com> - 2020-03-09 19:40 +0100
    Re: failure to install debian Steve McIntyre <steve@einval.com> - 2020-03-09 22:30 +0100
      Re: failure to install debian Leandro Noferini <lnoferin@cybervalley.org> - 2020-03-19 18:30 +0100

#219986 — failure to install debian

Fromkaye n <guikaye@gmail.com>
Date2020-03-09 04:50 +0100
Subjectfailure to install debian
Message-ID<zIhAt-2jv-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello Friends!

I messed up my Debian so I'm trying re-install with a live USB, however it
always fails. I get this message:

-------------------------------------------------------------------------------------------

Boost.Python error in job "bootloader".

Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi
--bootloader-id=Debian --force' returned non-zero exit status 1.

Installing for x86_64-efi platform. grub-install: warning: Cannot set EFI
variable Boot0000. grub-install: warning: efivarfs_set_variable: writing to
fd 7 failed: No space left on device. grub-install: warning:
_efi_set_variable_mode: ops->set_variable() failed: No space left on
device. grub-install: error: failed to register the EFI boot entry: No
space left on device.


Traceback:

File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
line 444, in run

    prepare_bootloader(fw_type)


  File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
line 411, in prepare_bootloader

    install_grub(efi_directory, fw_type)


  File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
line 285, in install_grub

    "--force"])


  File "<string>", line 8, in <module>
---------------------------------------------------------

I thought the problem was my live USB, but when I used another Debian
live USB (that was proven to be a successful installer),

I get the same result.

I did not resize the debian partitions, I merely reformatted it.

Thank you very much for your time!

kaye

[toc] | [next] | [standalone]

#219989

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2020-03-09 05:40 +0100
Message-ID<zIimS-305-1@gated-at.bofh.it>
In reply to#219986
On 2020-03-08 20:43, kaye n wrote:
> Hello Friends!
> 
> I messed up my Debian so I'm trying re-install with a live USB, however it
> always fails. I get this message:
> 
> -------------------------------------------------------------------------------------------
> 
> Boost.Python error in job "bootloader".
> 
> Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi
> --bootloader-id=Debian --force' returned non-zero exit status 1.
> 
> Installing for x86_64-efi platform. grub-install: warning: Cannot set EFI
> variable Boot0000. grub-install: warning: efivarfs_set_variable: writing to
> fd 7 failed: No space left on device. grub-install: warning:
> _efi_set_variable_mode: ops->set_variable() failed: No space left on
> device. grub-install: error: failed to register the EFI boot entry: No
> space left on device.
> 
> 
> Traceback:
> 
> File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
> line 444, in run
> 
>      prepare_bootloader(fw_type)
> 
> 
>    File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
> line 411, in prepare_bootloader
> 
>      install_grub(efi_directory, fw_type)
> 
> 
>    File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
> line 285, in install_grub
> 
>      "--force"])
> 
> 
>    File "<string>", line 8, in <module>
> ---------------------------------------------------------
> 
> I thought the problem was my live USB, but when I used another Debian
> live USB (that was proven to be a successful installer),
> 
> I get the same result.
> 
> I did not resize the debian partitions, I merely reformatted it.
> 
> Thank you very much for your time!
> 
> kaye


Installation is more predictable if you erase the primary and/or backup 
partition tables on the target drive before installing Debian.


The old-school solution is to boot the Debian Installer into a rescue 
shell, use lsblk(8) and parted(8) to find the target drive and number of 
sectors, and use dd(1) to copy /dev/zero to the first megabyte and the 
last megabyte of the target drive.  If you are concerned about leftover 
data from the  previous install (imaging, security), you can copy 
/dev/zero to the entire target drive.  If you choose the latter, be sure 
to increase the block size; I use 'bs=1M'.


Some SSD's feature Secure Erase, which erases every block on the drive. 
This has the added benefit that subsequent writes will proceed at 
maximum speed until all the blocks have been written once.  I don't know 
the command line incantations to do this, so I use a GUI tool from the 
drive manufacturer.


Most of my SSD's are Intel.  Unfortunately, the Intel SSD Toolbox 
requires Windows:

 
https://www.intel.com/content/www/us/en/support/products/80096/memory-and-storage/ssd-software/intel-ssd-toolbox.html


Most of my HDD's are Seagate.  SeaTools Bootable is, well, bootable, 
which I like.  But, it doesn't like USB 3.0 ports, which can be a problem:

     https://www.seagate.com/support/downloads/seatools/


Other drive manufacturers produce similar tools.


David

[toc] | [prev] | [next] | [standalone]

#219992

FromCurt <curty@free.fr>
Date2020-03-09 09:40 +0100
Message-ID<zIm77-5sP-3@gated-at.bofh.it>
In reply to#219986
On 2020-03-09, kaye n <guikaye@gmail.com> wrote:
>
> Hello Friends!
>
> I messed up my Debian so I'm trying re-install with a live USB, however it
> always fails. I get this message:
>
> Boost.Python error in job "bootloader".
>
> Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi
> --bootloader-id=Debian --force' returned non-zero exit status 1.
>

You didn't cut a line up there, did you? Is your efi partition formatted
FAT32?


-- 
Nous fîmes l'amour longtemps, à la façon des craquements qui se produisent dans
les meubles. Nous fîmes l'amour comme le soleil bat, comme les cercueils
ferment, comme le silence appelle, comme la nuit brille. Et dans nos yeux qui n'étaient 
jamais ouverts en même temps ne se débattaient rien que nos sorts les plus purs. --André Breton

[toc] | [prev] | [next] | [standalone]

#220015

Fromkaye n <guikaye@gmail.com>
Date2020-03-09 19:40 +0100
Message-ID<zIvtL-31t-11@gated-at.bofh.it>
In reply to#219992

[Multipart message — attachments visible in raw view] — view raw

On Mon, Mar 9, 2020 at 4:37 PM Curt <curty@free.fr> wrote:

> You didn't cut a line up there, did you? Is your efi partition formatted
> FAT32?
>


I'm not sure what you mean, but yes my efi partition is formatted FAT32 and
is flagged as esp.  That partition is 50MB, and 5.86MB is used.
Thank you

[toc] | [prev] | [next] | [standalone]

#220016

Fromkaye n <guikaye@gmail.com>
Date2020-03-09 19:50 +0100
Message-ID<zIvDr-35g-3@gated-at.bofh.it>
In reply to#220015

[Multipart message — attachments visible in raw view] — view raw

Also, does it matter that my efi partition is at the right-most part of the
hdd (when looking at it in GParted)?
Thank you!

On Tue, Mar 10, 2020 at 2:36 AM kaye n <guikaye@gmail.com> wrote:

> On Mon, Mar 9, 2020 at 4:37 PM Curt <curty@free.fr> wrote:
>
>> You didn't cut a line up there, did you? Is your efi partition formatted
>> FAT32?
>>
>
>
> I'm not sure what you mean, but yes my efi partition is formatted FAT32
> and is flagged as esp.  That partition is 50MB, and 5.86MB is used.
> Thank you
>

[toc] | [prev] | [next] | [standalone]

#220017

FromGene Heskett <gheskett@shentel.net>
Date2020-03-09 20:00 +0100
Message-ID<zIvN7-38V-1@gated-at.bofh.it>
In reply to#220016
On Monday 09 March 2020 14:40:29 kaye n wrote:

> Also, does it matter that my efi partition is at the right-most part
> of the hdd (when looking at it in GParted)?
> Thank you!

I think yes, it matters. Historicly fat needs to end not later that about 
4Gb from the beginning of the disk. There is now an exfat, but I think 
M$ patents are holding up its linux acceptance.  Generally its moot as 
most images to install linux, overwrite the disks file systems with an 
ext4 that just works. So it basicly is not an argument when the u-sd 
says its exfat, and trace of it is gone by the dd-ing of a linux install 
image to that 64GB u-sd tpo it.

>
> On Tue, Mar 10, 2020 at 2:36 AM kaye n <guikaye@gmail.com> wrote:
> > On Mon, Mar 9, 2020 at 4:37 PM Curt <curty@free.fr> wrote:
> >> You didn't cut a line up there, did you? Is your efi partition
> >> formatted FAT32?
> >
> > I'm not sure what you mean, but yes my efi partition is formatted
> > FAT32 and is flagged as esp.  That partition is 50MB, and 5.86MB is
> > used. Thank you


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#220019

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2020-03-09 20:30 +0100
Message-ID<zIwga-3zf-11@gated-at.bofh.it>
In reply to#220016
 >> On Mon, Mar 9, 2020 at 4:37 PM Curt <curty@free.fr> wrote:
 >>> You didn't cut a line up there, did you? Is your efi partition 
formatted
 >>> FAT32?

 > On Tue, Mar 10, 2020 at 2:36 AM kaye n <guikaye@gmail.com> wrote:
 >> I'm not sure what you mean, but yes my efi partition is formatted FAT32
 >> and is flagged as esp.  That partition is 50MB, and 5.86MB is used.
 >> Thank you

50MB might outdated and too small -- I have variously read 200MB and 
500MB for current recommended ESP partition size; especially for 
multi-boot situations.


On 2020-03-09 11:40, kaye n wrote:
 > Also, does it matter that my efi partition is at the right-most part 
of the
 > hdd (when looking at it in GParted)?
 > Thank you!

On 2020-03-09 11:52, Gene Heskett wrote:
 > I think yes, it matters. Historicly fat needs to end not later that about
 > 4Gb from the beginning of the disk. There is now an exfat, but I think
 > M$ patents are holding up its linux acceptance.  Generally its moot as
 > most images to install linux, overwrite the disks file systems with an
 > ext4 that just works. So it basicly is not an argument when the u-sd
 > says its exfat, and trace of it is gone by the dd-ing of a linux install
 > image to that 64GB u-sd tpo it.

I had thought one of the reasons for GPT is to solve that limitation of 
MBR, but...


In any case, putting the ESP at the end is unconventional.  I would put 
my partitions in order boot, ESP, swap, and root, with empty space at 
the end (for over-provisioning and to facilitate imaging to 
different-sized devices).


I still think you should wipe the partition tables and let whichever 
Debian Installer you are using partition the drive as it likes.


David

[toc] | [prev] | [next] | [standalone]

#220012

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2020-03-09 19:20 +0100
Message-ID<zIvap-2Uj-3@gated-at.bofh.it>
In reply to#219986
On Mon 09 Mar 2020 at 11:43:25 (+0800), kaye n wrote:
> 
> I messed up my Debian so I'm trying re-install with a live USB, however it
> always fails. I get this message:
> 
> -------------------------------------------------------------------------------------------
> 
> Boost.Python error in job "bootloader".
> 
> Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi
> --bootloader-id=Debian --force' returned non-zero exit status 1.
> 
> Installing for x86_64-efi platform. grub-install: warning: Cannot set EFI
> variable Boot0000. grub-install: warning: efivarfs_set_variable: writing to
> fd 7 failed: No space left on device. grub-install: warning:
               ↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑
> _efi_set_variable_mode: ops->set_variable() failed: No space left on
> device. grub-install: error: failed to register the EFI boot entry: No
> space left on device.

Sorry to be naive. Could it simply be that the ESP is full?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#220014

Fromkaye n <guikaye@gmail.com>
Date2020-03-09 19:40 +0100
Message-ID<zIvtL-31t-5@gated-at.bofh.it>
In reply to#220012

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 10, 2020 at 2:12 AM David Wright <deblis@lionunicorn.co.uk>
wrote:

> Sorry to be naive. Could it simply be that the ESP is full?
>

Upon checking in GParted, the FAT32 partition with the esp flag has a size
of 50MB, and it has used only 5.86MB.

[toc] | [prev] | [next] | [standalone]

#220021

FromSteve McIntyre <steve@einval.com>
Date2020-03-09 22:30 +0100
Message-ID<zIy8j-4Mx-17@gated-at.bofh.it>
In reply to#219986
guikaye@gmail.com wrote:
>-=-=-=-=-=-
>
>Hello Friends!
>
>I messed up my Debian so I'm trying re-install with a live USB, however it
>always fails. I get this message:
>
>-------------------------------------------------------------------------------------------
>
>Boost.Python error in job "bootloader".
>
>Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi
>--bootloader-id=Debian --force' returned non-zero exit status 1.
>
>Installing for x86_64-efi platform. grub-install: warning: Cannot set EFI
>variable Boot0000. grub-install: warning: efivarfs_set_variable: writing to
>fd 7 failed: No space left on device. grub-install: warning:
>_efi_set_variable_mode: ops->set_variable() failed: No space left on
>device. grub-install: error: failed to register the EFI boot entry: No
>space left on device.

OK. Your system has run out of space to store a boot variable. These
are normally stored in NVRAM (flash) by the firmware. The most common
cause I've seen for this is error logs stored in /sys/fs/pstore/
taking up lots of space. Could you check and see if you have any files
there please?

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

[toc] | [prev] | [next] | [standalone]

#220232

FromLeandro Noferini <lnoferin@cybervalley.org>
Date2020-03-19 18:30 +0100
Message-ID<zM79v-6Rq-3@gated-at.bofh.it>
In reply to#220021
On lun, mar 09, 2020 at 09:28:56 +0000, Steve McIntyre wrote:

> >Boost.Python error in job "bootloader".
> >
> >Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi
> >--bootloader-id=Debian --force' returned non-zero exit status 1.
> >
> >Installing for x86_64-efi platform. grub-install: warning: Cannot set EFI
> >variable Boot0000. grub-install: warning: efivarfs_set_variable: writing to
> >fd 7 failed: No space left on device. grub-install: warning:
> >_efi_set_variable_mode: ops->set_variable() failed: No space left on
> >device. grub-install: error: failed to register the EFI boot entry: No
> >space left on device.
> 
> OK. Your system has run out of space to store a boot variable. These
> are normally stored in NVRAM (flash) by the firmware. The most common
> cause I've seen for this is error logs stored in /sys/fs/pstore/
> taking up lots of space. Could you check and see if you have any files
> there please?

I have the same issue trying to install debian on a HP 255 G6 with a SSD
KingDian of 120 Gb: I have nothing in /sys/fs/pstore/

I installed debian before on the same pc but on a different disk.

As suggested on the #debian-efi channel I reported the bug against
debian-installer yesterday but I did not receive any response until today.

-- 
Ciao
leandro

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web