Re: Debian on NSA310S? September 12, 2015 03:49AM |
Registered: 9 years ago Posts: 118 |
Begin: Checking root file system ... fsck from util-linux 2.25.2 fsck: error 2 (No such file or directory) while executing fsck.ext3 for /dev/sda1 fsck exited with status code 8 done. Warning: File system check failed but did not detect errors [ 9.607328] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) done.
tar -xjf linux-4.2.0-kirkwood-tld-1-bodhi.tar.bz2 dpkg -i linux-image-4.2.0-kirkwood-tld-1_1.0_armel.deb mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.2.0-kirkwood-tld-1 -d vmlinuz-4.2.0-kirkwood-tld-1 uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.2.0-kirkwood-tld-1 -d initrd.img-4.2.0-kirkwood-tld-1 uInitrd
[ 16.029776] NET: Registered protocol family 10 [ 16.145141] mv643xx_eth: Set the PHY back to auto-negotiation mode [ 16.151461] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/5c:f4:ab:df:07:2b Sending on LPF/eth0/5c:f4:ab:df:07:2b Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 Unable to set up timer: unexpected error If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. Failed to bring up eth0. done. [ ok ] Starting rpcbind daemon.... [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Cleaning up temporary files.... [FAIL] startpar: service(s) returned failure: nfs-common ... failed! INIT: Entering runlevel: 2 [ 17.824301] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [ 17.834162] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [info] Using makefile-style concurrent boot in runlevel 2. [....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd... 1205 (syslogd) . ok [ ok ] Starting system message bus: dbus. [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. [warn] Not starting NFS kernel daemon: no exports. ... (warning). [ ok ] Starting NTP server: ntpd. [ ok ] Starting OpenBSD Secure Shell server: sshd. [....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd... 1206 (klogd) . ok [FAIL] startpar: service(s) returned failure: nfs-common ... failed!
USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found 13455 bytes read in 215 ms (60.5 KiB/s) 3147200 bytes read in 330 ms (9.1 MiB/s) 7148518 bytes read in 412 ms (16.5 MiB/s)
[ 15.670849] mv643xx_eth: Set the PHY back to auto-negotiation mode [ 16.107655] NET: Registered protocol family 10 [ 16.113318] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [....] Configuring network interfaces...Aborted done. [ ok ] Starting rpcbind daemon.... [ 17.447037] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [ 17.456826] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Cleaning up temporary files.... [FAIL] startpar: service(s) returned failure: nfs-common ... failed! INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd... 1254 (syslogd) . ok [ ok ] Starting system message bus: dbus. [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. [warn] Not starting NFS kernel daemon: no exports. ... (warning). [ ok ] Starting NTP server: ntpd. [ ok ] Starting OpenBSD Secure Shell server: sshd. [....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd... 1251 (klogd) . ok [FAIL] startpar: service(s) returned failure: nfs-common ... failed!
root@debian:~# ping www.google.com PING www.google.com (62.231.75.216) 56(84) bytes of data. 64 bytes from cache.google.com (62.231.75.216): icmp_seq=1 ttl=60 time=4.34 ms 64 bytes from cache.google.com (62.231.75.216): icmp_seq=2 ttl=60 time=4.38 ms ^C --- www.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 4.347/4.367/4.387/0.020 ms
root@debian:~# date Mon Nov 27 12:15:32 EET 1933but it's fine when i boot with 3.18.5 kernel. Maybe the culprit is this? (from 4.2.0 bootlog with static ip):
[ 11.684817] rtc rtc0: __rtc_set_alarm: err=-22
Re: Debian on NSA310S? September 12, 2015 04:26AM |
Admin Registered: 13 years ago Posts: 19,107 |
> Begin: Checking root file system ... fsck from > util-linux 2.25.2 fsck: error 2 (No such file or > directory) while executing fsck.ext3 for /dev/sda1 > fsck exited with status code 8 > done. > Warning: File system check failed but did not > detect errors > [ 9.607328] EXT4-fs (sda1): mounted filesystem > with ordered data mode. Opts: (null) > done. >
root@Nsa310s:~# myinfo Nsa310s 192.168.0.248 Machine model: Zyxel NSA310S Linux version 4.2.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Aug 31 23:12:00 PDT 2015 console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) uboot_version=U-Boot 2014.07-tld-4 (Aug 17 2015 - 16:10:11)
Re: Debian on NSA310S? September 12, 2015 04:29AM |
Admin Registered: 13 years ago Posts: 19,107 |
[ 11.684817] rtc rtc0: __rtc_set_alarm: err=-22
Re: Debian on NSA310S? September 12, 2015 04:36AM |
Admin Registered: 13 years ago Posts: 19,107 |
dmesg -T
Re: Debian on NSA310S? September 12, 2015 04:39AM |
Registered: 9 years ago Posts: 118 |
[Mon Nov 27 12:55:59 1933] NET: Registered protocol family 10 [Mon Nov 27 12:55:59 1933] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [Mon Nov 27 12:56:00 1933] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [Mon Nov 27 12:56:00 1933] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[Mon Nov 27 12:59:59 1933] NET: Registered protocol family 10 [Mon Nov 27 12:59:59 1933] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [Mon Nov 27 13:00:00 1933] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [Mon Nov 27 13:00:00 1933] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2.111905] ht1382 0-0068: rtc core: registered ht1382 as rtc0
Re: Debian on NSA310S? September 12, 2015 05:32AM |
Admin Registered: 13 years ago Posts: 19,107 |
> [Mon Nov 27 12:55:59 1933] NET: Registered > protocol family 10 > [Mon Nov 27 12:55:59 1933] IPv6: > ADDRCONF(NETDEV_UP): eth0: link is not ready > [Mon Nov 27 12:56:00 1933] mv643xx_eth_port > mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full > duplex, flow control disabled > [Mon Nov 27 12:56:00 1933] IPv6: > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >>
> [Mon Nov 27 12:59:59 1933] NET: Registered > protocol family 10 > [Mon Nov 27 12:59:59 1933] IPv6: > ADDRCONF(NETDEV_UP): eth0: link is not ready > [Mon Nov 27 13:00:00 1933] mv643xx_eth_port > mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full > duplex, flow control disabled > [Mon Nov 27 13:00:00 1933] IPv6: > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >>
> [ 2.111905] ht1382 0-0068: rtc core: registered > ht1382 as rtc0 >>
ps -deaf | grep -i ntp logread | grep -i ntp
Re: Debian on NSA310S? September 12, 2015 05:32AM |
Registered: 9 years ago Posts: 118 |
# You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: http://www.pool.ntp.org/join.html server 0.debian.pool.ntp.org iburst #server 1.debian.pool.ntp.org iburst #server 2.debian.pool.ntp.org iburst #server 3.debian.pool.ntp.org iburst
Re: Debian on NSA310S? September 12, 2015 05:37AM |
Registered: 9 years ago Posts: 118 |
root@debian:~# ps -deaf | grep -i ntp root 1518 1512 0 13:36 ttyS0 00:00:00 grep -i ntp root@debian:~# logread | grep -i ntp Nov 27 13:35:47 debian daemon.notice ntpd[1411]: ntpd 4.2.6p5@1.2349-o Fri Apr 10 19:35:06 UTC 2015 (1) Nov 27 13:35:48 debian daemon.notice ntpd[1412]: proto: precision = 1.722 usec Nov 27 13:35:48 debian daemon.err ntpd[1412]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Nov 27 13:35:55 debian daemon.err ntpdate[1041]: no server suitable for synchronization found Nov 27 13:35:55 debian daemon.err ntpdate[1073]: Can't adjust the time of day: Invalid argument
Re: Debian on NSA310S? September 12, 2015 05:48AM |
Admin Registered: 13 years ago Posts: 19,107 |
cat /etc/ntp.conf | grep serverIf no server specified in your ntp.conf, then you should uncomment all four. You can sync with other time servers, instead of using Debian pool servers. But normally, uncomment these pools is all you need to do.
Re: Debian on NSA310S? September 12, 2015 06:10AM |
Registered: 9 years ago Posts: 118 |
root@ionut-nas:~# cat /etc/ntp.conf | grep server # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will server 0.debian.pool.ntp.org iburst #server 1.debian.pool.ntp.org iburst #server 2.debian.pool.ntp.org iburst #server 3.debian.pool.ntp.org iburst server 192.12.19.20 server 164.67.62.194 server 140.142.16.34 server 206.246.122.250 # Note that "restrict" applies to both servers and clients, so a configuration # up blocking replies from your own upstream servers. # Local users may interrogate the ntp server more closely.
221.[ 2.177562] ht1382 0-0068: setting system clock to 2070-01-02 17:38:55 UTC (3155909935)
Re: Debian on NSA310S? September 12, 2015 10:46AM |
Registered: 9 years ago Posts: 47 |
Re: Debian on NSA310S? September 12, 2015 03:04PM |
Admin Registered: 13 years ago Posts: 19,107 |
Re: Debian on NSA310S? September 12, 2015 05:08PM |
Registered: 9 years ago Posts: 47 |
So.. we do not need rtc driver?Quote
ntpd is sync to the rtc,
Re: Debian on NSA310S? September 12, 2015 05:11PM |
Registered: 9 years ago Posts: 118 |
> So.. we do not need rtc driver?Quote
ntpd is sync to the rtc,
Re: Debian on NSA310S? September 12, 2015 05:47PM |
Admin Registered: 13 years ago Posts: 19,107 |
Re: Debian on NSA310S? September 12, 2015 06:00PM |
Registered: 9 years ago Posts: 118 |
Re: Debian on NSA310S? September 12, 2015 06:20PM |
Admin Registered: 13 years ago Posts: 19,107 |
nand read.e 0x2000000 0xc80000 0xA00000; bootm 0x2000000
Re: Debian on NSA310S? September 13, 2015 06:35AM |
Registered: 9 years ago Posts: 118 |
[ 4.217679] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 4.229066] sd 2:0:0:0: [sdb] Write Protect is off [ 4.237185] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 4.237928] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 4.253974] sdb: sdb1 [ 4.268303] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 14.495495] __nand_correct_data: uncorrectable ECC error [ 14.500828] __nand_correct_data: uncorrectable ECC error [ 14.506180] blk_update_request: I/O error, dev mtdblock5, sector 8 [ 19.678818] EXT3-fs (sdb1): mounted filesystem with ordered data mode [ 19.685334] kjournald starting. Commit interval 5 seconds [ 21.009295] random: nonblocking pool is initialized [ 21.092969] systemd-udevd[310]: starting version 215 [ 21.401518] input: gpio_keys as /devices/platform/gpio_keys/input/input0 [ 21.649244] orion_wdt: Initial timeout 25 sec [ 22.805560] __nand_correct_data: uncorrectable ECC error [ 22.810897] __nand_correct_data: uncorrectable ECC error [ 22.831596] blk_update_request: I/O error, dev mtdblock5, sector 8 [ 23.766717] EXT3-fs (sdb1): using internal journal
Ntpdate is running when you try to start the server. I haven't found reasons why to leave it installed so you could remove it if you are using ntp daemon:apt-get remove ntpdate
root@ionut-nas:~# logread | grep -i ntp Sep 13 14:51:23 ionut-nas daemon.notice ntpd[1533]: ntpd 4.2.6p5@1.2349-o Fri Ap r 10 19:35:06 UTC 2015 (1) Sep 13 14:51:23 ionut-nas daemon.notice ntpd[1534]: proto: precision = 1.728 use c Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen and drop on 0 v4wildcar d 0.0.0.0 UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen and drop on 1 v6wildcar d :: UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 2 lo 127.0. 0.1 UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 3 eth0 192. 168.1.173 UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 4 eth0 2a02 :2f0d:xxxx:ed00:xxxx:abff:fedf:xxx UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 5 lo ::1 UD P 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 6 eth0 fde9 :xxxx:493e:0:xxxx:abff:fedf:xxx UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 7 eth0 fe80 ::xxx:xxxx:fedf:72b UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: peers refreshed Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listening on routing socket on fd #24 for interface updates
Re: Debian on NSA310S? September 13, 2015 09:00AM |
Registered: 9 years ago Posts: 295 |
> [ 14.495495] __nand_correct_data: > uncorrectable ECC error > [ 14.500828] __nand_correct_data: uncorrectable > ECC error > [ 22.805560] __nand_correct_data: > uncorrectable ECC error > [ 22.810897] __nand_correct_data: uncorrectable > ECC error > [ 22.831596] blk_update_request: I/O error, dev > mtdblock5, sector 8 >>
Re: Debian on NSA310S? September 13, 2015 01:31PM |
Admin Registered: 13 years ago Posts: 19,107 |
Re: Debian on NSA310S? September 13, 2015 01:37PM |
Registered: 9 years ago Posts: 118 |
Re: Debian on NSA310S? September 13, 2015 01:42PM |
Admin Registered: 13 years ago Posts: 19,107 |
Re: Debian on NSA310S? September 13, 2015 01:48PM |
Registered: 9 years ago Posts: 118 |
Re: Debian on NSA310S? July 15, 2016 06:39PM |
Registered: 11 years ago Posts: 16 |