Resyncing task is still in progress, I don't know what to do.
Download the full log zip file now, as that will likely contain clues to what is happening with the main volume. If you have no backup of the main volume, then back it up while you are waiting for the resync to complete. Don't reboot the NAS until you complete the backup and the EDA500 resync completes.
At that point, I'd try rebooting the NAS, and see if the main volume remains read-only. I suspect it will (and it might not be mounted at all). But it is unusual that the read-only status was coincident with the EDA500 error, so it is possible that the main volume will end up read/write.
After that, you could either get a support contract with Netgear, and see if they can resolve the issue with the main volume remotely. Or you can try creating a new volume, and restore the files from your backup.
I don't understand why the volume of the main device has a read-only status due to resyncing task of the extension
It's likely not related to the resync, but it might be linked to the EDA disk error somehow. You could look in the log zip, and see what underlying errors happened - but focus on completing/updating your backup first. The data is definitely at risk.
Re: RN316 - Read Only status during resyncing task on EDA500 extension
Dear Stephen,
thanks for your quick feedback.
I want to precise a point : "read-only" issue happened yesterday afternoon, and in the evening after downloading log files I decided to switch off the system, I rebooted it this morning with exactly the same symptom.
I’m currently trying to download a new log sip but the system seems to answer too slowly and transaction goes to error status.
Nevertheless I just had a look in the system-journal.log file (downloaded before the switch off) and I found that :
May 19 15:48:51 nas-27-5B-DE kernel: WARNING: CPU: 0 PID: 29160 at fs/btrfs/extent-tree.c:7004 __btrfs_free_extent+0xaf4/0xb31()
May 19 15:48:51 nas-27-5B-DE kernel: BTRFS: Transaction aborted (error -28)
May 19 15:48:51 nas-27-5B-DE kernel: Modules linked in: sx8635(O) vpd(PO)
May 19 15:48:51 nas-27-5B-DE kernel: CPU: 0 PID: 29160 Comm: kworker/u8:10 Tainted: P W O 4.4.218.x86_64.1 #1
It seems that system considers the volume complety full, even if we can see 1.7TB left on web interface page.
I can easily remove 1TB of Data but as the volume is read only stated I can't.
Remark : I'm reluctant to upload complete log zip as there are some confidential files and data on the NAS and as I don't know what is listed in the log files I prefer to copy some elements. Nevertheless please find downloaed the system-journal.log file in PDF as log extension has been rejected by the system.
Regarding resyncing task, in the same file I see start of the problem earlier in the day (yesterday) :
May 19 10:28:03 nas-27-5B-DE rn-expand[4864]: Partitioning failed! [2]
That means both are not linked ! We have the answer of one question and probably I will have to replace one HDD.
Now remaining question is related to the read-only state and how to make space free under this condition.
Re: RN316 - Read Only status during resyncing task on EDA500 extension
The NAS usually puts a volume in read-only mode when it detects a problem with that volume. It's protecting the data from further damage. As @StephenB said, it is critical that you back up data before re-booting. After re-boot, the main volume may not even mount.
Before you re-boot, it may also be a good idea to EXPORT and disconnect the (fully re-synced) EDA volume. If you end up having to factory default, you can later add an exported volume, but you cannot add a volume that wasn't. And if you end up just having to destroy and re-create the main volume, the act of destroying it with the EDA attached will make the EDA volume primary, which is not a good situation with the eSATA multiplier interface it uses. If all ends up well after the re-boot, or after you fix the problem, you just power down, re-connect the EDA and power up, which will automatically import the EDA volume. Just make sure you don't duplicate any share names from the EDA if you have to start over with the main volume.
I suppose the problem with the main volume may have been caused in part by the re-sync of the EDA volume. The eSATA interface is, frankly, a poor choice for the EDA. An issue on the bus may have "spilled over" to the main volume. But that "spill over" may be real damage to the volume or just a perceived one, which will determine whether a re-boot fixes it or not.
If you end up not having exported the EDA volume and later need to add it to a newly created main one, there is a work-around. You put just the EDA drives in the main NAS, boot, then export. That'll work for you since you have a 6-bay NAS. But those with a smaller main NAS don't have that option.
Re: RN316 - Read Only status during resyncing task on EDA500 extension
Dear All,
I have finally succeeded to save all data and EXPORT the EDA extension device.
After disconnecting it I have reboot and the Read-Only Status disappeared.
And it's possible to add/remove files.
Then I have shut downed the system and reconnected the EDA module, restarted it and bad news : the main volume (on the RD316) got again the read-only status.
It seems that the connection with the EDA device generates this status.
I don't know what to do ....
Do you have some recommendations to fix this issue?
Re: RN316 - Read Only status during resyncing task on EDA500 extension
If you disconnect the EDA (power off- -- don't export) is the main volume still read-only? The NAS will complain about the missing volume, and will need to re-sync the OS partition of the EDA drives when you re-connect, but the volume should be fine so long as you are connecting to the same main volume.
You can try using another eSATA port. I believe port 3 (the red one) uses a different controller than the other two and the main drives. eSATA is the Achilles heel of the EDA500. If disconnecting doesn't clear the read-only flag of the main volume, you'll have to export, make a new one, then try connecting to another port. Maybe try with a single-drive main volume before all drives and RAID sync of the main volume.
Re: RN316 - Read Only status during resyncing task on EDA500 extension
Dear Sandshark
please find my answers in your text
If you disconnect the EDA (power off- -- don't export) is the main volume still read-only? ==> YES
The NAS will complain about the missing volume, and will need to re-sync the OS partition of the EDA drives when you re-connect, but the volume should be fine so long as you are connecting to the same main volume.
After that I have shutdowned the main device and startet it again, booting is stuck at 25% for 2 hours .... no progress
You can try using another eSATA port. I believe port 3 (the red one) uses a different controller than the other two and the main drives.
==> There is no red one port and I've tried to use the second one without different result
eSATA is the Achilles heel of the EDA500. If disconnecting doesn't clear the read-only flag of the main volume, you'll have to export, make a new one, then try connecting to another port. Maybe try with a single-drive main volume before all drives and RAID sync of the main volume.
Re: RN316 - Read Only status during resyncing task on EDA500 extension
I was thinking the 316 had three eSATA ports like the 516.
The first picture is with the EDA removed and the second is after it was re-connected with power off and then powered on? Then you re-booted and it doesn't even get that far? That would tend to indicate that the EDA volume had a problem before it was removed, but it didn't show up.
I doubt it's going to get any farther, but you can wait longer if you want to.
I don't have a lot of hope it will fix it, but you could power down and move the EDA drives to the main chassis. If it does boot, it'll make that volume into a primary one and you'll have to export it from the main NAS before you put the drives back in the EDA and mate it with the 316. And if you try and mate it with a main volume that shows the "missing" eda volume instead of a newly-created one, you'll have to destroy that (which will just make it forget the eda since it won't really be connected at that point).
