Erm why did you do this on md0?Richard wrote:I thought to try something and add the 4 disk.
But stupid me used this command.
mdadm --manage /dev/md0 -a /dev/sdd
instead of mdadm --manage /dev/md0 -a /dev/sdd4
And it started synching, but I stopped it in time, but I cant delete it anymore
but can't remove it anymore.Code: Select all
root@AS-304T-4BA9:~ # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md126 : active raid1 sdb3[0] sdc3[4] sda3[1] 2096064 blocks super 1.2 [4/3] [UUU_] md0 : active raid1 sdd[4](F) sdb2[0] sdc2[5] sda2[1] 2096064 blocks super 1.2 [4/3] [UU_U]
Code: Select all
root@AS-304T-4BA9:~ # mdadm --manage /dev/md0 --remove /dev/sdd mdadm: Cannot find /dev/sdd: No such file or directory root@AS-304T-4BA9:~ # mdadm --manage /dev/md0 --remove /dev/sdd4 mdadm: Cannot find /dev/sdd4: No such file or directory
Another to think of, before removing the partition should be shrinked.I think I will keep off things until I'm sure what I have to do.
Because I was just thinking, if I force rebuild a raid 5 on 3 disks, that would mean I would loose free space on those 3 disks, and I don't know if I have enough free space on those.
Oh yes your volume1 is not available yet.How do I do this? Because opkg install lsblk gives that opkg is not found.but you can install lsblk from opkg entware.