• Warning: graphical installer always formats root


    Installation went very smoothly, even from the graphical installer, and Antergos is proving to be a good system. The graphical installer did ignore my choice to not format the root partition; it did format root anyway, in fact it formatted the root partition as an ext4 filesystem although I had chosen xfs. The cli installer does not have this problem so for now I’d recommend that anyone wanting to do anything other than format root as ext4 should use the cli installer.


    Sit quietly, doing nothing, spring comes and the flowers grow all by themselves.

  • Installation went very smoothly, even from the graphical installer, and Antergos is proving to be a good system. The graphical installer did ignore my choice to not format the root partition; it did format root anyway, in fact it formatted the root partition as an ext4 filesystem although I had chosen xfs. The cli installer does not have this problem so for now I’d recommend that anyone wanting to do anything other than format root as ext4 should use the cli installer.


    Sit quietly, doing nothing, spring comes and the flowers grow all by themselves.

  • I believe that this is a known issue currently being worked on. It can’t hurt to open a bug report just in case though! You can do that at [http://bugs.antergos.com/][0]">[http://bugs.antergos.com/][1]

    [0]: <a href=
    [1]: http://bugs.antergos.com/

  • @“sitquietly”:3czenf2o said:

    Installation went very smoothly, even from the graphical installer, and Antergos is proving to be a good system. The graphical installer did ignore my choice to not format the root partition; it did format root anyway, in fact it formatted the root partition as an ext4 filesystem although I had chosen xfs. The cli installer does not have this problem so for now I’d recommend that anyone wanting to do anything other than format root as ext4 should use the cli installer.


    Sit quietly, doing nothing, spring comes and the flowers grow all by themselves.[/quote:3czenf2o]

    I was checking the xfs thing and it works correctly, but for some reason xfsprogs isn’t installed on the liveCD (it should be) so gparted detects xfs partitions as ext4, but if you run “sudo blkid” you will see “type=xfs”

    About formating the root partition, could you tell me why you wouldn’t format root? It is were Antergos is going to install the system, so it is normal to format that partition, but maybe we’re missing something, so if you could explain me it would be great, in that case we can fix it.

    Be aware that Cnchi doesn’t work with subvolumes, if that was the case why you wouldn’t format the root partition.

  • This “strange” behavior cannot be considered a bug anymore, since bugs that are known to cause total loss of user data, are invariably well publicized and get the utmost attention from developers. On the contrary, silently destroying user data by design is typical of malware…

    [http://forum.antergos.com/viewtopic.php?f=5&t=928][0]">viewtopic.php?f=5&t=928

    [0]: <a href=

  • @“faidoc”:1ms3fxdo said:

    … for some reason xfsprogs isn’t installed on the liveCD (it should be) so gparted detects xfs partitions as ext4, but if you run “sudo blkid” you will see “type=xfs”

    About formating the root partition, could you tell me why you wouldn’t format root?..[/quote:1ms3fxdo]

    Thanks for your reply.

    I think the partition really was formatted to ext4. I was able to boot and run that antergos installation afterward and didn’t notice at first that I was running on ext4, but when I rebooted into my funtoo and tried to mount the antergos parttion it failed to mount (my fstab was declaring that the antergos partition was xfs). It reported (wrongly) that it couldn’t find a superblock and I ran xfs_repair (still thinking that I had an xfs filesystem) and of course it failed to find any backup superblock. My stupidity got worse! I assumed that my filesystem had been corrupted when the power dropped out the night before and I re-installed antergos — and went through the same thing again.

    I don’t let distro installers format my partitions because I don’t entirely trust them

    I also do not let the distro install it’s boot loader to my main disk; it set to either install it’s bootloader to sdc or sdd, or not install any bootloader at all.

    AFTER the installer manages to simply get a system onto my target root partition, I edit the grub.cfg of my tried-and-true and never erased funtoo partition and get the new install booting from the grub menu. THEN I edit the fstab of the new install to add my real home partition and data partitions, edit the passwd file to move the user’s home directory to its new home (e.g. /home/antergos/sitquietly), copy the virgin (default) config files from the user’s temporary home (on root partition) into his final home. Reboot again! IF everything is ok then I link my user data directories into the new home so that I can access all of my files but work from a clean distro-specific configuration.

    In other words I end up with
    /home/antergos/sitquietly/{.config/,.local,.gconf…}
    /home/antergos/sitquietly/Documents -> /home/sitquietly/Documents
    /home/antergos/sitquietly/code -> /home/sitquietly/code

    There are also here directories /home/funtoo, /home/sabayon, /home/manjaro, /home/gentoo, /home/ubuntu, /home/opensuse – each with a “home” for my user with distro-specific configuration and shared data, including shared thunderbird email.

    The things I look for in a distro’s installer are

    • supports xfs
    • shows me clearly what it intends to do with each partition and can be told to install without formatting
    • allows me to install grub onto any mbr and preferably allows me to not install any bootloader

    Aside from my brief confusion about the filesystem the Antergos gui installer (and cli installer that I finally used to get installed onto xfs) worked quite well. I really like how it grabs the Archlinux packages and Gnome 3 has performed great.

    I plan on keeping Antergos installed.

    p.s. since I have an Intel Sandybridge system with Intel HD 3000 graphics, I used the modified iso from [http://mirrors.antergos.com/iso/antergos-2013.05.17-x86_64.iso][0]">[http://mirrors.antergos.com/iso/antergo][1] … x86_64.iso which of I’m told “this iso just fixes the Intel bug”.

    [0]: <a href=
    [1]: http://mirrors.antergos.com/iso/antergo

Posts 6Views 1924
Log in to reply