Finally NAS!

Matt

No, it wasn't reserved on the router (I can't even log into it, it's a managed service now). I did wonder if something else was taking the IP address, but it's not changed since I set it to DHCP either. I've also got the CCTV camera set on static configured on the device, and that has been fine since it was set up.

Sent from my Desire HD using Tapatalk

Sjdickso

Matt said:
No, it wasn't reserved on the router (I can't even log into it, it's a managed service now). I did wonder if something else was taking the IP address, but it's not changed since I set it to DHCP either. I've also got the CCTV camera set on static configured on the device, and that has been fine since it was set up.

Sent from my Desire HD using Tapatalk

It does sound like a IP conflict, oh well least it works fine on DHCP.

Matt

Yeah, that is why I was thinking it was actually something on the NAS, as I could ping it, and I could see the LAN port flash is it was responding, but was just inactive for everything else (I could also see the switch port active).

When I had the Netgear router set up, I'd assigned the IP on the router to the MAC, and not the other way round like it was this time.

Matt

Still having issues with the NAS becoming unresponsive. Trying to trouble shoot it now

Matt

Managed to catch this as it goes un-responsive

root@nas:/# uptime
 22:43:29 up 1 day, 12:07,  1 user,  load average: 5.68, 5.28, 4.54
root@nas:/# 
root@nas:/# 
root@nas:/# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 Mar18 ?        00:00:02 init [2]  
root         2     0  0 Mar18 ?        00:00:00 [kthreadd]
root         3     2  0 Mar18 ?        00:00:04 [ksoftirqd/0]
root         4     2  0 Mar18 ?        00:00:00 [events/0]
root         5     2  0 Mar18 ?        00:00:00 [khelper]
root        43     2  0 Mar18 ?        00:00:00 [kblockd/0]
root        46     2  0 Mar18 ?        00:00:00 [khubd]
root        61     2  0 Mar18 ?        00:00:00 [crypto]
root        62     2  0 Mar18 ?        00:00:00 [crypto_ret]
root        67     2  0 Mar18 ?        00:00:00 [pdflush]
root        68     2  0 Mar18 ?        00:00:01 [pdflush]
root        70     2  0 Mar18 ?        00:00:00 [aio/0]
root        71     2  0 Mar18 ?        00:00:00 [cifsoplockd]
root        72     2  0 Mar18 ?        00:00:00 [cifsdnotifyd]
root       231     2  0 Mar18 ?        00:00:00 [scsi_eh_0]
root       232     2  0 Mar18 ?        00:00:00 [scsi_eh_1]
root       251     2  0 Mar18 ?        00:00:00 [mtdblockd]
root       252     2  0 Mar18 ?        00:00:00 [nftld]
root       286     2  0 Mar18 ?        00:00:00 [kcryptd/0]
root       325     2  0 Mar18 ?        00:00:00 [md0_raid1]
root       334     2  0 Mar18 ?        00:00:04 [loop0]
root       337     2  0 Mar18 ?        00:00:00 [loop1]
root       348     2  0 Mar18 ?        00:00:00 [loop2]
root       496     2  0 Mar18 ?        00:00:00 [krfcommd]
root       502     2  0 Mar18 ?        00:00:01 [xfslogd/0]
root       507     2  0 Mar18 ?        00:00:00 [xfsdatad/0]
root       677     1  0 Mar18 ?        00:00:00 logsave -s /var/log/fsck/checkfs fsck -C -R -A -a
root       789     1  0 Mar18 ?        00:00:00 /usr/sbin/rsyslogd -c3 -f /etc/rsyslog.conf
root       833     1  0 Mar18 ?        00:00:00 /sbin/netplugd -c /etc/network/netplugd.conf -p /tmp/netplugd.pid
nobody     924     1  0 Mar18 ?        00:00:00 /usr/sbin/mdnsd
root       926     1  0 Mar18 ?        00:00:00 /bin/hostnamed
root       933     1  0 Mar18 ?        00:00:00 /sbin/executord -c /etc/sohoConfig.xml
root       951     1  0 Mar18 ?        00:00:00 /usr/sbin/cron
root       970     1  0 Mar18 ?        00:00:00 /usr/sbin/cupsd
root       972   933  0 Mar18 ?        00:00:00 /usr/bin/dbus-daemon --nofork --system
root       974   933  0 Mar18 ?        00:00:00 /usr/sbin/discoverd
root       998     1  0 Mar18 ttyS0    00:00:00 /sbin/getty -L ttyS0 115200 vt100
root       999   933  0 Mar18 ?        00:00:00 /usr/sbin/upnpd -webdir /etc/upnpd/web
nobody    1001   933  0 Mar18 ?        00:00:00 /usr/sbin/mdnsd -debug
root      1002   933  0 Mar18 ?        00:00:00 /usr/sbin/sshd -D

