Welcome! Log In Create A New Profile

Advanced

NSA 325 V2 Debian Is Possible!

Posted by Buttzy10169 
Re: NSA 325 V2 Debian Is Possible!
October 14, 2014 07:35AM
Hello everybody,

i've bought the zyxel NSA-325v2 several weeks ago. My first thought was to put any linux on it to be indipendet form the manufacturer in case that the stock BS isn't developed anymore.

Maybe i'm to much noob / to stupid or i got a strange box i don't know.... I tried my very best.

First i tried ALARM, as there exists an easy "install-how-to". I installed it to different usb sticks / SSD internal, it works.
With the 4TB HDD build in the NAS didn't start. An update of the kernel made the booting possible but network was no working anymore.

I tired Debian. On the stick it was very, very slow. Installing,OMV failed serveral times, locking into the webinterface was not possible.
Yesterday i installed Debian on the SSD, i works perfect, OMV works perfect.
I updated the kernel to 3.16 but booting with the 4TB isn't possible, even when the system is on the 160GB SSD.

Is the only way to get the hdd working to update the uboot?

Most of the times i can't access the usb stick, when i interrup the boot sequence.
Sometimes i've to powerup the usd interface
-> mw.l f1010100 0020c000
-> restart usb
Sometimes it works, that the stick is recognized

Marvell>> printenv ethaddr
ethaddr=00:50:43:00:02:02

Marvell>> md ff00003c
ff00003c: 00000000 00000000 00000000 00000000    ................
ff00004c: 00000000 00000000 00000000 00000000    ................
ff00005c: 00000000 00000000 00000000 00000000    ................
ff00006c: 00000000 00000000 00000000 00000000    ................
ff00007c: 00000000 00000000 00000000 00000000    ................
ff00008c: 00000000 00000000 00000000 00000000    ................
ff00009c: 00000000 00000000 00000000 00000000    ................
ff0000ac: 00000000 00000000 00000000 00000000    ................
ff0000bc: 00000000 00000000 00000000 00000000    ................
ff0000cc: 00000000 00000000 00000000 00000000    ................
ff0000dc: 00000000 00000000 00000000 00000000    ................
ff0000ec: 00000000 00000000 00000000 00000000    ................
ff0000fc: 00000000 00000000 00000000 00000000    ................
ff00010c: 00000000 00000000 00000000 00000000    ................
ff00011c: 00000000 00000000 00000000 00000000    ................
ff00012c: 00000000 00000000 00000000 00000000    ................

Debian loaded ->
cat /etc/fw_env.config 
# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors 
/dev/mtd0 0xc0000 0x20000 0x20000

fw_printenv ethaddr
Warning: Bad CRC, using default environment
## Error: "ethaddr" not defined

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"

./kwboot -t -B 115200 /dev/ttyUSB0 -b ./uboot.2013.10-tld-1.nsa325.uart.kwb -p 
/dev/ttyUSB0: No such file or directory


I don't know how to continue :-(

If you have any ideas what i can do / just give me the order :)



Edited 8 time(s). Last edit at 10/14/2014 01:03PM by addy75.
Re: NSA 325 V2 Debian Is Possible!
October 14, 2014 11:04PM
@addy75,

So can you boot into Debian with either USB stick or the SSD? which rootfs do you use?
uname -a

If you can, then keep it that way, you can install new u-boot:
http://forum.doozan.com/read.php?3,12381,17420#msg-17420

I have not formally released this new u-boot. So if you have installed u-boot before for another Kirkwood box as described in the instruction in the above link, then you already know what to do. If not, wait for the release when instruction will be provided.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
October 15, 2014 01:39AM
Hello bodhi,

thank you for your reply.
Yes, i'm able to boot the Debian either USB stick or the SSD.

I'm using the rootfs file from this webseite
Rootfs-File

No, until now i haven't installed the new uboot.

Question:
Does a new uboot really fix the problem, that debian stops booting when the 4TB HDD is put in the 2nd bay?

