Hi, i've updated to 4.2.20 because I was having an issue when creating, it gave an error no space left on device. I can go into tmp and mkdir test2 and it gives that error.I've tried update remote and it gives error error connecting to remote server.I have only used 30% out of 2TB. Thanks for help.

What's the output of the following?:df -h

nas-C1-4F-BC:/dev# df -hFilesystem Size Used Avail Use% Mounted on/dev/md0 4.0G 1.2G 2.7G 30% /tmpfs 16K 0 16K 0% /USB/dev/c/c 1.8T 555G 1.3T 31% /c/c/home 1.8T 555G 1.3T 31% /home/ftp/homes/c/backup 1.8T 555G 1.3T 31% /home/ftp/backup/c/media 1.8T 555G 1.3T 31% /home/ftp/media/dev/sdd1 1.9T 1.8T 26G 99% /USB/USB_HDD_4/dev/sdc1 932G 592G 340G 64% /USB/USB_HDD_3192.168.0.20:/media 926G 800G 127G 87% /home/ftp/NAS_C192.168.0.20:/mediad 464G 432G 33G 94% /home/ftp/NAS_D192.168.0.20:/USB_HDD_1 464G 384G 81G 83% /home/ftp/USB_NAS_1

df -i showsnas-C1-4F-BC:/tmp# df -iFilesystem Inodes IUsed IFree IUse% Mounted on/dev/md0 65536 65536 0 100% /tmpfs 127687 3 127684 1% /USB/dev/c/c 30285824 189563 30096261 1% /c/c/home 30285824 189563 30096261 1% /home/ftp/homes/c/backup 30285824 189563 30096261 1% /home/ftp/backup/c/media 30285824 189563 30096261 1% /home/ftp/media/dev/sdd1 61050880 2770 61048110 1% /USB/USB_HDD_4/dev/sdc1 953984 601 953383 1% /USB/USB_HDD_3192.168.0.20:/media 30474240 790633 29683607 3% /home/ftp/NAS_C192.168.0.20:/mediad 15269888 5413 15264475 1% /home/ftp/NAS_D192.168.0.20:/USB_HDD_1 15265792 628 15265164 1% /home/ftp/USB_NAS_1If thats of any use.

