On Fri, 11 Feb 2022, Michael Rasmussen wrote:
Perhaps you can read up on UUIDs? Two sources I used while reading this
thread were:
https://www.uuidtools.com/what-is-uuid
and
https://en.wikipedia.org/wiki/Universally_unique_identifier
Thanks, Michael.
Rich
On Fri, 11 Feb 2022, Galen Seitz wrote:
Wait! I think you are missing an important point. UUIDs are used for many
things on a modern Linux system. There will typically be *multiple* UUIDs
used for multiple purposes. Here is some trimmed output from an Ubuntu
system that has three physical
On 2022-02-11 09:34, Rich Shepard wrote:
On Fri, 11 Feb 2022, Tomas Kuchta wrote:
The point about not using /dev/sd*, especially with external
enclosures,
is that the device letter can change (not just once) during the array
build.
Tomas,
I'll kill the mdadm create process and use the
On 2/11/22 09:34, Rich Shepard wrote:
On Fri, 11 Feb 2022, Tomas Kuchta wrote:
The point about not using /dev/sd*, especially with external enclosures,
is that the device letter can change (not just once) during the array
build.
Tomas,
I'll kill the mdadm create process and use the two
On Fri, 11 Feb 2022, Bill Barry wrote:
You should also be aware of the useful tool blkid which lists your block
devices and their uuids.
BIll,
Ah, yes. Thanks. I forgot about that one.
Regards,
Rich
On Fri, 11 Feb 2022, Tomas Kuchta wrote:
The point about not using /dev/sd*, especially with external enclosures,
is that the device letter can change (not just once) during the array
build.
Tomas,
I'll kill the mdadm create process and use the two UUIDs instead. Do I
write:
mdadm --create
On Fri, Feb 11, 2022 at 9:50 AM Tomas Kuchta
wrote:
>
> On Fri, Feb 11, 2022, 08:39 Rich Shepard wrote:
>
> > On Thu, 10 Feb 2022, Galen Seitz wrote:
> >
> > > Using UUIDs should prevent much of this grief. For example, here's a line
> > > from mdadm.conf on one my my machines:
> >
> >
On Fri, Feb 11, 2022, 08:39 Rich Shepard wrote:
> On Thu, 10 Feb 2022, Galen Seitz wrote:
>
> > Using UUIDs should prevent much of this grief. For example, here's a line
> > from mdadm.conf on one my my machines:
>
> Galen/Tomas:
>
> Okay. I've six mdadm.conf files here, including
On Thu, 10 Feb 2022, Galen Seitz wrote:
Using UUIDs should prevent much of this grief. For example, here's a line
from mdadm.conf on one my my machines:
Galen/Tomas:
Okay. I've six mdadm.conf files here, including /etc/mdadm.conf which is all
commented out. Since mdadm has been working on
On 2/10/22 16:44, Tomas Kuchta wrote:
On Thu, Feb 10, 2022, 18:55 Rich Shepard wrote:
On Thu, 10 Feb 2022, Bill Barry wrote:
I don't know how far into setting this up, but you might want to
consider a ZFS mirror instead of the mdadm raid1.
Bill,
The 'create' function's been running about
On Thu, Feb 10, 2022, 18:55 Rich Shepard wrote:
> On Thu, 10 Feb 2022, Bill Barry wrote:
>
> > I don't know how far into setting this up, but you might want to
> > consider a ZFS mirror instead of the mdadm raid1.
>
> Bill,
>
> The 'create' function's been running about 2 hours so far. Now that
On Thu, 10 Feb 2022, Bill Barry wrote:
I don't know how far into setting this up, but you might want to
consider a ZFS mirror instead of the mdadm raid1.
Bill,
The 'create' function's been running about 2 hours so far. Now that I've dug
deep into mdadm (having to redo the array several times
On Thu, Feb 10, 2022 at 4:18 PM Rich Shepard wrote:
>
> On Thu, 10 Feb 2022, Rich Shepard wrote:
>
> > A clue is needed so I can rebuild the RAID1 and rebuild my backup bank.
>
> I turned off the Probox, waited a bit, turned it back on. Then rebooted the
> desktop. Once again the four drives in
On Thu, 10 Feb 2022, Rich Shepard wrote:
A clue is needed so I can rebuild the RAID1 and rebuild my backup bank.
I turned off the Probox, waited a bit, turned it back on. Then rebooted the
desktop. Once again the four drives in the Probox are /dev/sd{c,d,e,f} so I
can now rebuild the RAID1 on
14 matches
Mail list logo
