Hello to everyone, i just mounted an ssd on my laptop, i have already tried kaos making a quick install for the first time, i did not use the manual partition but i did do all the work at calamares, now the situation is this with Partitioning in GPT and uefi without secure boot, I have this situation:
/ Boot fat 32
/ Xfs
SWAP
Now my idea is to do a definitive and optimal partitioning, I would like to use brtfs and then the classic:
/ Boot fat32
/ Brtfs
/ Home brtfs
(No swap) i have 8 gb ram
Now I have given an eye to this guide:
https://kaosx.us/docs/btrfs/
There is talk of FSTAB
And / var / spool and / var / tmp partitions
I was wondering if they are all that can be done during partitioning or just have to modify fstab later in that way,
Thank you

Since that tutorial was written, btrfs support in Calamares has improved, but you still better check /etc/fstab after the install and see if it matches with what was recommended in the tutorial.

Excuse me, I just wonder why I never did it before, then partition normally and if something fstab is missing, such as lso and the like, just simply modify fstab and nothing else right?
Also, but maybe it's topic for another topic, after updating the system I had problems after booting with Xorg, maybe the Intel drivers after the latest updates require some modification to Xorg I had read during the installation but I was not sure it was My case, uxa stuff or the like: D sorry but i'm working now and i do not have the notebook in front

6 days later

