Any Qubes devs/experts please...? I asked on linuxquestions as well and 
according to them, mdadm will try to load whatever file it listed under 
`man mdadm.conf`, which in the case of dom0 is at /etc/mdadm.conf... but 
that file did not exist until I put it there so *this is Qubes specific.* 
does Qubes OS's mdadm get its settings from at boot?* I need to change 
those settings because they are corrupted... I literally have nowhere else 
to go but this mailing list. PLEASE HELP

On Thursday, April 13, 2023 at 3:10:09 PM UTC-5 brick wrote:

> Actually yeah that's not it at all. That's a `systemd-tmpfiles` file 
> whatever the fudge that is, nothing at all to do with mdadm
> On Thursday, April 13, 2023 at 2:34:38 PM UTC-5 brick wrote:
>> I don't think that's it. It's only one line long and has no reference to 
>> my arrays. I tried to put mine there anyway and rebooted but my arrays are 
>> still all raid0
>> On Thursday, April 13, 2023 at 2:18:59 PM UTC-5 Mike Keehan wrote:
>>> On Thu, 13 Apr 2023 11:08:09 -0700 (PDT) 
>>> wrote: 
>>> > Long story short I had a drive failure, now all my RAID arrays 
>>> incorrectly 
>>> > show up as "raid0 inactive". Apparently one way to fix this is to 
>>> manually 
>>> > change the arrays to the correct levels in mdadm.conf, but I can't 
>>> seem to 
>>> > find that in my dom0 with the `locate` command. 
>>> > 
>>> > Please help. I really need these arrays back. My damn fedora-34 
>>> template is 
>>> > there so I can't even use sys-net 
>>> > 
>>> Try "find / -name mdadm.conf -print 
>>> It's in /usr/lib/tmpfiles.d/ on my laptop, but I don't have raid. 
>>> Mike. 

You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To view this discussion on the web visit

Reply via email to