Hi bodhi! I have been working on this for some days now. The loop is working fine, but it would never boot. I tracked the problem down to the point, that the load command from UBoot (I also tried ext4load) would never work. Issuing the load command would always (100%) lead to "IDE read: device 0 not ready", regardless the partition was found before. I think there's nothing weby ElMariachi - uBoot
I am always just using: nc -lu 192.168.1.35 6666 Only this single line. And it reliably enables monitoring and interactivity with the connected GoFlexNet for me.by ElMariachi - uBoot
I'm not too lazy I hope :) I already ha some ideas: I made a modified uEnv.txt and simply set bootdev and dev manually in this, in an own variable: scan_fake=setenv device 0:1; setenv bootdev ide (I'm not yet sure about the correct parameters for device) then I changed the normal bootcmd from: bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; if run bootcmd_exec; thby ElMariachi - uBoot
Hello bodhi! I think there's a missunderstanding, or I didn't describe it precisely enough. This SSD has some very special behaviour. The problem is, that the SSD being correctly recognized by UBoot is just completely random, even at the first scan. It might be the first scan that is working, or it might any subsequent scan. But also after it worked once, then the next try is random aby ElMariachi - uBoot
Hi Bodhi! It's me again, with that annoying Transcend SSD. The problem is, that this SSD doesn't work reliably after the IDE reset. Sometimes it's working and some times it's timing out. This is not solved by increasing the time span between the ide resets, it seems just completely random. So what I need is a boot sequence that repeats the ide reset until the SSD is in worby ElMariachi - uBoot
As you said sour OS was booting, you just would need to add the right lines to /ets/fstab See here: https://help.ubuntu.com/community/Fstabby ElMariachi - uBoot
Those are Debian and OMV related problems. You shouldn't capture foreign threads in general and you should ask in the related communities for that. https://wiki.debian.org/InstallOpenMediaVaultOnDebian http://www.openmediavault.org/by ElMariachi - uBoot
That did the trick! I'll try understanding this tomorrow, I'm to tired right now. :)by ElMariachi - uBoot
>bodhi Wrote: >--- > When you see this rescue login prompt as shown the > log above, then it did boot to rescue system > > rescue:/tmp# > Wouldn't it be be bad if I couldn't even tell this? :). This question was related to the normal boot order instead. By this I meant: Is normal that this error occurs if I don't have an USB or IDE device plugged in?by ElMariachi - uBoot
No problem :) I was just wondering whether I had answered my own questions.. Regarding the MSf: I'm chronically out of money, so it's not so much, but better than nothing, I hope. I now did a colordiff. That pointed me to the mtdparts varibale not being complete, after having cleared this before. I already corrected mtdparts now, but this didn't help with the bootm error.by ElMariachi - uBoot
bodhi's edit with responses: Wrong Image Format for bootm command ERROR: can't get kernel image! That's not right. It means the attempted boot before that did not go to the alternate path. Meaning the bootm still executed even some image loading has failed. Your envs are not clean yet. QuoteThis message appers, no matter if I boot from USB or rescue system. Bothby ElMariachi - uBoot
Yippie! Finally got the rescue system booting! :) This was an interesting journey.. I applied your patch and it sitll wouldn't boot, claiming about not found partitions, corrupt images and such. Then I got really confused, when some variables wouldn't change in the printenv output, although I succesfully issued a setenv command on them just a second before. It was then, when Iby ElMariachi - uBoot
Hello! I didn't understand that you intended those changes to env to being temporarily only. So I entered them from bootloader using setenv, but also saved them using savenv, because I was too lazy for entering them on every try. Now I learned, why this is not a good idea... 192.168.1.35 is my notebook's IP, so that's correct. But netconsole is behaving unusual at the momentby ElMariachi - uBoot
OK. Now got the latest UBoot on the device :) Next I'm tried flashing rescue system v2 onto the NAND (I assume this still is the way to go, as v3 seems only suitable for Pogoplug and v4 still is beta, right?). But it still won't boot from internal NAND, using rescue system v2. I closely followed the tutorial and reset env with the commands there (inclusing net console). But nowby ElMariachi - uBoot
Bodhi, thank you very much, once more! :) It's booting into Debian from USB now. Without USB, by booting from NAND, it won't work, yet, although there was a working os on internal NAND before: U-Boot 2011.12 (Apr 18 2012 - 23:08:20) Seagate GoFlexNet SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err:by ElMariachi - uBoot
Here it is: Willkommen zu minicom 2.7 Optionen: I18n Übersetzt am Feb 7 2016, 13:37:27. Port /dev/ttyUSB0, 08:23:32 Drücken Sie CTRL-A Z für Hilfe zu speziellen Tasten U-Boot 2011.12 (Apr 18 2012 - 23:08:20) Seagate GoFlexNet SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In: serial Out: serial Err: serial Net: egigby ElMariachi - uBoot
Thank you. That solved the first problem regarding USB boot. Now USB boot hangs after loading the Kernel, just like after transferring any Image using UBoot's tftp. ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.12.1-kirkwood-tld-1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3833423 Bytes = 3.7 MiB Load Address: 00008000by ElMariachi - uBoot
Hello, Bodhi! I just tried using an old GoFlex NET that laid here for some years. It once worked with a recent UBoot and Debian in NAND. But when I tried it, it wouldn't boot like usually anymore. It would boot neither from SATA, nor from USB, only the NAND boot was working. I couldn't ssh to the device and also net console wasn't working. Thus I'm using serial atm. I trby ElMariachi - uBoot
From my experience you can't. When I last tried enabling SSH on the box, it was impossible without serial. And the pogo service isn't available anymore. But I doubt, that anyone without knowledge of the open source modification would bother buying this anyway, with it's bad reputation at amazon and such.by ElMariachi - uBoot
Hello, bodhi! I tried switching a Debian 8 installtion to systemd, using uEnv.txt It works if I append 'init=/bin/systemd' to the set_bootargs variable in flash. But setting by /boot/uEnv.txt doesn't have any effect. My uEnv.txt: set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params init=/bin/systemd My whole env:by ElMariachi - uBoot
Hi! In some threads I one had read that ext3 was the recommended filesystem to use for the rootfs. Does this still apply with current UBoot versions? Am I safe to use ext4 in the long instead? Thank you! :)by ElMariachi - Off-Topic
kwboot will replace your bootloader he moment you boot it. If there's a working system (rootfs) on your device and all environment settings are right, you might be able to fully boot the system using kwboot. Otherwise you might need to first start the device using kwboot and then interrupt the boot process (using ctrl-c or any key during the countdown), Then you can change your environment sby ElMariachi - uBoot
I successfully flashed the rescue system onto the device now, too. After all there where some env changes needed here and there. May I ask you for having a final look at it, if it's ok or could provoke some problems? rescue:~# fw_printenv arcNumber=3089 baudrate=115200 bootargs=root=/dev/nfs nfsroot=192.168.1.35: ip=192.168.1.40:192.168.1.35:::::off bootcmd=sleep 3; run scan_diby ElMariachi - uBoot
Hello! Debian is booting now, but I can't login: [....] Starting OpenBSD Secure Shell server: sshd@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Permissions 0666 for '/etc/ssh/ssh_host_rsa_key' are too open. It is required that your privatby ElMariachi - uBoot
Hello! Sorry, I don't have logs of the nanddump and flashing process anymore. The script results in: Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [............................................by ElMariachi - uBoot
Ok. I stored all partitions of my modded device and also stored all printenv and fw_printenv variables into files. Then I bootet another GoFlexNet device. There I checked partiton table (all same), checked for bad blocks (none) and flashed all mtd files back into the regarding partiton. After this I checked "mtd_parts", it was already same as on the previous GFN. Additonally I set theby ElMariachi - uBoot
> - fw_printenv is Debian command. printenv is > u-boot command. They are the same. I assumed they where same until I discovered, that I get very different results when comparing both using both commands in rescue system. I have attached both to the last post, could you please have a look at it? I need to know, which envs I should use for replicating on the target device. > -by ElMariachi - uBoot
Ok. I'll start with the GFN, that I have modded some days ago, using your instructions for Debian 4 and rescue system. As at first I just intend creating full backups of the devices, without flashing, I directly executed the commands. I booted from the rescue system rescue:/tmp# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 0002by ElMariachi - uBoot
I don't know if one of the three GFNs I got here is 'unbrickable', but I got UART and also an old JTAG lying around. And I'm planning on buying the bus pirate soon, btw. I think we are ready for some serious trouble here ;)by ElMariachi - uBoot