This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
on one of our ReadyNAS 4312 after a reboot all the disk in the Raid 5 are showing as inactive. nothing has been written to the NAS. Isa there a way to bring the drives on line and recover the data ?
on one of our ReadyNAS 4312 after a reboot all the disk in the Raid 5 are showing as inactive. nothing has been written to the NAS. Isa there a way to bring the drives on line and recover the data ?
There might be, it depends on what went wrong.
Do you know what happened (powerfail, disk failure, etc)?
You should be able sort out what happened by looking at system.log, kernel.log, and systemd-journal.log. A single disk failure should have mounted ok, something must have happened to at least one other disk (possibly just out of sync).
It is possible to boot up in tech support mode, and then connect with telnet (using backdoor credentials).
From there you can mount the OS partition, and examine the data volume.
If the volume is simply out-of-sync, then you'd assemble it using --force or --really-force, and then mount it. There could be some data loss (since if it is out of sync, there are lost writes), but often not much (if any).
If a second disk has failed, then it becomes much more difficult - I'd recommend using raid recovery software in that case. The drives would need to be connected to a PC in that scenario. Alternatively you could contract with a data recovery service.
ATA errors are not always due to the drive. SMART can't determine if it's the hardware on the drive side, the NAS (PC, etc.) side, or even another drive on a companion SATA bus. I had an EDA500 on which the eSATA cable became loose, and the result was dozens of ATA errors before the volume was corrupted and went read-only.
Agreed. And a non-zero ATA count doesn't necessarily mean the drive needs to be replaced. I've seen cases where drive X has failed to respond to a command, and an ATA error was then reported on Drive Y. I'm thinking that the SATA bus ended up hung, and that the OS couldn't figure out what drive was at fault.
In this case @PeteC2017 says there was one failed drive though, so I do agree that looking at the smart stats (and the other logs) was the right next step. I said that earlier in the thread.
In any event, the posts are quite stale (2 months old), so I don't why the mod decided to reply now.
