Just seeing these messages now. Unfortunatly I have long since bricked my ix2-200 and thrown it in the bin. I also either lost or possibly deleted all the sources I had for it. (unless they are burried in a corner of my new server / nas somewhere)by Buttzy10169 - uBoot
@renojim Did you try looking at the arch wiki? its easy to set the time aparently with this: https://wiki.archlinux.org/index.php/Systemd-timesyncd And on the systemd thing. I vote for systemd everyone shouldnt be held back on sysv or whatever just because a few people dont know how (or refuse to learn) to use systemd. I have switched all my plugs and linux machines over to systemd andby Buttzy10169 - Debian
@bodhi Sorry I took so long to reply. After reading your reply realised my mistake. When I set the mtdparts I ended up with this: 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) instead of: mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(stby Buttzy10169 - uBoot
@bodhi Im having an issue updateing to the latest uboot. (2014.07) Currently on the test version you released for the (2013.10) nsa325. when I cat /proc/mtd I get: dev: size erasesize name mtd0: 08000000 00020000 "orion_nand" Im using the default uboot env you posted in this thread with ethaddr changed and root set. Im also using your stock jessie 3.18.5 rootfs.by Buttzy10169 - uBoot
Tested with iperf today a little test on both box's the nsa325 is getting nearly 1Gbit. The NFS share is mounted with rsize=32768 wsize=32768 this gets me around 100 MBytes (maybe more) a sec going from my main computer to the server. The nsa320 through the powerplugs is getting about 85 Mbits.by Buttzy10169 - Debian
I just wanted to see what kind of speeds people were getting on their box's. I have an nsa325 on a gigabit network and my tests with rsync over an nfs share from the box are about 35MB's. And on an nsa320 through a 500mbit plugnetwork max's out around 9.5MB's with rsync and an nfs share. I just wanted to see if these speeds were good or bad compared to others. On theby Buttzy10169 - Debian
Try reading all the instructions. The fat32 step is for a script that changes the uboot variables on the stock uboot. And these instructions were written a while ago so I dont know if they still work with Bodhi's latest roots.by Buttzy10169 - Debian
Nekitip, You must a done something wrong. Just a few days ago I made my own quick and dirty Jessie (not upgrade) roofs for the nsa325v2 and used Bodhi's 3.17 kernel and no issue's with Jessie except some systems logind error on the serial output. Updating in my experience from 1 Debian release to the next never turns out well the is changes too much between releases.by Buttzy10169 - Debian
In case you haven't tried Eddie completely power off the box then turn on and check the box I had to do that after updating the uboot on my nsa325v2 before both drives were recognised.by Buttzy10169 - Debian
bodhi, I have a second serial gadget somewhere in my little server room just gotta find it an see if its still working. I think the problem might be with the cable or the cable connections I use to connect the serial adapter to the 3.5mm jack.by Buttzy10169 - Debian
bodhi, Took the plunge and flashed the new uboot and the second sata seems to be working now. Im using the uboot you pointed to 2013.10 version and kernel 3.18.1.by Buttzy10169 - Debian
Yeah I've been trying that and just hasn't worked its possible I have a dodgy connection on the serial. I might just flash anyway since a few people have it working. Might try that uboot you linked first though Eddie87.by Buttzy10169 - Debian
bodhi, Yes the UART version and the band version through UART but at most I think I got up to 30%.by Buttzy10169 - Debian
bodhi, I have tried both versions of the uboot in that thread and so far have not been able to get it to boot. I think the highest I got on it was about 30% yesterday.by Buttzy10169 - Debian
bodhi, I have tried several times to boot the new uboot via UART but have not been successful. Maybe the cable / connection I'm using is to unstable. Is it safe to just flash the new uboot? And is there anything I need to do after? Besides setup the uboot to boot Debian? As in is there any special settings from the original uboot I need to keep / transfer? edit: I tried compiby Buttzy10169 - Debian
bodhi, Yeah after a reboot its like it doesnt even try to detect the second sata drive. im attaching the output of the "ls -lR /proc/device-tree/" command. edit: At first look from me theres a: /proc/device-tree/ocp@f1000000/pin-controller@10000/pmx-pwr-sata1: for sata 1 but none for sata 0by Buttzy10169 - Debian
Bodhi, But even with the boot that I got that boot log from the second sata is not showing up in Debian.by Buttzy10169 - Debian
bodhi, Just tried the latest rootfs with the 3.17 kernel and the dtb for the nsa325 and only 1 (the first) of the sata ports appears to be working when debian is booted (the first sata port). The second port does not register the drive connected. Both drive's are the same make and model. just had a look in the patch and seen this: + sata1_power: regulator@3 { + compatible = &qby Buttzy10169 - Debian
No unfortunatly wont be able to get serial console until after xmas as i have the box packaged up as a gift at the moment. So I will try get it asap. It's possible it could end up being a problem with cheap usb stick but will have to wait and see.by Buttzy10169 - Debian
No even before installing OMV i could load uImage and uInitrd from usb but not rootfs. I think i tried rootfs as ext3 and 4 but it would not boot tried different settings in uboot and nothing. Then i put rootfs on sata out of curiosity and it booted straight away but the usb did not show up in debian after boot.by Buttzy10169 - Debian
There is power to the usb ports as i load the uImage and uInitrd from a usb stick then the rootfs is on a sata drive inside the nas. So somwhere between the loading of the kernel and the finished boot something is going wrong with the usb's. The only thing changed between your stock roofs and what im using is the installation of openmediavault i think. As in i used your rootfs booteby Buttzy10169 - Debian
bodhi, After plugging in the usb nothing at all happens in dmesg or any where else as far as i can tell no errors or anything. this is the output of lsmod: Module Size Used by softdog 1995 0 quota_v2 3820 2 quota_tree 6884 1 quota_v2 ipv6 301690 54 evdev 9355 1 fixedby Buttzy10169 - Debian
I dont have serial access to the device at the minute as its a gift for someone for xmas so its all back together for now. Its not the stock uboot though i upgraded it a few months ago i think its daveygravey's?(i forget the name) uboot from a while back. im also using the 3.17 kernel with the dtb appended as per your instructions on the first page. Which log do you need to see is it tby Buttzy10169 - Debian
The USB issue i mentioned a few posts back. Basically no usb drives i plug into the usb's are showing up. I posted the dmesg a few posts back aswel. and if i do an lsmod it looks like there is no usb modules loaded. I have openmediavault installed on the nsa32. I remember something before about issue's with openmediavault on these box's. Also i wasnt able to boot from usb eitby Buttzy10169 - Debian
Thanks Bodhi. Will the commands for flashing be the same as for absintos? And any idea on the usb's problem?by Buttzy10169 - Debian
I dont have a bootlog handy at the minute but i remember it did say something about detecting usb's. I will try get a dmesg later. I remember others had issues after installing openmediavault (which i have done). I might try with the stock rootfs again to see if that brings the usb's back. EDIT: Finaly got the dmesg everything looks ok to me but lets see what you think. Alsby Buttzy10169 - Debian
Im having issues with this new rootfs on an NSA320 no devices pluged into the usb's are being detected any idea whats going on? Also is there a new uboot for the NSA320? absintos mentoned up above uboot.2013.10-tld-1.nsa320.mtd0.kwb. edit: looks like no modules are being loaded for usb.by Buttzy10169 - Debian
if you cat the trigger file you will get a small list 2 of the options should be for hdd. like ide1 something and ide2 ( not sure what they are don't have access to mine at the minute to check) then you can just put in your rc.local file: echo (trigger name) > "/sys/class/leds/(led name)/trigger" or something to that effect then the hdd led will blink whenever the hddby Buttzy10169 - Debian
there are posts about the LEDs in Bodhi's thread I guess I forgot to add them here. basically you do: ls -l /sys/class/leds find the hdd leds then: cat /sys/class/leds/(led name)/trigger it gives a list of triggers then: echo (trigger you want) > /sys/class/leds/(led name)/trigger (on my tablet so difficult to give proper full instructions)by Buttzy10169 - Debian
since its a memory error is it possible they are just using too much memory and since memory is so limited in the device its running out? ( I don't know much about lvm and such )by Buttzy10169 - Debian