Originally Posted by volkerdi
This one was supposed to have been fixed by checking for an actual Windows partition with os-prober. Are you using a stick made with usbimg2disk.sh?
I'll take a look and see if I can spot a problem.
dd if=usbboot.img of=/dev/sdb bs=1M
48+1 records in
48+1 records out
51332096 bytes (51 MB) copied, 11.1188 s, 4.6 MB/s
Command (m for help): p
Disk /dev/sdb: 16.0 GB, 16000221184 bytes
64 heads, 32 sectors/track, 15259 cylinders, total 31250432 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x20ac7dda
This doesn't look like a partition table
Probably you selected the wrong device.
Device Boot Start End Blocks Id System
/dev/sdb1 ? 3224498923 3657370039 216435558+ 7 HPFS/NTFS/exFAT
/dev/sdb2 ? 3272020941 930513678 976730017 16 Hidden FAT16
/dev/sdb3 ? 0 0 0 6f Unknown
/dev/sdb4 50200576 974536369 462167897 0 Empty
Partition table entries are not in disk order
This ntfs partion is found by liloconfig in the installer and it adds /dev/sdb1 as a windows partion in lilo.conf and lilo fails to install
It's really easy to fix by chrooting into /mnt in the installer and removing the /dev/sdb1 ntfs line in lilo.conf but for those how are new it might be horrible!