Univention Bugzilla – Bug 42530
installation selects floppy (/dev/fd0) as disk to partition
Last modified: 2016-10-17 14:22:33 CEST
I'm currently trying to install the UCC 3.0 desktop image on a virtual machine (VMware). The VM boots via network and loads the initrd just fine. However, the initrd choses /dev/fd0 as the device to partition. Unpacking the initrd and looking at scripts/ucc I don't see any provision for skipping floppy devices or removable devices (there's one "if" dealing with removables, but that is only entered if "$device_blacklist" is set, which "grep -r device_blacklist /path/to/extracted/initrd" never to be the case). Looking at the output of "cat /proc/partitions" in a debug shell started from the UCC initrd I can see: 1. A lot of ram disk partitions 2. The fd0 partition 3. The sda partition This happens even if I remove the floppy device from the virtual machine configuration. Of course this is an edge case (installing the desktop in a virtual machine). However, I'm pretty sure that a floppy device can never the right target. I've circumvented this by adding the following lines to the "search_device" function and rebuilding the initrd: if echo "${device}" | grep -sq ^"fd[0-9]" ; then # Skipping floppy devices continue fi This is just copy-pasted and adjusted from the device mapper case.
Thanks for the report. I fixed the issue in r73007 univention-ucc-initramfs 5.0.0-26.164.201610071507 r73008 yaml
OK - fd[0-9] is ignored in search_device (initramfs-tools/scripts/ucc) OK - yaml
<https://errata.software-univention.de/ucc/3.0/4.html>