Ah looks like all the inodes on the OS partition (/dev/md0) are in use. This would explain the problem.You may wish to open a tech support (http://www.readynas.com/support) case. Edit the thread title (i.e. subject of first post in the thread) to include your case number.

OS partition is full.Please boot the device to telnet mode, and forward the port 23 to internet.Post the remote access host address into case.

Please help. CASE #18791951 | NETGEAR Communities

22 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Jun 18, 2012
ricster wrote:
Ultra 2
Ok.

4.2.21 is compatible with the ultra 2. Maybe they forwarded the wrong link.

There is a download page here: http://kb.netgear.com/app/answers/detail/a_id/20684/ Maybe try the "Download RAIDiator-x86 " link.

ricster wrote:
Ultra 2

ricster

Aspirant

Jun 18, 2012

StephenB wrote:
ricster wrote:
Ultra 2
Ok.

4.2.21 is compatible with the ultra 2. Maybe they forwarded the wrong link.

There is a download page here: http://kb.netgear.com/app/answers/detail/a_id/20684/ Maybe try the "Download RAIDiator-x86 " link.

No its the correct link. The nas says the file is the wrong architecture, but its not. Its the correct file. The box is dead now. No lights only the power light is on. Its not pingable :cry:

ricster
Aspirant
Jun 18, 2012
Ok. its back on, eventually. Ive looked at df -i and it says 3 free. tried update and it works. says to reboot, but it wont reboot. Now looking at df -i and its 0 free again and you cannot create any files.

Tried to update again and its says wrong architecture.

Frustrating.
ricster
Aspirant
Jun 18, 2012
Ok. stopped every service and addon i had. Finally updated to 4.2.21. Now its says Volume C is dead.

ricster

Aspirant

Jun 18, 2012

Managed to get the syslog

Jun 18 20:27:08 nas-C1-4F-BC kernel: ata1.00: status: { DRDY ERR }
Jun 18 20:27:08 nas-C1-4F-BC kernel: ata1.00: error: { UNC }
Jun 18 20:27:08 nas-C1-4F-BC kernel: ata1.00: configured for UDMA/133
Jun 18 20:27:08 nas-C1-4F-BC kernel: sd 0:0:0:0: [sda] Unhandled sense code
Jun 18 20:27:08 nas-C1-4F-BC kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun 18 20:27:08 nas-C1-4F-BC kernel: sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
Jun 18 20:27:08 nas-C1-4F-BC kernel: Descriptor sense data with sense descriptors (in hex):
Jun 18 20:27:08 nas-C1-4F-BC kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jun 18 20:27:08 nas-C1-4F-BC kernel: 00 94 4d 90
Jun 18 20:27:08 nas-C1-4F-BC kernel: sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
Jun 18 20:27:08 nas-C1-4F-BC kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 94 4d 90 00 00 08 00
Jun 18 20:27:08 nas-C1-4F-BC kernel: end_request: I/O error, dev sda, sector 9719184
Jun 18 20:27:08 nas-C1-4F-BC kernel: ata1: EH complete
Jun 18 20:27:08 nas-C1-4F-BC kernel: nfsd: last server has exited, flushing export cache
Jun 18 20:27:08 nas-C1-4F-BC exiting on signal 15
Jun 18 20:30:39 nas-C1-4F-BC syslogd 1.4.1#18: restart.
Jun 18 20:30:39 nas-C1-4F-BC syslog: Kernel log daemon terminating.
Jun 18 20:30:40 nas-C1-4F-BC exportfs[2035]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:30:40 nas-C1-4F-BC exportfs[2035]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:30:40 nas-C1-4F-BC exportfs[2035]: /proc/fs/nfs/exports:1: unknown keyword "test-client-(rw"
Jun 18 20:30:40 nas-C1-4F-BC rpc.statd[2043]: Version 1.1.2 Starting
Jun 18 20:31:55 nas-C1-4F-BC syslogd 1.4.1#18: restart.
Jun 18 20:31:57 nas-C1-4F-BC ifplugd(eth0)[2526]: ifplugd 0.28 initializing.
Jun 18 20:31:57 nas-C1-4F-BC ifplugd(eth0)[2526]: Using interface eth0/A0:21:B7:C1:4F:BC with driver <sk98lin> (version: 10.70.1.3 (01))
Jun 18 20:31:57 nas-C1-4F-BC ifplugd(eth0)[2526]: Using detection mode: SIOCETHTOOL
Jun 18 20:31:57 nas-C1-4F-BC ifplugd(eth0)[2526]: Initialization complete, link beat not detected.
Jun 18 20:31:58 nas-C1-4F-BC ifplugd(eth1)[2550]: ifplugd 0.28 initializing.
Jun 18 20:31:58 nas-C1-4F-BC ifplugd(eth1)[2550]: Using interface eth1/A0:21:B7:C1:4F:BD with driver <sk98lin> (version: 10.70.1.3 (01))
Jun 18 20:31:58 nas-C1-4F-BC ifplugd(eth1)[2550]: Using detection mode: SIOCETHTOOL
Jun 18 20:31:58 nas-C1-4F-BC ifplugd(eth1)[2550]: Initialization complete, link beat not detected.
Jun 18 20:32:01 nas-C1-4F-BC RAIDiator: System is up.
Jun 18 20:32:01 nas-C1-4F-BC ifplugd(eth0)[2526]: Link beat detected.
Jun 18 20:32:01 nas-C1-4F-BC ifplugd(eth1)[2550]: Link beat detected.
Jun 18 20:32:02 nas-C1-4F-BC RAIDiator: USB: Waiting for USB storage lock to clear.
Jun 18 20:32:02 nas-C1-4F-BC ifplugd(eth0)[2526]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2804]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2804]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2804]: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_3". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2804]: can't open /var/lib/nfs/etab.tmp for writing
Jun 18 20:32:03 nas-C1-4F-BC RAIDiator: Could not open USB storage remover.
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: Executing '/etc/ifplugd/ifplugd.action eth1 up'.
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: 2794: old priority 0, new priority 0
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: 2811: old priority 0, new priority 0
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2837]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup".
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Assuming default behaviour ('no_subtree_check').
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2837]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media".
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Assuming default behaviour ('no_subtree_check').
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2837]: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_3". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_3".
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Assuming default behaviour ('no_subtree_check').
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2837]: can't open /var/lib/nfs/etab.tmp for writing
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: exportfs: can't open /var/lib/nfs/etab.tmp for writing
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Running ntpd to synchronize clock.
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2855]: chronyd version 1.24 starting
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2854]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup".
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: Assuming default behaviour ('no_subtree_check').
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2854]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media".
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: Assuming default behaviour ('no_subtree_check').
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2854]: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_3". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_3".
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2855]: could not open lockfile /var/run/chronyd.pid for writing
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: Assuming default behaviour ('no_subtree_check').
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:03 nas-C1-4F-BC exportfs[2854]: can't open /var/lib/nfs/etab.tmp for writing
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: exportfs: can't open /var/lib/nfs/etab.tmp for writing
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2855]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2855]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2855]: Linux kernel major=2 minor=6 patch=37
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2855]: calculated_freq_scale=1.00000000 freq_scale=1.00000000
Jun 18 20:32:03 nas-C1-4F-BC ifplugd(eth1)[2550]: client: Running ntpd to synchronize clock.
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2871]: chronyd version 1.24 starting
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2871]: could not open lockfile /var/run/chronyd.pid for writing
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2855]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2871]: Initial txc.tick=10000 txc.freq=-1772892 (-27.05218506) txc.offset=0 => hz=100 shift_hz=7
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2871]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2871]: Linux kernel major=2 minor=6 patch=37
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2871]: calculated_freq_scale=1.00000000 freq_scale=1.00000000
Jun 18 20:32:03 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 20:32:04 nas-C1-4F-BC chronyd[2855]: System's initial offset : 0.051405 seconds slow of true (slew)
Jun 18 20:32:04 nas-C1-4F-BC chronyd[2871]: System's initial offset : 0.052030 seconds slow of true (slew)
Jun 18 20:32:04 nas-C1-4F-BC chronyd[2855]: Could not send to 209.249.181.23 : Bad file descriptor
Jun 18 20:32:04 nas-C1-4F-BC chronyd[2871]: Could not send to 209.249.181.23 : Bad file descriptor
Jun 18 20:32:05 nas-C1-4F-BC exportfs[2941]: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/backup". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:05 nas-C1-4F-BC exportfs[2941]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/media". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:05 nas-C1-4F-BC exportfs[2941]: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_3". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:05 nas-C1-4F-BC exportfs[2941]: /etc/exports [4]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_4". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jun 18 20:32:05 nas-C1-4F-BC exportfs[2941]: can't open /var/lib/nfs/etab.tmp for writing
Jun 18 20:32:05 nas-C1-4F-BC RAIDiator: Could not open USB storage remover.
Jun 18 20:32:05 nas-C1-4F-BC avahi-daemon[2949]: Found user 'avahi' (UID 20) and group 'avahi' (GID 20).
Jun 18 20:32:05 nas-C1-4F-BC avahi-daemon[2949]: Successfully dropped root privileges.
Jun 18 20:32:05 nas-C1-4F-BC avahi-daemon[2949]: avahi-daemon 0.6.23 starting up.
Jun 18 20:32:05 nas-C1-4F-BC avahi-daemon[2949]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jun 18 20:32:05 nas-C1-4F-BC avahi-daemon[2949]: bind(): No space left on device
Jun 18 20:32:05 nas-C1-4F-BC pcscd: pcscdaemon.c:464:main() pcsc-lite 1.3.2 daemon ready.
Jun 18 20:32:05 nas-C1-4F-BC pcscd: winscard_msg_srv.c:133:SHMInitializeCommonSegment() Unable to bind common socket: No space left on device
Jun 18 20:32:05 nas-C1-4F-BC pcscd: pcscdaemon.c:104:SVCServiceRunLoop() Error initializing pcscd.
Jun 18 20:32:05 nas-C1-4F-BC pcscd: pcscdaemon.c:489:at_exit() cleaning /var/run
Jun 18 20:32:05 nas-C1-4F-BC pcscd: pcscdaemon.c:508:clean_temp_files() Cannot unlink /var/run/pcscd.comm: No such file or directory
Jun 18 20:32:05 nas-C1-4F-BC chronyd[2855]: Could not send to 209.249.181.23 : Bad file descriptor
Jun 18 20:32:05 nas-C1-4F-BC chronyd[2871]: Could not send to 209.249.181.23 : Bad file descriptor
Jun 18 20:32:06 nas-C1-4F-BC chronyd[2855]: Could not send to 209.249.181.23 : Bad file descriptor
Jun 18 20:32:06 nas-C1-4F-BC chronyd[2871]: Could not send to 209.249.181.23 : Bad file descriptor
Jun 18 20:32:10 nas-C1-4F-BC ifplugd(eth1)[2550]: client: Starting SABnzbd+ binary newsgrabber:.
Jun 18 20:32:10 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Starting SABnzbd+ binary newsgrabber:.
Jun 18 20:32:11 nas-C1-4F-BC ifplugd(eth1)[2550]: client: Starting SickBeard
Jun 18 20:32:11 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Starting SickBeard
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Exception in thread HTTPServer Thread-1:
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Traceback (most recent call last):
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: File "/usr/lib/python2.6/threading.py", line 532, in __bootstrap_inner
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: self.run()
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: File "/usr/lib/python2.6/threading.py", line 484, in run
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: self.__target(*self.__args, **self.__kwargs)
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: File "/c/.sickbeard/cherrypy/process/servers.py", line 75, in _start_http_thread
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: self.httpserver.start()
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: File "/c/.sickbeard/cherrypy/wsgiserver/__init__.py", line 1634, in start
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: raise socket.error(msg)
Jun 18 20:32:19 nas-C1-4F-BC ifplugd(eth0)[2526]: client: error: [Errno 98] Address already in use
Jun 18 20:32:29 nas-C1-4F-BC ifplugd(eth1)[2550]: client: PID: 3175
Jun 18 20:32:29 nas-C1-4F-BC ifplugd(eth0)[2526]: client: PID: 3176
Jun 18 20:32:30 nas-C1-4F-BC ifplugd(eth0)[2526]: client: Starting plexserver
Jun 18 20:32:30 nas-C1-4F-BC ifplugd(eth1)[2550]: client: Starting plexserver
Jun 18 20:32:30 nas-C1-4F-BC ifplugd(eth1)[2550]: client: start-stop-daemon: Unable to open pidfile `/var/run/plexserver.pid' for writing: No space left on device (No space left on device)
Jun 18 20:32:30 nas-C1-4F-BC ifplugd(eth0)[2526]: client: start-stop-daemon: Unable to open pidfile `/var/run/plexserver.pid' for writing: No space left on device (No space left on device)
Jun 18 20:32:35 nas-C1-4F-BC ifplugd(eth0)[2526]: Program executed successfully.
Jun 18 20:49:11 nas-C1-4F-BC chronyd[2871]: Selected source 209.249.181.23
Jun 18 20:49:11 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 20:53:27 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 21:01:59 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 21:10:31 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 21:19:03 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 21:27:36 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing
Jun 18 21:31:52 nas-C1-4F-BC chronyd[2871]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing

