Hello alexr, thank you very much, it worked for me. Some hints for others: - you will need a swap partition/file, without, my Pogo went out of memory! - install python2.7 and type: ln -s /usr/bin/python2.7 /usr/bin/python Very cool, thanks again. Regards, Dieterby Dieter - Debian
Hello, it is a shame, my SSD does not feel well with the Pogo: [107171.445283] sata_oxnas: resetting SATA core [107171.815226] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [107171.822348] ata1.00: failed command: DATA SET MANAGEMENT [107171.827778] ata1.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 13 dma 512 out [107171.827778] res 51/04:01:00:00:00/00:00by Dieter - Debian
Hello, is it maybe, because I need an armel binary, and all the available binaries are armhf? I can not change to armhf, I assume, it it a cpu property, right? Regards, Dieterby Dieter - Debian
Hallo JT, thank you for your hint. Yes, but this does not work either: root@FHEM:~/tmp/node-v10.14.1# apt-get install nodejs Reading package lists... Done Building dependency tree Reading state information... Done Package nodejs is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another souby Dieter - Debian
Hello, I want to use my Pogoplug for my smart home. Unfortunately, I need node.js on it (for e.g. zigbee2mqtt). However, I can not install is. Using the Debian Repo I get: yoot@FHEM:/usr/local/lib/nodejs/node-v10.14.1/bin# apt-get install nodejs-legacy Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. Thby Dieter - Debian
Salut bodhi, thank you so much for your help! I have given up working on EXT4. I moved to ext3 and now it is working! Even the kernel update works fine, excellent! The note 2, however is not clear to me. It is not enough, to put init=/bin/systemd into the /boot/uEnv.txt, right? do I need to add usb_set_bootargs='setenv bootargs console=$console root=$usb_root rootdelay=$usb_rby Dieter - Debian
Sorry, forgot about the man pages! Checked them and found them in the man pages for ext4. It seems, that delalloc and nodelalloc are mount options, not format options. I can't set them as mount options in uboot, can I? I probably simply move to ext3 now and check if that works. Figured out, that trim should be supported, too. Anyway, thanks a lot! Dieterby Dieter - Debian
on my x84 Debian system, the option does not exist: root@openmediavault:/tmp# mkfs.ext4 -O nodelalloc /dev/sdj1 mke2fs 1.43.4 (31-Jan-2017) Ungültige Dateisystem-Option angegeben: nodelalloc root@openmediavault:/tmp# cat /etc/debian_version 9.6 However, because ext4 support trim, it might be gernerally a good idea for an SSD, right? Is there another way to fix the problem?by Dieter - Debian
Hello Bodhi, it seems, you are on the right track (as always ;-) ) : U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700) OXNAS OX820 DRAM: 128 MiB NAND: 128 MiB In: serial Out: serial Err: serial Net: dwmac.40400000 Hit any key to stop autoboot: 0 OX820> ide reset Reset IDE: Bus 0: OK Device 0: Model: SanDisk SDSSDP128G Firm: 2.0.0 Ser#: 123651401099by Dieter - Debian
Hello, one partition only, ext4. root@pogoplug:~# ls /dev/sd* /dev/sda /dev/sda1 /dev/sda2 /dev/sdb /dev/sdb1 root@pogoplug:~# e2label /dev/sdb1 rootfs root@pogoplug:~# fdisk /dev/sdb Command (m for help): p Disk /dev/sdb: 128.0 GB, 128035676160 bytes 30 heads, 63 sectors/track, 132312 cylinders, total 250069680 sectors Units = sectors of 1 * 512 = 512 bytes Sector sizeby Dieter - Debian
Hello bodhi, I updated uboot. but it is not booting my ssd, yet: Reset IDE: Bus 0: OK Device 0: Model: SanDisk SDSSDP128G Firm: 2.0.0 Ser#: 123651401099 Type: Hard Disk Supports 48-bit addressing Capacity: 122104.3 MB = 119.2 GB (250069680 x 512) no USB devices available Partition Map for IDE device 0 -- Partition Type: DOS Part Sby Dieter - Debian
Hello bodhi, here you go: U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS DRAM: 128 MiB NAND: 128 MiB In: serial Out: serial Err: serial Net: Led: GREEN mii0 Main Loop Hit any key to stop autoboot: 0 autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run dt_bootcmd_usb bootdelay=10 console=console=ttyS0,115200n8 dt_bootcmd_usb=usb staby Dieter - Debian
Hello, I have followed the rootfs Instrauctions of https://forum.doozan.com/read.php?2,16044 to transfer the Debian rootfs to an SSD.. I attached the SSD to my Pogoplug V3's SATA port and I am trying to boot now. I was hoping my uboot (U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS) would detect it and simply boot - but it does not. I searched now, if I need to change tby Dieter - Debian
Dear bodhi and Joerg, I have no clue, what went wrong so far - but now it is working, both, Debian & LEDE!! (after following again the receipe above, was it the wrong mtd1 entry?) Thank you so much! I am a happy chappy now! :-) Regards, Dieterby Dieter - Rescue System
Hello Bodhi, your're right, but I followed exactly joerg's steps to set the envs, starting with the import of uboot.2016.05-tld-1.environment.img. Then I added his proposals, step by step, copy and paste. Unfortunately, with my knowledge (or rather "no-knowledge"), I am lost. Thanks for your stamina! So here we go: root@LEDE:/# cat /proc/mtd dev: size erasesizeby Dieter - Rescue System
Hi bodhi, thanks, that did the job, the other errors remain, still no dual boot possible ... Dieterby Dieter - Rescue System
Hello Joerg, thanks, how embarrasing! Fixed that, but ended up where I have been before: U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) Seagate FreeAgent DockStar SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Using egiga0 device ping failed; host 1by Dieter - Rescue System
Hello, I tried again, but it is still not working?!? Seagate FreeAgent DockStar SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Using egiga0 device ping failed; host 192.168.180.21 is not alive Hit any key to stop autoboot: 0 DockStar> tftpboot 0x8000by Dieter - Rescue System
Hello, ok, system upgrade worked, I am able to run LEDE now. :-) However, it seems my envs are not fine, yet, I can not boot from stick. I inserted a stick, prepared as bodhi told me to, but Lede still boots and I get the following error messages: U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) Seagate FreeAgent DockStar SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Cacheby Dieter - Rescue System
Is something wrong with my mtd? Here is it: root@LEDE:/# cat /proc/mtd dev: size erasesize name mtd0: 000e0000 00020000 "u-boot" mtd1: 00100000 00020000 "u-boot environment" mtd2: 00200000 00020000 "second stage u-boot" mtd3: 0fe00000 00020000 "ubi" These are my boot message, there is an UBI Error: DockStar> usb reset; fatload usb 0 0by Dieter - Rescue System
Hello both of you, First of all, thanks again for your support! I followed joerg's suggestion and I believe I got pretty far. uboot is updated and so on. I booted lede, but the opkg installation failed: root@LEDE:/# opkg install ca-bundle ca-certificates libustream-openssl luci-ssl ubi-utils kmod-mtd-rw Installing ca-bundle (20170717) to root... Installing ca-certificates (201by Dieter - Rescue System
Dear bodhi, the uboot seems to have problems with your commands: All the setenvs were fine, but then: ... dockstar => boot (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found loading uImage ... Unknown command 'load' - try 'help' loading uInitrd ...by Dieter - Rescue System
Hello bodhi, I did not get very far: dockstar => usb start (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found dockstar => ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr 3232 bytes read in 301 ms (9.8 KiB/s) dockstar => source 0x800000 ## Executby Dieter - Rescue System
Hello bodhi, here it is: U-Boot 2014.10 (Jan 02 2016 - 02:33:53)Seagate FreeAgent DockStar SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 dockstar => printenv baudrate=115200 bootargs_root=ubi.mtd=3 root=ubi0:rootfs roby Dieter - Rescue System
Hello bodhi, Thank you for your ongoing excellent support. I got now this far: I generated my new USB Debian rootfs. But I don't know how to alter the envs to boot from usb. Could you please, once more, please help me? Thank you so much, Dieterby Dieter - Rescue System
Hello bodhi, I tried, and still get the same message: root@OpenWrt-Dockstar:/tmp# /usr/sbin/flash_erase /dev/mtd0 0 4 /bin/ash: /usr/sbin/flash_erase: not found So again, I must try it with the serial, I see no other way, do you? Before I brick my Dockstar, is the input for the serial connection above right, or does it need to be adjusted? How do I flash the envs? I currently donby Dieter - Rescue System
Hi bodhi, I am trying to update uboot, now, but flash_erase is not working: root@OpenWrt-Dockstar:/tmp/tools# ls busybox flash_erase fw_printenv nandwrite e2fsck fw_env.config nanddump root@OpenWrt-Dockstar:/tmp/tools# ./flash_erase /dev/mtd0 0 4 /bin/ash: ./flash_erase: not found root@OpenWrt-Dockstar:/tmp/tools# /tmp/tools/flash_erase /dev/mtd0 0 4 /bin/ash:by Dieter - Rescue System
Hi bodhi, I am a bit scared to update uboot, because my mtd sizes look very different: root@OpenWrt-Dockstar:/tmp/tools# cat /proc/mtd dev: size erasesize name mtd0: 000e0000 00020000 "uboot" mtd1: 00020000 00020000 "uboot_env" mtd2: 00100000 00020000 "second_stage_uboot" mtd3: 0fe00000 00020000 "root" Specially, the size of mtd0 does nby Dieter - Rescue System
Hi bodhi, thanks for your support. Ok, I will try to flash your u-boot tonight. Will the boot paremeters of Openwrt remain the same as before? Or how do I ensure, that my Openwrt will boot again? Regards, Dieterby Dieter - Rescue System
Thanks! It is Debian. As I said, I am nicht sure if it is ok. I would generate a new one, if I knew how. I have several linux systems running, but no other Dockstar. Dieterby Dieter - Rescue System