RN316 Upgraded Firmware, EDA500 Volumes are messed up
It's both. Here's a screenshot with what happens when I boot the NAS by itself and then turn on one EDA.
It still sees them.
I booted up with the EDAs unplugged, got this screenshot. Ran smartctl on each of those. Rebooted, the NAS came up fine, plugged in the EDA and smartctl ran fine on those drives as well.
So I booted NAS with the EDA connected and saw this:
root@NAS:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md123 : active raid5 sdg3[0] sdk3[4] sdj3[3] sdi3[2] sdh3[1]
39046344448 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
[>....................] resync = 0.1% (14019280/9761586112) finish=48698.8min speed=3328K/sec
md124 : active raid5 sda6[0] sdd6[5] sdc6[4] sde6[6] sdb6[2] sdf6[1]
9766864640 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md125 : active raid5 sda5[5] sdf5[6] sde5[9] sdc5[7] sdd5[10] sdb5[8]
9766864320 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md126 : active raid5 sda4[6] sdf4[11] sde4[10] sdd4[8] sdc4[9] sdb4[7]
4883113920 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md127 : active raid5 sda3[6] sdf3[11] sde3[10] sdd3[9] sdc3[8] sdb3[7]
14627073280 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md0 : active raid1 sda1[17] sdh1[8](W)(S) sdi1[9](W)(S) sdj1[10](W)(S) sdk1[11](W)(S) sdb1[16] sdc1[18] sdd1[19] sde1[20] sdf1[21] sdg1[7](W)
4192192 blocks super 1.2 [7/7] [UUUUUUU]
md1 : active raid10 sda2[0] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
1566720 blocks super 1.2 512K chunks 2 near-copies [6/6] [UUUUUU]root@NAS:~# mdadm --examine --scan
ARRAY /dev/md/1 metadata=1.2 UUID=e5669719:f7f40928:5ec19a48:dfa7e111 name=7c6e0558:1
ARRAY /dev/md/data-0 metadata=1.2 UUID=2f589054:264b7840:3326a501:d94222fc name=7c6e0558:data-0
ARRAY /dev/md/data-1 metadata=1.2 UUID=8f11ed86:83fff0ac:15af1aa8:ddce01b6 name=7c6e0558:data-1
ARRAY /dev/md/data-2 metadata=1.2 UUID=5a703268:6ae5a904:30dd4315:4381822d name=7c6e0558:data-2
ARRAY /dev/md/data-3 metadata=1.2 UUID=cf948dc9:d2131105:fb56745a:51033405 name=7c6e0558:data-3
ARRAY /dev/md/0 metadata=1.2 UUID=4baa4c4b:a622187f:542e6b5f:4bdbd583 name=7c6e0558:0
spares=4
ARRAY /dev/md/eda3-0 metadata=1.2 UUID=af898d78:0f5b4ce1:ec357aa6:5b12b8d9 name=7c6e0558:eda3-0root@NAS:~# mdadm --stop /dev/md123
mdadm: Cannot get exclusive access to /dev/md123:Perhaps a running process, mounted filesystem or active volume group?
root@NAS:~# umount /dev/md123
root@NAS:~# mdadm --stop /dev/md123
mdadm: stopped /dev/md123
root@NAS:~# mdadm --assemble /dev/md123
mdadm: /dev/md123 not identified in config file.So I am not really sure next step.
@joe_schmo wrote:
So I booted NAS with the EDA connected and saw this:
So I am not really sure next step.
It looks the eda volume was resyncing, so different symptoms from before. The data might have actually been accessible (with slow performance).
You could either
- add --scan to the assemble command, and see if that works
- reboot and see if you get the same resyncing status on eda 1. If you do, then check that the data is accessible. Wait for the resync to complete before doing anything with eda2.