davygravy wrote
Quote
davygravy
How to determine if UART-booting works: It seems like the best marker is the BootROM version. So far, all machines with version 1.21 do support it, but none of the version 1.11 machines seem to work with it. From within U-Boot (either serial or netconsole, execute the md memory-display command at offset ff00003c:

md ff00003c
If you see
ff00003c: 00000111
it is v1.11, and if you see
ff00003c: 00000121
it has v 1.21.
My output ist

Marvell>> md ff00003c
ff00003c: 00000000 00000000 00000000 00000000    ................
ff00004c: 00000000 00000000 00000000 00000000    ................
ff00005c: 00000000 00000000 00000000 00000000    ................
ff00006c: 00000000 00000000 00000000 00000000    ................
ff00007c: 00000000 00000000 00000000 00000000    ................
ff00008c: 00000000 00000000 00000000 00000000    ................
ff00009c: 00000000 00000000 00000000 00000000    ................
ff0000ac: 00000000 00000000 00000000 00000000    ................
ff0000bc: 00000000 00000000 00000000 00000000    ................
ff0000cc: 00000000 00000000 00000000 00000000    ................
ff0000dc: 00000000 00000000 00000000 00000000    ................
ff0000ec: 00000000 00000000 00000000 00000000    ................
ff0000fc: 00000000 00000000 00000000 00000000    ................
ff00010c: 00000000 00000000 00000000 00000000    ................
ff00011c: 00000000 00000000 00000000 00000000    ................
ff00012c: 00000000 00000000 00000000 00000000    ................
Is this a problem or should i ignore it?
Re: NSA 325 V2 Debian Is Possible!
October 15, 2014 02:37AM
addy75,

You are running my Debian-3.14.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs.

You can ignore the bootROM detection.
Marvell>> md ff00003c
It does not really tell. We've verified that the NSA325 has UART booting. So don't bother with this step.

And I see you have tried UART booting above:
./kwboot -t -B 115200 /dev/ttyUSB0 -b ./uboot.2013.10-tld-1.nsa325.uart.kwb -p
Sometime the serial console got a different device name. So to see which device name it was assigned to, look for it in your dmesg. Here is mine:
dmesg | grep tty

[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) zswap.enabled=1
[    0.885366] console [ttyS0] disabled
[    0.885428] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    1.480384] console [ttyS0] enabled
[   20.842452] usb 1-1.4.2: cp210x converter now attached to ttyUSB0
My serial console was assigned ttyUSB0. If it was assigned a different device name for yours then use it in the kwboot command.

After you got UART booting going, you can plug in your 4TB HDD rootfs, it should boot without problem.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 10/15/2014 02:39AM by bodhi.
Re: NSA 325 V2 Debian Is Possible!
October 15, 2014 05:31AM
Ok, thank you in advance.

I will try my best at home.

Quote
bodhi
After you got UART booting going, you can plug in your 4TB HDD rootfs, it should boot without problem.

My problem is that debian isn't booting when i put my 4TB in. Rootf is on a stick / ssd and working.
One time bootet, i can plug 4TB HDD in without problems...until i to the next reboot.
Re: NSA 325 V2 Debian Is Possible!
October 15, 2014 08:49AM
@addy75

Right. What we're saying is that the uboot on the box might be the problem, and not the kernel.
Re: NSA 325 V2 Debian Is Possible!
October 17, 2014 12:04AM
@davidedg,

I'm testing kernel 3.17 FDT for all Kirkwood boxes.

I am trying to compile the DTS file kirkwood-nsa325.dts, which I got from pkirchhofer Git (mentioned in your previous post, thanks!) And I got the syntax error:
Error: arch/arm/boot/dts/kirkwood.dtsi:2.1-9 syntax error
FATAL ERROR: Unable to parse input tree

Have you seen this? all other DTS files compiled OK.

Thanks,

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
October 17, 2014 03:47PM
> Error: arch/arm/boot/dts/kirkwood.dtsi:2.1-9
> syntax error
> FATAL ERROR: Unable to parse input tree

Have figured out why this error occured. On to the next error!

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 10/17/2014 03:48PM by bodhi.
Re: NSA 325 V2 Debian Is Possible!
October 17, 2014 04:58PM
I give up. I feel that my skill isn't high enough to be able to update the uboot.

The original software comes up when the 4TB is build in.
Booting Debian using the "sata-debian-uboot" script booting stops while scanning the HDDs

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: INTEL SSDSA2BW160G3L                     Firm: 4PC1LE04 Ser#: CVPR137009LE160DGN
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)

Sometimes it continuos and stopps while scanning the 4TB HDD. Whitout the 4TB it boots.

Is this really the uboot?
I've tried the last days to understand up to update the uboot but i'm not able to understand the procedure.
I've bootet the boot using kwboot, and then?
fw_printenv ethaddres -> no address set...

