On 06/03/2018 11:09 PM, Samuel Sieb wrote:
Did you stop the RAID array? "mdadm -S /dev/md127"
What is the output of "mount"?
yeah forgot that step... but stopping the array and mounting returns:
mount: /dev/sdb1: can't read superblock
Given your comments below and since cryptsetup can't seem
On 06/03/2018 11:09 PM, Samuel Sieb wrote:
Try "mount -t xfs -o ro /dev/sdb1 /mnt/localhost-sdb1".
returns:
mount: /dev/sdb1 is already mounted or /mnt/localhost-sdb1 busy
perhaps since i --created the array would this format the soft raid
but leave the drive data intact not needing to mkfs
On 06/03/2018 06:39 PM, Samuel Sieb wrote:
On 06/02/2018 11:39 PM, page p wrote:
file -s just returns : data
i since remove the mdadm.conf so it has auto assigned back to 127...
Can you show us the exact commands you are
trying and the result?
https://paste.fedoraproject.org/paste
On 06/03/2018 03:46 AM, François Patte wrote:
Le 03/06/2018 à 08:39, page p a écrit :
Hi and thank you,
file -s just returns : data
i since remove the mdadm.conf so it has auto assigned back to 127...
Is there any inconvenience to have an array with number 127?
not really, just numbering
, Samuel Sieb wrote:
On 06/02/2018 06:51 PM, page p wrote:
the two drives can be seen, are part of an array and a hexdump says
that they are still XFS but i can not get luks to open the array.
If it is supposed to be a LUKS device, then you should not be able to
see the XFS filesystem. Can you show
Hi,
I have two drives in a raid 1 configuration and used luks crypt on the
raid once created.
today i wanted to change the device number from 127 to 0 and can no
longer open the array as luks says it is not a valid device.
what i did was:
$ mdadm --stop /dev/md127
$ mdadm --create --verbos