Thomas_xh
Aspirant
Jun 18, 2012
You need reboot the unit to tech support mode and forward the port 23 to internet.
Or please PM the five digit number in the Raidar's.
dsm1212
Apprentice
Jun 18, 2012
Total WAG: I see you are running plex. You didn't delete the link /root/Library did you? If you did, then the next time you start plex it will recreate the plex library on your / partition at this location quickly filling it up. /root/Library needs to be a soft link to /c/.plex/Library.
ReadySECURE
Apprentice
Jun 19, 2012
Qinghong.he wrote:
You need reboot the unit to tech support mode and forward the port 23 to internet.
Or please PM the five digit number in the Raidar's.

Once you have3 completed with Qinghong.he please let us know what was found.
amac27
Aspirant
Jun 19, 2012
I've checked the case and seems that support has already taken care of the issue.

it seems that there are lot of small files that is written in the root folder.
ricster
Aspirant
Jun 20, 2012
HI, thanks all for posting. I've not heard anything back from netgear technical support yet. The last contact was that telnet was open and they would get in touch.

Forum Discussion

Please help. CASE #18791951

22 Replies

Related Content

Access Denied Help Please

Please help MS80 connection issue!!!!

Please Help

EX7000 NEW FIRMWARE HELP ME PLEASE

Help Please: Bridge Mode or Access Point?

NETGEAR Academy

ProSupport for Business