On Sun, 24 Jan 2021 19:26:12 -0800
Larry Brigman <[email protected]> dijo:
>There are tons of options for mdadm.
>No, you should not put a format on the devices prior to adding them to
>the array.
>It is recommended that you partition the drives prior to adding them
>to the array but you don't need to do that.
>You can just use the raw drive.
OK, I removed the array and started over. None of the four drives had
any partitions. I used the same command as before, and the array was
created without error. I found /dev/md0, although I also noted that I
had renamed /etc/mdadm/mdadm.conf by appending 'old' to it, and having
created the array I assumed that mdadm would have created a new
mdadm.conf file, but it did not.
I continued by formatting, which gave me a bunch of errors:
$ sudo mkfs.ext4 -F /dev/md0
mke2fs 1.45.5 (07-Jan-2020)
Warning: could not erase sector 2: Input/output error
Creating filesystem with 7501333504 4k blocks and 468834304 inodes
Filesystem UUID: 879ce4fd-04fd-4d54-b812-01722f7bd2df
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616,
78675968, 102400000, 214990848, 512000000, 550731776, 644972544,
1934917632, 2560000000, 3855122432, 5804752896
Allocating group tables: done
Warning: could not read block 0: Input/output error
Warning: could not erase sector 0: Input/output error
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: mkfs.ext4:
Input/output error while writing out and closing file system
I also tried mounting it by its UUID above, but got a message that the
UUID did not exist.
These are exactly the same errors that I got before. What did I do
wrong?
_______________________________________________
PLUG: https://pdxlinux.org
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
