Hi,
I am used to installing Debian by PXE and serial console. For that
purpose I'm familiar with editing the isolinux config files to have
the kernel serial settings (console=ttyS… etc) in isolinux/txt.cfg.
Now for the first time I am trying to install a system that has a
management controller th
Hi Steve,
Thanks for getting back to me.
On Sat, Nov 21, 2020 at 06:39:02PM +, Steve McIntyre wrote:
> The best way forward is to open a severity:important bug against the
> libefiboot1 package here. Could you do that please?
Sure. Here you go:
https://bugs.debian.org/cgi-bin/bugreport.cgi?b
On Sat, Nov 21, 2020 at 01:35:48AM +, Andy Smith wrote:
> Nov 21 01:02:25 grub-installer: info: Running chroot /target grub-install
> --force-extra-removable --force "dummy"
> Nov 21 01:02:25 grub-installer: Installing for x86_64-efi platform.
> Nov 21 01:02:25 grub-i
Hi,
I have a machine whose only storage is NVMe and I think this forces
me to use EFI if I want to boot it. This is something I've never
done before as I've always got by with the BIOS set to legacy boot.
It's not going well but I don't know if that is due to something I'm
doing wrong.
At the poi
Hello,
On Mon, Sep 14, 2020 at 08:08:39AM +0200, john doe wrote:
> Not realy an answer to your question, you could rebuild the package to
> your liking then fetch it from a local mirror.
Since my strace did show that it tries to also open
/tmp/mdadm.conf.d, maybe I could make that directory and p
Hello,
I did work out that mdadm in d-i uses a config file of
/tmp/mdadm.conf instead of the usual /etc/mdadm/mdadm.conf.
I thought this meant that if I put the things I needed into that
file then that would work out.
Unfortunately I see that any time you go into mdcfg it clobbers any
existing /
Hello,
TL;DR: the Debian installer uses an mdadm.conf located at
/tmp/mdadm.conf.
On Thu, Sep 10, 2020 at 04:18:27PM +, Andy Smith wrote:
> I have confirmed that creating a new array from the d-i shell using
> mdadm commands manually does result in a new array without a bbl (so
Hi,
By default mdadm will create md arrays with a bad blocks list
feature unless you tell it not to. I wish to tell the Debian
installer's mdadm to not do this.
The documented way to tell mdadm to not create arrays with a bad
blocks list is to put:
CREATE bbl=no
in /etc/mdadm/mdadm.conf
Once a
Package: installation-reports
Boot method: CD
Image version: http://cdimage.debian.org/cdimage/etch_di_rc2/i386/iso-cd/
Date: 03 Apr 2007
Machine: Supermicro PDSMi-based rackmount system
Processor: Core2Duo Xeon 2.4GHz
Memory: 4GiB
Partitions: No partitions were created because didn't get that fa
9 matches
Mail list logo
