You are not logged in.
I am crossposting this from EndeavourOS, as that's what I am running. A definitve solution hasn't been found there, so I am trying here. Apologies if this breaks any rules.
I am basically mostly following
https://matthiaslee.com/encrypted-parti … setupluks/
So I assemble the array with mdadm as described there, did all the cryptsetup stuff, and also created the “Everyday use” scripts as described there.
I do like to shutdown my NAS at night. I mean, it’s a home NAS, we are sleeping and nobody will use it. Just plain stupid to have it running all the time.
But when I boot again - the array is gone, and I have to recreate it with the same mdadm --create command.
Why is that? What am I missing?
This is my fstab
<code>
UUID=0B6C-4B1F /efi vfat fmask=0137,dmask=0027 0 2
UUID=b7f83d24-6b3d-4d02-ae42-ae83ee9ecd19 / ext4 noatime 0 1
UUID=1bdf2d7b-0717-4ea5-85cb-1897c10489f9 swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
</code>
My `/etc/mdadm.conf` in fact already contains:
<code>
DEVICE partitions
ARRAY /dev/md0 ....
</code>
I am starting to think that the issue could be that in that old tutorial, they were using whole disks (`/dev/sdd`, `/dev/sde`). Which I did myself, but using my `/dev/sda/` and `/dev/sdb`.
But maybe I should actually create partitions…
I also tried btw by putting `DEVICE /dev/sda /dev/sdb" in `/etc/mdadm.conf`, but this also did not work.
Offline
You were already told that in your other thread and instead of giving it a try, you ask here…
Something seems to be wiping your mdadm metadata. Something writing a partition table to where there is none would be doing that, so it's entirely possible for that to be your issue. Using whole drive without partition is not a good idea.
It could also be something else, in the end it is up to you to track it down since we can't possibly tell remotely. Dump the first 1MiB of your drive before/after reboot (with RAID / without RAID), then compare them. Might tell you something, or not…
Offline
> You were already told that in your other thread and instead of giving it a try, you ask here…
Excuse me, I was told what there?
I have tried everything which was discussed there.
The only practical advice in that thread is:
> Once that’s done and the system is bringing the array back up on reboots
1. I already had an `/etc/mdadm.conf`, it was not empty nor having missing entries
2. But even after running the mdadm commands as described in that wiki page, and having a fresh mdadm.conf, it did not work.
3. The above explicitly says "....and the system is bringing the array back up on reboots...", and that is not happening. I never get the array back on reboots, so I did not continue trying to add anything to `fstab`, as I perceived that to be too dangerous after the fact that a precondition was not met.
Last edited by phonky (2024-08-19 02:42:04)
Offline
What am I missing?
This forum is for Arch Linux
The forum uses bbc code, not markdown
Logs, configuration files, and/or error messages
Last edited by dakota (2024-08-19 03:25:05)
"Before Enlightenment chop wood, carry water. After Enlightenment chop wood, carry water." -- Zen proverb
Offline
Hey @dakota
Before providing more info, I want to make sure I understand your comment 100%
> This forum is for Arch Linux
Yes, of course, apologies. This would seem to suggest I should not continue this thread.
> Logs, configuration files, and/or error messages
This though sounds encouraging to post more info...
So, with all respect, is it ok to continue this thread or not?
Thank you.
Last edited by phonky (2024-08-19 15:12:03)
Offline
So, with all respect, is it ok to continue this thread or not?
Sorry. I can't answer that question as it's really not my decision.
The problem is that each Arch derivative modifies the installation process in ways that the Arch community may not be familiar with (additions, deletions, modifications). In your case, maybe there is no significant change and other people can help you. I guess I mentioned it because I thought it was kind of funny. "What have I forgot?" "Er... you're on the wrong board?" Edit - on reflection, maybe it wasn't so funny. Sorry.
I read the forums as a way of learning more about Arch. Someone poses a question and I ask myself how I'd go about troubleshooting it. Then I wait for a few days and read the answers.
My main concern is that it is really hard to read code when it's not formatted correctly (bbc code). I get bored pretty easily and wander off looking at other threads. I suspect there are people here who could help you, but maybe they get bored, too?
I guess you could report the thread and ask a moderator for a decision as to whether you can continue?
Best of luck.
Cheers,
Last edited by dakota (2024-08-20 19:14:05)
"Before Enlightenment chop wood, carry water. After Enlightenment chop wood, carry water." -- Zen proverb
Offline