For those on 1.04 firmware, you may want to upgrade to the 1.05 firmware asap.
Kenna amber light on my raid1 left drive - checked the dns-323 forums and learned that there's some bug in 1.04 firmware which detects drive status incorrectly and kicks out your drive from the array set even though the drive is fine.
Upgraded to 1.05 firmware (thanx richneo for posting the direct official links) and the amber light went away.
Thereafter, next step was to manually join the left drive back into the array - else the DNS-323 will continue to run in degraded state. Once joined, the added drive will be automatically resync-ed - which can take very long for huge drive capacities.
To hot add a disk back into raid:
mdadm /dev/md0 -a /dev/sdb2 (or /dev/sda2 - depending on which drive was kicked out)
Check status of raid resync:
cat /proc/mdstat
... btw, you'll need to telnet or ssh into the dns-323 first before running the above commands... outside scope of this post as I think it's been covered in other posts in this thread.
Kenna amber light on my raid1 left drive - checked the dns-323 forums and learned that there's some bug in 1.04 firmware which detects drive status incorrectly and kicks out your drive from the array set even though the drive is fine.
Upgraded to 1.05 firmware (thanx richneo for posting the direct official links) and the amber light went away.
Thereafter, next step was to manually join the left drive back into the array - else the DNS-323 will continue to run in degraded state. Once joined, the added drive will be automatically resync-ed - which can take very long for huge drive capacities.
To hot add a disk back into raid:
mdadm /dev/md0 -a /dev/sdb2 (or /dev/sda2 - depending on which drive was kicked out)
Check status of raid resync:
cat /proc/mdstat
... btw, you'll need to telnet or ssh into the dns-323 first before running the above commands... outside scope of this post as I think it's been covered in other posts in this thread.
