News:

RAID is not a replacement for a backup! Here's why.

Main Menu

Help with TS-XE12TL/R5

Started by sieve, June 11, 2020, 03:34:21 PM

Previous topic - Next topic

sieve

A couple of days ago the NAS became inaccessible.  I was able to log in to the web interface at that time.  From what I recall from the logs, disk2 had failed first, but it seems subsequently disk3 and disk4 had also been dropped from the array.  3 simultaneous disk failures seemed unlikely to me, so I initiated a restart from the web interface.  The NAS did not boot back up.  I heard the click of death while it was trying to boot.  I powered off the NAS and proceeded to check the drives in a PC with SystemRescueCD.

Disk2 had failed and would not reach a ready state to get to the boot selection menu of the PC.  On the other 3 drives SMART seems good, and running mdadm --examine shows superblock is intact.  However, the Events count is different for disk1 at 219873 while the count for disk3 and disk4 is 219847.  Also, the Update Time of disk 1 is about 21 hours more recent than disk3 and disk4.  Lastly, the Array State for disk1 is "A..." while disk3 and disk4 show "AAAA".

What should my next steps be?  Can I just boot the NAS with disk2 removed?  I am unsure if the NAS would automatically resync and become accessible in degraded mode since the event count is out of sync.  If it gets to degraded mode, then insert a new disk into the NAS and rebuild?

Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 109 (show)
Files included: 35 - 1354KB. (show)
Memory used: 932KB.
Tokens: post-login.
Queries used: 15.

[Show Queries]