From: buhtz@posteo.de
To: David T-G <davidtg-robot@justpickone.org>
Cc: linux-raid@vger.kernel.org
Subject: re: partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc")
Date: Tue, 01 Dec 2020 09:41:47 +0100 [thread overview]
Message-ID: <8fa1ae68716e406423039419f10ec219@posteo.de> (raw)
In-Reply-To: <20201130200503.GV1415@justpickone.org>
Dear David and others,
thanks a lot for so much discussion and details. I learn a lot.
Following your discussions I see there still is some basic knowledge
missing on my side.
Am 30.11.2020 21:05 schrieb David T-G:
> You don't see any "filesystem" or, more correctly, partition in your
>
> fdisk -l
I do not see the partition in the output of "fdisk -l".
But I can (when both discs are present) mount /dev/md127 (manualy via
mount and via fstab) to /Daten and create files on it.
> So the display isn't interesting, although the logic behind that
> approach
> certainly is to me.
I plugged in the nacked hard discs and they appear as /dev/sdb and
/dev/sdc. After that
mdadm --create /dev/md/md0 --level=1 --raid-devices=2 /dev/sdb
/dev/sdc
Then I did
ls -l /dev/md/md0 and found out this is just a link to /dev/md127.
I formated the raid with
mkdfs.ext4 /dev/md127
Then I mounted (first manually via mount and after sucess via fstab)
/dev/md127 to /Daten
Is this unusual?
next prev parent reply other threads:[~2020-12-01 8:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 8:44 “root account locked” after removing one RAID1 hard disc c.buhtz
2020-11-30 9:27 ` antlists
2020-11-30 10:29 ` c.buhtz
2020-11-30 11:40 ` Wols Lists
2020-11-30 10:31 ` Reindl Harald
2020-11-30 11:10 ` Rudy Zijlstra
2020-11-30 11:18 ` Reindl Harald
2020-11-30 20:06 ` ???root account locked??? " David T-G
2020-11-30 21:57 ` Reindl Harald
2020-11-30 22:06 ` RAID repair script (was "Re: ???root account locked??? after removing one RAID1 hard disc" David T-G
2020-11-30 12:00 ` “root account locked” after removing one RAID1 hard disc Wols Lists
2020-11-30 12:13 ` Reindl Harald
2020-11-30 13:11 ` antlists
2020-11-30 13:16 ` Reindl Harald
2020-11-30 13:47 ` antlists
2020-11-30 13:53 ` Reindl Harald
2020-11-30 14:46 ` Rudy Zijlstra
2020-11-30 20:05 ` partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc") David T-G
2020-11-30 20:51 ` antlists
2020-11-30 21:03 ` Rudy Zijlstra
2020-11-30 21:49 ` Reindl Harald
2020-11-30 22:31 ` antlists
2020-11-30 23:21 ` Reindl Harald
2020-11-30 23:59 ` antlists
2020-11-30 22:04 ` partitions & filesystems David T-G
2020-12-01 8:45 ` partitions & filesystems (was "Re: ???root account locked??? after removing one RAID1 hard disc") c.buhtz
2020-12-01 9:18 ` Rudy Zijlstra
2020-12-01 10:00 ` Wols Lists
2020-12-01 8:41 ` buhtz [this message]
2020-12-01 9:13 ` Reindl Harald
2020-12-01 8:42 ` c.buhtz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8fa1ae68716e406423039419f10ec219@posteo.de \
--to=buhtz@posteo.de \
--cc=davidtg-robot@justpickone.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.