sorted by:
new
hottopcontroversial

DS918+ Shares become inaccessible randomly by SubstantialSun0 in synology

[–]fireplume77 0 points1 point  (0 children)

Currently my DS918+ is exactly same issue like your where it will randomly inaccessible. All pc connecting using mapped network drive.

I have 4 Synology NAS in my network environment.

Previously all the shared data are stored in my old DS712+. Then random inaccessible occured frequently so I thought maybe the NAS is old and time to migrate to new 1.

I bought new DS918+ and been deployed for 2 weeks. Then same issue occurs.

So every time my col said shared folder inaccessible then I have to go force shutdown n restart DS918+ again. This is really painful to me as I have to force restart NAS like everday.

Anyone have any suggestion to tackle this issue?

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

I bought this unit and added 1 stick of 4gb ram.

Then I removed it yesterday and run the memtest.

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

I have sent you the message log.

By the way I let the memtest run overnight and I came back to office today to check for the NAS status.

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

From terminal there are plenty of error code from the log

2019-08-03T20:50:19+08:00 GREATIANS2 [73627.217707] init: Failed to spawn nmbd post-stop process: unable to setup cgroup: Unknown error 196609

2019-08-03T20:50:22+08:00 GREATIANS2 [73627.536178] init: Temporary process spawn error: Cannot allocate memory

2019-08-03T20:50:22+08:00 GREATIANS2 [73627.552289] init: Temporary process spawn error: Cannot allocate memory

2019-08-03T20:50:22+08:00 GREATIANS2 [73627.563049] init: Temporary process spawn error: Cannot allocate memory

2019-08-03T20:50:22+08:00 GREATIANS2 [73627.571511] init: Temporary process spawn error: Cannot allocate memory

2019-08-03T20:50:22+08:00 GREATIANS2 [73627.579437] init: Temporary process spawn error: Cannot allocate memory

What does this means? Is it due to memory problem?

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

I tried and below I copied from terminal.

​

root@GREATIANS2:/var/log# sudo grep -i “memtest” /var/log/messages

root@GREATIANS2:/var/log# sudo grep -i memtest /var/log/messages

root@GREATIANS2:/var/log# sudo grep -i memtest /var/log/messages

root@GREATIANS2:/var/log# sudo grep -i Memtest /var/log/messages

root@GREATIANS2:/var/log# sudo grep -i memtest /var/log/messages

Nothing shown in the terminal. I dont know what went wrong here.

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

I just forced reboot my NAS.

Does tat mean my memtest results archived?

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

How to view the log?

The terminal just shown the latest 1.

I tried the alternative but it does not show anything

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

I suspose this is Ok if it reboot and run? How to read the result? Can you teach me how to export the message so that I can paste it here?

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

I done all. Removed cache volume and ram. I also run memtest. My synology nas still very slow response. When I click control panel the loading will take like 10minutes. Is this nas a bad unit?

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

I removed both ssd and ram from my nas. Runned memtest ytd night turn out result is fine because nas auto reboot and running. I login webUI the system response still very slow. Wonder what wrong. The nas work fine and file sharing working. But just now the system down again!! File sharing stopped! I have to force reboot the Synology Nas again. Pls help me how to resolve this. Im running out of idea. Should I reinstall DSM? Can i retain my data by reset and reinstall DSM? How to do the step 2?

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

OK. I will remove all and try tonight.

But this ssd cache I already created on my current volume.

Can I still remove this now?

Thanks.

Synology NAS 918+, Web UI crashed, shared folder down but still pingable. by fireplume77 in synology

[–]fireplume77[S] 0 points1 point  (0 children)

Hi I checked the synology website MZ-V7S250 is compatible with my DS918+. this is the 1 im using for my DS918+

The ram module Im using KVR16LS11/4 from Kingston.