Thanks bodhi! Found this post from WareheadSE: https://archlinuxarm.org/forum/viewtopic.php?f=55&t=1172&start=20#p7533by schnee - Debian
I thought about that, but i would like to use an ESP8266 to monitor the serial output and reboot the pogoplug in case it freezes. I would like to do it without cutting the power, as cutting the power would also reboot the ESP8266 and it needs additional electronics added to the ESP (relay and transitor etc).by schnee - Debian
Maybe this is not the best place for this post, but I did not find any better.... I am trying to install a reset button for the pogoplug v3/pro, but unable to find anything look like a reset pin on the board. Does anyone know if such point exist? Thanks Schneeby schnee - Debian
bodhi Wrote: ------------------------------------------------------- > Do you have a GoFlex Net/GoFlex Home/Pogo V4? I > wonder how this SSD behaves in these small plugs > when you plug in the drive directly to the SATA > slot. It might be a better verification than the > laptop or other boxes that you have tried. I do not have any of those devices unfortunatelly. I willby schnee - Debian
Hi Bodhi, by any chance did you look into this issue while you were working on the new release (https://forum.doozan.com/read.php?2,16044,38109#msg-38109) Thanksby schnee - Debian
After reinstalling the drive with the root fs and completely redoing the uboot params, the Pogo boots from the 32G SSD with kernel 4.4.54. Here are the redone uboot envs: U-Boot 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12) for OXNAS DRAM: 128 MiB IDE: Bus 0: OK Device 0: Model: 25000128-02 Firm: 505ABBF0 Ser#: DSHKSH124404005 Type: Hard Disk Supports 4by schnee - Debian
I put together a USB boot, and yes the drive recognized in Linux: root@debian:/# uname -r 4.4.54-oxnas-tld-1 [ 98.557393] sata_oxnas: resetting SATA core [ 98.571842] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen [ 98.579038] ata1: SError: { PHYInt } [ 98.582661] ata1: hard resetting link [ 99.490158] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310by schnee - Debian
Changes the uboot enviroment (yesterday i used a copy of a working box). Here is the boot result with 4.4.54 (4.4.38 has the same result): U-Boot SPL 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12) Boot device: SATA Attempting to set PLLA to 800 MHz ... plla_ctrl0 : 0000030a plla_ctrl1 : 00400000 plla_ctrl2 : 007f0068 plla_ctrl3 : 00000193 PLLA Set Bus 0: OK Device 0:by schnee - Debian
And this is the serial log with kernel 4.1.0 4488520 bytes read in 758 ms (5.6 MiB/s) 7033 bytes read in 29 ms (236.3 KiB/s) magic: 0xd00dfeed totalsize: 0x1b79 (7033) off_dt_struct:by schnee - Debian
here you are OX820 # run ext4_ideboot 4621824 bytes read in 825 ms (5.3 MiB/s) 7033 bytes read in 29 ms (236.3 KiB/s) magic: 0xd00dfeed totalsize: 0x1b79 (7033)by schnee - Debian
Today i played with an other pogoplud with a SSD Kingstone SHS450S3/32G It works with kernel 4.1.0, but does not boot on 4.4.38 or 4.4.54 This is the console output: [ 1.139781] Key type encrypted registered [ 1.160573] UBI error: cannot open mtd data, error -2VFS: Cannot open root device "sda2" or unknown-bl ock(0,0): error -6 [ 1.173859] Please append a correct &by schnee - Debian
I did some test today with debian: Installed debian stable --> 3.18 kernel --> upgraded to strech --> 4.9.0.2-amd64 kernel --> reboot The system works fine. So either the driver is fixed in 4.9 or it would work fine with any 4.X kernel in debian-amd64by schnee - Debian
> I don't recall if you have tried this SSD on anoth > er box as SATA drive? Bodhi, i used to use this SATA SSD in a laptop with ubuntu linux (12.04LTS) in the past and it worked fine. I did not try it recently though. If i attach this as a normal SATA drive to my 14.04 Ubuntu desktop it works fine. Schneeby schnee - Debian
Hi Bodhi, i see that you released new kernels in the 4.4.X line. By any chance did you look into the sata driver? Does it make sense to start testing again with the problematic HDD? Thanks schneeby schnee - Debian
I was a bit busy with some other things, so i only got back to testing today.. I made my pogo to boot from USB and attached the disk to it after it booted up. The result is the same, the drive is failing with "ata1.00: failed to set xfermode (err_mask=0x5)" full log output on the serial console: [ 88.996234] sata_oxnas: resetting SATA core [ 89.010711] ata1: exception Emaby schnee - Debian
bodhi, corrected the bootargs, but the result is the same Quote 2) The SATA initialization might be because a change in driver. SSD sometime is picky (HDD is never so). Some SSD could never be used for booting. In this case, apparently kernel 4.1 works, so it might be tthe difference in sata_oxnas driver between 2 kernels. I think the best way to solve this SATA problem is either: 1by schnee - Debian
Hi bodhi, thanks for the reminder. I indeed forgot to update the dts files. I did it now, the result is the same, but the time to get there is longer - attached the boot log. Also edited the envs to use rootfs and 10 sec delay. I flashed your envs to the ssd, but it did not work, so it started with defaults. current uboot.env autoload=no baudrate=115200 bootargs=console=ttyS0,115200nby schnee - Debian
bodhi, i installed today the new uboot on my sata drive with partial success. The new uboot loads, but i still use the old SPL from warehead. The results are the same -> fine boot with 3.17, no boot with 4.4. The main difference is that now it drops to busybox, instead of a loop trying to boot. The error is get is: [ 2.853009] Freeing unused kernel memory: 228K (c080f000 - c0848000by schnee - Debian
Hi bodhi, it is really great that you don'T let our small plug computer to become obsolete! Huge thanks for that! I just recently installed 4.4.38 on all my pogoplugs and now they work fine. So far i used 160 GB 2.5' SATA drives as i boot completely from SATA. Some of those drives i replaced with 160 GB SSD and everything went fine. Now i received a 180 GB SSD and the trouble starteby schnee - Debian
bodhi Wrote: ------------------------------------------------------- > In that case, you should install the new u-boot 20 > 15.10: > > http://forum.doozan.com/read.php?3,16017 Thanks for the suggestions! I looked into the uboot thread already. Now i modified my uboot envs, based on the one posted there. See the result below. As on my setup everything is on the sata drive iby schnee - Debian
bodhi Wrote: ------------------------------------------------------- > You are not booting with uInitrd, only uImage and > DTB were used in booting. That's why the LABEL=roo > tfs did not work. The initrd is responsible to fin > d that partition (using the label) for the kernel > to mount. Is it intentional or an oversight? I have minimal knowledge about uboot. I siby schnee - Debian
bodhi Wrote: ------------------------------------------------------- > > > setenv bootargs 'console=ttyS0,115200n8 root=LABEL > =rootfs rootfstype=ext4' > > Tried your suggestion but it did not work. Boot started but ended with kernel panic. See attached log. Filesystem labels look good: root@xxxxxx:~# ls -l /dev/disk/by-label total 0 drwxr-xr-x 2by schnee - Debian
bodhi Wrote: ------------------------------------------------------- > Hi schnee, > > > > > Will try to dump the mtd0 from my other pogo tom > or > > row probably, but tbh i expect the same result > > You meant mtd1? > Hi bodhi! yes i meant mtd1 Attached the complete boot log to the message (pogoBoot.log) printenv.log has the uboot variabby schnee - Debian
afaik nandwrite -n /dev/mtd1 ./mtd1.stock_pogo_v3_rootfs is the same as nandwrite --noecc /dev/mtd1 ./mtd1.stock_pogo_v3_rootfs root@schnee:~/tools# cat /proc/mtd dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 0720by schnee - Debian
Quote bodhi Wrote: ------------------------------------------------------- > Does this mean the flashing works fine, or boot fine? nandwrite finished without errors. It still can't boot from the flash, but boots from the sata drive, but spams with the mtd1 ecc errors and ubi erros Quote > > > The error could be that: > > 1. The rootfs tarball is bad Whicby schnee - Debian
Thanks LeggoMyEggo & bodhi for the stock root image! I received a mis-flashed pogoplug pro recently (i think mtd0 and mtd1 went through a flasherase). It can't boot on its own but works from sata. So i started to reflash mtd0 following http://forum.doozan.com/read.php?3,16017 (this went fine) now i tried to reflash mtd1 with the above image with nandwrite -n /dev/mtd1 mtd1.stock_poby schnee - Debian
Hi bodhi, do you have any plans to compile a new kernel for the Pogo? Thanksby schnee - Debian
As i remember cron is not installed by default, run "apt-get install cron" as root to install it.by schnee - Debian
1st of all: Thank you Bodhi for the 4.1 kernel and the hiddev support. Now my pogo can handle the UPS next to i properly :) I also created an "installer". With that anybody can prepare a sata harddrive with which the pogo can boot from its sata port. Unfortunatelly to reach the sata port the pogo has to be opened. As these devices are out of warranty anyway this won't hurt anyby schnee - Debian
Next challenge: trying to get apcupsd working.... I have a small APC ups with USB connection. Connecting it to the pogo it shows up in lsusb: Bus 001 Device 012: ID 051d:0002 American Power Conversion Uninterruptible Power Supply dmesg [84001.411456] usb 1-1.3.1: new low-speed USB device number 12 using oxnas-ehci [84001.621964] usb 1-1.3.1: New USB device found, idVendor=051d, idProdby schnee - Debian