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.
This was upgrading to 6.10.0? (I've learned it's always wise to confirm "latest" ). Also, did you have a full root partition when you attempted the upgrade? You might want to wait a bit and see if @JohnCM_S or other Netgear folks want to take a look.
BTW, do you have any idea on what triggered the ethernet overruns?
Obviously make a backup if you haven't got a current one, since btrfs repair is uncertain.
Then access with telnet (I generally use putty). Log in as root; the password is infr8ntdebug.
You then chroot and start raid by entering
# rnutil chroot
Although you don't want to do this in your case, the data volume for a healthy array can be mounted using
# btrfs device scan
# btrfs fi show
# mount /dev/md127 /volume-name
But if you expanded your storage vertically in xraid or have multiple RAID groups in flexraid, you might need to do the device scan before you attempt repair.
I'm sorry if I was unclear, its was after updating to 6.10.0 not during. This happened aprox 10 days after upgrade. During the nightly snapshot it got some error as shown in the previus log. I want to try repair the file system if possible. So thanks for all tips tricks to try ...
I can not access the data so doing a backup is not possible
I can not access the data so doing a backup is not possible
The volume is no longer mounted read-only?
You can atttempt to mount it using the procedure above, though you should probably add -o ro to the mount command (mounting it read only). If that works, you can make a local backup (connecting a USB drive to the NAS, and backing up from the linux CLI).
