Re: daily images not deploying?

[Michael Kesper]

Hi Vincent,

On 05.11.19 02:06, McIntyre, Vincent (CASS, Marsfield) wrote:
> I was trying to retrieve
> 
> http://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/
> 
> and got a 404.
...
> PS I now see the build_netboot.log (and others) contains this failure:
> 
>   The following packages have unmet dependencies:
>haveged-udeb : Depends: libhavege2 (>= 1.9.8) but it is not installable
>   E: Unable to correct problems, you have held broken packages.

Please have a look at https://lists.debian.org/debian-boot/2019/11/msg00045.html

Bye
Michael




signature.asc
Description: OpenPGP digital signature

Re: Bug#880122: Bug#939798: floppy support in d-i

[Michael Kesper]

Hi all,

On 04.11.19 12:34, John Paul Adrian Glaubitz wrote:
> On 11/4/19 12:06 PM, Holger Levsen wrote:
>> On Sun, Nov 03, 2019 at 11:27:07PM +0100, John Paul Adrian Glaubitz wrote:
>>> And I just saw the "argument". The argument was "It's 2018". That's not
>>> an argument.
>>  
>> the longer form of the argument is: it's 2018 and except for 100 people
>> on this planet, noone is using floppies anymore.
> 
> Yes, and it's 2018 and except for a handful of people, no one is browsing
> the internet on a PC anymore. I don't see how this is an argument.
> 
>> "cognitive strain" is another argument. 90% of the people installing a
>> computer today have no idea what a floppy (disk) is. (for those who
>> don't know, it's the icon for saving a file.)
> 
> I don't really see the problem here. And I would like to see a source
> for that 90% claim. I don't think anyone who is able to install Debian
> using debian-installer doesn't know what a floppy is. Anyone who is capable
> of creating a bootable USB flash drive will absolutely know what a floppy
> is.

How should that be true?
 
> I really have the impression that some people are trying with all force
> to smash out support for older architectures and hardware 

No, the support will be kept but without confusing people.

> Debian is certainly not the distribution for Linux beginners so there is
> really no reason to pretend that such changes make any difference
> in user-friendlyness.

Non sequitur.

Bye
Michael



signature.asc
Description: OpenPGP digital signature

Re: Bug#367515: Bug#749991: debian-installer: Wrong kernel in debian-installer package

[Michael Kesper]

Hi all,

On 28.10.19 15:56, Cyril Brulebois wrote:
> Philipp Wollschlegel  (2019-10-28):
>> On 28.10.19 15:11, Ben Hutchings wrote:
>>> On Sun, 2019-10-27 at 20:18 +0100, Holger Wansing wrote:
 Bugreport against kernel version mismatch, when using outdated or broken 
 netboot images:
>>
>> This isn't a package / message  problem, this is a process problem.
...
> That's not true for stable or oldstable. Also, we ship netboot images in
> packages, use that and be happy?
> 
> If users are tracking testing or unstable, well, yes; those
> distributions are WIP.
> 
> But the script you quoted seems to be about buster, so using d-i-n-i
> packages should be a no-brainer.
> 
>   https://tracker.debian.org/pkg/debian-installer-netboot-images

But even those packages do not contain the kernel modules without which the
installation can't work.
So as soon as there's a kernel upgrade due to security reasons, you got to
make sure to update your tftp files.
This adds a whole new layer of abstraction (Jenkins jobs etc.) to an already
complicated process: The basic install process just is not self-contained
as it is the case with even the netboot CD/usb image.

My 2 cents
Michael




signature.asc
Description: OpenPGP digital signature

Re: how to setup a small local Debian mirror to install a VM without an internet access

[Michael Kesper]

Hi Fred,

On 04.10.19 09:52, Fred Boiteux wrote:
> Meanwhile, I've tried to understand what is going on : on my VM being 
> installed, stuck because the standard 'locales' package can't be installed, 
> as the given repository is not signed and then ignored, I've done this : I've 
> connected to the VM with SSH, then I've done a 'chroot /target' to check what 
> is going on. Trying to install the locales packages don't actually work :
> 
>   # apt-get install locales
>   Reading package lists... Done
>   Building dependency tree... Done
>   Package locales is not available, but is referred to by another package.
>   This may mean that the package is missing, has been obsoleted, or
>   is only available from another source
>   E: Package 'locales' has no installation candidate
> 
> 
> Trying an apt update gives the same error message than in the previous log :
> 
>   # apt update
>   Ign:1 http://192.168.254.254/buster_debian_installer buster InRelease
>   Get:2 http://192.168.254.254/buster_debian_installer buster Release [33.5 
> kB]  Ign:3 http://192.168.254.254/buster_debian_installer buster 
> Release.gpg
>   Reading package lists... Done
>   E: The repository 'http://192.168.254.254/buster_debian_installer buster 
> Release' is not signed.
>   N: Updating from such a repository can't be done securely, and is therefore 
> disabled by default.
>   N: See apt-secure(8) manpage for repository creation and user configuration 
> details.
> 
> I've checked the apt config :
> 
>   # cat target/etc/apt/apt.conf.d/00AllowUnauthenticated
>   APT::Get::AllowUnauthenticated "true";
>   Aptitude::CmdLine::Ignore-Trust-Violations "true";
> 
> 
> And looking (on a working Buster system) the apt-secure manual page suggest 
> me to add following line in this conf file :
> 
> Acquire::AllowInsecureRepositories "true";
> 
> 
> With this config item, the « apt update » runs well, the error message 
> becomes a warning message :

