During an Ubuntu installation, “No Root File System Is Defined” usually means that the installer has no suitable filesystem assigned to the root mount point, /. In a manual installation, creating a partition is not enough: the installer must also know that it is intended to hold the root filesystem.
The methods below explain what to check before continuing. Do not delete existing partitions merely because you see this message. Formatting or removing the wrong partition can destroy data or prevent another operating system from starting.
What the root mount point means
Linux organises files under a directory tree beginning at /. The root filesystem contains the base of that tree. A partition assigned only to /home or /boot does not replace the need for a root filesystem.
The word “root” here does not mean that you need to create a root-user password. It describes where the operating system’s filesystem will be mounted. Changing your login name or password will not correct a missing mount-point assignment in the disk setup.
Before changing the partition layout
Identify the intended disk by its size and model, especially if the computer has several drives. Confirm that important files are backed up somewhere separate and that the backup can be read. Keep recovery information for any encrypted installation you want to retain.
If you are installing alongside Windows or another operating system, first decide which space Ubuntu should use and which partitions must remain untouched. Unallocated space is different from free space inside an existing filesystem. The installer cannot treat an entire existing partition as empty merely because some of its storage is unused.
Ubuntu’s current desktop guide describes manual partitioning as an advanced option. If the partition table is unfamiliar, return to a suitable guided installation option or ask for help before committing changes. “Erase disk” is appropriate only when you intend to replace the contents of the selected disk.
Method 1: assign / to the intended Linux partition
- Return to the installer’s manual disk or partition setup screen.
- Select the partition you deliberately reserved for the new Linux installation.
- Open its editing controls and inspect the filesystem choice.
- For a conventional installation, choose a supported Linux filesystem such as ext4 and assign the mount point /.
- Review whether formatting is selected and what data that would erase before accepting the change.
Button names differ between installer versions. Older releases may call the editing action Change, while newer layouts organise the same choices differently. The important result is that the intended root filesystem appears in the summary with / as its mount point.
Method 2: create a root partition in intended free space
If no suitable partition exists, you may need to create one in space deliberately allocated for Ubuntu. Choose the size according to the release requirements and the applications and files you plan to store. Do not copy an arbitrary size from a screenshot without checking your needs.
Choose the appropriate filesystem and assign / during creation. Review the target disk again before proceeding. An installer showing a plus button does not mean that every selected area can safely be overwritten.
For encrypted, LVM or other advanced layouts, the root filesystem may live inside a logical volume rather than a simple disk partition. Follow the documentation for that layout instead of applying a basic partition recipe to a different storage design.
Do not confuse an EFI partition with the Linux root
A FAT32 partition can be an EFI System Partition, which stores boot-related files. Its presence is not an error. Ubuntu’s UEFI documentation explains that an existing EFI partition can be shared and should not be formatted when retaining its boot contents.
The earlier suggestion to delete FAT or FAT32 partitions as a general fix was unsafe. A filesystem unsuitable for the Linux root can still be necessary elsewhere in the installation. Inspect the partition’s role, not just its filesystem label.
Also keep the installation’s boot mode consistent with the operating system you intend to retain. If the installer reports a separate boot-partition requirement, investigate that message rather than assuming the missing-root fix covers it too.
Method 3: review the final storage summary
Before starting installation, check that the summary identifies a root filesystem, shows the intended disk and lists only the formatting operations you planned. Read every proposed deletion or format action. A summary that mentions a partition you wanted to preserve is a reason to stop.
For a dual-boot setup, check that the existing operating-system partitions remain present. If encryption prevents the installer from understanding them, follow Ubuntu’s guidance for that situation or use a separate suitable disk. Do not disable encryption or erase a partition simply to make the warning disappear.
If the error remains
Record the Ubuntu version, the installer wording and a screenshot of the proposed layout with private details removed. Note which entry has / assigned and whether the setting remains after you close its editing window. That helps distinguish an unsaved choice from an unsuitable filesystem or a more complex storage issue.
Do not keep changing partitions at random. Correcting this message is about defining a valid installation destination, not proving that the rest of the disk can be discarded. Continue only when the root assignment and every planned disk change match your intended setup.
