Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

It crashes with NAS storage

Jan Bonczek

it crashes every time I click on a folder in the catalog that is on the NAS and I am not connected to the NAS (home network)
I wanted to buy CO but it looks like it doesn't support data on the NAS.

 

Is it just me?

0

Comments

2 comments

Date Votes
  • SFA

    Things work on my NAS.

    I do not use it as a primary source of sessions, catalogue and files but the archive is on there and I sometimes open sessions directly in the NAS. 

    It is on a local wireless network so nowhere near as fast as a local SSD drive will be.

    There are times when the NAS seems to go into hibernation that my Windows 10 Notebook seems unable to awaken without some additional effort. Also the mapped drive I have set up becomes unmapped from time to time.

    If I the last session or catalog I was using was on the NAS this can result in a failure to load (or a long delay) because C1 will default to opening the last used session or catalogue unless you instruct it to do otherwise as you fire it up. 

    If you have a catalog open (loaded into memory) and the NAS has become unavailable I could understand the system might crash. It would be better to have the catalogue local and the image file on the NAS.

    There may be a system or NAS configuration setting that could prevent that problem. The most obvious thing to consider might be to prevent the NAS from adopting any power-saving tricks that would appear to put it off-line when you are using it as a primary resource.

    I have also see some challenges using a Wi-Fi range extender but that seemed to be due to some connection issues between the extender and the main router. The NAS is wired to the extender to connect it to the Wi-Fi. One needs to take car about which "network" link one is using on the active PC when such problems appear.

    0
  • Jan Bonczek
    • Edited

    I have a catalogue locally. I also have active data locally and only data older than 2020 is on the NAS.Every time the NAS is disconnected (I am away from home) and I accidentally click on a folder from the NAS that is not on the local SSD, the whole CO crashes. 

    This doesn't happen to me in any other program. 
    Does this not happen to you when you don't have the NAS available?

    It is clear to me that the NAS will always be slower, but the program should certainly not crash if I just click on a folder in the catalog. 

    Sessions don't make sense to me. 

    1

Post is closed for comments.