.*
*Where
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
I fixed the problem. Turns out there's a --config option. I just forced it
to use my config once which was enough to repair the array that was broken.
I rebooted and all my stuff is back :)
On Thursday, April 13, 2023 at 4:28:37 PM UTC-5 brick wrote:
> Any Qubes devs/experts please...? I as
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
I created my own mdadm.conf and put it in /etc/mdadm.conf as well as in
/etc/mdadm/mdadm.conf but Qubes doesn't seem to be reading it from either
of those places. Does Xen do things differently or something?
On Thursday, April 13, 2023 at 1:09:03 PM UTC-5 brick wrote:
> Long story short I
EDIT: And no I can't just rebuild the arrays. I need to recover the data if
it's still there, and something tells me it just might be.
On Thursday, April 13, 2023 at 1:09:03 PM UTC-5 brick wrote:
> Long story short I had a drive failure, now all my RAID arrays incorrectly
> show up as
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)
> leo...@gmail.com
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
