| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008586 | Kali Linux | General Bug | public | 2024-01-10 16:29 | 2024-01-17 01:40 |
| Reporter | dadianton | Assigned To | arnaudr | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0008586: Kali-Rolling Netboot fails to install when reaching Package Selection after Base install | ||||
| Description | It appears that the latest kali-rolling netboot fails installation when attempting to select packages for install after the base installation. Attempting to retry, ignore, or switch Repos fails with the same error over and over or stops the install process. Looking at what failed it seems that the Packages file for kali-rolling/non-free-firmware is an empty zero byte file. Even though the file exists on the repo being used for installation the empty file is not read correctly resulting in a failure to install. I run a nightly refreshing repository mirror and this issue began this week sometime around Jan 8th. Previous to this we had no issues installing from the netboot image. | ||||
 |
This is not a bug. The installer fails to reach the mirror, and the mirror is 192.168.45.65. This is an IP on your local network, this is something you configured. I suppose you configured a proxy mirror, or a custom mirror, or something, early during the install steps. You did set this mirror to http://192.168.45.65/kali, but there's nothing at this IP. In short: your configuration is not correct. To be a bit more precise... It's only request for non-free-firmware that fails. So it's likely that your mirror at 192.168.45.65 is either 1) unreachable or 2) outdated, thus it doesn't have the non-free-firmware directory in there. |
 |
You didn't understand my initial explanation. I know I am using a separate mirror from the main http.kali.org repo. I mirror http.kali.org nightly to my server at 192.168.45.65/kali so I have the most recent updates daily. The directory and file for non-free-firmware are available on my repo. I double checked my version of the file on 192.168.45.65/kali against what was showing at http.kali.org and found them to be identical. I then tried to install once again and hit the same error message. I use the Package files in non-free/debian-installer/binary-amd64, main/debian-installer/binary-amd64 and free/debian-installer/binary-amd64 without issues, however when attempting to use non-free-firmware/debian-installer/binary-amd64 the file is an empty 0 byte file. I grabbed the entire /non-free-firmware directory since the installer instead points to the binary-amd64 directory and not debian-installer/binary-amd64 and got things working. This was unexpected behavior that differed from how all the other directories' Package files have behaved. This is the issue I was attempting to raise but needed to explain in more detail. |
|
|
Heya, so I just tested the netinst-amd64 image, both the latest weekly image
It's been like this for a year now, we added the non-free-firmware component to Kali back in 2023.1, but so far there was no package in there. So empty file, normal, and never been a problem. This being said, this week I moved packages from non-free to non-free-firmware (on Jan 8th, when you started experiencing the issue), so I'm a bit surprised to see that this file is still empty. Maybe there's something going on here... Can you tell me which netinst ISO you use? Where do you install, in a VM, or baremetal? Thanks! |
|
|
Actually, that's normal. The In your logs above, apt gets a "404 Not Found". This is not what you'd get for a empty file. 404 really means "file not found". You should check the directory |
|
|
Yes, in the end I figured that out. It was strange since we have had no issues excluding the non-free-firmware folders from our mirror until the Jan 8th update. I have now included those folders in the mirror and everything is working properly now. |
|
|
Glad to hear that it's resolved! We're about to write a quick blog post to notify about the change with |
