Re: Upgraded to 6.5x can no longer access original shares or create shares that stick

Fretting · ‎2016-06-26

I have a ReadyNAS 516 that I updated to 6.5.0 (and now .1) along with one expansion chassis. Using it as a media server mostly.

Older shares do not appear on the main unit except the home share. I had a media share, and although the folder is still there, it is not shown as a share.
I renamed the Media folder to Media3 to preserve data as I can get to it via the nas\data share/volume.

If I create a new share, it doesn't "stick"; after a reboot of the NAS. It is gone. However, the folder that was created for the share remains. If I delete the folder via Explorer, it reappears.

I cannot create a share if the folder name is the same. But a new share disappears upon reboot anyway.
The only way I see currently out of this mess is to backup my data, remove the DATA volume and recreate it.

I did not update my ReadyCloud account. I saw the notice but didn't realize that it would cause a problem such as this. This is the only thing that has changed, so I cannot attribute it to nothing else.. I had installed ReadyCloud but never really used it. If indeed this was the root cause of this corruption which I have spent 5 hours on tonight to no avail, I cannot fathom why Netgear would create such a potential issue. My ReadNAS just runs 24/7. I do keep firmware updated, but obviously wish I had never upgraded to 6.5x. I had a stable system. This backup and restoration will take me a week.

My 516 is my 4th ReadyNAS. I'm no newbie.I've had small issues over the past 10 years or so but nothing like this!

StephenB · ‎2016-06-26

Just to make sure I understand this - you create a share from the web ui, and then reboot the NAS. After the reboot the share doesn't appear in the web ui list. Correct?

When you say you can see the folder, do you mean it is showing up when you access \\readynas in explorer? Or are you accessing \\readynas\data and seeing in the volume listing?

Fretting · ‎2016-06-26

Correct.

\\readynas\data\media
\\readynas\data\folder2
\\readynas\data\folder3
etc.
However, I can also see the original share that is not showing on the web ui.
\\readynas\media

On my secondary esata expansion chassis volume, \data2, all is normal and the shares show in the web ui correctly. Just the shares in the first volume can't be seen or "stick" if created in the web ui.

Fretting · ‎2016-06-26

Sorry about the incorrect statement that the original share "media" was not showing as a share. It is, but not in the web ui.

It was 5am when I posted that. My apologies.

StephenB · ‎2016-06-27

@Fretting wrote:
Sorry about the incorrect statement that the original share "media" was not showing as a share. It is, but not in the web ui.

It was 5am when I posted that. My apologies.

Just to make sure I am clear...

"media" is showing up in file explorer, but not in the web ui?

Fretting · ‎2016-06-28

Yes.

I can browse the network and see \\readynas\data\media just fine... and it is still there as a share, \\readynas\media

It's not in the web ui.

If I try to recreate it, I get an error, so the system is seeing it physically, but the web ui won't show it.

Does the web ui use some sort of database to pull this information? Something is corrupted somewhere.

Meanwhile I am continuing to make a backup while the data is still there and accessable.

Let me ask this. On my expansion chassis (Volume Data2)... If I simply leave it turned off and force a factory reset on the NAS, will the NAS be able to "see" it after the reset and configuration? Or will it wipe out that data also?

StephenB · ‎2016-06-29

I am thinking it might be wise to use Netgear support.

Did you purchase between June 1, 2014 and May 31, 2016? If so you have lifetime chat support. Even if you need per-incident paid support, it might be worth it.

JMehring · ‎2016-07-01

I have same issue. None of my original shares show up in web UI on boot and I am unable to mount them remotely via samba, NFS, etc.. Only the home share and removable USB appear.

Do you have encryption enabled? I was thinking it may have something to do with that? What I currently need to do is wait for ReadyNAS to boot, open a SSH terminal session and restart readynasd: At that point the shares will then re-appear within web UI and configuration files are populated properly (/etc/exports, etc). I think (have not have much time to test) I need to do this manually everytime I boot. I may create an additional systemd boot override to start readynad later or something if it turns out that it is starting before encrypted drive is ready.

systemctl restart readynasd

These are the issues I came across while attempting to get things working again:

I noticed the permissions were really messed up in /frontview. Don't know why attention was not given to this area as the user ID is listed as 115 (undefind user name) for some files and guest as the group for others which is not really standard. So I cleaned them up. As a note, previous versions of readynas also have had messed up permissions.
For some reason I needed to softlink /etc/frontview/Samba.conf. to /etc/frontview/Samba.conf as one of the configuration files seems to attempt to add an additional period '.' to the path.
There are hundreds of dmesg errors in relation to UPS (usb 6-1: usbfs: process 3151 (usbhid-ups) did not claim interface 0 before use)

Also been getting some stack dumps:

