Installing first time firmware version 11

[fvdw]

the only way to see if it has positive influence is using te webinterface to see actual HDD temp

[favroom]

the only way to see if it has positive influence is using te webinterface to see actual HDD temp

Thanks for your reply, but I am not looking for temp data. I am looking for logs that indicate what processes are stopped and why.

Now I need to reboot it by unplugging the mains...

Just want to make sure it's the temperature, not something else...

Ferdinand

[Jocko]

Thanks for your reply, but I am not looking for temp data. I am looking for logs that indicate what processes are stopped and why

If you are not in debug mode, no warning of this type is saved in the logs

[fvdw]

and even so, during boot the logs are cleared, so after boot you can not see what happened

If a program fails it rarely hangs the nwsp2, the program in question will stop responding. There is something that can make it hang (amongst others), which is if you filled up the system partition with file or wrong setting you made.

If the power supply is overheated it might cause a reboot but no a hanging NAS

[favroom]

and even so, during boot the logs are cleared, so after boot you can not see what happened

If a program fails it rarely hangs the nwsp2, the program in question will stop responding. There is something that can make it hang (amongst others), which is if you filled up the system partition with file or wrong setting you made.

If the power supply is overheated it might cause a reboot but no a hanging NAS

Thanks!

So how should I research why my NAS is hanging?

Ferdinand

[Jocko]

So how should I research why my NAS is hanging?

When you write this, you mean : no more any access ? (no ssh access; no samba access; no web access...) or just that the web interface is hanging.

[favroom]

So how should I research why my NAS is hanging?

When you write this, you mean : no more any access ? (no ssh access; no samba access; no web access...) or just that the web interface is hanging.

Indeed, no ssh, no smb, no http...

[fvdw]

sorry but I have a few days leave, so not too much tie to be online, maybe Jocko is able to give some support

[Jocko]

Hi favroom,

Before doing anything, two questions:
- what are the daemons that are enabled (do you use transmissionCli ?)
- do you open some ports on your router to get some WAN access ?

Otherwise to detect what is wrong, you can use this way :
- put the NAS in debug mode
- and when the NAS is hanging, stop it and use the fvdw console to get a telnet access which will allow you to read the log files.

Put the NAS in debug mode.

Save the file attached to the share fvdw and open a Putty window. So run these command to overwrite the file globals.inc in the folder /etc/inc:

Code: Select all

save the current file
cp /etc/inc/globals.inc /etc/inc/globals.inc.org

copy the new file
cp /share/1000/fvdw/globals.inc /etc/inc/globals.inc

In the same time, watch what partition is used (will be useful with the telnet)

Code: Select all

ls /lacie-boot

. So if you have sda1boot then partition sda1 is used (same thing with sda2boot)

So reboot the NAS to put it in debug mode.

Get a telnet access
Install on your PC the fvdw-sl console. http://www.plugout.net/viewtopic.php?f=7&t=1271
When the NAS is hanging, stop it but do not restart it !!!
In the console, select the action 'Standalone kernel, load and start' and follow the help to get the telnet access.

So in the telnet window, mount the partition previously used (sda1 or sda2) and sda5

Code: Select all

cd /tmp
mkdir -m 777 /tmp/sdax
mount /dev/sda? /tmp/sdax  (change sda? by sda1 or sda2)
mkdir -m 777 /tmp/sda5
mount /dev/sda5 /tmp/sda5

Now you can read several log files :
check if there are some errors in boot.log in /tmp/sdax/boot.log (but I don't think so)
and read these logs :
/tmp/sda5/tmp/var/log/messages (or in httpd error_log and access_log; or in protfpd protfpd.log; or in samba log.smbd)

Other idea, in telnet check if you still have enough free space on sda5

Code: Select all

df -h /tmp/sda5

[favroom]

So how should I research why my NAS is hanging?

When you write this, you mean : no more any access ? (no ssh access; no samba access; no web access...) or just that the web interface is hanging.

My problem with the LaCie NAS is still not solved. Strangely it worked ok for a month when I was not at home and used it remotely. But back at home it stops responding. First the web interface and miniDLNA, soon also ssh but it is still pingable...

Any advice on how to attack this problem?

Ferdinand