An attempt to configure apt failed

Enshuldigung bitte. I don’t speak German.

I found UCS when looking for options to move away from Windows Server. I downloaded two versions, and both are having the same problem.

“An attempt to configure apt to install additional packages from the CD failed.”

In the first install attempt I continued anyway, and also got an error with GRUB, which would have left the computer unbootable.

The server is an old Dell PowerEdge 1850.

Can anyone help? Bitte? It looks like UCS would be a great option, if I could get it to install and try it.

Thank you in advance!


[quote=“zen0”]Enshuldigung bitte. I don’t speak German.[/quote]no problem! :slight_smile: I’m moving your thread to the englisch forums.

Which UCS ISO-Images did you try?
Olease verify that the files you downloaded and the DVD you burned have the correct checksums as this sound a lot like a “broken image” Problem.

In addition you could try to use a USB thumb drive instead of a DVD, just copy the image with “cat” or “dd” (like cat UCS_4.0-0-amd64.iso > /dev/USB-Device-Name).

Janis Meybohm

Thank you, Janis! (I didn’t even see the English section of the forum)

I attempted two versions, one being the version that was downloaded by unetbootin (for making USB boot sticks) of unknown version. Secondly I downloaded the 4.0 version from the UCS site and burned to DVD. The MD5 hash matches the ISO.

The DVD boots, and starts the installation, but in the configuring, both apt and GRUB set up fail.


so that would be UCS_4.0-0-amd64.iso with the MD5 hash from UCS_4.0-0-amd64.iso.md5 (2c82650ec4111c9080a642adc659e42c at time of writing).

As I have not heard of this before, could you provide screenshots of the error messages?
Do you get a command prompt when the error shows up so you could do some testing (like output of “cat /proc/partitions”)?

Janis Meybohm

Hello again, Janis,

Yes, it is version UCS_4.0-0-amd64.iso.

The errors are inside the Univention installer, no command line visible.

I have taken photos of the screen with my phone (since I cannot get to the saved screenshots on the server itself)


is the system already reachable via ssh when this happens? You could copy the file /var/log/syslog then (and send it to us). It should contain the installer progress and the reason for the problem.

Kind regards,
Tim Petersen

I am not well versed in the Linux world, but I think the installation is not at the point where it is actually on the network, since it has not finished the basic installer. I do not want to just “Continue” through the installer because it is telling me that GRUB will not be installed, and therefore will not boot into UCS. (according to the error message in the installer, linked above)

Is there any way to get to a command line from inside the installer? some way I could find out if it has an IP address that I could attempt to ssh into?

Any help folks can offer is greatly appreciated. This was an evaluation install for our small(ish) company, and I was really looking forward to trying it out.


the screenshots suggest that you already went thru the process of network configuration. Anyways, you should be able to copy the logfile to an usb thumb drive in this state:
[li]Switch to the console using the shortcut: Strg + Alt + F2[/li]
[li]Press “Enter” and you should get a command prompt[/li]
[li]Plug in your (FAT32 formatted) thumb drive[/li]
[li]Type “dmesg | tail” and press enter, you should see something like this:

[quote=“dmesg | tail”][31798.602020] sd 14:0:0:0: [sdb] 15687680 512-byte logical blocks: (8.03 GB/7.48 GiB)
[31798.602816] sd 14:0:0:0: [sdb] Write Protect is off
[31798.602822] sd 14:0:0:0: [sdb] Mode Sense: 03 00 00 00
[31798.602996] sd 14:0:0:0: [sdb] No Caching mode page found
[31798.603002] sd 14:0:0:0: [sdb] Assuming drive cache: write through
[31798.634252] sdb: sdb1
[31798.636224] sd 14:0:0:0: [sdb] Attached SCSI removable disk[/quote][/li]
[li]Now use the following commands to create a mount point, mount the thumb drives first partition (/dev/sdb1 in the above example), collect the information needed and unmount the drive:

mkdir /tmp/usbdrive mount -t vfat /dev/sdb1 /tmp/usbdrive/ cp /var/log/syslog /proc/partitions /tmp/usbdrive/ blkid >> /tmp/usbdrive/blkid umount /tmp/usbdrive/[/li]
[li]Remove the thumb drive from the system and send us the files[/li][/ul]

Janis Meybohm

Thanks! I tried to copy and paste the three files, but the syslog was too large. Here are the two smaller files. What is the best way to attach/send you the syslog?

blkid:/dev/sdb1: UUID="c1829cfb-2aef-4c4b-8450-283847df4d96" TYPE="ext2" /dev/sr1: LABEL="UCS 4.0-0 amd64 1" TYPE="iso9660" /dev/sdb5: UUID="BehbJ0-qhW6-Mhqy-y0de-2aXR-4ul1-4avi9E" TYPE="LVM2_member" /dev/mapper/vg_ucs-root: UUID="706dea17-1a17-414e-bc39-7d482dac09cd" TYPE="ext4" /dev/mapper/vg_ucs-swap_1: UUID="2fe50730-daa0-4ef8-ab35-c3fff726484c" TYPE="swap" /dev/sdc1: LABEL="DATA" UUID="CA7D-4FB7" TYPE="vfat"

partitions:[code]major minor #blocks name

11 0 1048575 sr0
11 1 2243712 sr1
8 16 71557120 sdb
8 17 498688 sdb1
8 18 1 sdb2
8 21 71055360 sdb5
253 0 66859008 dm-0
253 1 4194304 dm-1
8 32 7624416 sdc
8 33 7620384 sdc1[/code]

[quote=“zen0”]What is the best way to attach/send you the syslog?

You can use for this task if the syslog is <150MB.

Kind regards,
Tim Petersen

Thanks very much. I have uploaded zen0s_syslog to upload_maz3vY.unknown


I just had a look - from what I can see in the log file, this has to be an issue with either the iso or the finished DVD:
Dec 31 17:26:03 apt-setup: [e48eeed3806bd067d9ded86ff3c86feb-2]
Dec 31 17:26:03 apt-setup: Scanning disc for index files…
Dec 31 17:26:03 apt-setup:
Dec 31 17:26:03 apt-setup: W: Failed to mount ‘/dev/sr0’ to ‘/media/cdrom/’
Dec 31 17:26:03 apt-setup:
Dec 31 17:26:03 apt-setup: E: Unable to locate any package files, perhaps this is not a Debian Disc or the wrong architecture?

Did you specificly check the MD5 sum of the downloaded ISO? If this is the case, I’m afraid that either the burning went wrong or the DVD drive is faulty.

Kind regards,
Tim Petersen

Thanks, Tim.

I did in fact check the MD5 against the version on the UCS site (2c82650ec4111c9080a642adc659e42c) and it did match. I will try a USB version to eliminate the possibility of DVD drive problems.

I’ll let you know how things go.

Thanks again for your persistence!