Booting Debian from the SRM console (the only disk boot method supported by &releasename;) requires you to have a BSD disk label, not a DOS partition table, on your boot disk. (Remember, the SRM boot block is incompatible with MS-DOS partition tables — see .) As a result, partman creates BSD disk labels when running on &architecture;, but if your disk has an existing DOS partition table the existing partitions will need to be deleted before partman can convert it to use a disk label. If you have chosen to use fdisk to partition your disk, and the disk that you have selected for partitioning does not already contain a BSD disk label, you must use the b command to enter disk label mode. Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), it is suggested that you do not make the third partition contain the whole disk. This is not required by aboot, and in fact, it may lead to confusion since the swriteboot utility used to install aboot in the boot sector will complain about a partition overlapping with the boot block. Also, because aboot is written to the first few sectors of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you must leave enough empty space at the beginning of the disk for it. In the past, it was suggested that you make a small partition at the beginning of the disk, to be left unformatted. For the same reason mentioned above, we now suggest that you do not do this on disks that will only be used by GNU/Linux. When using partman, a small partition will still be created for aboot for convenience reasons. For ARC installations, you should make a small FAT partition at the beginning of the disk to contain MILO and linload.exe — 5 megabytes should be sufficient, see . Unfortunately, making FAT file systems from the menu is not yet supported, so you'll have to do it manually from the shell using mkdosfs before attempting to install the boot loader.