On Sat, 14 Nov 2020 12:15:47 -0700
Charles Curley wrote:
> Or (afterthought here) did I give it the wrong UUID?
A week later, I came back to this. It appears I did use the wrong UUID
in /etc/crypttab.
root@hawk:~# ll /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 180 Nov 20 10:25 ./
drwxr-xr
On Sat, 14 Nov 2020 23:00:35 +0100
Toni Mas Soler wrote:
> I have more or less the same configuration. I am a no-systemd user
> (yet?) so I cannot show you the full example.
> You could verify:
> - Is there a mdraid1x module in your grub menu entry?
> - If I not wrong you made your RAID by mdadm
I have more or less the same configuration. I am a no-systemd user
(yet?) so I cannot show you the full example.
You could verify:
- Is there a mdraid1x module in your grub menu entry?
- If I not wrong you made your RAID by mdadm metadata version 1.2. I
think in this version metadata is located at
On Sat, 14 Nov 2020 08:12:41 +0100
john doe wrote:
> >
> > What do I do to automate that?
> >
>
>
>
> Is your '/etc/crypttab' file properly populated?
Well, I thought it was
At first I got the UUID for the RAID device, /dev/md0:
root@hawk:~# mdadm --detail /dev/md0
/dev/md0:
On 11/14/2020 4:23 AM, Charles Curley wrote:
I've added RAID and two new hard drives to my desktop. The RAID appears
to work, once it is up and running. Alas, on boot it is not being
properly set up. Everything else comes up correctly.
I have two new four terabyte drives set aside for RAID. They
I've added RAID and two new hard drives to my desktop. The RAID appears
to work, once it is up and running. Alas, on boot it is not being
properly set up. Everything else comes up correctly.
I have two new four terabyte drives set aside for RAID. They are
partitioned, with one partition on each, a
6 matches
Mail list logo
