rebooted a couple more times, looked ok, no more resets, even went through the apt-get upgrade with no issue started installing the omv. as soon as i got to Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 12699 files and directories currently installed.) Removing busybox-syslogd (1:1.22.0-9+deb8u4) ... [....] Stopping busybox' klogd implemeby veriqster - Debian
while typing the previous it continued with this [ 312.738721] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 313.018711] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 323.288431] usb 1-1: reset high-speed USB device number 2 using orion-ehci [ 323.439458] sd 0:0:0:0: Device offlined - not ready after error recovery [ 323.446307] sd 0:0:0:0: tag#by veriqster - Debian
reinstalled uboot, latest, exactly according to instructions. created a 4.4 rootfs and booted it. the only thing I modified is the fstab this is all I have in it LABEL=rootfs / ext3 noatime,errors=remount-ro 0 1 tmpfs /run tmpfs nosuid,noexec,size=20M,nr_inodes=4096 0 0 boots with some warnings. once at login I ran apt-get update and ran into the same "reset USB&quby veriqster - Debian
exactly the same result with a 32G Sandisk ultra stick (the ones that can also be plugged into the micro usb from the other end of the stick). But the old 2GB still works, I just can't replicate it.by veriqster - Debian
and here is the result of trying to install the armel script. makes me wonder if this is related to the drives rather than the software, they are all 32GB Sandisk Cruzer Glide that came as freebies with the WD drives I bought from BestBuy. Setting up libdconf1:armel (0.26.0-2+b1) ... Processing triggers for man-db (2.7.6.1-2) ... [ 503.265396] usb 1-1: reset high-speed USB device numberby veriqster - Debian
you know, the funny thing is I have a 2GB old sandisk cruizer that I somehow installed this OMV onto debian 9, don't know how, it was all in this process of trying and failing, I just booted from it to see what's on it and realized the OMV was working. so I went ahead and created a tar file of the filesystem and then tried to untar it onto larger and newer drive (tried a few). I useby veriqster - Debian
I have, the only thing I found was the armbian config at https://github.com/armbian/config. I wonder what happens if I install it given how little resources the board has I expect it will simply drag like heck. creating a new rootfs as we speak and will try it. I'm stuck at this point. Would it be safe to run the uboot install script with the no verify option? Is that going to provideby veriqster - Debian
I think that was related to using ext4 on the usb stick, a 32GB Sandisk Cruzer Slide. not sure what to do now as I cannot get it to install the OMV anymore, tried repeatedly and failed, even repeated attempts to start with a fresh rootfs. I am contemplating in using the debian8 rootfs but that one will not boot under current environment. in order to rule out any and all extraneous things, coby veriqster - Debian
it throws a [ 21.729007] usb 1-1: reset high-speed USB device number 2 using orion-ehci and freezes it was also printing messages about adding time but I think I fixed that via /etc/ntp.conf, activated different serversby veriqster - Debian
and this is all it did while left running over night, no progress on the terminal that was installing OMV [ 1104.708843] bfe0: 00000000 bea4c79c 004730d8 b6f2ec8c [ 1195.988134] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating. [ 1226.669790] INFO: task kworker/u2:1:63 blocked for more than 120 seconds. [ 1226.676639] Not tainted 4.19.0-kirkwby veriqster - Debian
and after a couple more minutes waiting [ 918.397961] systemd[1]: anacron.timer: Adding 2min 7.836199s random time. [ 918.405967] systemd[1]: apt-daily-upgrade.timer: Adding 35min 42.524551s random time. [ 921.877301] systemd[1]: anacron.timer: Adding 2min 46.031036s random time. [ 921.885432] systemd[1]: apt-daily-upgrade.timer: Adding 2min 27.092424s random time. [ 925.565517] systeby veriqster - Debian
latest occurrence: output from terminal running the install update-initramfs: Generating /boot/initrd.img-4.19.0-kirkwood-tld-1 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. output from the terminal connected via serial 918.397961] systemd[1]: anacron.timer: Adding 2min 7.836199s random time. [ 918.405967] systemd[1]: apt-daily-upgrade.timer: Adding 35min 42.524551s random timby veriqster - Debian
it also throws a lot of messages like this [ 493.451382] systemd[1]: apt-daily-upgrade.timer: Adding 48min 26.468635s random time.by veriqster - Debian
just my luck with these devices, bumped into something else. it works fine until I try to install OMV on it and then during install it throws a [ 270.568958] usb 1-1: reset high-speed USB device number 2 using orion-ehci and it freezesby veriqster - Debian
Fixed, sorry for the disturbance. Booted 4.4 and flashed latest U-Bootby veriqster - Debian
Formatted the stick with mke2fs and put the 4.12.1 on it according to instructions. recreated uImage. now I get the following at which point the front light goes off and everything stays put. U-Boot 2011.12 (Apr 18 2012 - 23:08:20) Seagate GoFlexNet SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net:by veriqster - Debian
Hi, I got a go flex net and ran the "kirkwood-debian-wheezy.sh" script on it. It completed and created the usb stick as supposed. I was able to boot and ssh into it after but noticed it's a really old debian so I decided to make a new rootfs. Little did I know that it will not boot with the new rootfs, tried both the 4.4.0 and the 4.12.1; no luck below please find the environby veriqster - Debian
If you can dd your drive to an iso file I'd more than happy to have a copy of that. The spinup time seemed to not be an issue, at least I did not see any.by veriqster - uBoot
I would still like to get the SATA boot down pat, the first unit I bought it still (very rarely) acting up on reboot, it does not recognize the USB devices.by veriqster - uBoot
yes I did, the 2A 12V power brick is more than sufficient for running this thing. In fact it will power a 3.5in HDD as well with no problem. I have another pogo and, be that happenstance or just my luck but in my experience the power board in these things are bottom of the barrel or not designed for ANY load. While this one was having issues even booting with the stock board, the other one bootby veriqster - uBoot
Took out the power board, it supplies 11.95V at no load, makes a buzzing loud noise under no load so I assume some caps or something else is going on it. Connected a 2AMP 12V power supply and the issue has not surfaced since. Ordered a 12V 5A power board off EBay and will update once I have that installed. Thank you for the help figuring this out!by veriqster - uBoot
yup, it's a little power board at the base of the device, takes 120 via a tv style power cord and puts out god knows what. I could try and measure it but not sure how accurate that would be, especially given something is acting up. An than there's the question of amperage, I assume having 4 USB ports it would require something of at least 3 amps output.by veriqster - uBoot
most definitely a hardware problem, it boots even with autoboot just fine as long as I leave it alone or about 30 min. If I try and reboot or shut down and restart immediately it acts up randomly, the more I use it (like the dist-upgrade I did) the more more it acts up. Do you know what kind of power it takes? I have some power bricks around the house and could try and rig something to test thby veriqster - uBoot
booted, did an apt-get update and apt-get dist-upgrade rebooted and now this is what I get U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700) OXNAS OX820 DRAMby veriqster - uBoot
and now I have another issue, this thing is CURSED!!!! [....] Checking root file system...fsck from util-linux 2.29.2 rootfs: clean, 33009/247008 files, 390990/986363 blocks done. [ 10.264046] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro [....] Activating lvm and md swap...[ 13.845619] Adding 393212k swap on /swap. Priority:-1 extents:11 across:1584856k FS done. [....] Checkiby veriqster - uBoot
this is what I get now 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> usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80 unable to get device descriptor (erroby veriqster - uBoot
OX820> printenv bootargs=root=/dev/sda1 rootfstype=ext3 console ttyS0, 115200 mem=128M bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm 0x60500000 0x60e00000 0x62c00000; else bootm 0x60500000 0x60e00000; fi; else if run load_dtb; then bootm 0x60500000 - 0x62c00000; else booby veriqster - uBoot
reinstalled uboot according to https://forum.doozan.com/read.php?3,16017 this is what I get from a cold start: U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700)by veriqster - uBoot
well, hit another snag. The drive worked until I rebooted and than nothing. Upon logging into the serial console I found that it does not boot I made another drive on Linux exactly according to the instructions. It worked once and upon reboot the same story. I made a couple more drives, including an usb hdd and the story repeats itself every time: it boots, I reboot is and the same error. Iby veriqster - uBoot
I know I took a parallel road on extracting that archive, for some reason my ubuntu box did not want to execute the tar command on it so I extracted the files in the tarball with 7zip under windows and than just copied them recursively. going through the pages that I've used for creating the root file system I think I figured out my original mistake, I used the "tune2fs -L ROOTFSby veriqster - uBoot