Load is VERY high, but it then died half was through running the ps -ef command.

Sjdickso

Are you doing anything spacific when it dies? I presume after a reset it fires back to life?

Matt

Sjdickso said:
Are you doing anything spacific when it dies? I presume after a reset it fires back to life?

Yeah, it fires back up fine mate.

I did notice that when it died last night, my laptop was trying to write some files to it (it was active mirroring of my documents to the NAS).

I've disabled a load of stuff to try and keep it just as a file server.

Matt

Another problem is that is clears all the logs when it gets reloaded, so I can't see what was happening as it died.

Sjdickso

Its a shame the logs clear but i woudl expect that to happen after a hard power off, are you using any 3rd party software to sync your docs?

Matt

Software I'm using is what came with the NAS. I'm tempted to take everything off it, and see if there is a way to do a full factory reset on it.

Sjdickso

Is there any firmware updates for the unit? I would be tempted not to use the sync software which came with it also as a test.

Matt

No, it's running the latest firmware. I'm going to disable the sync software, and try and have another play about with it tonight

Matt

Been looking over the stuff I've done to the NAS since I set it up to work with my CCTV camera.

~~_9th December, I enabled CRON to run, when it wasn't even started, so I could manually archive my CCTV images.~~

http://www.matt1206.co.uk/forum/index.php/topic,38.0.html

It looks like this is a sym link back to /etc/init.d/cron

lrwxrwxrwx  1 root root  14 Aug 27  2010 S89cron -> ../init.d/cron

However, I think this may be the problem with the NAS.

I've stopped cron from running

root@nas:/# /etc/init.d/cron stop 
Running file /etc/init.d/cron
Stopping periodic command scheduler: crond.
root@nas:/#

I've also deleted the S89cron file to stop it from starting on bootup

root@nas:/etc/rc2.d# ls
README      S12dbus          S20postfix        S23ntp      S50samba  S59hostnamed  S89cron  S99rc.local  S99stop-bootlogd
S10rsyslog  S14avahi-daemon  S20smartmontools  S41netplugd  S50sshd  S60executord  S99cups  S99rmnologin
root@nas:/etc/rc2.d# rm S89cron
root@nas:/etc/rc2.d#

Will see how it goes!

Matt

Actually, it was back in October I set the cron stuff up:
CCTV

Matt

Well since turning cron off, the NAS is actually running a lot quieter, and not constantly doing things! Still up and appears to be stable.

Sjdickso

Thats good news, hopefully that has fixed it.

Matt

Yeah, I do hope so. It can't be doing it any good having to just pull the power on it.

Sjdickso

No it won't, one easy way to kill a disk.

Matt

Sjdickso said:
No it won't, one easy way to kill a disk.

or two! It's running Raid 1, so won't be doing the raid any good either

Matt

Touch wood! It's been stable for over a week now

root@nas:/# uptime
 08:38:53 up 9 days, 10:00,  1 user,  load average: 0.24, 0.20, 0.18
root@nas:/#

« Previous Page Next Page »