I think it would be better to sign your archive instead.
With your modification you would completely disable checking GPG signatures for 
every repository (who checks warnings?)
Sadly, the Debian wiki is full of outdated setups but I cannot find a stringent 
howto for setting up a trusted repo.

Reprepro seem like a possible way to go.
It overcomes another misfeature of these minimal repositories: You cannot pin 
packages to versions
of this repository but have to set them on hold, else you always risk getting 
packages from Debian proper.

My 2 cents
Michael



signature.asc
Description: OpenPGP digital signature

Re: pxe booting qemu

[Michael Kesper]

Hi John,

On 23.09.19 10:27, john doe wrote:
> I'm currently using the netinst.iso file to install Debian as a guest VM
> using Qemu.
> This approach works fine if you want to install multiple VM on the same
> host.
> My goal with using PXE booting is to test how to install from the
> network using Qemu, that way, I can get everything the way I like before
> implementing PXE booting on my network.

I'd start with a real tftp server on a Debian box (You wrote that you were on 
windows).
Configuration of tftp server with qemu and without are different and
probably so different that it makes no sense to try the qemu one first.
 
> What I want is:
> - Fully install Debian from the network using a preseed file (the less I
> do on the host on which I want to install Debian the better)

preseed.cfg is the next step. You need to be able to get your boot media
via network first.
 
> What I don't want:
> - Using a phisical media (usb key, cd/dvd rom ...)
> 
> As far as I understand it, PXE booting is the only way to avoid using a
> usb key to install Debian, is that correct?

Yes.

But in my opinion it's better to start from solid grounds: 
A reliable DHCP and TFTP server on a Debian system.
Best if you start in a seperate network (or at least network segment) so you
don't risk influencing your productive systems.
Maybe it's even easier to start with an integrated solution like
fai, I didn't try that yet.

Oh, and by the way: If you try to pxeboot via UEFI, many tutorials etc.
are plain wrong: You don't use pxelinux.0 in that case at all!
You'll be loading bootnetx64.efi which then will load grubnetx64.efi.
This enables (but does not depend on) secure boot.

This guide is relatively good because you can verify that each step worked.
No mentioning of UEFI pxe boot, though:

https://wiki.debian.org/PXEBootInstall

NB also this (from that guid):

If the kernel in the netboot image gets out of sync with the kernel module 
packages, 
then the modules won't load and the install will fail,
the usual symptoms are that messages about "missing symbols" appear
in the ctrl-alt-f4 console.

To fix this, update the kernel and initrd on the netboot server.

About UEFI PXE, hava look at this thread:
https://lists.debian.org/debian-boot/2019/02/msg00285.html

FAI: http://fai-project.org/features/

Best wishes
Michael



signature.asc
Description: OpenPGP digital signature

Re: pxe booting qemu

[Michael Kesper]

Hi John,

On 22.09.19 09:47, john doe wrote:
> Hi,
> 
> I'm trying to install Debian 10.1 using pxe and qemu.

Is pxe booting a strong requirement for you?
It's much easier to start booting from a cdrom image.

A "netinst" image is sufficient:
https://www.debian.org/CD/netinst/

Bye
Michael



signature.asc
Description: OpenPGP digital signature

Adding flexibility to Debian Installer paths

[Michael Kesper]

Hi all,

I was wondering whether it would be possible to add some more flexibility to
the paths of Debian installer as used by e.g. netboot.tar.gz for PXE install.
At the moment, it's not trivially possible to offer e.g. Debian 10 and 9 or 11
at the same time for tftpboot as paths are hardcoded as e.g.:

grub.cfg (excerpt):

menuentry --hotkey=s 'Install with speech synthesis' {
set background_color=black
linux/debian-installer/amd64/linux vga=788 speakup.synth=soft --- quiet
initrd   /debian-installer/amd64/initrd.gz
 ^ can there really be only one?
}

which I turned for my purposes into:

menuentry --hotkey=s 'Install with speech synthesis' {
set background_color=black
linux/debian-10/debian-installer/amd64/linux vga=788 speakup.synth=soft 
--- quiet
initrd   /debian-10/debian-installer/amd64/initrd.gz
 ^^ So we can have debian-9, debian-11 etc.
}

Having to change all affected places after downloading the bootfiles can be 
error prone
and should be avoidable, I think.

Best wishes
Michael



signature.asc
Description: OpenPGP digital signature

Re: Download of old CD images not possible?

[Michael Kesper]

Hi all,

On 01.08.19 11:46, Samuel Thibault wrote:
> Michael Kesper, le jeu. 01 août 2019 11:40:59 +0200, a ecrit:
>> There seems to be currently no way to download other
>> CD images than current and current-live:
>>
>> https://cdimage.debian.org/debian-cd/
>> There are no links to oldstable or oldoldstable and no paths to other 
>> releases.
> 
> They are in the archive: https://cdimage.debian.org/cdimage/archive/

Ok but this is not mentioned anywhere on the download pages.
-> Documentation bug?

Michael



signature.asc
Description: OpenPGP digital signature

Download of old CD images not possible?

[Michael Kesper]

[Sorry if this should be posted on another list]

There seems to be currently no way to download other
CD images than current and current-live:

https://cdimage.debian.org/debian-cd/

Parent Directory-
[DIR]   10.0.0-live/2019-07-06 13:20-
[DIR]   10.0.0/ 2019-07-06 20:49-
[DIR]   current-live/   2019-07-06 13:20-
[DIR]   current/2019-07-06 20:49-
[DIR]   project/2005-05-23 18:50-
[ARC]   ls-lR.gz

There are no links to oldstable or oldoldstable and no paths to other releases.

Bye
Michael



signature.asc
Description: OpenPGP digital signature

Re: Fragility of PXE netboot

[Michael Kesper]

Hi Cyril,

On 17.07.19 16:25, Cyril Brulebois wrote:
> We maintain d-i-n-i so that people don't have to deal with the tarball:
>   
> https://packages.debian.org/search?searchon=sourcenames=debian-installer-netboot-images

Thanks. So we need to make sure on e.g. a Jenkins instance /
bootstrapping machine we react to updates of that package.
Nasty but doable.

Thank you!
Michael




signature.asc
Description: OpenPGP digital signature

Bug#932272: [debian-installer] Shasums of "other image" variants (hd-media, netboot etc.) not signed

[Michael Kesper]

Package: debian-installer
Severity: important
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

--- Please enter the report below this line. ---

Images for system installation need to be checkable against
tampering, otherwise breaking any security chain.
That's why Debian CD-Images come with sha*sums which are signed by
Debian CD signing keys (https://www.debian.org/CD/verify).

This is not the case for all "other images" (hd-media, netboot).
They're official ways of installing Debian, being mentioned in
the install manual:
https://www.debian.org/releases/stable/amd64/ch04s02.de.html#where-files

Is there a way to make sure one gets something officially released by
Debian when using these install media?

Bye
Michael



signature.asc
Description: OpenPGP digital signature

Fragility of PXE netboot

[Michael Kesper]

Hi all,

[reposting here instead of debian-user]

how do you handle the fragility of netboot.tar.gz regarding
kernel updates? (When the kernel modules get updated, the
kernel from netboot.tar.gz cannot find them and (automated)
installs will break.)

Is it possible / recommended to just use a netinst.iso
for (UEFI) PXE booting instead?

Bye
Michael





signature.asc
Description: OpenPGP digital signature

Re: enabling salsa-CI pipeline

[Michael Kesper]

Hi Phil,

On 12.07.19 15:08, Philip Hands wrote:
> Hi All,
> 
> I just configured salsa-CI pipeline for 'user-setup', and it seems to
> work, so I thought I'd say what was involved so that others can do the
> same for other bits of d-i in a similar manner ... if they get to it
> before I do (and also so I don't forget things next time I do it :-) ).
> 
> The first thing to do is configure the 'Custom CI config path' to be:

A detailed description can be found under:
https://salsa.debian.org/salsa-ci-team/pipeline

[...]
 
> I'm sure there are ways of scripting the above using the gitlab API, so
> once I've discovered how I'll think about applying similar changes to
> all our repos -- if you already know how to prod the API, feel free to
> tell me.

Did you ask on #salsaci?
Afaik there is currently no mailing list re salsa-ci.

Bye
Michael




signature.asc
Description: OpenPGP digital signature

Re: Bug: Buster 10.0 Testing 20190617 Image LiveCD Will Not Boot

[Michael Kesper]

Hi John,

> There were no replies to my post to
>  of
> .
> 
> I then posted to 
> starting with
> 
> where there were various replies, suggestions and my
> responses/actions to same.
> 
> The net my attempts to report a bug by validating my concerns
> of bugs in the Buster Live CD image were such I gave up.  If I
> could not be just a bit successful in confirming to the Debian
> Community of bugs, then experience has already demonstrated
> opening a bug report would be far more time consuming and way
> too much spinning of others and more.
> 
> I had no guidance how to capture the error messages flashing on
> the  splash screen.  

Can you interrupt them by hitting the "Break" key on your keyboard?
(Might require some key combination on laptops)
Otherwise, there was a "bootdelay" parameter mentioned.
As can be seen on
https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html
the parameter really is "boot_delay" with an underscore.

> I managed using my own technical
> skills, knowledge and alot of time to obtain the complete and
> exact error messages that were flashing on the boot splash
> screen.  Despite having the exact error messages and what
> conditions the error messages displayed in I still received
> basically an opinion of not a Buster issue.

Sorry, I did not find them in that thread?
 
> I gave up as too much wild goose chasing advise or m being told
> not a bug at all.  In my opinion the facts were not being not
> accepted of what was clear to me a bug (I actually discovered a
> few bugs and only reported the easy bug in my technical
> opinion) and not much help in the ask I posted for how to
> obtain the error messages flashing on the splash screen.

In this case you might need the same (or at least similar:
AMD CPU/GPU, legacy BIOS boot) hardware to reproduce this issue 
so it's not that easy.
 
[...]

> A familiar Open Source project response is they do not have the
> time to work on bugs/issues, works for them so cannot exist,
> nobody else has reported the issue/bug so cannot exist.  The
> latter two are actually far from truth of determining if a bug
> exists.  I worked many years in roles where the issue reported
> was a bug and often serious, but only one person/client often
> was only experiencing the issue.  I have worked on bugs that
> only occur once every few months.  I have found the cause of
> bugs in less than an hour the software engineering teams have
> not been able to identify in two years.  This is not me
> bragging or similar.  The point here is it takes a special set
> of soft skills, technical skills and problem solving skills
> that seems to be less and less understood and strived for with
> software/firmware.  

I can relate to this.

I don't have any solution though, sadly.
As Debian is completely made up of volunteers, everyone does what they
can but time is limited for everyone.

[...]

> As to the trying the released Buster Live, I happened to do so
> for secondary reasons this past weekend.  Serious issues in my
> opinion that may or may not be Live image specific.  I do not
> know as I was not going to investigate.

Unfortunately I cannot reproduce your specific bug.
When testing the live image with kvm though, I noticed many
squashfs errors, though, when shutting down.
Will try to report that when I find the time.

Best wishes
Michael



signature.asc
Description: OpenPGP digital signature

Re: Bug: Buster 10.0 Testing 20190617 Image LiveCD Will Not Boot

[Michael Kesper]

Hi John,

> Using the LiveCD LXDE image of 20190617 Will not boot to Live
> Image.
> 
> Messages flash very quickly that make it difficult to see the
> actual messages.  Adding the "debug" option to the boot command
> line for the LiveCD boot has no impact on the speed or type of
> error occurring.
> 
> The best I can see from several attempts to boot the LiveCD
> image is some sort of error in the options for booting the
> LiveCD image.
> 
> If one chooses any other menu option to boot such as installing
> Debian there is no error and the image boots to the install or
>  intended menu item of initial boot splash screen to select
> what one wants.
> 
> This is actually not strictly a Buster  Testing 10.x error.
> This is fact also occurs more selectively with Debian Stretch
> 9.9.0 and many prior versions.  I will skip the messy details
> of how I have played the bugs against each other to workaround
> what is in essence the same bug.

Just some general question:
Did you verify the checksums of the images you downloaded?
They are in the same directory where the iso images are placed.

Did you have a chance to try them on a different PC or with kvm?

Also there are official debian-live-10.0.0... isos now available. :)

Best wishes
Michael





signature.asc
Description: OpenPGP digital signature

Re: Building CD images including firmware

[Michael Kesper]

Hi all,

On 16.05.19 10:09, Thomas Schmitt wrote:
> John Paul Adrian Glaubitz wrote:
>> But in the end, I get:
>> libisofs: WARNING : Cannot add /debian to Joliet tree. Symlinks can only be
>> added to a Rock Ridge tree.
> 
> This is normal, unavoidable, and harmless. All debian-cd runs will issue
> this kind of message if symbolic links are present in the input trees.

Maybe a message could be added to the script telling the user so?

Best wishes
Michael



signature.asc
Description: OpenPGP digital signature

Re: Debian buster EFI netinstall timeout getting grubx64.efi - Bug#928750

[Michael Kesper]

Dear list members,

I filed a bug regarding the issue:
Bug #928750 [grub-efi-amd64] [grub-efi-amd64] On EFI pxeboot grubx64.efi only 
loads config when loaded directly
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928750

It seems you need to use
  filename "debian-installer/amd64/grubx64.efi";
instead of
  filename "debian-installer/amd64/bootnetx64.efi";
contradicting documentation:
https://d-i.debian.org/manual/en.amd64/ch04s05.html

bootnetx64.efi seems to be the shim nowadays 
(https://lists.debian.org/debian-efi/2019/01/msg4.html)

And then grub is searching its config files not in the same folder as 
grubx64.efi but in the root path
of your tftp dir.

Bye
Michael



signature.asc
Description: OpenPGP digital signature

Re: Debian buster EFI netinstall timeout getting grubx64.efi

[Michael Kesper]

Dear Rory,

On 09.05.19 12:18, Rory Campbell-Lange wrote:
> I'm no expert but are you on a monitor or console. If the latter it is
> possible that you need to set the Supermicro setup to redirect the first
> serial port. Alternatively I believe you can reconfigure the netboot
> configuration for serial configuration.

For debugging purposes?
 
> Recent Supermicros have a handy HTML5 console view available via the BMC
> which should allow you to connect to both a redirected virtual screen or
> serial console (where the latter is typically serial 2, I believe).

I could see the local console screen without problems (screenshot), it's just
that there's no info what's happening on it.
The idea is that grubx64 loads its menu and we load a preseed.cfg via that.

Bye
Michael



signature.asc
Description: OpenPGP digital signature

Debian buster EFI netinstall timeout getting grubx64.efi

[Michael Kesper]

Dear list members,

please excuse my ignorance, but I cannot figure out how to netboot Debian 
buster.
Can you give me pointers to a working setup for multiple distributions (e.g. 
Debian 9 and Debian 10)
with EFI boot?

I come as far as getting the GRUB2 shell displayed (version 2.0.2+dfsg1-16).
I can see "Fetching Netboot Image" (see screenshot), then after 30s the Grub 
shell gets displayed.
I can see no more files being tried to download, no NAKs.

Setup:
Supermicro Server with E5-2600, boot mode: UEFI

Network boot gets started by choosing UEFI: IP4 Intel... in boot menu.
F12 does not work (might only try IPv6?)

dhcpd: isc-dhcpd-4.1.1-P1
tftp-hpa 0.49, with remap, with tcpwrappers
(Yes, CentOS host...)

Relevant dhcp setup:

if exists dhcp-parameter-request-list {
   # Always send the PXELINUX options (specified in hexadecimal, ie: 208 = 
0xd0, 209 = 0xd1, etc.)
   option dhcp-parameter-request-list = concat(option 
dhcp-parameter-request-list,d0,d1,d2,d3);
 }

group  {
use-host-decl-names on;
max-lease-time 300;
default-lease-time 120;
next-server 10.45.10.5;

  host ssfnkvm112 {
option host-name "myhost";
hardware ethernet 0C:C4:...;
fixed-address 10.45.10.32;
filename "debian-10/bootnetx64.efi";
  }
}

tftproot is:
/var/lib/tftproot

As there are different distributions served from here, I created a folder
/var/lib/tftproot/debian-10
and extracted netboot.tar.gz below it.

I added several symlinks, last setup was this:
(Yes, probably the server should not be run as root, but that's another 
issue...)

# ls -lh /var/lib/tftpboot/debian-10
total 8.0K
lrwxrwxrwx 1 root root   36 May  9 11:34 boot-screens -> 
debian-installer/amd64/boot-screens/
lrwxrwxrwx 1 root root   37 May  8 11:15 bootnetx64.efi -> 
debian-installer/amd64/bootnetx64.efi
drwxrwxr-x 3 root root 4.0K Apr 10 20:55 debian-installer
lrwxrwxrwx 1 root root   27 May  9 10:59 grub -> debian-installer/amd64/grub
lrwxrwxrwx 1 root root   34 May  9 10:58 grubx64.efi -> 
debian-installer/amd64/grubx64.efi
lrwxrwxrwx 1 root root   47 May  8 13:46 ldlinux.c32 -> 
debian-installer/amd64/boot-screens/ldlinux.c32
lrwxrwxrwx 1 root root   33 May  8 13:46 pxelinux.0 -> 
debian-installer/amd64/pxelinux.0
lrwxrwxrwx 1 root root   35 May  8 13:46 pxelinux.cfg -> 
debian-installer/amd64/pxelinux.cfg
-rw-rw-r-- 1 root root   55 Apr 10 20:55 version.info


Excerpt from logs:
May  8 16:02:07 ssfnctl111 dhcpd: DHCPREQUEST for 10.45.10.32 (10.45.10.5) from 
0c:c4:xxx via eth0
May  8 16:02:07 ssfnctl111 dhcpd: DHCPACK on 10.45.10.32 to 0c:c4:xxx via eth0
May  8 16:02:07 ssfnctl111 in.tftpd[21355]: RRQ from :::10.45.10.32 
filename debian-installer/amd64/bootnetx64.efi
May  8 16:02:07 ssfnctl111 in.tftpd[21355]: tftp: client does not accept options
May  8 16:02:08 ssfnctl111 in.tftpd[21356]: RRQ from :::10.45.10.32 
filename debian-installer/amd64/bootnetx64.efi
May  8 16:02:08 ssfnctl111 in.tftpd[21357]: RRQ from :::10.45.10.32 
filename debian-installer/amd64/grubx64.efi
(Nothing re tftp afterwards)

Thanks
Michael


signature.asc
Description: OpenPGP digital signature

Re: bts reassign 878722 partman-auto

[Michael Kesper]

Dear Cyril,


On 07.11.2017 08:12, Cyril Brulebois wrote:
> Michael Kesper <mkes...@schokokeks.org> (2017-11-06):
>> I think this bug is specific to partman-auto.
>> Partman should allow rescanning devices and recognize NVMe devices when
>> preconfigured with /dev/sda.
>> Alternatively, there should be an installation target "largest disk" or
>> something similar.
> 
> I'm not sure hardcoding /dev/sda as the target device is right when all you
> have is NVMe… Don't feed wrong info through preseed in the first place?

Yes sure but why can't I correct it after the fact?
Even "rescanning disks" does not let you chose any other disks.

> Also, “largest disk” doesn't seem too good an idea, as evidenced here:
>   https://lists.debian.org/debian-boot/2017/11/msg00028.html

Is there a way of chosing "first internal disk" then?
Imagine I want to create one installation medium for laptops which only
differ whether they are set up with a NVM or a sata SSD.
I did not find any documentation helping me with this.

Best wishes
Michael



signature.asc
Description: OpenPGP digital signature

bts reassign 878722 partman-auto

[Michael Kesper]

control: reassign -1 partman-auto


Dear maintainers,

I think this bug is specific to partman-auto.
Partman should allow rescanning devices and recognize NVMe devices when
preconfigured with /dev/sda.
Alternatively, there should be an installation target "largest disk" or
something similar.

Best wishes
Michael





signature.asc
Description: OpenPGP digital signature

Bug#878722: bts reassign 878722 partman

[Michael Kesper]

control: reassign -1 debian-installer

Dear maintainers,

I think this bug is specific to partman.
Partman should allow rescanning devices and recognize NVMe devices when
preconfigured with /dev/sda.
Alternatively, there should be an installation target "largest disk" or
something similar.

Best wishes
Michael



signature.asc
Description: OpenPGP digital signature

Bug#878722: bts reassign 878722 partman-partitioning

[Michael Kesper]

signature.asc
Description: OpenPGP digital signature

Bug#878722: Preseeding: Unable to correct partitioning manually if preseed fails

[Michael Kesper]

Hi,

Additional information:
Preseeding was configured for /dev/sda but the system did only contain a
NVMe drive so /dev/sda pointed to the installation usb stick.

Best wishes
Michael

Bug#878722: Preseeding: Unable to correct partitioning manually if preseed fails

[Michael Kesper]

Package: debian-installer
Severity: normal

Dear Maintainer,

If preseeding the debian-9.2-amd64-netinst installer, it's not possible to
correct a failed automatic partitioning.
Installation only claims that there's no root file system chosen and I should
correct it but I can't get past that screen, even when rescanning harddisks.

Preseed.cfg regarding partitioning:
d-i partman-auto/disk string /dev/sda
d-i partman-auto/method string crypto
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-md/device_remove_md boolean true
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true
d-i partman-auto/choose_recipe select atomic
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
d-i partman-auto-crypto/erase_disks boolean false
d-i partman-auto-lvm/guided_size string max
d-i partman-auto-lvm/new_vg_name string crypt



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
 Contents of the preconfiguration file (for strecth)
### Localization
d-i debian-installer/locale string de_DE.UTF-8
d-i debian-installer/language string de
d-i debian-installer/country string DE

# Keyboard selection.
d-i keyboard-configuration/xkb-keymap select de
d-i keyboard-configuration/layoutcode string de
d-i keyboard-configuration/variantcode string

### Network configuration
# if more than one interfaces, skip displaying a list
d-i netcfg/choose_interface select auto

# link detection timeout, default 3
d-i netcfg/link_detection_timeout string 5

# for slow networks, set dhcp timeout to 60 seconds, default 3
d-i netcfg/dhcp_timeout string 10

# any hostname and domain assigned by dhcp or reverse dns takes precedence
# over values set here
# uncomment me after test phase
# d-i netcfg/get_hostname string unassigned-hostname
# d-i netcfg/get_domain string unassigned-domain

# disable annoying wep/wpa key dialog, we dont want installation over air
d-i netcfg/wireless_wep string

# enable non-free firmware for wifi adapter
d-i hw-detect/load_firmware boolean true

### Mirror settings
## Change URL to local mirror
## TODO: howto set two or more mirrors with puppet
# ftp.informatik.rwth-aachen.de == http.informatik.rwth-aachen.de
d-i mirror/country string manual
d-i mirror/http/hostname string ftp2.de.debian.org
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string

### Accounts setup
# Skip creation of root account, Admin Station Account will be able to use sudo
d-i passwd/root-login boolean false

# Create a normal user account for administration purposes
# Everything needs to be entered manually

### Clock and time zone setup
d-i clock-setup/utc boolean true
d-i time/zone string Europe/Berlin

# Use ntp
d-i clock-setup/ntp boolean true

### Partitioning
## The system have only one disk and the installer will default to using that

# If the system has free space you can choose to only partition that space.
# This is only honoured if partman-auto/method (below) is not set.
#d-i partman-auto/init_automatically_partition select biggest_free

# Alternatively, you may specify a disk to partition. If the system has only
# one disk the installer will default to using that, but otherwise the device
# name must be given in traditional, non-devfs format (so e.g. /dev/sda
# and not e.g. /dev/discs/disc0/disc).
# For example, to use the first SCSI/SATA hard disk:
d-i partman-auto/disk string /dev/sda
# In addition, you'll need to specify the method to use.
# The presently available methods are:
# - regular: use the usual partition types for your architecture
# - lvm: use LVM to partition the disk
# - crypto:  use LVM within an encrypted partition
d-i partman-auto/method string crypto

# If one of the disks that are going to be automatically partitioned
# contains an old LVM configuration, the user will normally receive a
# warning. This can be preseeded away...
d-i partman-lvm/device_remove_lvm boolean true
# The same applies to pre-existing software RAID array:
d-i partman-md/device_remove_md boolean true
# And the same goes for the confirmation to write the lvm partitions.
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true

# You can choose one of the three predefined partitioning recipes:
# - atomic: all files in one partition
# - home:   separate /home partition
# - multi:  separate /home, /var, and /tmp partitions
d-i partman-auto/choose_recipe select atomic

# Or provide a recipe of your own...
# If you have a way to get a recipe file into the d-i environment, you can
# just point at it.
#d-i partman-auto/expert_recipe_file string 

Bug#778426: Package: installation-reports

[Michael Kesper]

Package: installation-reports

Comments/Problems:

As much as I try, if I'm not using the whole disk, if I choose encrypted 
containers, I always end up with each encrypted filesystem in its own 
container instead of one encrypted container for all filesystems. So, 
e.g. for encrypted swap and root I have to enter two passphrases at boot.

If using the whole disk, this always worked as expected.

Bye
Michael


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54dfbf76.3040...@schokokeks.org

Bug#775060: Package: installation-reports

[Michael Kesper]

Package: installation-reports

Boot method: usb stick (unetbootin media)
Image version: 
http://cdimage.debian.org/cdimage/jessie_di_beta_2/amd64/iso-cd/debian-jessie-DI-b2-amd64-netinst.iso

Date:2015-01-09

Comments/Problems:

Unable to activate rescue mode.
Adding boot parameter rescue/enable=true and/or manually loading the 
rescue udeb didn't change anything, only normal installation was shown.


Bye
Michael


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54b19802.9040...@schokokeks.org

Bug#489588: closed by Frans Pop [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]) (Re: Bug#489588: Install report Medion akoye E1210 (MD96910))

[Michael Kesper]

Hi,

* Debian Bug Tracking System [EMAIL PROTECTED] [2008-07-17 10:24:10 +]:
 As the system should be supported well with current daily builds of the 
 installer I'm closing this report.

Sadly I must ask to reopen this bug.
Daily installer builds still immediately reboot after uncompressing the
initrd. (Read something like ABORT, but it really boots too fast).
Tried again with hd-media of 18th and 19th july.

Best wishes
Michael
-- 
Free Software Foundation Europe (FSFE) [] (http://fsfeurope.org)
Join the Fellowship of FSFE! [][][]   (http://fsfe.org/join)
Your donation powers our work! ||  (http://fsfeurope.org/donate)


signature.asc
Description: Digital signature

Bug#489588: Install report Medion akoye E1210 (MD96910)

[Michael Kesper]

Hi,

On Mon, Jul 07, 2008 at 01:56:04AM +0200, Jérémy Bobbio wrote:
 On Sun, Jul 06, 2008 at 11:49:22PM +0200, Michael Kesper wrote:
  network card (r1000?) isn't detected
  module r8169 is loaded and chokes, see syslog
 
 You forgot to attach it, it seems…

Sorry, it was too late! ;)

Logs now attached, all logs also available at
http://valshaq-waldschrat.de/install/

An opensuse 2.6.25.5 kernel loads this driver without errors.

Best wishes
Michael
-- 
Free Software Foundation Europe (FSFE) [] (http://fsfeurope.org)
Join the Fellowship of FSFE! [][][]   (http://fsfe.org/join)
Your donation powers our work! ||  (http://fsfeurope.org/donate)


syslog.gz
Description: Binary data


hardware-summary.gz
Description: Binary data


signature.asc
Description: Digital signature

Bug#489588: Install report Medion akoye E1210 (MD96910)

[Michael Kesper]

Hi,

On Mon, Jul 07, 2008 at 12:18:02PM +0200, Frans Pop wrote:
  module r8169 is loaded and chokes, see syslog
 
 Known issue; see: http://bugs.debian.org/471892
 Upgrading to the 2.6.25 kernel from unstable may well fix this.

Will have to try. How can I do this during install?
With 2.6.24 I have no network and after installation I do not get any
drives.

  The installed system fails to load its root file system and I'm unable
  to get anything useful after it falls into the emergency shell
  (initramfs).
 
 Well, you're not really giving us anything useful either here...
 My guess is that you are affected by the first erratum listed for the 
 Beta2 release: http://www.debian.org/devel/debian-installer/errata.
 
 Please check (in the debug shell) the contents of /etc/fstab and compare 
 that to what disk devices are being recognized (by listing contents 
 of /dev/ or using the output of dmesg).
 Also provide the output of 'echo $ROOT'.

The problem is that there are NO drives (sdx) under dev and I don't
know how to get the system to recognize any media (also no usb devices etc.).
$ROOT gives /dev/sda1 which should be correct.
If I put a newer business-card iso image on the beta2 hd-media,
I'm not able to install because the installer does not recognize the
codename of the distribution.
If I'm trying a daily build for the hd-media, I was yet unlucky as
these immediately rebooted after unpacking the kernel.

Thank you!
Michael


signature.asc
Description: Digital signature

Bug#489588: Install report Medion akoye E1210 (MD96910)

[Michael Kesper]

On Mon, Jul 07, 2008 at 04:06:17PM +0200, Frans Pop wrote:
 That is very strange as the driver needed by your disk controller is a 
 standard ahci driver. Please check in the initramfs debug shell:
 - if that driver is loaded
 - if some other (IDE?) disk driver is loaded
 - any messages in 'dmesg' regarding recognition of hard disks

udev aborts its work before any of these devices are created.
Drivers seem to be half-loaded, upon modprobe ahci (for example), the
system hangs. It takes already several minutes to reach the initramfs
debug shell.

 Are there any /dev/hda devices (other than maybe for an IDE CD drive)?

No, there are no ide devices in this system.
This device is a version of the MSI Wind U100:
http://en.wikipedia.org/wiki/MSI_Wind

Best wishes
Michael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#489588: Install report Medion akoye E1210 (MD96910)

[Michael Kesper]

On Mon, Jul 07, 2008 at 04:06:17PM +0200, Frans Pop wrote:
 On Monday 07 July 2008, Michael Kesper wrote:
  Will have to try. How can I do this during install?
  With 2.6.24 I have no network and after installation I do not get any
  drives.
 
 Change to a debug shell (on VT2 or VT3) some time after base system 
 installation is complete but no other steps are actually running and do:
 - chroot /target
 - wget http://debian mirror/debian/pool/main/l/linux-2.6/package
 - dpkg -i package

This did the trick. Now I'm able to boot into my system.
Thanks! :)
A report is at http://valshaq-waldschrat.de/install/

Best wishes
Michael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#489588: Install report Medion akoye E1210 (MD96910)

[Michael Kesper]

Package: installation-reports

Boot method: hd-media, netinst 
Image version: 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/hd-media/boot.img.gz
http://cdimage.debian.org/cdimage/lenny_di_beta2/i386/iso-cd/debian-LennyBeta2-i386-netinst.iso
Date: 2008-07-06

Machine: Medion akoya mini E1210 (MD96910)
Partitions: 
artitions: #id  length  typefs  pathname
(0,0,0)(0,0,62) -1  0-32255 32256   primary label   /dev/sda-1
(0,1,0)(850,254,62) 1   32256-69997132796999681024  
primary ext3/dev/sda1
(851,0,0)  (8667,254,62)3   6999713280-71296727039  64297013760 
primary extended/dev/sda3
(851,0,0)  (851,0,0)-1  6999713280-6999713791   512 
logical label   /dev/sda-1
(851,0,1)  (851,1,62)   -1  6999713792-699991   64000   
logical label   /dev/sda-1
(851,2,0)  (1093,254,62)5   699992-8998456319   1998678528  
logical linux-swap  /dev/sda5
(1094,0,0) (1094,0,62)  -1  8998456320-8998488575   32256   
logical label   /dev/sda-1
(1094,1,0) (8667,254,62)6   8998488576-71296727039  62298238464 
logical ext3/dev/sda6
(8668,0,0) (9728,254,62)2   71296727040-80023749119 8727022080  
primary fat32   /dev/sda2
(9729,0,0) (9729,80,62) -1  80023749120-80026361855 2612736 
primary label   /dev/sda-1


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [E]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:
network card (r1000?) isn't detected
module r8169 is loaded and chokes, see syslog
The installed system fails to load its root file system and I'm unable to
get anything useful after it falls into the emergency shell (initramfs).

Best wishes
Michael




  



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]