14:51 <jdoss> I am trying to install to bare metal with BIOS RAID enabled and FCOS can't find the md device. Booting off the live CD and running in RAM finds it just fine. https://usercontent.irccloud-cdn.com/file/9vN0ualp/image.png

14:57 <travier[m]> jdoss: If it's BIOS based RAID, then the kernel should just see a disk like normal?

14:57 <jdoss> yeah that's what I thought too @travier[m]

14:58 <jdoss> It does show up if I do coreos-installer iso customize --live-ignition vs coreos-installer iso ignition embed -i

14:59 <jdoss> maybe coreos-installer.service needs to start later in the boot.

15:05 <dustymabe> jdoss: BIOS RAID, i.e. hardware RAID versus software RAID?

15:05 <jdoss> BIOS enabled raid. Software RAID but with extra steps and more regrets.

15:07 <jdoss> also known as hybrid raid? Here is some lite bathroom reading materials https://www.supermicro.com/manuals/other/Intel_PCH_RAID_Config.pdf

15:07 <dustymabe> jdoss: yeah, must be some gaps in my knowledge there

15:07 <dustymabe> anyone able: needs LGTM: https://github.com/coreos/fedora-coreos-config/pull/2219

15:08 <jdoss> Instead of using mdadm to setup the drives it is done in the BIOS and then mdraid can pick it up.

15:08 <jdoss> If I boot with coreos-installer iso customize --live-ignition FCOS sees /dev/md126 just fine.

15:12 <dustymabe> jdoss: yeah, sounds like maybe timing?

15:12 <jdoss> dustymabe: here is the butane that I am booting https://gist.github.com/jdoss/7783fae724c9b737c2874e9b50d9185b

15:13 <dustymabe> jdoss: maybe add an `ExecStartPre=sleep 60` to that installer service to test your theory

15:14 <jdoss> I guess maybe that coreos-installer.service needs another After= to let the mdraid stuff settle.

15:14 <jdoss> dustymabe: ooo I like it.

15:30 <dustymabe> spresti[m]: hold off on starting the production builds for this week just yet

15:30 <dustymabe> i'm investigating something

15:32 <ChinaDoug> I am unable to get Fedora CoreOS to blank the console screen on my lapotp.  I have added consoleblank=15 as a kernel argument and I have verified that the value in /sys/module/kernel/parameters/consoleblank is 15 but my console screen still doesn't blank after 15 seconds.  On the same laptop I used this same kernel argument on Fedora 37 Server

15:32 <ChinaDoug> Edition and screen blanking works.

15:32 <ChinaDoug> Is something different in the kernel between these two versions that causes the consoleblank argument not to work?

15:36 <spresti[m]> Ok, I will hold off!

15:36 <spresti[m]> * hold off! dustymabe

16:20 <dustymabe> ChinaDoug: hmm. I've never had to use that feature before

16:21 <ChinaDoug> Yeah.  I have this installed on a laptop and I would like to close the lid and not have the display on.  In general I don't access the laptop physically, just SSH into it to make changes.

16:23 <dustymabe> what does `cat /sys/module/kernel/parameters/consoleblank` show?

16:23 <ChinaDoug> 15

16:23 <ChinaDoug> if I don't put in the kernel argument the default is 0

16:25 <dustymabe> ChinaDoug: maybe open an issue in the tracker

16:25 <dustymabe> other people may know the answer

16:25 <ChinaDoug> will do.  thanks!

16:29 <dustymabe> thank you ChinaDoug

16:30 <jlebon> dustymabe: before we forget, do you want to open an issue against cosa for the kola denylist warning idea?

16:32 <dustymabe> jlebon: yeah I can do that

16:32 <jlebon> +1

17:09 <jdoss> @dustymabe Maybe calling coreos-installer-pre which then calls coreos-installer-disable-auto-activation prevents the activation of DM which will setup the BIOS RAID devices. https://usercontent.irccloud-cdn.com/file/WPBlKWzx/image.png

17:10 <jdoss> Yepp that will do it https://usercontent.irccloud-cdn.com/file/SF1K8GCE/image.png

17:11 <jdoss> I will open an issue to address installing to BIOS RAID with this stuff for discussion.

17:14 <dustymabe> jdoss++

17:14 <zodbot> dustymabe: Karma for jdoss changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any

17:24 <bgilbert> jdoss: to make sure we're talking about the same thing, I assume you mean "FakeRAID" rather than hardware RAID?

17:24 <jdoss> yah FakeRAID / BIOS Raid

17:24 <bgilbert> jdoss: in that case, I don't think it'll be supported. it's equivalent to trying to install FCOS onto /dev/md0.

17:24 <bgilbert> we expect to do our own RAID setup through Ignition

