On Wed, Sep 18, 2024 at 1:09 AM Yu Kuai <yukuai1@xxxxxxxxxxxxxxx> wrote:
>
> Perhaps can you try latest kernel?(6.11)
>
I'm on 6.11
>
> You should assemble the array as read-only, so that the reshape won't
> start, and you'll able to copy the data.
>
It is read only now, but it isn't mounting...
>
> Thanks,
> Kuai
>
Thank you for the suggestions. Currently I am already on kernel 6.11:
bill@bill-desk:~$ sudo uname -a
Linux bill-desk 6.11.0-061100-generic #202409151536 SMP
PREEMPT_DYNAMIC Sun Sep 15 16:01:12 UTC 2024 x86_64 x86_64 x86_64
GNU/Linux
I've noticed that sometimes when I reboot, the array automatically
assembles in read-only mode:
bill@bill-desk:~$ cat /proc/mdstat
Personalities : [raid10] [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid10 sdb1[1] sdd1[3] sdc1[2] sda1[0]
15627786240 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
bitmap: 0/117 pages [0KB], 65536KB chunk
md127 : active (auto-read-only) raid10 sdh1[3] sdn1[5] sdf1[1] sdk1[8]
sdg1[2] sdl1[9] sdj1[7] sdm1[4] sde1[0] sdi1[6]
46877236224 blocks super 1.2 512K chunks 2 near-copies [10/10]
[UUUUUUUUUU]
resync=PENDING
bitmap: 0/88 pages [0KB], 262144KB chunk
unused devices: <none>
(note md1 is an unrelated array that is working just fine)
Here is my fstab file:
bill@bill-desk:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p1 during installation
UUID=291e31b9-fe93-4ca2-a55e-925bd52e22ce / ext4
errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=3D01-0380 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw
0 0
# /dev/md1
UUID=8f645711-4d2b-42bf-877c-a8c993923a7c /media/bill/ARRAY2
ext4 defaults,nofail 0 2
# /dev/md2
UUID=1c11229a-df0f-4642-b7ea-a86a31d2339e /media/bill/ARRAY3
ext4 defaults,nofail 0 2
Note that before the reshape, the array in question was /dev/md2 but
now it is called /dev/md127. I don't know why that happened or whether
it needs to be fixed.
Here is my mdadm.conf:
bill@bill-desk:~$ cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR therealbrewer@xxxxxxxxx
MAILFROM therealbrewer@xxxxxxxxx
# definitions of existing MD arrays
ARRAY /dev/md/1 metadata=1.2 UUID=00cb57fc:23e1ccd3:af14db43:98b61d97
name=bill-desk:1
ARRAY /dev/md/2 metadata=1.2 UUID=8a321996:5beb9c15:4c3fcf5b:6c8b6005
name=bill-desk:2
# This configuration was auto-generated on Sun, 06 Sep 2020 17:31:04
-0500 by mkconf
Should I just try to mount md127 manually?
Thanks for the help.
Bill
