Bizarre Behavior: Data Missing, Shares Inaccessible

Thanks for checking in, mdgm-ntgr

Skywalker, to whom I'm eternally grateful, accessed my unit via SDM and got rid of the files on root that were "hidden" by the properly mounted data share. They were some iTunes files that were saved to root during one or more "bad" boots that didn't mount the data volume.

I've since dusted off an old ReadyNAS Ultra 4, loaded it with OS 6 (feels like a brand new NAS!) and some spare HDDs I could cobble together, and am using it as an rsync backup for my 314. At some point I'll wipe my 314, factory reset it, and then perform a fresh install of my data and select apps to clear all the accumulated software cruft. I'm waiting for the various Logitech Media Server apps (by NAStools and super_poussin) to be fixed before I do, though, because they were partly responsible for past issues with a dangerously full root drive.

I'm still no closer to learning what caused the boot sequences that didn't mount the data volume. I'm fine with learning how to do it myself, but right now I don't even know where to begin looking.

Another thing Skywalker (and kohdee too, apparently) are looking into is an Amazon Cloud Sync issue where some files are not being uploaded. I thought this was causing a strange error dialog on the admin page (see that linked thread), but that error dialog only seems to appear in Safari Technical Preview.

So here's where I am right now:

1. Still getting a cryptic "An error has occurred" dialog when accessing the admin console in Safari Technical Preview. It doesn't appear in Firefox beta, Chrome beta or normal Safari.

2. Reluctant to reboot the 314 in case the data volume fails to mount again (and no closer to identifying the offending process).

3. Wary of ever installing another app on a trial basis because the "Remove" process leaves so many potentially problematic residual files.

4. Waiting on S-P and/or NASTools to update their LMS apps—ideally with squeezebox files saved in a selectable share on the data volume—and get the all clear from other forum members.

The question I posed to Skywalker via PM was:

• If the data volume is being mounted over the directory created during a "bad boot," how is it possible to track those files down and delete them under normal operation? Would Netgear consider adding a self-repairing feature whereby those "bad boot" files were moved to a separate directory when a successful boot took place – a bit like the "lost+found" folder on UNIX systems? That might prevent the root volume from getting dangerously full in these cases.