On Tue, May 1, 2018 at 7:47 AM, Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx> wrote: > On Sat, Apr 28, 2018 at 09:42:04PM -0500, o1bigtenor wrote: >> root@debianbase:/# cat /proc/mdstat >> Personalities : [raid10] [linear] [multipath] [raid0] [raid1] [raid6] >> [raid5] [raid4] >> md0 : active (auto-read-only) raid10 sde1[7] sdf1[8] sdc1[5] sdb1[4] >> 1953518592 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU] > > Your RAID seems to be running fine. > >> Device Boot Start End Sectors Size Id Type >> /dev/md0p1 2048 3907037183 3907035136 1.8T 83 Linux > > So the question is: what's on it? Partition table aside... > > # file -sL /dev/md* /dev/md/* > root@debianbase:/# file -sL /dev/md* /dev/md/* /dev/md0: DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x0,32,33), end-CHS (0x21,208,15), startsector 2048, 3907035136 sectors, extended partition table (last) /dev/md0p1: Linux rev 1.0 ext4 filesystem data, UUID=49552036-b46f-4956-ade9-3541a3dd7f0a (extents) (large files) (huge files) /dev/md/*: cannot open `/dev/md/*' (No such file or directory) looking in # /etc/mdadm/mdadm.conf this is confusing # definitions of existing MD arrays ARRAY /dev/md/0 metadata=1.2 UUID=79baaa2f:0aa2b9fa:18e2ea6b:6e2846b3 name=debianbase:0 I would think it should read /dev/md0 not /dev/md/0 . Either way I cannot access the array. Thanks for the suggestions. Dee -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