[  600.068436] INFO: task nfsd:3398 blocked for more than 200 seconds.
[  600.068438]       Tainted: P           O    4.1.21.x86_64.1 #1
[  600.068440] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  600.068441] nfsd            D ffff88006ef7ba28     0  3398      2 0x00000000
[  600.068444]  ffff88006ef7ba28 ffffffff88d804a0 ffff88014b1d6c80 ffff88006ef7ba88
[  600.068448]  ffffffff882edcd9 ffff88006ef7ba08 ffff88006ef7c000 ffff8800aade61ac
[  600.068451]  ffff88014b1d6c80 00000000ffffffff ffff8800aade61b0 ffff88006ef7ba48
[  600.068454] Call Trace:
[  600.068457]  [<ffffffff882edcd9>] ? btrfs_iget+0x59/0x6e0
[  600.068460]  [<ffffffff889c4af2>] schedule+0x32/0x80
[  600.068463]  [<ffffffff889c4cb9>] schedule_preempt_disabled+0x9/0x10
[  600.068466]  [<ffffffff889c5df2>] __mutex_lock_slowpath+0x92/0x100
[  600.068469]  [<ffffffff889c5e76>] mutex_lock+0x16/0x2a
[  600.068472]  [<ffffffff882f810a>] btrfs_file_write_iter+0x6a/0x3f0
[  600.068474]  [<ffffffff882299f0>] ? _fh_update.isra.12.part.13+0x50/0x50
[  600.068477]  [<ffffffff881221cd>] ? __kmalloc+0x2d/0x100
[  600.068480]  [<ffffffff88127454>] do_iter_readv_writev+0x54/0x70
[  600.068482]  [<ffffffff881280f6>] do_readv_writev+0x1a6/0x240
[  600.068485]  [<ffffffff882f80a0>] ? btrfs_fdatawrite_range+0x70/0x70
[  600.068488]  [<ffffffff8814dfbb>] ? inode_to_bdi+0x2b/0x70
[  600.068491]  [<ffffffff880f2434>] ? file_ra_state_init+0x14/0x30
[  600.068494]  [<ffffffff88125379>] ? do_dentry_open+0x299/0x330
[  600.068496]  [<ffffffff88124e80>] ? finish_no_open+0x10/0x10
[  600.068499]  [<ffffffff881281c4>] vfs_writev+0x34/0x50
[  600.068502]  [<ffffffff8822ab32>] nfsd_vfs_write.isra.18+0xa2/0x270
[  600.068504]  [<ffffffff8822ce0c>] nfsd_write+0xec/0x100
[  600.068507]  [<ffffffff8823450d>] nfsd3_proc_write+0x9d/0xe0
[  600.068511]  [<ffffffff88227251>] nfsd_dispatch+0xa1/0x1b0
[  600.068514]  [<ffffffff8899f00d>] ? svc_tcp_adjust_wspace+0xd/0x20
[  600.068516]  [<ffffffff8899d797>] svc_process+0x427/0x6d0
[  600.068519]  [<ffffffff889ac255>] ? svc_recv+0x125/0x8a0
[  600.068522]  [<ffffffff88226c97>] nfsd+0xf7/0x170
[  600.068525]  [<ffffffff88226ba0>] ? nfsd_destroy+0x70/0x70
[  600.068528]  [<ffffffff88082624>] kthread+0xc4/0xe0
[  600.068531]  [<ffffffff88082560>] ? __kthread_parkme+0x80/0x80
[  600.068533]  [<ffffffff889c7c92>] ret_from_fork+0x42/0x70
[  600.068536]  [<ffffffff88082560>] ? __kthread_parkme+0x80/0x80

Fretting · ‎2016-07-01

I do not have encryption enabled, but certainly had permissons set for each share and I also noticed this was an issue. I had some users (both admin and users) that would show but were "grayed out" and one could not select them.

I also only show the home share on the main volume, but on the expansion chassis volume it is showing okay.

My current course of action is to simply back up the bazillion terrabytes that are in RAID5 and do a complete factory reset and start all over. I have 4TB drives filled in the main unit as well as 4TB drives in the expansion unit.

At least at this point I am not missing files, so I'm diligently backing up everything. I purchased an additional 3 ea 5TB drives just so I can back this beast up.

Netgear has cost me much time and money on this fiasco. I've been a solid fan (I have 4 Netgar NAS'), but no longer. It's obvious this release was rushed and not ready for prime time.

Thanks for sharing, JM! I'm not savvy on Linux so I've not dived into the OS. And neither of us should have to.

Fretting · ‎2016-07-01

Thanks for the suggestion, Stephen!

I'm going the long route as I don't want this to rear its ugly head again. Full backup and factory reset. I only hope this resolves the issue.

Thanks kindly for your help!