17:25 <jdoss> Why wouldn't it be supported? It's a drive managed in the BIOS.

17:25 <bgilbert> because of the "Fake" in "FakeRAID"

17:25 <dustymabe> bgilbert: to be clear, if it was full hardware RAID your answer would be different?

17:26 <bgilbert> dustymabe: yup. hardware RAID always looks like a real disk. fake RAID is just headers to tell Linux md what block devices should be RAIDed together.

17:26 <jdoss> Seems kinda short sighted to totally disable the usage of BIOS backed RAID.

17:27 <dustymabe> I think there is a difference between the wording "disable" and the fact that it doesn't work

17:27 <dustymabe> I don't know if it's ever been tried TBH

17:27 <bgilbert> jdoss: why would you want it? FCOS doesn't support dual-booting with other OSes, so this only affects the ergonomics of setting up FCOS

17:27 <bgilbert> and configuring RAID outside the Ignition config just means there's an additional source of truth

17:30 <jdoss> bgilbert: I have always setup BIOS backed RAID in the past without FCOS. I actually I tried to have Ignition setup RAID in the Ignition config and it didn't work so I figured I would do what I normally do if I don't have a hardware RAID card and I need disk redundancy.

17:30 <dustymabe> i see bgilbert's point here. basically FakeRAID is still software RAID so you might as well specify it in your Ignition file and have it manage setting it up

17:31 <bgilbert> jdoss: software RAID for the boot disk is a supported feature, and has Butane sugar. if it isn't working for you, please ask here or file an issue

17:31 <dustymabe> though as jdoss mentioned he was seeing a failure that way, so maybe we should dig into that failure?

17:31 <dustymabe> +

17:31 <dustymabe> +1

17:31 <bgilbert> jdoss: if you want to file a bug re FakeRAID, feel free, but I suspect supporting it would be non-trivial and not a high priority

17:31 <jdoss> The beatings will continue until the FCOS koolaid is drank ;P

17:32 <bgilbert> jdoss: always :-P

17:32 <bgilbert> (we have too many things to support already)

17:33 <jdoss> I always appreciate your help bgilbert even tho it can be frustrating as a user to go down a rabbit hole that ends in a dead end.

17:34 <jdoss> I will PR some document changes to explicitly tell users that FakeRAID is not supported at this time so they don't waste time with it.

17:34 <bgilbert> jdoss: no worries, I know this sort of response is frustrating

17:34 <bgilbert> jdoss: +1 to docs, thanks!

17:35 <bgilbert> and please do let us know if you're having problems with the Ignition RAID flow

17:35 <jdoss> yah I will back this sever out of it's current state and try again.

17:35 <bgilbert> +1

17:51 <travier[m]> TIL about Fake RAID

17:57 <dustymabe> travier[m]: yeah I had never used it before

20:37 <dustymabe> jlebon: anything changed recently with ostree that could cause rebasing to our compose repo to not work? it's complaining about not being able to grab a signature file but we don't even have a summary file for that repo.

20:37 <dustymabe> [core@coreos-s390x-builder ~]$ sudo rpm-ostree rebase fedora-compose:fedora/s390x/coreos/testing-devel --reboot

20:38 <dustymabe> error: While pulling fedora/s390x/coreos/testing-devel: While fetching https://kojipkgs.fedoraproject.org/compose/ostree/repo/summary.sig: [28] Timeout was reached

20:42 <dustymabe> oh. hmm. I think this box is having trouble reaching the internet

20:46 <dustymabe> spresti[m]: you can go ahead with the prod builds now

20:53 <jlebon> dustymabe: i think ostree might always try to fetch that URL and it's erroring because it's not a 404

20:53 <jlebon> i'd have to check the code to be sure

20:54 <spresti[m]> kk dustymabe

20:55 <dustymabe> jlebon: yeah the machine didn't have internet connection

20:55 <dustymabe> it worked after I poked a hole in the security group

20:55 <jlebon> +1

22:13 <jdoss> bgilbert: the thing that I think caught me up on the Software RAID documentation is on the moving the root file system to RAID0 (RAID1 in my case) does that mean that I should set `coreos-installer install --offline -i /etc/install.ign /dev/md/root` to install to that device?

22:14 <bgilbert> jdoss: nope, see the last example in https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_reconfiguring_the_root_filesystem

22:14 <bgilbert> install onto one device, then let Ignition redo everything

22:14 <jdoss> so set it to `/dev/sda`

22:15 <bgilbert> yup

23:59 <jdoss> @bgilbert weird, the second drive in the RAID 1 wouldn't clear correctly. https://usercontent.irccloud-cdn.com/file/IxOfsFJ1/image.png