So, after the last test that appears to be an official candidate, I wanted to try again after the failure of previous experience, to install Kaos with brtfs filesistem on notebook with ssd disk, I really tried everything, tried various Partitioning types, both gpt and mbr, both Uefi and Legacy, always following the chaos guides and suggestions, helping me with Arch Wiki, I tried to modify fstab as in the Kaos wiki, the problem is that everything seems to work The installation is successful, the disk is aligned well, it looks okay, i with gpt and uefi boot i can see systemd-efi grub (or as it's called) but after starting kaos from efigrub I always have black screen with this message:

ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
[rootfs /]#

Also from live i checked out, that everything looks ok with the partitions and in fstab, the only thing that looks strange and that in the dolphin i see the disk and inside i find the subvolumi @ and @home that seems right but if i go Inside the boot folder i find nothing, it is empty, but in partitionmanager I see that boot / boot in fat 32 is not empty, and if it is empty i would not see the efi grub at boot, maybe it would also want a Subvolume for booting something like @boot do not know!
I also tried to make default installation with only the system erasing all the disk and recreating only with kaos which by default creates / boot 300 Mb fat32 / all the rest xfs and 8gb swap, so obviously everything works well then after This I tried to do the same without booting / booting but leaving it as the system had just worked, and just changing and formatting the XFS partition / with brtfs but it did not work the same problem and error before!
Now with that message on google I've found several directions but I'm not familiar enough to fix the problem!
So I installed it again in xfs and it's all ok, for me it's okay for now!
But I would like this to be fixed in Calamares or delete this option from Calamares, now I know that as @demm said she is not brtfs expert, but someone should try it, I'd also like to ask or send this message to Calamares dev.
One really nice thing would be to have a default Calamares setting for ssd, as it does with default XFS but without swap and with brtfs because ssd disks are now widespread!

P.S.
@demm apologize for the long message: P
Going out of the question I meant that with the last test iso I enabled the repo [build] for now until the final release, did I do it right?

All I can say that is tested and working by quite a few users, so what is different in your setup I don't know. If subvolumes in use then that might be the issue.

Yes [build] is needed. But looks like all is well, so the ISO will be released today, then you can remove [build] again.

Thank you, as always, anyway I have not set them up but have set themselves in automatic, that's right! I know you do not have brtfs experience, I'd love to find someone who with Calamares installed in brtfs without problems, because I I think I did everything right, also because I've tried in all possible ways and it seems to be the installer wrong something!
So I hope maybe somebody who managed to tell me if he did something special, thank you 🙂
However for now I have fun with Kaos and Xfs and with your fantastic job, the new iso looks ok as always

We have run a couple of test installs with btrfs (vbox with msdos, real hardware with UEFI), absolute zero issues just using Calamares as is. Of course you need to use manual partitioning, since KaOS sets XFS as default for the automated options.
Example of a btrfs install on msdos vbox:

So you need to check the steps you are taking, since this is not an issue in Calamares or the latest ISO.

First of all, thanks for your tests and tests, I'm sure your test is as you say! But unfortunately in my various tests I have always failed, I tried various types of partitioning but nothing to do but also wanted to specify that the same manual partitioning made using xfs has always worked well, just modifying the filesystem with btrfs the result was systemd-boot efi And then this message:

ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
[rootfs /]#

So I do not understand the reason, because even Calamares's installation seemed smooth and error-free, only after the post-installation reboot did not work!
The only thing I'm sorry about now, I've never thought of doing after install #calamares -d! To see what happened!
Also my installation with the various attempts was the last test iso before the official release, which I think is the same as the official one!
For now, anyway, so with XFS that's fine, maybe if it happens the chance will look again in the future, maybe with more live signals if it fails!
Thank you for your time

    As said, not just me testing, "crazy" who you know from IRC also did some tests, neither one of us can get any fail or have to do anything special with btrfs.
    And yes, that is with the released ISO from 2 days ago, which is the same as the last test ISO.

    th3g3ntl3m4n

    Please tell us the way how you install KaOS with btrfs ..

    For me it looks like you just install with xfs and then change fstab values
    and that OFC does NOT work!

        abucodonosor
        Hi, First of all, sorry but because of my bad English I did not understand OFC does not work what it refers to, maybe out of the box bfrts?
        However as I explained my partition with btrfs has been tried in various ways, the simplest with GPT and Uefi:
        / Boot (only unformatted mount) Fat32 300 Mb
        / Everything else without SWAP
        As I said during installation but after restarting systemd-grub ok and then that error message without getting to SSDM, then starting from live to see what happened everything seemed ok in the dolphin going to the disk I saw two subvolums, @ and @ Home the strange thing is that @ the Boot folder was empty though in partitionmanager / boot was not empty, since at boot I had systemd-grub with the various voices of the kaos kernel, i think maybe the boot / boot was not mounted by the dolphin and i saw Just boot in @, empty!
        I also wanted to point out that even though I'm not a mega hacker superuser, I'm not even the first of the newbies, I've been using linux for many years now and I have installed it several times with Calamares in Chakra and Kaos both in Legacy and in Uefi mode and GPT That MBR in ext4 without problems, now since I had a new SSD drive I wanted to try BTRFS!
        However later I have installed with XFS always manual as follows:
        / Boot (as before with btrfs)
        / XFS
        / Var XFS
        No Swap
        And it works fine, with XFS, FSTAB I left it as default because it seems already optimized so, also I do not think you can do in FSTAB the same optimizations that you do with BTRFS

          So far nothing you post can help us help you, start with posting an installation.log whenever you have a failed install with btrfs, so we at least know where you went wrong:
          https://kaosx.us/docs/
          https://kaosx.us/docs/#info-to-provide-for-installation-issues

          But there never is an unformatted /boot in use, not in UEFI (boot has to be fat32), not in legacy BIOS (there you ONLY need an unformatted space at the start of the disk if you use a GPT partition table, certainly not an unformatted /boot).
          And as mentioned often, there does not exists any systemd-grub, you either use grub or systemd-boot.
          As you note, all you have posted so far is full of riddles and obvious mistakes. Make up your mind how you want to install, like in UEFI mode or Legacy BIOS and stick with one, post an installation.log for such an attempt and don't switch to something else until the errors are corrected.

          Thanks @demm
          But as I said, for now I'm fine with xfs, also because in the last few days I've tried so many times, and now I've configured kde as i like and i do not want to get started again, obviously since I'm still moving and never stopped, Often make irreparable mistakes, XD if I have to reinstall in the future, I will surely try again with btrfs and try to give more information and help as much as possible 🙂

          Have you tried doing the partitioning manually? I always do that to get in control of what's happening, and I usually never encounter any problems. I use btrfs on both home and system. I don't use UEFI thou, never seen point of using it (it's a bit messy imo) because I only use one OS.

          Hi, obviously my English does not understand well (in fact, writing using google translate),!
          I used manual partitioning, and I installed only one OS, no windows, but I used Uefi mount / boot, as I always do with ext4 and how I did with xfs without problems!