!oNSIfazDqEcwhcOjSL:matrix.org

disko

354 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko89 Servers

Load older messages


SenderMessageTime
18 Sep 2024
@artur:glasgow.socialmoved to @amadaluzia:tchncs.de changed their profile picture.23:00:32
19 Sep 2024
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) Enzime: 09:18:57
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)image.png
Download image.png
09:18:58
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)on our DMs09:18:59
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)can't accept your new request09:19:06
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)tried to make a new room as a result, accept that :D09:19:23
20 Sep 2024
@mannp:mannuk.rocksmannp ⚡️Hi all. I am trying to add a /storage ssd to my existing disko system and have done a dry run and edited the output script to just format and mount the additional ssd only. This works fine, but when I add the same config to the full system, it won't boot due to the additional storage drive 😕 I have fileSystems."/storage".neededForBoot = false; but it still won't boot.....any possible reasons why, or things to check? thanks 12:19:22
@mannp:mannuk.rocksmannp ⚡️I tried previously and fried my main drive and installed it all from scratch...that boots and works with the additional storage file fine, with the same config....12:20:24
@mannp:mannuk.rocksmannp ⚡️ * I tried previously and fried my main drive and installed it all from scratch...that boots and works with the additional storage ssd fine, with the same config....12:20:47
@mannp:mannuk.rocksmannp ⚡️ * I tried previously (on an identical system) and fried my main drive and installed it all from scratch...that boots and works with the additional storage ssd fine, with the same config....12:21:53
@joerg:thalheim.ioMic92 mannp ⚡️: are you missing block device drivers in your hardware-configuration.nix? 13:42:43
@mannp:mannuk.rocksmannp ⚡️ left the room.15:34:44
@joerg:thalheim.ioMic92also try nofail for debugging: https://github.com/Mic92/dotfiles/blob/5f4c782602e2f7ac89237fee62a874caba0a15cc/machines/turingmachine/modules/disko.nix#L1713:43:26
21 Sep 2024
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) Mic92: https://github.com/nix-community/disko/pull/465#issuecomment-2365230543 15:40:28
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)what do you mean by "more accurate algorithm", what is currently inaccurate about it?15:40:39
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)The PR works well, and functions correctly, it doesn't have any bugs that I'm aware of that cause invalid outputs (disk images that don't work)15:41:04
@joerg:thalheim.ioMic92Have you looked at the disk calculation that make-disk-image does?15:41:41
@joerg:thalheim.ioMic92It's way more than just using the closure size.15:41:52
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)make-disk-image doesn't do calculation? It just asks you for an imageSize right now, doesn't it?15:42:16
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)or do you mean in my PR?15:42:48
@joerg:thalheim.ioMic92I mean the implementation in nixpkgs15:43:25
@joerg:thalheim.ioMic92It's ext4 only afaik15:43:31
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)what does that have to do with disko?15:43:33
@joerg:thalheim.ioMic92https://github.com/NixOS/nixpkgs/blob/636c5a8db5eb31a9ce04d0e75779ab684b0f8ae3/nixos/lib/make-disk-image.nix#L45315:43:57
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)ah okay so make-disk-image from nixpkgs has a complex thing, and my thing is too simple15:44:50
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)and just using the path-info size is wrong in some way?15:45:01
@joerg:thalheim.ioMic92It's just the raw content and doesn't take into account that filesystem need more data structures for inodes and stuff.15:45:31
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)I don't actually understand in what way it is wrong to just use the path-info -Sh output though, because it worked in my cases15:45:41
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192)
In reply to @joerg:thalheim.io
It's just the raw content and doesn't take into account that filesystem need more data structures for inodes and stuff.
Oh right, so for that I just hardcode a little bit more in, since I was unable to figure that out
15:45:58
@matthewcroughan:defenestrate.itmatthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) I don't think that's a bad approach, to just +10M it 15:46:07

Show newer messages


Back to Room ListRoom Version: 10