access to Readynas admin page impossible, one disk looks dead
Hi all,
since few days, I'm not able to access to my readynas admin page from a web browser. I'm not able to access to the shared directories. The readynas seems to be (too) busy. After some search on the forum, I've be running Raidar, and it looks like my 3rd hard disk is faulty (see below). Can I replace it, in the state where the readynas is ? No need to access to the admin page before replacing the disk ? Any chance the "busy" state is due to the faulty disk and can stop with a new disk ? Will a restoration start automatically, and will I be able to recover my data ?
It looks like I have no other choice than replacing the disk, but I want to avoid to do a mistake.
here is the raidar result :
thanks for your help.
Vincent
Model: RN10400|ReadyNAS 100 Series 4- Bay (Diskless)
Re: access to Readynas admin page impossible, one disk looks dead
I suggest removing the disk, and then rebooting the NAS.
Normally the volume would be available after doing this, but degraded (e.g., RAID redundancy is lost). Best practice is to back up the data, and then hot-insert the replacement disk. If the disk is blank (and you are using XRAID), then the system should start resyncing automatically.
If the volume isn't available (for instance, if it shows up as inactive), then let us know.
Re: access to Readynas admin page impossible, one disk looks dead
It is not normal that it's showing volumes data, data-0, date-1 and data-2 as inactive. In fact data-0 through data-2 shouldn't be visible at all. Some thing else is going on.
This does not look like a filesystem side issue. Hence you running the "btrfs rescue zero-log" command would not fix this. That is also what you reported in the PM to me, as you tried this on your own accord. It fails to actually run the command because the filesystem complains about a missing device.
root@SERVEUR:~# btrfs rescue zero-log /dev/md126
warning, device 1 is missing
Looking at the dmesg log it can be seen that md127 tries to start with sda3 and sdb3 but that fails due to not enough partitions to start the raid.
It reports that md127 only see 2/4 partitions, but the RAID5 would require 3/4 partitions. Due to different sized disks, you have multiple raid instanced which the filesystem "glues" together. It appears that you have 3 different raid instances for the data. One of these raids can't start and that causes the entire data volume to be inaccessible.
You have enough disks in the box to start these raids and the disks are healthy. I very much suspect the issue is that the partition table on sdc (Disk 1) is messed up. It is missing partitions... definitely missing sdc3 and possibly sdc4 as well. But the lack of sdc3 is the reason that the raid fails to assemble.
We have seen before that partitions goes missing, for unknown reasons. I cannot see any health issues on the remaining disks and the logs don't immediately indicate why this happened. The solution would be to copy the correct partition layout (likely from disk 2 - sdb), to disk 1 (sdc). That should allow the raids to assemble properly.
However, one should look at the md-superblocks to ensure this is done correctly. Netgear should assist with this, realistically. I agree with @StephenB on that. They used to offer some data recovery service, and I think they still do. Not sure how you would go about making a ticket these days. Perhaps @StephenB knows (or maybe we need to tag the forums mods?)
Netgear should assist with this, realistically. I agree with @StephenB on that. They used to offer some data recovery service, and I think they still do. Not sure how you would go about making a ticket these days. Perhaps @StephenB knows (or maybe we need to tag the forums mods?)
@Vincefr34I would not advise to try this on your own. Logs don't contain everything and I am conjecturing that you just need a fix to the sdc (disk 1) partition table but it is important to point out that one should examine md-superblocks and look at the md-logs to determine/confirm that this is the correct action to take. Doing this incorrectly or taking the wrong action can cause even more issues. Letting Netgear Level 3 support assess the situation, is the best at this point.
