Page 1 of 1

Lacie 5big Automatically Shutting Down

PostPosted: Fri Mar 16, 2018 10:05 am
by mm3610789
Hi,

I've been using my Lacie 5big Network 2 for a few years now using the Lacie firmware, but had trouble with it shutting down due to overheating the past few weeks. The unit didn't feel any hotter than usual but the log file from within the Lacie web interface said the drives were critically overheated. Replacing the fan didn't make any difference, so I installed the custom firmware from here to see if I could get better info about the actual temperature of the drives. However the NAS is still shutting itself down after about 5-7 minutes after I turn it on. Looking at the drive temperatures just before it turns off, they are < 35 degrees C. Plus I've used the "smartctl -x" command suggested from another thread to look at the temperature history, and the drives aren't overheating there either (the highest I've seen over the past week is 43 degrees). I've tried disabling/enabling the drive temperature guard setting but it doesn't seem to make any difference.

Is there any way to determine why the NAS is switching itself off? Log files, etc.

Thanks,
Mark

Re: Lacie 5big Automatically Shutting Down

PostPosted: Fri Mar 16, 2018 1:20 pm
by fvdw
Hi , what does the disk menu of fvdw-sl web interface specify as disk temperatures. It gives a table of all disk installed with current temp max temp during last boot and max temp ever reached

dikstemp.JPG


Furthermore our temp guard can indeed be disabled. If it is disabled our firmware will not shut down the nas when a disk gets too hot.
If it shuts down in that situation there is something else causing it. Most likely your power supply would be my guess (there is nothing else in the firmware that can trigger a shutdown).

If you connect via ssh you can give on the command line the command
Code: Select all
debugon


