Dmitriy, Your envs were somehow messed up. There is no disks env. That's why the scan did not work. Interrupt console and setenv disks '0 1 2 3 4 5 6 7' boot Note: if you have used uEnv.txt before to define some envs, once it works you need to set them permanently to avoid this type of problem. Did you use uEnv.txt in the USB rootfs? if you did, that uEnv.txt file neeby bodhi - uBoot
the first partition was formatted with the command mkfs.ext4 -L rootfs / dev / sda1. 1. Try reformat this partition with Ext3. 2. Make sure the Hitachi disk does not contain rootfs. See this post, it might be related to your problem: https://forum.doozan.com/read.php?2,51369by bodhi - uBoot
But I do think I have a backup for the stock OS on internal card, so you can count on it and go ahead and wipe it :) Here they have the installation procedure for the inernal card: https://wiki.debian.org/FreedomBox/Hardware/DreamPlug/InternalMicroSDby bodhi - Off-Topic
Joey, > Found instructions to > open the case and will do that soon. Kind of > tempted to just flash the image onto the card > that's inside. Don't do that. Use the external SD card. IIRC, the card inside contains the Dreamplug stock OS. So you want to preserve that just in case. With that said, I have not read the instruction to flash Freedomx box, so ...by bodhi - Off-Topic
Dieter , Try using the OpenWrt flash_erase. ---- If you flash it in serial console, you also need to flash the default envs image too. Or you can also use a script I had posted to populate the envs.by bodhi - Rescue System
echowarrior108, > also my new question,its about the pcie , I am > never going to use the wifi card , so I came up > with a crazy idea and hope I can make it work, I > found a pcie card with 2 micro usb ports , my plan > it so install it and put in 2 16 gb sandisk cards > and use one as rootfs and the other as linux swap, > do you think that this is doable? Yes, iby bodhi - uBoot
Dmitriy, The new u-boot 2017 and old u-boot 2016 are not much different. However, the new code size and new driver would probably results in a slightly different timing and behavior (especially with EXT4 rootfs). I believe this has brought up some problem in your configuration. QuoteI disabled hitachi hdd Netgear Stora> setenv devices 'ide usb' setenv devices 'ide usbby bodhi - uBoot
Last post moved here: https://forum.doozan.com/read.php?2,56284by bodhi - Debian
Dmitriy, Somehow the Hitachi drive partition was not good. Power up, interrupt netconsole and setenv devices 'ide usb' ide reset ide partby bodhi - uBoot
Quotebut before that everything worked without it Which u-boot version was installed before this uboot.2017.07-tld-1? I suspect that the Hitachi disk partition was not well done. Try this to see if u-boot can see it. Power up, interrupt serial console and, setenv devices 'ide usb' boot post the entire serial console log here.by bodhi - uBoot
Dmitriy , QuoteDevice 1: Model: Hitachi HDS721010CLA332 Firm: JP4OA3EA Ser#: JP2911HD00GTPC Type: Hard Disk Supports 48-bit addressing Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) ** First descriptor is NOT a primary desc on 1:1 ** loading uImage ... ** Bad device specification 0x800000 /boot/uImage ** loading uInitrd ... ** Bad device specifby bodhi - uBoot
enkel Wrote: ------------------------------------------------------- > I found this u-boot: > https://downloads.lede-project.org/snapshots/targets/kirkwood/generic/u-boot-nsa310/ > but it's abnormally big. It should has 512KB, but > those from a link 606KB. I'm afraid to use that > u-boot. That's definitely not stock u-boot. Is there a reason you want toby bodhi - uBoot
schnee, > ICMPv6: ndisc: ndisc_alloc_skb failed to allocate an skb I have not come acrossed this error before. There was a related issue a few years ago, but the proposed patch was widthdrawn/rejected: https://patchwork.ozlabs.org/patch/358850/by bodhi - Debian
echowarrior108, > other is a seagate 5tb drive its much newer and I > cannot format it as I have no drive big enough to > store that much data at this time. That probably explained the error! This looks like a hybrid GBT/MBR paritition structure is used currently. With the new u-boot, this 5TB can be formatted a whole single GPT partition, and then it should work in all OS.by bodhi - uBoot
echowarrior108, > Hi Bodhi, looks like something wrong in the > bootargs, That was OK. It will be set correctly later by the env set_bootargs. > starting USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 5 USB Device(s) > found > scanning usb for storage devices... EHCI > timed out on TD - token=0x800d8d80 > EHCI timed out on TD - tokby bodhi - uBoot
Dieter, You're right to be careful. You should not upgrade u-boot without knowing that it still boots OpenWrt. > Specially, the size of mtd0 does not fit. Can I > still upgrade? No, you can't upgrade u-boot just yet. > What have I got to consider? If you are willing to reinstall OpenWrt/LEDE then see joerg's howto here: https://forum.doozan.com/read.php?4by bodhi - Rescue System
Quote1.I have installed multiple apps in SATA disk and can able to see the files and folders. Looks like the files in the sata disk/boot has corrupted. Is there a way i can fix this and boot from SATA HDD without losing my program data? As habibie suggested, boot with USB first and plug in the HDD. Run checkdisk to see if any error and fix them. For example, e2fsck /dev/sdb1 Quote2.Whaby bodhi - uBoot
Echowarrior108, You have serial console so don't need netconsole, and that has slowed down the boot and difficult to troubleshoot. So at Debian shell, remove it. fw_setenv preboot And then make sure ethernet and all disks are plugged in as they should. Reboot, interrupt serial console at count down and printenv printenv bootargs and go ahead and boot boot Post the enby bodhi - uBoot
meddle, > My usb/serial cable > (www.amazon.com/gp/product/B00QT7LQ88/) > arrived and I was able to fix it, install, and > update Debian to 4.15. this cable worked > perfectly and already had the correct jumpers. > Glad you got it working! > Question:. To create a 'backup' rootfs file after > upgrading, Would this work? > > tar -cvzf myrby bodhi - uBoot
Hi sebr, > now appear to have totally abandoned the NAS > section. Really! that's bad news and also good news in a way. Less competition so other NAS manufacturers will have less incentive to reduce price. OTOH, we'll see Zyxel NAS prices coming down on fire sale.by bodhi - Debian
Meddle, I've just realized I had a typo previously :) sorry about that. Please follow the instruction to reset the envs above using uEnv.txt and try booting.by bodhi - uBoot
Somewhere in this Rescue subforum there was a post that showed how to boot Debian with OpenWrt u-boot. But if you flashed my released u-boot, you can also boot both OpenWrt and Debian.by bodhi - Rescue System
Booting with the default envs using uEnv.txt loading capability using uboot.2016.05-tld-1.environment (the content of the default envs in text format) in u-boot envs tarball uboot.2016.05-tld-1.environment.bodhi.tar 1. Copy the default envs in text format to the rootfs on USB. Assuming the USB rootfs is mounted on another Linux box as /media/sdb1 (If the SD is used for rootfs, then the drby bodhi - uBoot
Dieter, > Openwrt is running fine, but I wanted to use it as > dual boot system, i.e. when there is a USB stick > inserted, it should boot it, but is does not. > Can anybody please tell me what I have to > configure at the console to enable it? > (I have a serial console available) > Is there a tutorial to prepare the USB system? I > am not sure if my old one isby bodhi - Rescue System
Thanks Manuel.by bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?3,55984by bodhi - uBoot
ShapeShifter499, > Do you want me to explain the bridge network setup > with the Pis? Yes. I think the bridge setup would be a good topic. No need to include docker.by bodhi - Debian
Thanks to your question, I can see it is a little bit hard to find info to finish uboot installation. Will beef up the instruction next uboot release.by bodhi - uBoot
2 more setenvs and you're done. fw_setenv mtdparts '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)' fw_setenv dtb_file '/boot/dts/kirkwood-nsa325.dtb'by bodhi - uBoot
Meddle, > I'm trying to flash the latest U-Boot on my > NSA-320. I got to step c and I get a bad block > error when I try to execute "fw_printenv > > current_envs.txt". In step 8 the "Device offset" > was "0x0000", so I changed it to "0xc0000" as > directed. When I changed it back to "0x0000" the > "fwby bodhi - uBoot