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.
Best to deal with that after the volume is fixed. The NAS does have a backup job capability. There are also PC utilities like FreeFileSync that can be used to back up shares on the NAS.
- Accéder au NAS me fait un peu peur... Je ne voudrais pas faire plus de dégâts. Si vous avez une idée de "comment faire" ou y accéder directement ?
There is risk, and that is why I also suggested the options of RAID recovery software and data recovery. They do cost, but the risk is much less.
I have helped several folks manually mount the volume. If you want to pursue that, then the first step is to download the full log zip file. Then copy the full zip into cloud storage (dropbox, google drive, etc). Send me a private message (PM) using the envelope icon at the top right of the forum page. Include a link to the zip file. Make sure the link permissions allow anyone with the link to download.
Then you must not have an NV+ v2. It can only run 5.3.x firmware.
Can you give us the correct model information? You will see it on the system->overview page of the admin web ui.
The guidance from @schumaku on your other thread assumed the model information was correct. It doesn't apply to OS-6 systems.
If you like, I can review the NAS logs for you. Download the full log zip from the logs page, and then put that into cloud storage (dropbox, google drive, etc). Then send me a private message (PM), using the envelope icon in the upper right of the forum page. Put a link to the log zip in that PM. Make sure the permissions are set to allow anyone with the link to download the logs.
Me revoilà enfin de retour. Je voulais vous montrer ce que je vois sur la page d’administration. Je l’ai mis en fichier joint. Dites moi ce que vous en pensez. Il y a, d’après moi, un souci. ☹
You actually have an RN424, not an NV+V2. They are very different platforms.
The inactive volume error you are seeing generally has two different causes
two or more failed disks
cached writes never being written to the disks (usually a result of power loss, or doing a forced shutdown of the NAS).
Although it failed quite a while ago, the errors might still in the system logs. I suggest downloading the full log zip file from the logs page in the web ui.
Do you have a backup of the files?
If you have no backup, then there are three paths to try and recover the files:
Access the NAS in tech support mode, and attempt to repair and mount the volume. This requires use of the linux command line and there is risk of doing more damage if you make a mistake.
Connect the disks to a Windows PC (with USB adapter/docks) and purchase RAID recovery software that supports BTRFS. ReclaiMe is a software package many here have used successfully. You'll also need enough storage to copy off the data.
Find a data recovery service, use them to recover your files.
Best to deal with that after the volume is fixed. The NAS does have a backup job capability. There are also PC utilities like FreeFileSync that can be used to back up shares on the NAS.
- Accéder au NAS me fait un peu peur... Je ne voudrais pas faire plus de dégâts. Si vous avez une idée de "comment faire" ou y accéder directement ?
There is risk, and that is why I also suggested the options of RAID recovery software and data recovery. They do cost, but the risk is much less.
I have helped several folks manually mount the volume. If you want to pursue that, then the first step is to download the full log zip file. Then copy the full zip into cloud storage (dropbox, google drive, etc). Send me a private message (PM) using the envelope icon at the top right of the forum page. Include a link to the zip file. Make sure the link permissions allow anyone with the link to download.
