| 10 Nov 2025 |
no-mood | Link to that discussion: https://matrix.to/#/!6oudZq5zJjAyrxL2uY:0upti.me/$nd9QnFGo3-5Q9JB3tgef3V0_PyyaGoEqR_rdyyPITCY?via=laas.fr&via=matrix.org&via=node.marinchik.ink | 18:06:42 |
no-mood | Now I just don't know how to fix, I even tried to move files from the root to the subvolumes; it still fails | 18:07:12 |
blimbus | I've been having the same issue, I cant get my system to boot with root on bcachefs using disko. The filesystem exists, I can mount create and view files but the system just doesnt boot. I can boot off another fs and have disko create and mount drives other than root. Was trying to debug more before I posted anything. | 21:57:34 |
blimbus | * I've been having the same issue, I cant get my system to boot with root on bcachefs using disko. The filesystem exists, I can mount create and view files but the system just doesnt boot. I can boot off another fs and have disko create and mount drives other than root. Was trying to debug more before I posted anything.
Been feeling a little crazy cause I couldn't find any mention of the issue, almost glad to see its not just me
| 22:01:25 |
| 11 Nov 2025 |
no-mood | Okay I'm pretty sure it's related to: https://github.com/nix-community/disko/issues/1045 | 00:27:23 |
| @whispers:catgirl.cloud left the room. | 00:28:16 |
no-mood | And (thanks ElvishJerrico and dramforever) actually I think people didn't realized this because mount were broken: https://github.com/NixOS/nixpkgs/pull/414391 | 00:29:01 |
no-mood | The issue is indeed related to the subvolumes: I think they are created, but they aren't mounted end all the files go into the root as descrived in the issue. I couldn't get them to work even by moving the files where they should be (inside the subvolumes) | 00:30:36 |
no-mood | Now I got it to work (in the 5th install of the day) by avoiding subvolumes until this is fixed :) | 00:31:15 |
no-mood | As I expected you're creating subvolumes. It should be the same issue | 00:32:53 |
| 12 Nov 2025 |
Chris P Bacon | I have been wanting to add disko to my flake for a while now, but I am uncertain as how to do that without losing any data on disk. I have been running nixos at home for about 2 years now and I would like to up my game by introducing disko, with future installs/reinstalls in mind. But I am afraid that when I add it that my disks will get formatted according to the disk config I will have created. Is there an onboarding/getting started guide somewhere for adding disko to existing systems? | 07:09:13 |
lassulus | they are not getting formatted if you add disko, but they will get mounted according to it | 07:21:57 |
lassulus | so if you add something that is not what you currently have, you could not boot it | 07:22:16 |
lassulus | but rollback should still work in that case | 07:22:23 |
Chris P Bacon | so besides not being able to boot (which I could solve with a live-usb and mounting manually), there are no dangers to my data when adopting disko? cool! | 07:23:59 |
lassulus | well there is also rollback when booting, you can just boot an older generation without the usb | 07:27:56 |
lassulus | but disko is not run automatically, only nixos-anywhere or disko-install is running disko | 07:28:17 |
lassulus | or if you run it manually | 07:28:21 |
Chris P Bacon | ooooooooooh, gotcha | 07:28:41 |
Chris P Bacon | awesome, tnx! | 07:28:48 |
lassulus | a downside of that model is: if you add new volumes, pools, mount or something in your disko config, it will not automatically apply without reinstalling | 07:29:33 |
lassulus | in theory you can run the format script again, it has some checks to not delete data | 07:29:58 |
lassulus | but that is not super tested, so better do it with backups | 07:30:10 |
Chris P Bacon | Agreed. That is also not my goal. what I want to do is to migrate my current snowfall based config for my machines at home to a clan based one, and the only hurdle I saw was the adoption of disko. But knowing that disko is not really ran outside of install or manual invocations I can happily do my migration. If and when I ever do end up reconfiguring my disk I get it that the best course of action is to first to a backup, but then again, this would have been the flow if I'd done it all manually anyway! So again, thanks for dispelling my worries! | 07:35:57 |
| Inayet changed their display name from inayet to Inayet. | 12:38:55 |
| 13 Nov 2025 |
| @brian:bmcgee.ie left the room. | 09:40:01 |
| debtquity joined the room. | 20:24:28 |
| 18 Nov 2025 |
| jopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 (4094@39c3). | 20:18:55 |
| dave :3 joined the room. | 22:59:07 |
| 19 Nov 2025 |
| tioan joined the room. | 23:45:13 |