Will there be a new uboot soon? Is it possibile to give me an hint how it works to update the uboot?
Kwboot has to be startet from "outside" the box. How to proced?
Start debian from the "updated" box and continue or type use the PC where i have startet the kwboot?

Many thanks in advance!!!



Edited 1 time(s). Last edit at 10/17/2014 05:00PM by addy75.
Re: NSA 325 V2 Debian Is Possible!
October 18, 2014 12:27AM
addy75,

Quote

Sometimes it continuos and stopps while scanning
the 4TB HDD. Whitout the 4TB it boots.

Is this really the uboot?

No, it is the watchdog, which resets the box when you take too long to boot with the 4TB.

Quote

Will there be a new uboot soon?

You can bug WarheadsSE :) Warhead will do a GitHub release after he's happy with what we have. And then I will release it here.

Quote

Is it possibile to give me an hint how it works to update the uboot?

Read the first post of this thread: http://forum.doozan.com/read.php?3,12381
and this post: http://forum.doozan.com/read.php?3,12381,17420#msg-17420

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
October 18, 2014 01:56AM
Re: NSA 325 V2 Debian Is Possible!
October 18, 2014 06:46AM
bodhi Wrote:
-------------------------------------------------------
> @davidedg,
>
> I'm testing kernel 3.17 FDT for all Kirkwood
> boxes.
>
> I am trying to compile the DTS file
> kirkwood-nsa325.dts, which I got from
> [url=https://github.com/pkirchhofer/nsa325-kernel/
> blob/master/arch/arm/boot/dts/kirkwood-nsa325.dts]
> pkirchhofer Git[/url]

I had succeeded in compiling a working FDT kernel by manual cherrypicking specific patches - but it was a nightmare to figure out (still have the related notes if you need them).