After doing that reboot the nas you should be able the read the syslog (file with name messages in /var/log, however if the nas shutdowns and reboots the message file is deleted and renewed.
To look at content on moment of shutdown you will need to run the standalone kernel and look in file /tmp/var/log of partition sda5
To do that you need to mount sda5 after connecting via standalone kernel
Code: Select all
mkdir /sda5
mount /dev/sda5 /sda5
cd /sda5/tmp/var/log
cat messages



Second what happens if you install only 1 disk (in most lefthand slot seen from the back)

Re: Lacie 5big Automatically Shutting Down

PostPosted: Sat Mar 17, 2018 9:21 am
by mm3610789
Hi,

Here are the disk temperatures from the web interface:
https://imgur.com/a/RFukz

I tried booting with only 1 drive in the NAS, but the same thing happens.

Here are the contents of the log file from sda5

Code: Select all
Mar 17 08:50:42 kirkwood-4 syslog.info syslogd started: BusyBox v1.21.0
Mar 17 08:50:50 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/lsscsi -t
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/lsscsi -t
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sda8
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sdb8
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sdc8
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sdd8
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sde8
Mar 17 08:50:51 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:50:52 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l
Mar 17 08:50:52 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sda
Mar 17 08:50:52 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sda
Mar 17 08:50:53 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Mar 17 08:50:53 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/gdisk -l /dev/sda
Mar 17 08:50:53 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/block/sda/sda8/size
Mar 17 08:50:53 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sda8
Mar 17 08:50:53 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sdb
Mar 17 08:50:54 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sdb
Mar 17 08:50:55 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdb
Mar 17 08:50:55 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/gdisk -l /dev/sdb
Mar 17 08:50:55 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/block/sdb/sdb8/size
Mar 17 08:50:55 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sdb8
Mar 17 08:50:55 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sdc
Mar 17 08:50:55 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sdc
Mar 17 08:50:56 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdc
Mar 17 08:50:56 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/gdisk -l /dev/sdc
Mar 17 08:50:56 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/block/sdc/sdc8/size
Mar 17 08:50:56 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sdc8
Mar 17 08:50:56 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sdd
Mar 17 08:50:57 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sdd
Mar 17 08:50:57 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdd
Mar 17 08:50:57 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/gdisk -l /dev/sdd
Mar 17 08:50:57 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/block/sdd/sdd8/size
Mar 17 08:50:57 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sdd8
Mar 17 08:50:57 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sde
Mar 17 08:50:58 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl -a /dev/sde
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sde
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/gdisk -l /dev/sde
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/cat /sys/block/sde/sde8/size
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --examine --brief /dev/sde8
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/file -bs /dev/md0
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/e2label /dev/md0
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdb
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdb
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdc
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdb
Mar 17 08:50:59 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdc
Mar 17 08:51:00 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdd
Mar 17 08:51:00 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Mar 17 08:51:00 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdb
Mar 17 08:51:00 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdc
Mar 17 08:51:00 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdd
Mar 17 08:51:00 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sde
Mar 17 08:51:00 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/blkid -o value -s TYPE /dev/md0
Mar 17 08:51:06 kirkwood-4 local0.warn API[2018/03/17 08:51:06] api_dhcpc.php(25)[1812]: calling /etc/api/api_dhcpc.php deconfig
Mar 17 08:51:06 kirkwood-4 local0.warn API[2018/03/17 08:51:06] dhcpcfunc_daemon_state_change.finc(43)[1812]: dhcpc script got state: deconfig as input
Mar 17 08:51:06 kirkwood-4 local0.warn API[2018/03/17 08:51:06] api_dhcpc.php(57)[1812]: deconfig retcode: 0
Mar 17 08:51:11 kirkwood-4 local0.warn API[2018/03/17 08:51:11] api_dhcpc.php(25)[1815]: calling /etc/api/api_dhcpc.php bound
Mar 17 08:51:11 kirkwood-4 local0.warn API[2018/03/17 08:51:11] dhcpcfunc_daemon_state_change.finc(43)[1815]: dhcpc script got state: bound as input
Mar 17 08:51:11 kirkwood-4 local0.warn API[2018/03/17 08:51:11] api_dhcpc.php(57)[1815]: bound retcode: 0
Mar 17 08:51:13 kirkwood-4 user.info noflushd: noflushd 2.8 fvdw version 18 jun 2015 started
Mar 17 08:51:16 kirkwood-4 auth.info passwd: Password for dummy changed by root
Mar 17 08:51:16 kirkwood-4 local0.warn API[2018/03/17 08:51:16] userfunc_users_commit.finc(137)[1062]: userfunc_users_commit: no smb user for dummy.
Mar 17 08:51:16 kirkwood-4 local0.warn API[2018/03/17 08:51:16] nasapi.inc(36)[1880]: nasapi: lock time = 0
Mar 17 08:51:16 kirkwood-4 local0.warn API[2018/03/17 08:51:16] nasapi.inc(49)[1880]: calling 'mrvlDropbearStart'
Mar 17 08:51:16 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chmod 777 /rw_fs/.ssh
Mar 17 08:51:16 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chmod 700 /rw_fs/.ssh
Mar 17 08:51:16 kirkwood-4 authpriv.warn dropbear[1894]: Failed loading /etc/dropbear/dropbear_dss_host_key
Mar 17 08:51:16 kirkwood-4 authpriv.warn dropbear[1894]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key
Mar 17 08:51:16 kirkwood-4 authpriv.info dropbear[1895]: Running in background
Mar 17 08:51:16 kirkwood-4 authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/ps -ef
Mar 17 08:51:16 kirkwood-4 local0.warn API[2018/03/17 08:51:16] nasapi.inc(467)[1880]: mrvlDropbearStart Return Code: 0
Mar 17 08:51:18 kirkwood-4 local0.warn API[2018/03/17 08:51:18] nasapi.inc(36)[1905]: nasapi: lock time = 0
Mar 17 08:51:18 kirkwood-4 local0.warn API[2018/03/17 08:51:18] nasapi.inc(49)[1905]: calling 'mrvlNfsRestart 0'
Mar 17 08:51:18 kirkwood-4 local0.warn API[2018/03/17 08:51:18] nasapi.inc(467)[1905]: mrvlNfsRestart Return Code:
Mar 17 08:51:18 kirkwood-4 user.info hostd: host daemon V2 started
Mar 17 08:51:18 kirkwood-4 user.info hostd: updating hosts file, next update in 7200 seconds when disk remains active
Mar 17 08:51:18 kirkwood-4 user.info temp-guard: temp-guard vs5may15 daemon started
Mar 17 08:51:18 kirkwood-4 user.info temp-guard: temp-guard: temperature limit = 55 oC
Mar 17 08:51:18 kirkwood-4 user.info temp-guard: temp-guard: disks installed: sda=1 sdb=1 sdc=1 sdd=1 sde=1
Mar 17 08:51:30 kirkwood-4 daemon.info init: starting pid 2303, tty '': '/bin/sh'
Mar 17 08:51:37 kirkwood-4 local0.warn API[2018/03/17 08:51:37] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:51:37 kirkwood-4 local0.warn API[2018/03/17 08:51:37] nasapi.inc(49)[2304]: calling 'mrvlGetLanguage'
Mar 17 08:51:37 kirkwood-4 local0.warn API[2018/03/17 08:51:37] nasapi.inc(467)[2304]: mrvlGetLanguage Return Code: en
Mar 17 08:51:38 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -ef
Mar 17 08:51:39 kirkwood-4 local0.warn API[2018/03/17 08:51:39] nasapi.inc(36)[1858]: nasapi: lock time = 0
Mar 17 08:51:39 kirkwood-4 local0.warn API[2018/03/17 08:51:39] nasapi.inc(49)[1858]: calling 'mrvlGetSystemData'
Mar 17 08:51:39 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -eo cmd
Mar 17 08:51:39 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/df
Mar 17 08:51:39 kirkwood-4 local0.warn API[2018/03/17 08:51:39] nasapi.inc(464)[1858]: mrvlGetSystemData Return Code: Array():system => Array()...
Mar 17 08:51:39 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/uname -rv
Mar 17 08:51:39 kirkwood-4 local0.warn API[2018/03/17 08:51:39] nasapi.inc(36)[1858]: nasapi: lock time = 0
Mar 17 08:51:39 kirkwood-4 local0.warn API[2018/03/17 08:51:39] nasapi.inc(49)[1858]: calling 'mrvlGetDateTimeStr'
Mar 17 08:51:39 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/date +%B %e, %Y %r
Mar 17 08:51:39 kirkwood-4 local0.warn API[2018/03/17 08:51:39] nasapi.inc(467)[1858]: mrvlGetDateTimeStr Return Code: March 17, 2018 08:51:39 AM
Mar 17 08:51:39 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/bin/test -f disk.image.1
Mar 17 08:51:39 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -ef
Mar 17 08:51:46 kirkwood-4 user.info discoverd: fvdw-sl discoverd vs8sep15 daemon started
Mar 17 08:51:46 kirkwood-4 user.info discoverd: discoverd uses ip: 192.168.0.50 and mac address 00d04b92eec7
Mar 17 08:54:53 kirkwood-4 local0.warn API[2018/03/17 08:54:53] nasapi.inc(36)[1858]: nasapi: lock time = 0
Mar 17 08:54:54 kirkwood-4 local0.warn API[2018/03/17 08:54:54] nasapi.inc(49)[1858]: calling 'mrvlGetLanguage'
Mar 17 08:54:54 kirkwood-4 local0.warn API[2018/03/17 08:54:54] nasapi.inc(467)[1858]: mrvlGetLanguage Return Code: en
Mar 17 08:54:54 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -ef
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(49)[2304]: calling 'mrvlGetTempGuardStatus'
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(464)[2304]: mrvlGetTempGuardStatus Return Code: Array():enable => 1...
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(49)[2304]: calling 'mrvlGetTempGuardCurrentStatus no'
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(464)[2304]: mrvlGetTempGuardCurrentStatus Return Code: Array():enable => 1...
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/hdstatus-spd
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(49)[2304]: calling 'mrvlGetTempGuardStatus'
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(464)[2304]: mrvlGetTempGuardStatus Return Code: Array():enable => 1...
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(49)[2304]: calling 'mrvlGetHddPowerManage sda'
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/cat /sys/block/sda/device/vendor
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/cat /sys/block/sda/device/model
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(464)[2304]: mrvlGetHddPowerManage Return Code: Array():inactivityperiod => 00:30...
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(49)[2304]: calling 'mrvlGetCurrentHddPowerManage sda'
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -o %a
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(464)[2304]: mrvlGetCurrentHddPowerManage Return Code: Array():enable => 1...
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(49)[2304]: calling 'mrvlGetDisk high all'
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sda
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdb
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdc
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdd
Mar 17 08:54:59 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sde
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(464)[2304]: mrvlGetDisk Return Code: Array():0 => Array()...
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(36)[2304]: nasapi: lock time = 0
Mar 17 08:54:59 kirkwood-4 local0.warn API[2018/03/17 08:54:59] nasapi.inc(49)[2304]: calling 'mrvlGetVolume high all'
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/df
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/sbin/mdadm --detail /dev/md0
Mar 17 08:55:00 kirkwood-4 local0.warn API[2018/03/17 08:55:00] nasapi.inc(464)[2304]: mrvlGetVolume Return Code: Array():0 => Array()...
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/blkid -o value -s TYPE /dev/md0
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/blkid -o value -s TYPE /dev/md0
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/blkid -o value -s TYPE /dev/md0
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/blkid -o value -s TYPE /dev/md0
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/blkid -o value -s TYPE /dev/md0
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/hdstatus-spd sda
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/hdstatus-spd sdb
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/hdstatus-spd sdc
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/hdstatus-spd sdd
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/sbin/hdstatus-spd sde
Mar 17 08:55:00 kirkwood-4 authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/ps -ef


If the times are accurate, the NAS automatically shut down about 2 minutes after the final entry.
The NAS also shuts down about after 8-10 minutes when booting from the standalone kernel.

Re: Lacie 5big Automatically Shutting Down

PostPosted: Sat Mar 17, 2018 10:14 am
by fvdw
It is not the firmware that shuts it down. Proof is that it also happens when standalone kernel is running.

What can cause it?
An interupt of the power supply?
Yes possible, how does it shutdown ? Suddenly all power cut, light on power supply out? And how how does it reboot? By itself or after pushing a button or taken out power supply and reconnecting?

Something in flash memory?
Yes possible if it has same feauture as network space 2 then there is something in flash memory that might cause this. In the lacie firmware there is a routine that set some bytes in flash nvram and influences the boot behavior or lets the nas shutdown and start up at specific times.
What you could try as first step is using the shutdown command in the fvdw-sl firmware to shutdown the nas and powering it up after shutdown is complete by pressing the front button. The fvdw-sl firmware has also the a binary from lacie inside and using shutdown via webinterface set a specific sleep command which might reset the flash. If this doesn't solve it I need to check my notes on how we can reset this part of flash memory

Re: Lacie 5big Automatically Shutting Down

PostPosted: Mon Mar 19, 2018 5:16 am
by mm3610789
When it shut downs (about 10 minutes after it is turned on) it just turns off suddenly and all lights go out. It never restarts or boots up again on its own. To get it going again I need to move the power switch to the off position, wait a few seconds, and then switch it to on. It's not a problem with the power supply brick because I borrowed one from a friend who has the same model NAS and it makes no difference, the NAS still turns off.

I've tried using the shutdown and reboot commands from within the web interface but the NAS still turns off when it is next powered on.

I'm guessing that there must be some kind of hardware fault within the NAS unit itself.

Re: Lacie 5big Automatically Shutting Down

PostPosted: Mon Mar 19, 2018 3:48 pm
by fvdw
before jumping to conclusions let see what is configuration of nvram sleep

Connect with ssh and give these commands and post output (be careful with these commands as wrong settings may make the nas inaccessible)
Code: Select all
sleepmode_config --is-enabled

response should be: no

Code: Select all
sleepmode_config --is-enabled-wol

should be: yes

Code: Select all
sleepmode_config --is-enabled-rtc

should be: no

Code: Select all
sleepmode_config --is-enabled-scheduling

should be: yes

Code: Select all
sleepmode_config --is-enabled-button

should be: yes

Code: Select all
sleepmode_config --read-schedule

response should be : +:+:+:+:+:+

Re: Lacie 5big Automatically Shutting Down

PostPosted: Mon Mar 19, 2018 11:26 pm
by mm3610789
Code: Select all
root@NAS.local /$ sleepmode_config --is-enabled
no
root@NAS.local /$ sleepmode_config --is-enabled-wol
yes
root@NAS.local /$ sleepmode_config --is-enabled-rtc
no
root@NAS.local /$ sleepmode_config --is-enabled-scheduling
yes
root@NAS.local /$ sleepmode_config --is-enabled-button
yes
root@NAS.local /$ sleepmode_config --read-schedule
+:+:+:+:+:+

Re: Lacie 5big Automatically Shutting Down

PostPosted: Tue Mar 20, 2018 10:16 am
by fvdw
so the standard setting, so this is also not the cause.
In my notes made 7 years ago on study of sleepmode-config I marked that sleepmode_config is used to set some bits in eeprom. The content of that eeprom is available in userland via /sys/bus/i2c/devices/0-0050/eeprom
However the way it is used is according my findings that uboot and lacie firmware read the content of the eeprom and act accordingly.
For instance if uboot reads the button setting and acts accordingly the way it will react to pressing a button, the kernel will read early in boot proces if the WOL bit is sets it holds boot and wait until a magic packet is received to power up the nas completely and load all services.
So this eeprom doesn't run a program that can shut down the nas. There must ne something else (hardware issue) that cuts power. Maybe one of the capacitors on the mainboard has gone bad and needs replacement. You could inspect it and replace the ones that are leaking or show damage.
Further you could hook up the serial port on the mainboard to see what's happening when it powers off. You could also use the uboot console of the fvdw-sl console to see what is send to the serial port until power is cut.
For that you need to choose option uboot console in fvdw-sl console and then load the standalone kernel using commands on the uboot prompt.
Besides choosing uboot console also start tftp server from the fvdw-sl console
When uboot console window pops up give commands
Code: Select all
marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/

(leave ipaddr and serverip as it is in this command do not replace them with actual ips !)
then give command
Code: Select all
marvell> tftpboot 0x800000 UIMAGE-3142-KIRKWOOD-158-standalone

then
Code: Select all
bootm

and wait the uboot console will remain open and display at a certain moment the output normally sent to serial output.