Yesterday I bought a new drive for my Netgear ReadyNAS NV+ v2. Here is my disk configuration:
I changed disk No.2 (I wanted to replace 2TB with 4TB)
On a working system, I removed one of the previously installed ones and installed a new one. But the disk that I installed turned out to be faulty (it did not start, it seemed damaged during transportation). I tested it a little and after that I realized that this new disk is not suitable. I returned the disk that was installed earlier. Unfortunately, by this time there was already a “lifesupp” error on the NAS screen.
Now I can’t open my files - the NAS can’t find the path...
Please give me some advice on how to recover data?
But the disk that I installed turned out to be faulty (it did not start, it seemed damaged during transportation). I tested it a little and after that I realized that this new disk is not suitable. I returned the disk that was installed earlier. Unfortunately, by this time there was already a “lifesupp” error on the NAS screen.
Now I can’t open my files - the NAS can’t find the path...
Download the full log zip file, it might give some clues what happened.
Thanks. There is some privacy leakage when you post the log zip publicly - normally they are sent via private messages (PMs) using the envelope icon in the upper right of the forum page. So I took the liberty of redacting your link after I downloaded the zip.
It looks like two of your disks are out of sync - this can happen as a result of failed disks, or if the NAS is improperly shut down.
The array can be forcibly assembled using ssh - is that something you have used before?
Another option (probably safer) is to connect the disks to a Windows PC and then use R-linux for Windows to access the data. You'd need one or more suitable USB adapter/dock(s), and enough storage to offload the files.
Please tell me, to use R-linux for Windows, do I need to connect all drives to the PC at the same time or can they be connected one by one?
You'd need to connect them all somehow. If the PC has enough space, I think you could image them to iso (one at a time) and then mount them as drive letters.
I agree it is less convenient. It is a bit safer (assuming you don't accidentally damage a disk in handling), as it doesn't change the contents of any of the disks.
If I use SSH, I don't need a PC and adapters? Will it be enough to connect to the NAS and run commands through the terminal?
Correct, you'd just be running commands from the linux command line. If you can't enable ssh now, then you could instead boot in tech support mode (connecting with telnet instead of ssh, but still using the linux command line).
I don't have much experience in executing SSH commands, but I do. But with a volume equal to the ISO images of all disks, I will almost certainly have problems.
@Alexandr_kudrov wrote: I don't have much experience in executing SSH commands, but I do. But with a volume equal to the ISO images of all disks, I will almost certainly have problems.
Yes. Then you log into the NAS using either the built-in ssh command or with a client called putty. You normally use root as the username with the NAS admin password.
If that fails for some reason, you can fall back to tech support mode.
I successfully installed the plugin and connected to the NAS via SSH. Please tell me how exactly I need to restore unlinked volumes? Is there a link to the instructions?
If this fails, you could try again with --really-force instead of --force. Not all versions of mdadm support --really-force though,and I am not sure if the NV+ v2 does.
If the assembly suceeds, then try mounting the array
mount /dev/md2 /C
Then reboot the NAS.
If you see anything that looks wrong as you enter these commands, then copy what you are seeing and post it here. Best to stop at that point, and not attempt to continue.
You can try the mdadm --assemble --force command without /dev/sdb3 and see what happens there.
There was a disk failure for sdb in system.log reported on 25 December.
There was also disk failure message for sdd on 26 December - if that is real, then you might be unable to recover if sdb has also failed. The issue with sdd might not be real though - the NAS detected a disk removal at about the same time.
On the mount point - you won't find anything useful in /dev. But you should see the mount point the NV+ v2 uses in //
Unfortunately it's hard to find the mount point in the logs when the volume doesn't mount. Normally it is the same as the volume name (which I think defaults to C on the NV+ v2). Maybe I'm wrong about that (or maybe it is actually lower case???)
Unfortunately, the commands did not help... Here is the result of their execution.
After running the command mdadm --assemble --force error: mdadm: an md device must be given in this mode
root@RN_NVplus_v2:~# mount /dev/md2 /c
mount: special device /dev/md2 does not exist
I am very grateful to you for your help! Perhaps it will be easier to understand if I describe my actions in more detail (before the error occurred). Before the failure, I took out disk 2 and put another one in its place (which did not start). The NAS was without one disk for some time while I was looking for the reason that the new disk did not start (it turned out to be defective) and a day later I returned the old disk, but by this time an error appeared...
After removing the log (which I sent earlier), I rebooted the NAS several times. Perhaps something has changed. I'll send you the latest version now.
I wanted to save the updated log file, but there are no logs in the system...
mdadm: /dev/md2 assembled from 2 drives and 1 spare - not enough to start the array.
Likely problems with sdd as well then.
I think your only option for data recovery would be to use RAID recovery software on your PC. Unfortunately that could easily also fail with two problem disks.
I was able to find a PC and connect HDDs to it. and this is what I understood: one of the disks has an unallocated area. On this disk, like on the other 3 partitions. two small ones with system information and one large 1.8 TB (it has an unallocated area). However, the program cannot find one disk... How can I register the one with the unallocated area as the missing disk? Is this possible?
I started searching for files in volume C, but all the files there are marked as deleted... Perhaps a full scan can solve the problem (I’ll run it a little later, it’s about 30 hours). It seems to me that after I took out one disk, the NAS rebuilt the array and during this one of the remaining disks became damaged...