AFAIK, now there's a new repo which tracks more recent kernels:
[url=https://github.com/pkirchhofer/nsa325-linux-upstream]https://github.com/pkirchhofer/nsa325-linux-upstream[/url]

So this should not be needed anymore, but had not a chance to test it (just too happy with your new u-boot and your kernel patches ;P)
Bye!

--
DavideDG
[url=https://github.com/davidedg/NAS-mod-config/]My NAS userspace configs[/url]
[url=https://github.com/davidedg/NAS-NSA325-mod/]My Zyxel NSA325 mod[/url]
[url=http://davidedg.github.io/NAS-DNS325-mod/]My D-Link DNS325 mod[/url]
[url=https://github.com/davidedg/NAS-NS2MAX-mod/]My Lacie NS2MAX mod[/url]



Edited 1 time(s). Last edit at 10/18/2014 06:52AM by davidedg.
Re: NSA 325 V2 Debian Is Possible!
October 18, 2014 06:49AM
> You can bug WarheadsSE :) Warhead will do a GitHub release
> after he's happy with what we have. And then I will release it here.

@WarheadsSE: any chances that this will be included in upstream u-boot ? I just dislike fragmentation :D

--
DavideDG
My NAS userspace configs
My Zyxel NSA325 mod
My D-Link DNS325 mod
My Lacie NS2MAX mod
Re: NSA 325 V2 Debian Is Possible!
October 18, 2014 01:54PM
davidedg,

> AFAIK, now there's a new repo which tracks more
> recent kernels:
> [url=https://github.com/pkirchhofer/nsa325-linux-u
> pstream]https://github.com/pkirchhofer/nsa325-linu
> x-upstream[/url]

Thanks. I'll take a look there.

>
> So this should not be needed anymore, but had not
> a chance to test it (just too happy with your new
> u-boot and your kernel patches ;P)
> Bye!

:) glad it works well. I've been hesitate in going forward with FDT, because we are doing fine with non-FDT patches. But kernel 3.17 code change in mvebu SoC has made retrofitting the patches too clumsy. So I thought I'd bite the bullet and work on 3.17 FDT. The 3.17 patches became much smaller. So far all the other Kirkwood boxes are running fine (for a about a week now).

-bodhi
===========================
[b][color=#3333FF][url=http://forum.doozan.com/read.php?2,23630]Wiki[/url][/color][/b]
[url=http://forum.doozan.com/read.php?2,12096]latest Kirkwood kernel builds and rootfs[/url]
[url=http://forum.doozan.com/read.php?3,12381]latest u-boot-kirkwood builds[/url]
[url=http://forum.doozan.com/read.php?2,16044]latest Oxnas kernel builds and rootfs[/url]
[url=http://forum.doozan.com/read.php?3,16017]latest u-boot-oxnas builds[/url]
[url=http://forum.doozan.com/read.php?2,32146]latest MVEBU Armada kernel builds and rootfs[/url]
[url=http://forum.doozan.com/read.php?3,19093]U-Boot & Kernel Booting process[/url]
[url=https://github.com/mibodhi]bodhi's u-boot GitHub[/url]
[url=https://mibodhi.blogspot.com]bodhi's corner[/url]
Re: NSA 325 V2 Debian Is Possible!
October 20, 2014 07:26AM
Hello everybody,

this sunday I used the time to update the uboot. Updating worked without problems but i don't know why the env-settings got "lost".

Theser were the original settings
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000
bootdelay=2
baudrate=115200
loads_echo=0
ipaddr=10.4.52.165
serverip=10.4.52.7
rootpath=/srv/ubuntu
netmask=255.255.255.0
nandEcc= 1bit
kernel_addr=C80000
MODEL_ID=AE03
PRODUCT_NAME=NSA-325v2
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=MitraStar Technology Corp.
run_diag=yes

As i understand these settings aren't usefull anymore?

I enterd these settings, which i found here
arcNumber=4495
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot;
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=3
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:50:43:00:xx:yy
ethprime=egiga0
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0 orion_nand
mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext4
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
set_bootargs_mmc=setenv bootargs console $console root $mmc_root rootdelay $rootdelay rootfstype $rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console $console root $sata_root rootdelay $rootdelay rootfstype $rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console $console root $usb_root rootdelay $rootdelay rootfstype $rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /uInitrd
usb_root=/dev/sda1

I've to change all /boot/uxxxxx -> /uxxxxx because the working debian stick doesn't work anymore.
After changing these stettings the debian startet to booting but stops just after uncompressing the kernel

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
2461416 bytes read in 240 ms (9.8 MiB/s)
6362802 bytes read in 2772 ms (2.2 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.14.0-kirkwood-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2461352 Bytes = 2.3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.14.0-kirkwood-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6362738 Bytes = 6.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Can you please help me to get the system working?



/ update

Until my linux / uboot skills aren't the best this is only try & error.

I've used the orig env-settings with the information i've found here
arcNumber=4495
baudrate=115200
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
bootcmd=run bootcmd_usb
bootcmd_usb=mw.l f1010100 0020c000; setenv bootargs $set_bootargs_usb; usb start; ext2load usb 0:1 0x800000 /uImage; ext2load usb 0:1 0x01100000 /uInitrd; bootm 0x800000 0x01100000
bootdelay=3
ethact=egiga0
filesize=6116b2
machid=118f
mainlineLinux=yes
set_bootargs_usb=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
stderr=serial
stdin=serial
stdout=serial

I had to change $loadaddr -> 0x800000, then the boot proceded until


[   15.657856] ata1: SATA link down (SStatus 0 SControl F300)
[   16.027847] ata2: SATA link down (SStatus 0 SControl F300)
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
modprobe: module unknown not found in modules.dep
mount: can't read '/etc/fstab': No such file or directory
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
[   16.215517] uhci_hcd: USB Universal Host Controller Interface driver
[   16.227278] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   16.240088] usbcore: registered new interface driver usbhid
[   16.245717] usbhid: USB HID core driver


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) [   16.943421] scsi 0:0:0:0: Direct-Access     Intenso  Micro Line       1100 PQ: 0 ANSI: 4

(initramfs)


Please HELP :-(



Edited 1 time(s). Last edit at 10/20/2014 01:36PM by addy75.
Re: NSA 325 V2 Debian Is Possible!
October 20, 2014 03:30PM
Re: NSA 325 V2 Debian Is Possible!
October 21, 2014 06:50AM
It doesn't work

scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** No boot file defined **
6362802 bytes read in 686 ms (8.8 MiB/s)
## Booting kernel from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.14.0-kirkwood-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6362738 Bytes = 6.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Wrong Image Type for bootm command
Error occured, error code = 5
ERROR: can't get kernel image!

Re: NSA 325 V2 Debian Is Possible!
October 22, 2014 12:54AM
I don't know why.... but now it works.

Later i will check if the NAS starts when te 4TB HDD is connected
Re: NSA 325 V2 Debian Is Possible!
October 22, 2014 02:48PM
Box comes up with ext4 FS and 4TB build in.
Sometimes it reboots just after the DHCPREQUEST.

I had to install Debian on an SSD. The stick causes a lot of problems installing OMV...
Re: NSA 325 V2 Debian Is Possible!
October 22, 2014 03:30PM
Bad new:

The box restarts when the system is not loaded in time, everytime after 30sec.
The FS wants to performe a self-check

[ ok ] Activating swap...done.
[   28.799809] EXT4-fs (sda1): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.20.1
rootfs contains a file system with errors, check forced.
rootfs: |==================================                      - 61.2%

U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26)

if i put the 4TB HDD in the check arrives at ~41% and the box restarts.
I thought the watchdog was killed?
Re: NSA 325 V2 Debian Is Possible!
October 22, 2014 11:50PM
Re: NSA 325 V2 Debian Is Possible!
October 22, 2014 11:52PM
Re: NSA 325 V2 Debian Is Possible!
October 22, 2014 11:52PM
bodhi,

ok. I though the dog was "killed" by the new uboot....

Anyway - Thank you for the good work !!!
Re: NSA 325 V2 Debian Is Possible!
October 22, 2014 11:55PM
addy75 Wrote:
-------------------------------------------------------
> bodhi,
>
> ok. I though the dog was "killed" by the new
> uboot....
>
> Anyway - Thank you for the good work !!!

New u-boot did! But it seems the older kernel version turned it back on. Install the latest kernel and try again.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
October 23, 2014 01:54PM
I think something might make sense here:
u-boot disables watchdog when it starts, then, we re-enable it just before starting the kernel.

Why? In case the kernel hangs.

Obviously, for we'd do this via a memory write, instead of in c code for u-boot. Why? Because then that bit can be flipped on/off :)
Re: NSA 325 V2 Debian Is Possible!
October 23, 2014 03:16PM
WarheadsSE Wrote:
-------------------------------------------------------
> I think something might make sense here:
> u-boot disables watchdog when it starts, then, we
> re-enable it just before starting the kernel.
>
> Why? In case the kernel hangs.
>
> Obviously, for we'd do this via a memory write,
> instead of in c code for u-boot. Why? Because then
> that bit can be flipped on/off :)

:) yeah. I think the hard part is to know when to flip that bit to disable again before the fsck, since it takes too long to fsck a 4TB HDD. So leaving it disabled always seems reasonable.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
October 24, 2014 02:09PM
... i don't know why... it only sux.

Yesterday i prepared the SSD and updated the kernel.
It started everytime without problems. Now i want to configure OMV and the system but... the box restarts after 30sec.
I used the USB Stick with kernel 3.14 -> restart.
After >20 retrys the system starts with the USB stick.
New uboot & new kernel but it restarts.

As there are people having a working box... what can be my mistake :-(
Re: NSA 325 V2 Debian Is Possible!
October 24, 2014 02:20PM
Re: NSA 325 V2 Debian Is Possible!
October 24, 2014 04:24PM
I'm running the latest kernel :-(

I've reinstalled the system, all i working. I'll see tomorrow what daylight brings :)
Re: NSA 325 V2 Debian Is Possible!
October 25, 2014 07:06AM
I don't know why.
Yesterday everything works great. Shutdown, restarts, all works perfect.

Now i turn on the nas and it continues rebooting.
Lastet kernel & uboot installed.

U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_??
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0 [PRIME]
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: INTEL SSDSA2BW160G3L Firm: 4PC1LE04 Ser#: CVPR137009LE160DGN
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
2753400 bytes read in 426 ms (6.2 MiB/s)
6031616 bytes read in 913 ms (6.3 MiB/s)
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-3.16.0-kirkwood-tld-3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2753336 Bytes = 2.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.16.0-kirkwood-tld-3
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6031552 Bytes = 5.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.16.0-kirkwood-tld-3 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 PREEMPT Sat Sep 27 02:01:41 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: ZyXEL NSA325 2-Bay Power Media Server
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200 rootfstype=ext4 root=LABEL=hdd-root rootdelay=3 :::orion:eth0:none
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 505588K/524288K available (5441K kernel code, 397K rwdata, 1840K rodata, 257K init, 299K bss, 18700K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07248b0   (7283 kB)
[    0.000000]       .init : 0xc0725000 - 0xc0765444   ( 258 kB)
[    0.000000]       .data : 0xc0766000 - 0xc07c975c   ( 398 kB)
[    0.000000]        .bss : 0xc07c975c - 0xc08144dc   ( 300 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[   12.501055] Console: colour dummy device 80x30
[   12.501078] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
[   12.590856] pid_max: default: 32768 minimum: 301
[   12.590954] Security Framework initialized
[   12.591008] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   12.591023] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   12.591725] Initializing cgroup subsys devices
[   12.591778] Initializing cgroup subsys freezer
[   12.591800] Initializing cgroup subsys net_cls
[   12.591839] Initializing cgroup subsys blkio
[   12.591922] CPU: Testing write buffer coherency: ok
[   12.592309] Setting up static identity map for 0x5273f0 - 0x527448
[   12.594284] devtmpfs: initialized
[   12.597357] prandom: seed boundary self test passed
[   12.600358] prandom: 100 self tests passed
[   12.600376] pinctrl core: initialized pinctrl subsystem
[   12.600796] regulator-dummy: no parameters
[   12.601278] NET: Registered protocol family 16
[   12.601615] DMA: preallocated 256 KiB pool for atomic coherent allocations
[   12.602625] cpuidle: using governor ladder
[   12.602647] cpuidle: using governor menu
[   12.602758] Kirkwood: MV88F6282-Rev-A1, TCLK=200000000.
[   12.602778] Feroceon L2: Enabling L2
[   12.602809] Feroceon L2: Cache support initialised.
[   12.603633] Start platform NSA325
[   12.604304] Kirkwood PCIe port 0: link up
[   12.604313] PCI: bus0 uses PCIe port 0
[   12.604466] PCI host bridge to bus 0000:00
[   12.604481] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[   12.604491] pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
[   12.604500] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[   12.605141] PCI: bus0: Fast back to back transfers disabled
[   12.605186] pci 0000:00:01.0: BAR 0: assigned [mem 0xe0000000-0xe0001fff 64bit]
[   12.632107] vgaarb: loaded
[   12.632376] usbcore: registered new interface driver usbfs
[   12.632434] usbcore: registered new interface driver hub
[   12.632531] usbcore: registered new device driver usb
[   12.633316] Switched to clocksource orion_clocksource
[   12.663689] NET: Registered protocol family 2
[   12.664478] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[   12.664534] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[   12.664584] TCP: Hash tables configured (established 4096 bind 4096)
[   12.664639] TCP: reno registered
[   12.664650] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   12.664669] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   12.664840] NET: Registered protocol family 1
[   12.665115] RPC: Registered named UNIX socket transport module.
[   12.665124] RPC: Registered udp transport module.
[   12.665129] RPC: Registered tcp transport module.
[   12.665135] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   12.665186] pci 0000:00:01.0: enabling device (0140 -> 0142)
[   12.665478] Unpacking initramfs...
[   13.047128] Freeing initrd memory: 5884K (c1101000 - c16c0000)
[   13.047245] NetWinder Floating Point Emulator V0.97 (double precision)
[   13.048160] futex hash table entries: 256 (order: -1, 3072 bytes)
[   13.048215] audit: initializing netlink subsys (disabled)
[   13.048266] audit: type=2000 audit(0.540:1): initialized
[   13.048936] zbud: loaded
[   13.049152] VFS: Disk quotas dquot_6.5.2
[   13.049197] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   13.049643] NFS: Registering the id_resolver key type
[   13.049693] Key type id_resolver registered
[   13.049700] Key type id_legacy registered
[   13.049721] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[   13.049732] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   13.049862] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   13.050104] msgmni has been set to 998
[   13.050229] Key type big_key registered
[   13.052075] alg: No test for stdrng (krng)
[   13.052167] bounce: pool size: 64 pages
[   13.052218] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[   13.052233] io scheduler noop registered
[   13.052244] io scheduler deadline registered
[   13.052385] io scheduler cfq registered (default)
[   13.052723] mv_xor mv_xor.0: Marvell shared XOR driver
[   13.083375] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   13.123366] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   13.123497] mv_xor mv_xor.1: Marvell shared XOR driver
[   13.163366] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   13.203365] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   13.203694] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   13.204432] console [ttyS0] disabled
[   13.224481] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[   13.825414] console [ttyS0] enabled
[   13.830007] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
[   13.836413] nand: Eon NAND 128MiB 3,3V 8-bit
[   13.840696] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[   13.846390] Scanning device for bad blocks
[   13.909460] Creating 9 MTD partitions on "orion_nand":
[   13.914698] 0x000000000000-0x000000100000 : "uboot"
[   13.919941] 0x000000100000-0x000000180000 : "uboot_env"
[   13.925507] 0x000000180000-0x000000200000 : "key_store"
[   13.931020] 0x000000200000-0x000000280000 : "info"
[   13.936172] 0x000000280000-0x000000c80000 : "etc"
[   13.941173] 0x000000c80000-0x000001680000 : "kernel_1"
[   13.946638] 0x000001680000-0x000004640000 : "rootfs1"
[   13.952009] 0x000004640000-0x000005040000 : "kernel_2"
[   13.957499] 0x000005040000-0x000008000000 : "rootfs2"
[   13.963549] libphy: Fixed MDIO Bus: probed
[   13.978237] libphy: orion_mdio_bus: probed
[   13.982444] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   13.991912] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:50:43:00:02:02
[   14.000918] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   14.007515] ehci-pci: EHCI PCI platform driver
[   14.012031] ehci-orion: EHCI orion driver
[   14.016158] orion-ehci orion-ehci.0: EHCI Host Controller
[   14.021593] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   14.029328] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   14.053345] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   14.059435] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   14.066268] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   14.073534] usb usb1: Product: EHCI Host Controller
[   14.078431] usb usb1: Manufacturer: Linux 3.16.0-kirkwood-tld-3 ehci_hcd
[   14.085174] usb usb1: SerialNumber: orion-ehci.0
[   14.090399] hub 1-0:1.0: USB hub found
[   14.094222] hub 1-0:1.0: 1 port detected
[   14.098838] mousedev: PS/2 mouse device common for all mice
[   14.413361] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   14.564837] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   14.571574] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   14.578764] usb 1-1: Product: USB2.0 Hub
[   14.583517] hub 1-1:1.0: USB hub found
[   14.587585] hub 1-1:1.0: 4 ports detected
[   15.113343] rtc-mv rtc-mv: internal RTC not ticking
[   15.118389] i2c /dev entries driver
[   15.122316] rtc-pcf8563 0-0051: chip found, driver version 0.4.3
[   15.129700] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[   15.137622] hidraw: raw HID events driver (C) Jiri Kosina
[   15.143350] drop_monitor: Initializing network drop monitor service
[   15.149829] TCP: cubic registered
[   15.153168] NET: Registered protocol family 17
[   15.157758] Key type dns_resolver registered
[   15.162595] registered taskstats version 1
[   15.168682] rtc-pcf8563 0-0051: setting system clock to 2014-10-25 13:04:58 UTC (1414242298)
[   15.178860] Freeing unused kernel memory: 256K (c0725000 - c0765000)
Loading, please wait...
[   15.244087] udevd[57]: starting version 175
[   15.339136] xhci_hcd 0000:00:01.0: xHCI Host Controller
[   15.376118] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
[   15.427482] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   15.445900] SCSI subsystem initialized
[   15.453485] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   15.460743] usb usb2: Product: xHCI Host Controller
[   15.505240] sata_mv sata_mv.0: cannot get optional clkdev
[   15.510755] sata_mv sata_mv.0: slots 32 ports 2
[   15.522615] usb usb2: Manufacturer: Linux 3.16.0-kirkwood-tld-3 xhci_hcd
[   15.551653] usb usb2: SerialNumber: 0000:00:01.0
[   15.575902] scsi0 : sata_mv
[   15.580695] hub 2-0:1.0: USB hub found
[   15.595613] scsi1 : sata_mv
[   15.598701] ata1: SATA max UDMA/133 irq 21
[   15.602818] ata2: SATA max UDMA/133 irq 21
[   15.609246] hub 2-0:1.0: 2 ports detected
[   15.627685] xhci_hcd 0000:00:01.0: xHCI Host Controller
[   15.632947] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 3
[   15.646537] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[   15.653579] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   15.660832] usb usb3: Product: xHCI Host Controller
[   15.665791] usb usb3: Manufacturer: Linux 3.16.0-kirkwood-tld-3 xhci_hcd
[   15.672517] usb usb3: SerialNumber: 0000:00:01.0
[   15.678147] hub 3-0:1.0: USB hub found
[   15.681951] hub 3-0:1.0: 2 ports detected
[   16.153359] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   16.173521] ata1.00: ATA-8: INTEL SSDSA2BW160G3L, 4PC1LE04, max UDMA/133
[   16.180258] ata1.00: 312581808 sectors, multi 1: LBA48 NCQ (depth 31/32)
[   16.203509] ata1.00: configured for UDMA/133
[   16.223651] scsi 0:0:0:0: Direct-Access     ATA      INTEL SSDSA2BW16 LE04 PQ: 0 ANSI: 5
[   16.573357] ata2: SATA link down (SStatus 0 SControl F300)
[   16.622996] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[   16.631763] sd 0:0:0:0: [sda] Write Protect is off
[   16.636803] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   16.648056]  sda: sda1
[   16.651840] sd 0:0:0:0: [sda] Attached SCSI disk
[   16.665674] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[   19.824010] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[   19.830919] EXT4-fs (sda1): write access will be enabled during recovery
[   19.847972] EXT4-fs (sda1): recovery complete
[   19.852756] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevd[   20.528552] udevd[248]: starting version 175
.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...[   20.741032] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   20.884751] alg: hash: Test 3 failed for mv-sha1
[   20.889400] 00000000: 10 bf d7 00 71 0b bb 83 3a 26 d0 97 13 05 99 f5
[   20.903792] 00000010: 3a 92 53 3c
[   20.948298] alg: hash: Test 1 failed for mv-hmac-sha1
[   20.963387] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24
[   20.969856] 00000010: b7 c3 16 0c
[   20.973550] nsa3xx-hwmon nsa3xx-hwmon: initialized
[   21.303528] ata1.00: configured for UDMA/133
[   21.307825] ata1: EH complete
done.
Setting parameters of disc:[   21.833526] ata1.00: configured for UDMA/133
[   21.837826] ata1: EH complete
  /dev/sda failed!
 (none).
