Okay, not too bad as it realy looks you messed up your env's I updated the SATA Uboot, with env's from sata -> please try again with updated files. Here the link again: KD20_sata_boot.tar.gzby Peacemaker - Debian
bodhi Wrote: ------------------------------------------------------- > @Peacemaker, > > > @bodhi here is as well my problem, I've no idea > > why Uboot doesn't load up the harddrives. If I > > choose a newer Uboot (this is the vendors > Uboot). > > I's not working anything (as the original > Stage1 > > can't load fat partitiby Peacemaker - Debian
Okay, my fault: 1. Beeping and Red color is a good sign as your Uboot is running normal. Do you get this by trying to start from sata & nand or only from sata? 2. I forget that the UBoot even from sata try's to load env's from nand and maybe there is the problem. Two options: 1. I'll try to figure out a "better" Sata Uboot so really every thing is load froby Peacemaker - Debian
Okay, am I right here: You have connected at first a Serial/UART and you somehow messed up something ( Uboot, stage1,..). and you can't get a console over UART now. So if you load everything from SATA (Stage1 & Uboot), then you shoud get uboot, stage1 and so UART back to live. If you cant get UART back to live this way there are not so much things to investigate. 1. Check ifby Peacemaker - Debian
Okay, that is really strange. The SATA-boot is a real fail save boot. It should boot, not Linux but Uboot. I got the script from this thread: http://archlinuxarm.org/forum/viewtopic.php?f=55&t=6193 It even is working with these files but Uboot is then more buggy. So redownload the file I uploaded, prepare a hhd & try again. And make sure you uses the right sata port or just tby Peacemaker - Debian
Okay, here it is: SATA-Uboot Its a modified version of Warheads SATA rescue for the pogoplug, so most of the cedits to him :-) What you got to do: 1. Connect a SATA disk to your Linux. 2. Find the disk (/dev/sdX) 3. Modify the disk_create script. Correct the /dev/sdX in second line to your system and uncomment it. 4. Make the script executable. 5. Check if you choose the right disby Peacemaker - Debian
Jacq, are you still able to boot into debian and access via ssh? If you can do this, maybe you can print out the env of uboot. fw_printenv If you are not able to do this, you can boot into uboot via SATA and reflash your Uboot, if you need to do this I'll upload a files for this and a manual. Bodhi, I have already on my list to update 1. post, but had not so much time the lastby Peacemaker - Debian
Okay, didn't know this with 1Gbit problem, with my Netgear switch + TFTP on PogoE02 both Gbit, its working most of the time, but I have seen sometimes these errors as well. Okay, what console do you talking about, SSH, Serial/UART? I have seen that sometimes after rebooting Uboot did not activate the Ethernet. But I've not figured out so far, as debian loads it. As I hadn't mby Peacemaker - Debian
Or perhaps try to direct connect the kd20 to the tftpserver (without any switch, router or so in between), I have read that these errors comes often from half/full duplex or routing problems. I tried to load files from sata but tftp, was more suitible for me. You need to active IDE via ide reset if its not done allready, then you can load from ext2 via ext2load. I don't remember theby Peacemaker - Debian
Okay, load things from usb will not work, from sata you can load data. These errors comes most of the time from bad network settings. As your server has really the IP 213.x.x.x, this might not to be right. The tftp server should be in the same network so 192.168.1.x so check your tftp server settings, and the dhcp server. May be its easyer to set the ip static :-)by Peacemaker - Debian
I uploaded everything via tftp and it is working most of the time quote good. What kind of error do you get? Maybe wie can fix.by Peacemaker - Debian
Hey, @DeDenker: You don't have to replace the uboot. I work with stock Uboot. But you need a way to access it, and there for a serial connection via UART is simply the best. The soldering is not a too hard task and by the way there are "ways" to do such a connection without soldering. Just a thought here: https://hackingecibfocusv2fubirevb.wordpress.com/2012/08/13/a-solder-freeby Peacemaker - Debian
Look at the pictures from crosser @ Google+ i linked it.by Peacemaker - Debian
Jacq Wrote: ------------------------------------------------------- > On the mainboard of Omninas i do not have any pin > to connect uart cable(console). > Do I have to solder this pins for console ? YES, you have to solder them or just pin the conectors: https://gitorious.org/openwrt-oxnas/pages/omninas-kd20-board.jpg https://gitorious.org/openwrt-oxnas/pages/omninas-kd20-serby Peacemaker - Debian
If you "hacked" into your device you can just backup the nand with nanddumper, if not you can do this from debian or from just ask me for my nand backup :-) Befor you start: +Connect to the UART and see if you can access vedors uboot +Make bootdisk (sata or usb) a rootfs partition (ext2 o. ext3) and extract my wheezy_rootfs or bodhi's oxnas rootfs (both will work) Rrecommendby Peacemaker - Debian
@Kluch: Okay I thought you can reach ~40mb/s wright and 80mb/s read. with the original FW Sure, I can do that the next days step by step. But for now: For dismantle the device you can thank Crosser for his pictures: Dissemble KD20 With them you can easy open up the device. For Installation there are 2 ways :-): 1. (what I did): You access vendors U-Boot via UART and configure itby Peacemaker - Debian
Okay, USB 3.0 and Cardreader is still buggy, so I left it out of the Kernel. uImage3.18.1_7 the 3.18.1_7 is my current Kernel One other think is that the samba performace is quite bad, even with some tweaks: read ~30mb/s write ~22-25mb/sby Peacemaker - Debian
I uesd the additional files & all kernel patches from the openwrt trunk. For now I compiled the released 3.18.1 There's not much changed to a prior version. # SATA+Raid's working well ( ok a bit slow 80mb/s r/w) What's not working, buggy, or not well: # USB 3.0 & Cardreader: SD card / USB-Stick is recognized, but If you try access the storage, I got Errors.by Peacemaker - Debian
I just patched 3.18.0 Kernelby Peacemaker - Debian
Okay, I compiled an 3.18 Kernel for my Debian Initrd and did some short tests: uImage3.18_2 Initrd_w What is working: - Booting with original uBoot - Ethernet - Both HDD and Raid Whats not working: - Cardreader - USB3.0 is buggy Everything else I'd tested yet. The next I'll do some more test and hope to fix the usb3.0 & find out the kernel module for the cardrby Peacemaker - Debian
Ohhhhh,... this is looking not so bad. I compiled this openwrt, for so far, it is working. + uboot find 2 HDD + openwrt find 2 HDD - Uboot Mac address must be set manual - usb is not working (ehci timeouts) But as I'm not a big fan of openwrt on a nas, I'll try to patch this for the debian-kernel. For now on everything compiles quite well but I've got to fix the machinby Peacemaker - Debian
Hey, your right so far, Warhead has this driver in an old git. https://github.com/WarheadsSE/OX820-3.1-Linux And beside from raid, cardreader, front usb3.0 and gpio, this non-fdt works so far. The cardreader, front usb3.0 and gpio is I not the hard task. With try to use the raid here I got: [ 273.010000] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 273.020000by Peacemaker - Debian
Freenas on an ARM device, even if it is possible, is not a good idea. 1.: You need an FreeBSD ARM port, with a good working FreeBSD-Kernel. 2.: FreeNAS use ZFS and ZFS loves RAM, RAM and RAM. A good point to start is 1 gb ram / 1 tb hdd. And the ram is higly recomended to be ECC So FreeNAS is a good system for big X86 mashines and not small arm nas. A really intby Peacemaker - Debian
@shv I tryed to use OMV on the PogoE02, but stopped it. I See OMV has a big overhead, so everything is much slower but it comes with some tweaks for smb. And the mainthing with smb is CPU performace. + With OMV I had about 95-99% CPU-Load @ ~28-30mb/s write speed. + Without OMV, I got about 28-30mb/s write speed but only 65-70% CPU load. So as the NSA325 is about 25% faster and youby Peacemaker - Debian
Hey I had a simlar problems with my Pogo E02: Sometimes it worked with full 1Gbit and most of the time only with 100mbit. Plugout-In ethernetcable helped, for a bit of time. But after upgrading to 3.17-fdt these probs are gone.by Peacemaker - Debian
For the initramfs or initrd there are two options. First you build your own rootfs or chroot in an existing rootfs and generate it by: mkinitramfs Or you just load the initrd.img from bodhi's rootfs it's in /boot/ So just load first kernel, then initrd -> boot edit: for building rootfs this is a quite good howto http://www.yoovant.com/debian-wheezy-rootfs/by Peacemaker - Debian
At first try to build an initramfs, this will help to load the right modules. Second where is your rootfs located? Maybe your bootargs are just wrong.by Peacemaker - Debian
Thanks, Warhead I see that the *.dts does not accept an array. But what do you think of the array in the driver (sata_oxnas.c)? In the vendores driver there are similar code for the with an pointer-array for the port address.by Peacemaker - Debian
Sure, but why do you think the drive is goning to inital the controller a second time, with an arraysize of 2 instead of 1 ? As I read the bootlog it panics on instand, and there is no second initial with SATA_OXNAS_MAX_PORTS = 2by Peacemaker - Debian
Hey, the } was a mistake within the copy & past. I tried several ways to input an array QuoteAnd we still need it to truly understand it is _one_ controller with _two_ ports. This really needs to be handled @ the driver code, and then only the difference adjusted @ the dts would be nr-ports. Sry warhead I do not realy get what you mean. I realized that this board has 1 sata contrby Peacemaker - Debian