General NAS-Central Forums

Welcome to the NAS community
It is currently Wed Nov 22, 2017 9:04 am

All times are UTC




Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Tue Aug 09, 2016 12:47 pm 
Offline

Joined: Sat Jun 08, 2013 9:02 am
Posts: 116
Greetings.

So today at 01:30 i noticed that my NAS restarting continuously without end. Pulled the plug and hooked up the TTL to USB adapter to my PC. I got some worrying output at stage 2:
Code:
*** Stage 2: Prepare the root file s˙˙?**+
mknod: /dev/gpio: File exists
Initialize fan control
Wrote to  0x90470058: 0x05000000
Wrote to  0x90458000: 0x80000001
Wrote to  0x90458028: 0x80001388
Mount system partition...
crw-rw----    1 root     root  ŕ‚{«Â[Ő±12  2012 /dev/ubi_ctrl
sda
sdb
checking sda
Trying to mount0/dev/sda1
mount: unknown filesystem type 'linux_raid_member'
Fail to mount /dev/sda1
checking sdb
Trying to mount /dev/sdb1
mount: unknown filesystem type 'linux_raid_member'
Fail to mount /dev/sţ[   22.705455] UBI: attaching mtd7 to ubi7
[   23.434253] UBI: scanning is finished
[   23.450256_ UBI: attached mtd7 (name "rootfs2", size 110 MiB) to ubi7
[   23.456740] UBI: PEB size: 131072 â˙BŠňĂZĄ   Ą, |EB size: 12697¶ bytes
[   23.463548]0UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[   23.470287] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[   23.477187] UBI: good PEBs: 880, bad PEBs: 0, corrupted PEBs: 0
[   23.4>3122] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[   23.490282] UBI: max/mean erase>counter: 2/1, WL threshold: 4096, image sequence number:81770726842
[   23.´ęUBI: available PEBs: 10, total reserved<PEĂs: 870, PEBs reserved for bat PEB handling: 40
[   23.508618] UBI: background thread "ubi_bgt7d" started, PID 928
UBI device number 7, total 880 LEBs (111738880 bytes, 106.6 MiB), available 10 LEBs (1269760 bytes, 1.2 MiB), LEB size 126976 bytes (124.0 KiB)
[   23.670225] UBIFS: mounted UBI device 7, volume 0, name "ubi_rootfs2"
[   23.676704] UBIFS: mounted read-only
[   23.680291] UBIFS: file system size:   103612416 bytes (101184 KiB, 98 MiB, 816 LEBs)
[   23.688152] UBIFS: journal size:       5206016 bytes (5084 KiB, 4 MiB, 41 LEBs)
[   23.695482] UBIFS: media format:       w4/r0 (lat.şŃ/r0)
[   23.701338] UBIFS: default {ďmpressor: lzo
[   23.705444] UBIFS: ruserved for root:  4893869 bytes (4779 KiB)
/sbin/mdadm --assemble /dev/md0 --uuéţ‚2Á{d:21bd2b6b:7e0db729:d1be1e17 --force?/dev/sda1 /dev/sdb1
[   23.910936] md: md0 stopped.
[   23.917002] md: bind<sdb1>
[   23.920259] md: bind<sda1>
[   23.927536] bio: create slab <bio-1> at 1
[   23.931752] md/raid1:md0: active with 2 out of 4 mirrors
[   23.937191] md0: detected capů˙˙ˇ…ąÝ•from 0 to 2045706240
mdatm: /dev/md0 has been started with 2 drives (out of 4).
/sbin/mdadm --assemble /dev/md1 --uuid=937d7b78:5834eaab:83d74ccf:d964bcf6 --force /dev/sda2 /dev/sdb2
[   23.964842] md: md1 stopped.
[   23.981106] md: bind<sdb2>
[   23.986377] md: bind<sda2>
[   23.99289:] md/raid1:md1: active with 2 out of 4 mirrors
[   23.998331] md1: detected capacity change from 0 to 2046754816
mdadm: /dev/md1 has been started with 2 drives (out of 4).
[   24.187578]  md1: unknown partition table
[   24.252082] Adding 1998780k swap on /dev/md1.  Priority:-1 extents:1 across:1998780k
[   24.276603]  md0: unknown partition table
[   24.396140] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
0
Boot from disk
[   26.845828] PHY: comcerto-0:04 - Link is Up - 1000/Full
[   26.851101] pfe_eth_adjust_link: PHY: comcerto-0:04, phy->link: 1
[   26.875822] PHY: comcerto-0:06 - Link is Up - 1000/Full
[   26.881092] pfe_eth_adjust_link: PHY: comcerto-0:06, phy->link: 1
Checksum of sysdisk.img : 23dc7628c8770dff74d80b8d70facf46
Checksum from8INFO  : 23dc7628c8770dff74d80b8d70facf46
Checksum pass!
[   28.095694] EXT4-fs (md0): re-mounted. Opts: (nuűMount system disk image ...
[   28.119692] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
[   28.130385] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
mount: mount point /usr/local/var does not exist
[   28.331147] UBI: attaching mtd3 to ubi3
[   28.401351] UBI:0scanning is finished
[   28.416235] UBI: attached mtd3 (name "conţýšµé•10 MiB) to ubi3
[   28.422530] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[   28.429356] UBI: méŞůt sizes: 2>48/2048, sub-page size 2048
[   28.436098] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[   28.442996] UBI: good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[   28.448854] UBI: user volume: 1, interoal volumes: 1, max. volumes count: 128
[   28.456014] UBI: max/mean erase counter: 31/ý˙
˘ˇ˙éř096, imu啁number: 3690207712
[   28.465260] UBI: available PEBs: 0, total reserved PEBs: 80, PEÂs reserved for bad PEB handling: 40
[   28.474346] UBI: background thread "ubi_bgt3d" started, PID 1126
UBI device number 3, total 80 LEBs (10158080 bytes, 9.7 MiB), available 0 LEBsŕŃ•íĄ, LEB size 126976 bytes 0?KiB)í
[   28.632910] UBIFS: mounted UBI device 3, volume 0, name "ubi_config"
[   28.639303] UBIFS: file system size:   3428352 bytes (3348 KiB, 3 MiB, 27 LEBs)
[   28.646649] UBIFS: journal size:       1015809 bytes (992 KiB, 0 MiB, 6 LEBs)
[   28.653797] UBIFS: media format: >     w4/r0 (latest is w4/r0)
[   2ř˙˙Ş‚ęWBIFS: default compressor: lzo
[ > 28.663757] UBIFS: reserved for root:  161928 bytes (158 KiB)
mount /etc/zyxel successfully and /etc/zyxel/conf exist, nothing special.
Start rcS2 of ZyXEL8style
*** Stage 3: Start services on HDD ***
[   28.876249] NTFS driver 2.1.30 [Flags: R/O MODULE].
[   28.894933] tntfs: module license 'Commercial. For supporil nwfs-support@tuxera.com.' taints kernel.
[   28.904583] Disabling lock debugging due to kernel taint
[   28.917722] Tuxera NTFS driver 3014.4.29 [Flags: R/W MODULE].
[   28.936269] PPP generic driver version 2.ô[   28.960592] PPP MPPE Compression module registered
[   28.982837] PPP Deflate Compression module registered
[   28.996789] NET: Registered protocol family 24
[   29.013639] PPP BSD Compression module registered
[   29.329872] elp_register_ocf: Comcerto 2000 ELP Crypto Ofć˙_Engine
[   29.336300] m86xxx_elp: Registering 0keţi"•Íaes md5 sha1 sha2_256 sha2_384 sha2_512 sha256_hmac null
sda
sdb
checking sda
Trying to mount /dev/sda1
mount: unknown filesystem type 'linux_raid_member'
Fail to mount /dev/sda1
ˇ•Ť­Ąąg sdb
Trying to mount /dev/sdb1
mount: unknown filesystem type 'linux_raid_member'
Fail to mount /dev/sdb1
Press ENTQ*˘˝continue...
Starting zylogd...
 zylog starts.
Starting uamd...
[   34.261031] md: md2 stopped.
[   34.273469] md: bind<sdb3>
[ üj˙Ąą‘ńsda3>
[   34.283547] md/raid1:md2: active with 2 out of 2 mirrors
[   34.288994] md2: detected capacity change from 0 to 3996556197888
[8  34.420875]  md2: unknown partition>wable
[   35.125786] EXT4-fs (md2): recovery complete
[   35.130373] EXT4-fs (md2): mounted filesystem with ordered data mode. Opts: usrquota,data=ordered,barrier=1
Stating to mount web_cache for webframwork...
Starting ZySH daemon and client...
Start NAS540 system daemon....
 Start ZySH daemon
zyshd: version 2.0.0 (build: 10:56:56 Jun 14 2016)
% zylog init start
cat: can't open '/var/run/syslog-ng.pid': No such file or directory
Try to KILL SIGHUP to syslog-ng: pid=0
syslog-ng not running, start /usr/sbin/syslog-ng
Aug  8 22:18:20 (none) syslog-ng[1678]: syslog-ng starting up; version='2.0.10'
zyio_open_config success. (/etc/__system_default.xml. 0)
zyio_open_config success. (/etc/zyxel/conf/__system_default_device_ha.xml, 0)
/usr/sbin/zic -d /etc /var/zyxzone_rule
/bin/ln -s -f /etc/MyZone /etc/localtime
/bin/hostname NAS540

Usage:
 umount [-hV]
 umount -a [options]
 umount [options] <source> | Ľd˙osy>Í

Options:
 -a, --all               unmount alě filesystems
 -A, --all-targets       unmount all mountpoints for the given device in the
              8            current namespace
 -c, --no-canonicalize   don't canonicalize paths
 -d, --detach-loop       if mounted loop<device, also free this loop device
     --fake              dry run; skip the umount(2) syscall
 -f, --force             force unmount (in case of an unreachable NFS syóHîkJ± --internal-only     don't call the umount.<type> helpers
 -n, --no-mtab           don't write to /etc/mtab
 -l, --lazy >            detach the filesystem now, clean up things later
 -O, --test-opts <list> <limit the set of filesystems (use with -a)
 -R, --recursive         recursively unmount a target with all its children
 -r, --read-only         in case unmounting fails, try to remount read-only
 -t, --types <list>      limit the set of?system types
 -v, --verbose          řsyy8what is being donĺ

 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more details see umouaçý§H޵˝ŐąŃů[-hV] uoounô -}>[options]
 umount [options] <source> | <directory>

Options:
 -a, --all               unmount all filesystems
 -A, --all-targets       unmount all mou~tpoints for the given device in the
                           cýţ˙r嵕Íá…Ť•5
 -c, --no-canonicalize   don't canonicalize paths
 -d, --detach-loop       if mounted loop device, also free this loop device
     --fake              dry run; skip the umount(2) syscall
 -f, --force             force unmount (in case of an unreachable NFS system)
 -i, --internal-only     don't call the umount.<type> helers
 -n, --no-mtab           don't write to /etc/mtab
 -l, --lazy              detach the filesystem now, clean uąťĎůlyter
 -O, --test-opts <list>  limit the set of filesystems (use with -a)
 -R, --recursive   <Ľ    recursively unmount a target with all its children
 -r, --read-only         in case unmounting fails, try to remount read-only
 -t, --types <list>      limit the set of filesystem types
 -v, --verbose           say what is being done

 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more dýsue>umount(8).
find: /home/shares: No such file or directory
BusyBox v1.19.4 (2016-06-14 10:55:13°CST) multi-call binary.

Usage: rmdir [OPTIONS] DIRECTORY...

Init SMB DB aăéř˙an't remove '/var/log/samba/smb.db': No such file or directory

(I can send the full log but only in PM.)

I taken out one of the disks and mounted it under linux with mdadm. The partitions were there and since i use RAID1 i was able to start up the array with this single disc. Everything seemed to be fine so i put it back. Then came the surprise, it booted up fine but i had to start a repair and its now re-syncing...

Have someone any idea what can cause this?

Thanks in advance for the help :) .

_________________
Zyxel NSA325 [4.71(AAAJ.0) + FFP, retired]
Zyxel NAS540 [V5.20(AATB.0)]


Top
 Profile  
 
PostPosted: Wed Aug 10, 2016 6:31 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6073
Which worrying output do you mean? (Apart from the damaged characters, here and there.) It doesn't look very different from this bootlog.

The reboot isn't logged. Doesn't the log give a reason for that reboot?


Top
 Profile  
 
PostPosted: Wed Aug 10, 2016 10:51 pm 
Offline

Joined: Sat Jun 08, 2013 9:02 am
Posts: 116
This part:
Code:
checking sda
Trying to mount /dev/sda1
mount: unknown filesystem type 'linux_raid_member'
Fail to mount /dev/sda1
ˇ•Ť­Ąąg sdb
Trying to mount /dev/sdb1
mount: unknown filesystem type 'linux_raid_member'
Fail to mount /dev/sdb1


After this i saw several errors that stating a given path/file dose not exist so i would bet this was the problem. Im still nut sure if this is a good idea but here iss the full log:
https://dl.dropboxusercontent.com/u/120 ... /putty.log

/EDIT
I just did some digging in my syslog server but the only thing i can see there is the weekly scheduled restart...

_________________
Zyxel NSA325 [4.71(AAAJ.0) + FFP, retired]
Zyxel NAS540 [V5.20(AATB.0)]


Top
 Profile  
 
PostPosted: Thu Aug 11, 2016 6:34 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6073
jagdtigger wrote:
This part:
That is normal. It's the firmware searching for usb_key_function sticks. On a 500 it does so by trying to mount all first partition on all disks (and usb sticks). /dev/sda1 and /dev/sda2 cannot be mounted as they are both member of a raid array.

This seems a 'normal' reboot. It starts all packages, and directly hereafter it seems to reboot. I believe the line 'killall: zyxel_device_register: no process killed' after '---> start "myZyXELcloud-Agent" successfully.' is part of the shutdown.

On the 300 series there was a long-standing bug where the auto-shutdown caused a bootloop. For some reason the condition where it should shutdown was always true directly after boot. Maybe because the clock didn't have time to synchronize itself. Maybe this was the same bug on your weekly reboot?

Because of this bug the 'Shutdown Daemon' in 'Tweaks' refuses to shutdown in the first half hour. Just to avoid it.

If this is a firmware bug, you can work around it by using a cronjob which looks at the output of 'uptime' before rebooting the box.


Top
 Profile  
 
PostPosted: Thu Aug 11, 2016 10:31 am 
Offline

Joined: Sat Jun 08, 2013 9:02 am
Posts: 116
Dont know if its a bug or not, it never done it before... I also dont know the clock is working in this thing but it was doing it even on the next day when i tried to switch it on after it was pulled out for the whole night...

_________________
Zyxel NSA325 [4.71(AAAJ.0) + FFP, retired]
Zyxel NAS540 [V5.20(AATB.0)]


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 13 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group