Activating swap...done.
[   22.047138] EXT4-fs (sda1): re-mounted. Opts: (null)
Checking root file system...fsck from util-linux 2.20.1
hdd-root: clean, 41096/1310720 files, 399650/5242880 blocks
done.
[   22.142687] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
Loading kernel modules...done.
Assembling MD arrays...done (no arrays found in config file or automatically).
Cleaning up temporary files... /lib/init/rw.
[   22.503029] device-mapper: uevent: version 1.0.3
[   22.518332] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[   22.584677] random: vgscan urandom read with 102 bits of entropy available
Setting up LVM Volume Groups...  No volume groups found
  No volume groups found
done.
[   24.406429] random: nonblocking pool is initialized
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux 2.20.1
done.
Mounting local filesystems...done.
Activating swapfile swap...done.
Cleaning up temporary files....
Cleaning up...done.
Setting kernel variables ...sysctl: cannot stat /proc/sys/net/ipv6/conf/all/use_tempaddr: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/use_tempaddr: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/lo/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/autoconf: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/autoconf: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/accept_ra: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/accept_ra: No such file or directory
done.
Setting up resolvconf...[   25.660323] NET: Registered protocol family 10
done.
Configuring network interfaces...RTNETLINK answers: File exists
Failed to bring up lo.
[   26.928575] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[   26.934780] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
done.
Starting rpcbind daemon....
Starting NFS common utilities: statd idmapd.
Cleaning up temporary files....
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Starting NFS common utilities: statd idmapd.
[   29.661663] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   29.671686] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Starting rpcbind daemon...Already running..
Starting RRDtool data caching daemon: rrdcached.
[   30.106761] softdog: Software Watchdog Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
Starting watchdog keepalive daemon: wd_keepalive.
Starting enhanced syslogd: rsyslogd.
Starting ACPI services...RTNETLINK1 answers: No such file or directory
acpid: error talking to the kernel via netlink
.
Starting anac(h)ronistic cron: anacron.
Starting periodic command scheduler: cron.
Starting: esekeyd not yet configured: Enable ESE Key Daemon first by editing /etc/default/esekeyd:.
Starting system message bus: dbus.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Loading cpufreq kernel modules...done (none).
CPUFreq Utilities: Setting conservative CPUFreq governor...disabled, governor not available...done.
Starting statistics collection and monitoring daemon: collectd.
Starting MD monitoring service: mdadm --monitor.
Starting nginx: nginx.
Starting NTP server: ntpd.
Starting OpenMediaVault engine daemon:

U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26)



Edited 1 time(s). Last edit at 10/25/2014 07:08AM by addy75.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: