On Tue, May 1, 2018 at 8:31 AM, Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx> wrote: > On Tue, May 01, 2018 at 08:05:23AM -0500, o1bigtenor wrote: >> /dev/md0p1: Linux rev 1.0 ext4 filesystem data, >> UUID=49552036-b46f-4956-ade9-3541a3dd7f0a (extents) (large files) >> (huge files) > > So there is a filesystem, which you should be able to mount. > > # mount -o loop,ro /dev/md0p1 /mnt/somewhere > # df -h /mnt/somewhere > # ls /mnt/somewhere > > If that works then everything is probably fine, not a RAID problem. > Did this and as a result have access to the raid array. It seems that by using the 'ro' in the initial command that I have a read-only raid array. I really don't want to fubar this thing but I also need the array to be rw rather than ro. Please - - - commands to umount? (I think using umount in the first command would be what I need with everything else remaining the same. Then I would reenter using rw to achieve the needing rw ability. The last two commands are not needed either in the umount nor in the subsequent remount. Please advise.) 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
