Everything gone wrong Cannot boot anything on GoFlex Net
Posted by ElMariachi
|
Everything gone wrong Cannot boot anything on GoFlex Net September 24, 2017 02:23AM |
Registered: 7 years ago Posts: 90 |
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 tried updating UBoot using the script.
But after this things even became worse.
The script seems to have installed a very old version of UBoot and it won't even boot from NAND anymore.
I tried kwboot for booting to the NAND using a recent UBoot, but this won't work either.
The device just shuts down after 100% of uboot have been transferred using kwboot. I think everything is crippled, from the MTD to the env.
When trying to boot from USB I get:
When trying to boot from NAND I get:
Also I tried tftp from UBoot console to transfer and boot uboot.2015.10-tld-1.goflexnet.mtd0.kwb, but it will just hang, also.
I don't know where to continue now.
Edited 6 time(s). Last edit at 09/24/2017 02:53AM by ElMariachi.
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 tried updating UBoot using the script.
But after this things even became worse.
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: egiga0 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0
The script seems to have installed a very old version of UBoot and it won't even boot from NAND anymore.
I tried kwboot for booting to the NAND using a recent UBoot, but this won't work either.
sudo kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-1.goflexnet.mtd0.kwb -p
97 % [......................................................................] 99 % [....................................] [Type Ctrl-\ + c to quit]
The device just shuts down after 100% of uboot have been transferred using kwboot. I think everything is crippled, from the MTD to the env.
GoFlexNet> printenv baudrate=115200 bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset bootdelay=3 console=ttyS0,115200 ethact=egiga0 ethaddr=00:50:43:00:02:02 force_rescue=0 force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ipaddr=192.168.1.15 led_error=orange blinking led_exit=green off led_init=green blinking mainlineLinux=yes mtdids=nand0=orion_nand mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) partition=nand0,2 pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi rescue_installed=0 rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params serverip=192.168.1.35 stderr=serial stdin=serial stdout=serial ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi ubifs_mtd=3 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_device=0:1 usb_init=run usb_scan usb_root=/dev/sda1 usb_rootdelay=10 usb_rootfstype=ext2 usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found booe usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_scan_list=1 2 3 4 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params Environment size: 2389/131068 bytes
When trying to boot from USB I get:
Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x07fa825c). Available machine support: ID (hex) NAME ffffffff Generic DT based system ffffffff Marvell Kirkwood (Flattened Device Tree) Please check your kernel config and/or bootloader.
When trying to boot from NAND I get:
GoFlexNet> nboot ** No boot device **
Also I tried tftp from UBoot console to transfer and boot uboot.2015.10-tld-1.goflexnet.mtd0.kwb, but it will just hang, also.
I don't know where to continue now.
Edited 6 time(s). Last edit at 09/24/2017 02:53AM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 24, 2017 03:05AM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
This error is the rootfs related.
Because the u-boot is quite old (U-Boot 2011.12), when you create the USB rootfs to boot with this u-boot, you must do step 4:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
> Error: unrecognized/unsupported machine ID (r1 =
> 0x07fa825c).
>
> Available machine support:
>
> ID (hex) NAME
> ffffffff Generic DT based system
> ffffffff Marvell Kirkwood (Flattened Device
> Tree)
>
> Please check your kernel config and/or
> bootloader.
This error is the rootfs related.
Because the u-boot is quite old (U-Boot 2011.12), when you create the USB rootfs to boot with this u-boot, you must do step 4:
Quote
Latest released rootfs: Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Jul 2017)
Quote
Updated 24 Jul 2017:
Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:
Quote
4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 24, 2017 03:24AM |
Registered: 7 years ago Posts: 90 |
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.
All LEDs are off after this and I can only connect to the device again after unplugging power.
Sorry, I fear I killed much more in my confusion. When I tried booting from NVRAM there where JFFS2 errors before, but since flashing UBoot I cannot even boot NVRAM anymore.
I thought it possibly could hel if I booted the old Non-FTD-Kernel, but I cannot find the download anymore.
Edited 4 time(s). Last edit at 09/24/2017 03:03PM by ElMariachi.
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: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: initramfs-4.12.1-kirkwood-tld-1 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7245632 Bytes = 6.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel.
All LEDs are off after this and I can only connect to the device again after unplugging power.
Sorry, I fear I killed much more in my confusion. When I tried booting from NVRAM there where JFFS2 errors before, but since flashing UBoot I cannot even boot NVRAM anymore.
I thought it possibly could hel if I booted the old Non-FTD-Kernel, but I cannot find the download anymore.
Edited 4 time(s). Last edit at 09/24/2017 03:03PM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 24, 2017 06:17PM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
With the USB rootfs plugged in, power up, interrupt serial console and
And post the entire serial console log here (from the u-boot banner until the last line in your log).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
With the USB rootfs plugged in, power up, interrupt serial console and
setenv usb_custom_params 'earlyprintk=serial' printenv boot
And post the entire serial console log here (from the u-boot banner until the last line in your log).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 25, 2017 01:36AM |
Registered: 7 years ago Posts: 90 |
Here it is:
I have already tried recreating rootfs multiple times (ext2).
Edited 1 time(s). Last edit at 09/25/2017 01:46AM by ElMariachi.
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: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
GoFlexNet> setenv usb_custom_params 'earlyprintk=serial'
GoFlexNet> printenv
arcNumber=3089
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=00:50:43:00:02:02
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ipaddr=192.168.1.15
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.1.35
set_bootargs_usb=etenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_custom_params=earlyprintk=serial
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; doe
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
Environment size: 2583/131068 bytes
GoFlexNet> boot
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt
** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1752
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
3833487 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7245696 bytes read
## 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: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.12.1-kirkwood-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7245632 Bytes = 6.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.12.1-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] OF: fdt: Machine model: Seagate GoFlex Net
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) earlyprintk=serial
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 109436K/131072K available (8192K kernel code, 716K rwdata, 1972K rodata, 1024K init, 288K bss, 21636K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff800000 ( 880 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0900000 (9184 kB)
[ 0.000000] .init : 0xc0c00000 - 0xc0d00000 (1024 kB)
[ 0.000000] .data : 0xc0d00000 - 0xc0db3274 ( 717 kB)
[ 0.000000] .bss : 0xc0db9b9c - 0xc0e01e60 ( 289 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000007] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.007980] Switching to timer-based delay loop, resolution 5ns
[ 0.014476] Console: colour dummy device 80x30
[ 0.019097] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.029803] pid_max: default: 32768 minimum: 301
[ 0.034718] Security Framework initialized
[ 0.039078] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.045816] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.053883] CPU: Testing write buffer coherency: ok
[ 0.059948] Setting up static identity map for 0x100000 - 0x100058
[ 0.066506] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.075095] devtmpfs: initialized
[ 0.083036] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.093098] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.099754] prandom: seed boundary self test passed
[ 0.108536] prandom: 100 self tests passed
[ 0.112747] pinctrl core: initialized pinctrl subsystem
[ 0.119291] NET: Registered protocol family 16
[ 0.124356] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.132989] cpuidle: using governor ladder
[ 0.137258] cpuidle: using governor menu
[ 0.141806] Feroceon L2: Enabling L2
[ 0.145517] Feroceon L2: Cache support initialised.
[ 0.150903] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[ 0.166255] No ATAGs?
[ 0.175594] vgaarb: loaded
[ 0.181139] SCSI subsystem initialized
[ 0.185459] usbcore: registered new interface driver usbfs
[ 0.191177] usbcore: registered new interface driver hub
[ 0.196671] usbcore: registered new device driver usb
[ 0.203003] clocksource: Switched to clocksource orion_clocksource
[ 0.299002] VFS: Disk quotas dquot_6.6.0
[ 0.303184] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.320871] NET: Registered protocol family 2
[ 0.326130] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.333264] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.339746] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.346316] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.352279] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.358860] NET: Registered protocol family 1
[ 0.363757] RPC: Registered named UNIX socket transport module.
[ 0.369792] RPC: Registered udp transport module.
[ 0.374670] RPC: Registered tcp transport module.
[ 0.379480] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.386299] Unpacking initramfs...
[ 0.389808] Initramfs unpacking failed: junk in compressed archive
[ 0.416078] Freeing initrd memory: 7076K
[ 0.420278] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.427895] audit: initializing netlink subsys (disabled)
[ 0.433930] Initialise system trusted keyrings
[ 0.438527] Key type blacklist registered
[ 0.442715] audit: type=2000 audit(0.420:1): state=initialized audit_enabled=0 res=1
[ 0.450720] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[ 0.450782] zbud: loaded
[ 0.458369] NFS: Registering the id_resolver key type
[ 0.458386] Key type id_resolver registered
[ 0.458390] Key type id_legacy registered
[ 0.458403] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.458408] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.458601] jffs2: version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.
[ 0.458792] fuse init (API version 7.26)
[ 0.459156] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 0.459421] orangefs_init: module version upstream loaded
[ 0.459427] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 2.563010] random: fast init done
[ 6.389390] Key type asymmetric registered
[ 6.393851] Asymmetric key parser 'x509' registered
[ 6.398895] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 6.406580] io scheduler noop registered
[ 6.410607] io scheduler deadline registered
[ 6.415120] io scheduler cfq registered (default)
[ 6.421007] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 6.436601] loop: module loaded
[ 6.441486] libphy: Fixed MDIO Bus: probed
[ 6.446487] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 6.453194] ehci-pci: EHCI PCI platform driver
[ 6.457804] ehci-orion: EHCI orion driver
[ 6.462106] usbcore: registered new interface driver usb-storage
[ 6.468583] mousedev: PS/2 mouse device common for all mice
[ 6.474601] i2c /dev entries driver
[ 6.478554] kirkwood-cpufreq kirkwood-cpufreq: Unable to get cpuclk
[ 6.485027] kirkwood-cpufreq: probe of kirkwood-cpufreq failed with error -22
[ 6.492681] hidraw: raw HID events driver (C) Jiri Kosina
[ 6.498597] drop_monitor: Initializing network drop monitor service
[ 6.505247] NET: Registered protocol family 17
[ 6.509891] Key type dns_resolver registered
[ 6.515097] registered taskstats version 1
[ 6.519302] Loading compiled-in X.509 certificates
[ 6.524289] zswap: loaded using pool lzo/zbud
[ 6.531171] Key type big_key registered
[ 6.537051] Key type encrypted registered
[ 6.542435] hctosys: unable to open rtc device (rtc0)
[ 7.672427] Unable to handle kernel paging request at virtual address c8000000
[ 7.679778] pgd = c0004000
[ 7.682584] [c8000000] *pgd=00000000
[ 7.686271] Internal error: Oops: 5 [#1] PREEMPT ARM
[ 7.691340] Modules linked in:
[ 7.694500] CPU: 0 PID: 1 Comm: swapper Not tainted 4.12.1-kirkwood-tld-1 #1
[ 7.701663] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[ 7.708039] task: c7832e00 task.stack: c7834000
[ 7.712688] PC is at crc32_be+0x6c/0x160
[ 7.716715] LR is at 0xc0950bd0
[ 7.719953] pc : [<c0584814>] lr : [<c0950bd0>] psr: 20000053
[ 7.719953] sp : c7835ef0 ip : c09523a0 fp : 00000000
[ 7.731652] r10: c0db9ba0 r9 : c0c4b838 r8 : 31608756
[ 7.736981] r7 : 00000000 r6 : c7fffffc r5 : 1d3e9e27 r4 : 00000007
[ 7.743617] r3 : 6f5fedc7 r2 : 1e1bdfbc r1 : c115f354 r0 : 0978d353
[ 7.750262] Flags: nzCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment none
[ 7.757604] Control: 0005397f Table: 00004000 DAC: 00000053
[ 7.763454] Process swapper (pid: 1, stack limit = 0xc7834190)
[ 7.769393] Stack: (0xc7835ef0 to 0xc7836000)
[ 7.773852] 5ee0: c115f358 f0defde7 465e9d65 c0c59544
[ 7.782156] 5f00: 00000000 c0c3f8f0 00000007 c0c3f8bc 000000b8 c010178c 00000000 c01334d0
[ 7.790457] 5f20: 00000000 c0299eec 00000000 c0aeb5e0 000000b8 00000007 00000007 c0aec440
[ 7.798759] 5f40: 000000b7 c0aec440 c7ffce5f c7ffce6b c0d0bc24 00000007 c0c4b830 000000b8
[ 7.807060] 5f60: 00000007 c0c4b834 000000b8 c0c59544 c0db9ba0 c0c00e18 00000007 00000007
[ 7.815361] 5f80: 00000000 c0c005ac 00000000 c08331f8 00000000 00000000 00000000 00000000
[ 7.823662] 5fa0: 00000000 c0833200 00000000 c01070f0 00000000 00000000 00000000 00000000
[ 7.831963] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 7.840265] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 d0898e2b 58220303
[ 7.848583] [<c0584814>] (crc32_be) from [<c0c3f8f0>] (of_fdt_raw_init+0x34/0x78)
[ 7.856193] [<c0c3f8f0>] (of_fdt_raw_init) from [<c010178c>] (do_one_initcall+0xa8/0x158)
[ 7.864503] [<c010178c>] (do_one_initcall) from [<c0c00e18>] (kernel_init_freeable+0x198/0x260)
[ 7.873340] [<c0c00e18>] (kernel_init_freeable) from [<c0833200>] (kernel_init+0x8/0x10c)
[ 7.881647] [<c0833200>] (kernel_init) from [<c01070f0>] (ret_from_fork+0x14/0x24)
[ 7.889342] Code: e1a05002 e59fe0f4 e3550000 0a00002b (e5963004)
[ 7.895551] ---[ end trace 3fa03d35fce52ad7 ]---
[ 7.900363] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 7.900363]
[ 7.909722] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 7.909722]
[ 133.873067] random: crng init done
I have already tried recreating rootfs multiple times (ext2).
Edited 1 time(s). Last edit at 09/25/2017 01:46AM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 25, 2017 03:17AM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
Very good!.
Try this
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/25/2017 03:18AM by bodhi.
Very good!.
Try this
setenv usb_custom_params 'earlyprintk=serial' setenv usb_set_bootargs 'setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_custom_params' setenv usb_boot 'mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x2100000 /boot/uInitrd; then bootm 0x800000 0x2100000; else bootm 0x800000; fi' printenv boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/25/2017 03:18AM by bodhi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 25, 2017 04:15AM |
Registered: 7 years ago Posts: 90 |
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:
I think the next step would be flashing a current UBoot, but I don't dare updating UBoot atm, though, because when I try kwbooting the latest UBoot, it will just stall after transfer:
All LEDs are off, device doesn't respond through serial or through TCP/IP.
Why is it, that kwboot won't make it boot? Should I still try flashing uboot.2016.05-tld-1.goflexnet.mtd0.kwb to mtd0?
Edited 4 time(s). Last edit at 09/25/2017 04:24AM by ElMariachi.
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: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1752
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
## Error: "sata_bootcmd" not defined
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ....... read_nand_cached: error reading nand off 0x10e2c00 size 8192 bytes
. done.
read_nand_cached: error reading nand off 0x10e1800 size 8192 bytes
off = 0x10e1198 magic 0x1985 type 0xe002 node.totlen = 2388
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...
Yellow LED remains flashing. No response on IP or serial.
I think the next step would be flashing a current UBoot, but I don't dare updating UBoot atm, though, because when I try kwbooting the latest UBoot, it will just stall after transfer:
elite:~$ kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-1.goflexnet.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [......................................................................] 5 % [......................................................................] 6 % [......................................................................] 8 % [......................................................................] 10 % [......................................................................] 11 % [......................................................................] 13 % [......................................................................] 15 % [......................................................................] 17 % [......................................................................] 18 % [......................................................................] 20 % [......................................................................] 22 % [......................................................................] 23 % [......................................................................] 25 % [......................................................................] 27 % [......................................................................] 29 % [......................................................................] 30 % [......................................................................] 32 % [......................................................................] 34 % [......................................................................] 35 % [......................................................................] 37 % [......................................................................] 39 % [......................................................................] 41 % [......................................................................] 42 % [......................................................................] 44 % [......................................................................] 46 % [......................................................................] 47 % [......................................................................] 49 % [......................................................................] 51 % [......................................................................] 53 % [......................................................................] 54 % [......................................................................] 56 % [......................................................................] 58 % [......................................................................] 59 % [......................................................................] 61 % [......................................................................] 63 % [......................................................................] 64 % [......................................................................] 66 % [......................................................................] 68 % [......................................................................] 70 % [......................................................................] 71 % [......................................................................] 73 % [......................................................................] 75 % [......................................................................] 76 % [......................................................................] 78 % [......................................................................] 80 % [......................................................................] 82 % [......................................................................] 83 % [......................................................................] 85 % [......................................................................] 87 % [......................................................................] 88 % [......................................................................] 90 % [......................................................................] 92 % [......................................................................] 94 % [......................................................................] 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] [Type Ctrl-\ + c to quit]
All LEDs are off, device doesn't respond through serial or through TCP/IP.
Why is it, that kwboot won't make it boot? Should I still try flashing uboot.2016.05-tld-1.goflexnet.mtd0.kwb to mtd0?
Edited 4 time(s). Last edit at 09/25/2017 04:24AM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 25, 2017 04:56AM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
> Bodhi, thank you very much, once more! :)
You're welcome!
>
> It's booting into Debian from USB now.
>
Cool!
> Without USB, by booting from NAND, it won't work,
> yet, although there was a working os on internal
> NAND before:
> Scanning JFFS2 FS: ....... read_nand_cached:
> error reading nand off 0x10e2c00 size 8192 bytes
> . done.
> read_nand_cached: error reading nand off 0x10e1800
> size 8192 bytes
Your stock FW has been corrupted. So it can not be used for booting into stock annymore.
> Why is it, that kwboot won't make it boot?
You seem to have the GoFlex Net that does not support UART booting. Most GFlexNet models do have this capability, but a few Goflex Net series do not.
> Should
> I still try flashing
> uboot.2016.05-tld-1.goflexnet.mtd0.kwb to mtd0?
Sure, it should work fine. But since you dont have UART booting, you need to be very careful. Don't reboot right away after you flash the image, if you see any error, or anything that is different from the expect outputs described in the installation instruction, post the log and I'll take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Bodhi, thank you very much, once more! :)
You're welcome!
>
> It's booting into Debian from USB now.
>
Cool!
> Without USB, by booting from NAND, it won't work,
> yet, although there was a working os on internal
> NAND before:
> Scanning JFFS2 FS: ....... read_nand_cached:
> error reading nand off 0x10e2c00 size 8192 bytes
> . done.
> read_nand_cached: error reading nand off 0x10e1800
> size 8192 bytes
Your stock FW has been corrupted. So it can not be used for booting into stock annymore.
> Why is it, that kwboot won't make it boot?
You seem to have the GoFlex Net that does not support UART booting. Most GFlexNet models do have this capability, but a few Goflex Net series do not.
> Should
> I still try flashing
> uboot.2016.05-tld-1.goflexnet.mtd0.kwb to mtd0?
Sure, it should work fine. But since you dont have UART booting, you need to be very careful. Don't reboot right away after you flash the image, if you see any error, or anything that is different from the expect outputs described in the installation instruction, post the log and I'll take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 25, 2017 05:56AM |
Registered: 7 years ago Posts: 90 |
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 now I cannot even interrupt boot process anymore, by pressing a key in serial terminal. It's always booting straight into the crashing internal NAND, unless I put in the USB drive, which is the last resort for any operation now.
I think the serial-keypress interrupt not working is normal, if netconsole is enabled, but netconsole isn't working either, so there's a problem (there's no output in netconsole and it also doesn't react to keypresses).
Edited 8 time(s). Last edit at 09/25/2017 07:08AM by ElMariachi.
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 now I cannot even interrupt boot process anymore, by pressing a key in serial terminal. It's always booting straight into the crashing internal NAND, unless I put in the USB drive, which is the last resort for any operation now.
I think the serial-keypress interrupt not working is normal, if netconsole is enabled, but netconsole isn't working either, so there's a problem (there's no output in netconsole and it also doesn't react to keypresses).
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700) Seagate GoFlex Net SoC: Kirkwood 88F6281_A1 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 host 192.168.1.35 is alive Using egiga0 device host 192.168.1.35 is alive Using egiga0 device host 192.168.1.35 is alive Using egiga0 device host 192.168.1.35 is alive Using egiga0 device host 192.168.1.35 is aliveNo chance for interrupting and then it hang's (from internal NAND). 192.168.1.35 is my Notebooks IP for netsoncole usage.
root@debian:~# fw_printenv bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootdelay=10 bootdev=usb device=0:1 devices=usb ide mmc disks=0 1 2 3 ethact=egiga0 if_netconsole=ping $serverip led_error=orange blinking led_exit=green off led_init=green blinking load_dtb_addr=0x1c00000 load_initrd_addr=0x1100000 load_uimage_addr=0x800000 load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage mainlineLinux=yes mtdids=nand0=orion_nand partition=nand0,2 scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; stderr=serial stdin=serial stdout=serial uenv_addr=0x810000 uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done; uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done; uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi usb_ready_retry=15 arcNumber=3089 mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params set_bootargs_usb=etenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_paras usb_set_bootargs=setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_custom_params ethaddr=00:50:43:00:02:02 bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3 dtb_file=/boot/dts/kirkwood-goflexnet.dtb preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi preboot=run preboot_nc ipaddr=192.168.1.15 serverip=192.168.1.35 set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootcmd_pogo=run bootcmd_rescue set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2 root@debian:~#
Edited 8 time(s). Last edit at 09/25/2017 07:08AM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 25, 2017 01:21PM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
> 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 now I cannot even interrupt boot process
> anymore, by pressing a key in serial terminal.
> It's always booting straight into the crashing
> internal NAND, unless I put in the USB drive,
> which is the last resort for any operation now.
That's why you should not run fw_setenv in Debian to test your setup, because you have serial console. Use setenv in serial console to test your setup first, and use fw_setenv after it's all checked out.
>
> I think the serial-keypress interrupt not working
> is normal, if netconsole is enabled, but
> netconsole isn't working either, so there's a
> problem (there's no output in netconsole and it
> also doesn't react to keypresses).
>
Open up a terminal on the box that has IP 192.168.1.35, run netconsole on it. The count down will appear on that netconsole. This is because the box that has serial console also is being set up for netconsole.
You can also change the serial console server box to use different IP address (something different from 192.168.1.35). Then netcosnole will time out, and only serial console can be used.
I'll take a look at the envs later. In the mean time you can play with changing envs in u-boot (using setenv), as long as you don't use saveenv to save them, everything will be back to the last saved state after power down.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/25/2017 01:30PM by bodhi.
> 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 now I cannot even interrupt boot process
> anymore, by pressing a key in serial terminal.
> It's always booting straight into the crashing
> internal NAND, unless I put in the USB drive,
> which is the last resort for any operation now.
That's why you should not run fw_setenv in Debian to test your setup, because you have serial console. Use setenv in serial console to test your setup first, and use fw_setenv after it's all checked out.
>
> I think the serial-keypress interrupt not working
> is normal, if netconsole is enabled, but
> netconsole isn't working either, so there's a
> problem (there's no output in netconsole and it
> also doesn't react to keypresses).
>
Open up a terminal on the box that has IP 192.168.1.35, run netconsole on it. The count down will appear on that netconsole. This is because the box that has serial console also is being set up for netconsole.
You can also change the serial console server box to use different IP address (something different from 192.168.1.35). Then netcosnole will time out, and only serial console can be used.
I'll take a look at the envs later. In the mean time you can play with changing envs in u-boot (using setenv), as long as you don't use saveenv to save them, everything will be back to the last saved state after power down.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/25/2017 01:30PM by bodhi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 26, 2017 12:42AM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
Once you done the above to see output from netconsole and able to interrupt it, please relist the envs again at u-boot prompt.
Your rescue setup seems incompleted.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Once you done the above to see output from netconsole and able to interrupt it, please relist the envs again at u-boot prompt.
Your rescue setup seems incompleted.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 26, 2017 06:17AM |
Registered: 7 years ago Posts: 90 |
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 moment:
Yesterday I didn't get any output at all, no matter how often I tried (maybe it was a stuck 'nc' process on my notebook). Now I tried the first time for today, and it's working. But the weird thing is that while I just used
I have never before seen netconsole being bidirectional with only this one command, on any of the other GoFlexes. Usually I always had to enter
Here's the env from bootloader:
Rescue system v2 installed with no problem, using Jeff's old script . Also there wasn't a NAND error reported.
Edited 27 time(s). Last edit at 09/26/2017 06:55AM by ElMariachi.
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 moment:
Yesterday I didn't get any output at all, no matter how often I tried (maybe it was a stuck 'nc' process on my notebook). Now I tried the first time for today, and it's working. But the weird thing is that while I just used
nc -l -u -p 6666for monitoring only, I was yet able to interrupt the countdown though, using 'Enter' key.
I have never before seen netconsole being bidirectional with only this one command, on any of the other GoFlexes. Usually I always had to enter
nc -u 192.168.1.15 6666 #(192.168.1.15 is the IP I usually set the GoFlexes to.)also, for being able to send keystrokes to the netconsole. Is this an update in UBoot?
Here's the env from bootloader:
admin@elite:~$ nc -l -u -p 6666 U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700) Seagate GoFlex Net gcc (Debian 4.9.2-10) 4.9.2 GNU ld (GNU Binutils for Debian) 2.25 Hit any key to stop autoboot: 7 0 GoFlexNet> printenv printenv arcNumber=3089 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi bootcmd_pogo=run bootcmd_rescue bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3 bootdelay=10 bootdev=usb device=0:1 devices=usb ide mmc disks=0 1 2 3 dtb_file=/boot/dts/kirkwood-goflexnet.dtb ethact=egiga0 ethaddr=00:50:43:00:02:02 if_netconsole=ping $serverip init_ide=ide reset init_mmc=mmc rescan init_usb=usb start ipaddr=192.168.1.15 led_error=orange blinking led_exit=green off led_init=green blinking load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file load_dtb_addr=0x1c00000 load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd load_initrd_addr=0x1100000 load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage load_uimage_addr=0x800000 mainlineLinux=yes mtdids=nand0=orion_nand mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)\ rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params\ set_bootargs_usb=etenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2\ ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_paras\ usb_set_bootargs=setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_custom_params nc_ready=1 ncip=192.168.1.35 partition=nand0,2 preboot=run preboot_nc preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done scan_ide=ide reset scan_mmc=mmc rescan scan_usb=usb start serverip=192.168.1.35 set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2 start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; stderr=nc stdin=nc stdout=nc uenv_addr=0x810000 uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done; uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done; uenv_loaded=0 uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi usb_ready_retry=15 Environment size: 4085/131068 bytes GoFlexNet>
Rescue system v2 installed with no problem, using Jeff's old script . Also there wasn't a NAND error reported.
Edited 27 time(s). Last edit at 09/26/2017 06:55AM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 26, 2017 05:03PM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
> I have never before seen netconsole being
> bidirectional with only this one command, on any
> of the other GoFlexes.
It is not unusual. It is bi-directional. Jeff's instruction is a little old, so he used 2 commands. I always use one command like this:
U-Boot netconsole has been the same for a while. But netcat has too many flavors. You Notebook runs a different implementation, the GoFlex Net runs another flavor, ..... Ubuntu runs another implementation :) and they are not just different in versions. They are actually different code.
Here is what missing in your env.
Unplug the USB rootfs, Power up, Interrupt serial console and
Once the rescue system is working, power down. Plug in the USB rootfs, power up, and enter the same command to test it to make sure it boot into USB.
After boot into Debian, you can use fw_setenv to set the bootcmd (copy/paste it):
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I have never before seen netconsole being
> bidirectional with only this one command, on any
> of the other GoFlexes.
It is not unusual. It is bi-directional. Jeff's instruction is a little old, so he used 2 commands. I always use one command like this:
nc -lup 6666 192.168.1.15 6666
U-Boot netconsole has been the same for a while. But netcat has too many flavors. You Notebook runs a different implementation, the GoFlex Net runs another flavor, ..... Ubuntu runs another implementation :) and they are not just different in versions. They are actually different code.
Here is what missing in your env.
Unplug the USB rootfs, Power up, Interrupt serial console and
setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset' boot
Once the rescue system is working, power down. Plug in the USB rootfs, power up, and enter the same command to test it to make sure it boot into USB.
After boot into Debian, you can use fw_setenv to set the bootcmd (copy/paste it):
fw_setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset'
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 26, 2017 06:49PM |
Registered: 7 years ago Posts: 90 |
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 I finally noticed the '\' (backslashes at the end of some lines (you need to scroll to the far right):
So all these lines where nothing, but the content of the corrupt 'mtdparts' variable.
I believe the default width of the forum's text box fooled us both, by hiding this faux pas :)
In my infinite wisdom I seem to have copy'n'pasted multiple lines at once during setup, and this most probably is the reason for all those troubles we have gone through here...
I have also noticed some other variables wheren't really what the seemed to be in the pure text output, because of line feeds and other special characters making them overlap.
So: Thank you, thank you thank you! :) Wished your forum had a little donation feature..
What's left now:
There's a blemish variable:
Because of that non ANSI sign, I got no clue on how to delete this faulty variable, yet, but maybe it could work using redirection of fw_printenv output into a file for making the fw_setenv command use the same characters I hope..
And then there also is the insecurtiy, if some of the other variables are crippled, too of course. I wonder what the best solution for checking them all would be, besides typing every single variable's name with fw_printenv.
Also there are some errors left during startup:
I think the IDE and USB related errors are, because there's no drive plugged in atm. But what about the 'Unknown command 'mmc' - try 'help'' error and the other mcc related errors?
Current ENV is:
Edited 11 time(s). Last edit at 09/26/2017 07:43PM by ElMariachi.
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 I finally noticed the '\' (backslashes at the end of some lines (you need to scroll to the far right):
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)\ rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params\ set_bootargs_usb=etenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2\ ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_paras\ usb_set_bootargs=setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_custom_params
So all these lines where nothing, but the content of the corrupt 'mtdparts' variable.
I believe the default width of the forum's text box fooled us both, by hiding this faux pas :)
In my infinite wisdom I seem to have copy'n'pasted multiple lines at once during setup, and this most probably is the reason for all those troubles we have gone through here...
I have also noticed some other variables wheren't really what the seemed to be in the pure text output, because of line feeds and other special characters making them overlap.
So: Thank you, thank you thank you! :) Wished your forum had a little donation feature..
What's left now:
There's a blemish variable:
set_bootargs_usbXb= setenv bootargs console= root= rootdelay= rootfstype= mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params set_bootargs_usb=etenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_paras usb_set_bootargs=setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_custom_params
That red X is a non ANSI sign, displayed as a binary symbol in terminal.
Because of that non ANSI sign, I got no clue on how to delete this faulty variable, yet, but maybe it could work using redirection of fw_printenv output into a file for making the fw_setenv command use the same characters I hope..
And then there also is the insecurtiy, if some of the other variables are crippled, too of course. I wonder what the best solution for checking them all would be, besides typing every single variable's name with fw_printenv.
Also there are some errors left during startup:
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Reset IDE: ide_preinit failed
Unknown command 'mmc' - try 'help'
no USB devices available
no IDE devices available
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide
Reset IDE: ide_preinit failed
device ide 0:1
** Bad device size - ide 0 **
device ide 1:1
** Bad device size - ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-goflexnet.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
NAND read: device 0 offset 0x100000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-2.6.32.18-dockstar
Created: 2011-02-17 8:10:10 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3236180 Bytes = 3.1 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Starting kernel ...
I think the IDE and USB related errors are, because there's no drive plugged in atm. But what about the 'Unknown command 'mmc' - try 'help'' error and the other mcc related errors?
Current ENV is:
rescue:/tmp# fw_printenv arcNumber=3089 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi bootcmd_pogo=run bootcmd_rescue bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3 bootdelay=10 bootdev=usb device=0:1 devices=usb ide mmc disks=0 1 2 3 dtb_file=/boot/dts/kirkwood-goflexnet.dtb ethact=egiga0 ethaddr=00:50:43:00:02:02 if_netconsole=ping $serverip ipaddr=192.168.1.15 led_error=orange blinking led_exit=green off led_init=green blinking load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file load_dtb_addr=0x1c00000 load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd load_initrd_addr=0x1100000 load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage load_uimage_addr=0x800000 mainlineLinux=yes mtdids=nand0=orion_nand mtdparts=mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs) nc_ready=0 ncip=192.168.1.35 partition=nand0,2 preboot=run preboot_nc preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done serverip=192.168.1.35 set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts set_bootargs_usbb= setenv bootargs console= root= rootdelay= rootfstype= mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params set_bootargs_usb=etenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts rootfstype=ext2 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_paras usb_set_bootargs=setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_custom_params start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; stderr=serial stdin=serial stdout=serial ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params uenv_addr=0x810000 uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done; uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done; uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi usb_ready_retry=15 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params rescue:/tmp#
Edited 11 time(s). Last edit at 09/26/2017 07:43PM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 26, 2017 07:43PM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
> Yippie!
>
> Finally got the rescue system booting! :)
Cool!
>
> 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 I finally noticed the '\'
> (backslashes at the end of some lines (you need to
> scroll to the far right):
Right there in front of us :)
> So all these lines where nothing, but the content
> of the corrupt 'mtdparts' variable.
> I believe the default width of the forum's text
> box fooled us both, by hiding this faux pas :)
> In my infinite wisdom I seem to have copy'n'pasted
> multiple lines at once during setup, and this most
> probably is the reason for all those troubles we
> have gone through here...
Good job figuring this out!
> So: Thank you, thank you thank you! :) Wished your
> forum had a little donation feature..
No need to, but you could check out bodhi corner in my signature.
> And then there also is the insecurtiy, if some of
> the other variables are crippled, too of course. I
> wonder what the best solution for checking them
> all would be, besides typing every single
> variable's name with fw_printenv.
You can do this:
And then do a diff (using color) with the default envs uboot.2016.05-tld-1.environment (you've downloaded this in the u-boot tarball). That will show your changes. Hopefully it will be easier to see the weird characters, if any.
> Also there are some errors left during startup:
>
> I think the IDE and USB related errors are of
> course, becaus there's no drive plugged in atm.
> But what about the 'Unknown command 'mmc' - try
> 'help'' error and the other mcc related errors?
Yes. They are all scanned by u-boot envs, so the errors are expected. Since this box has no MMC you can set the devices to USB and IDE only. That will reduce the noise.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Yippie!
>
> Finally got the rescue system booting! :)
Cool!
>
> 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 I finally noticed the '\'
> (backslashes at the end of some lines (you need to
> scroll to the far right):
Right there in front of us :)
> So all these lines where nothing, but the content
> of the corrupt 'mtdparts' variable.
> I believe the default width of the forum's text
> box fooled us both, by hiding this faux pas :)
> In my infinite wisdom I seem to have copy'n'pasted
> multiple lines at once during setup, and this most
> probably is the reason for all those troubles we
> have gone through here...
Good job figuring this out!
> So: Thank you, thank you thank you! :) Wished your
> forum had a little donation feature..
No need to, but you could check out bodhi corner in my signature.
> And then there also is the insecurtiy, if some of
> the other variables are crippled, too of course. I
> wonder what the best solution for checking them
> all would be, besides typing every single
> variable's name with fw_printenv.
You can do this:
fw_printenv > current_envs.txt
And then do a diff (using color) with the default envs uboot.2016.05-tld-1.environment (you've downloaded this in the u-boot tarball). That will show your changes. Hopefully it will be easier to see the weird characters, if any.
> Also there are some errors left during startup:
>
> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 > -0700) > Seagate GoFlex Net > gcc (Debian 4.9.2-10) 4.9.2 > GNU ld (GNU Binutils for Debian) 2.25 > Hit any key to stop autoboot: 0 > starting USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 1 USB Device(s) > found > scanning usb for storage devices... 0 > Storage Device(s) found > > Reset IDE: ide_preinit failed > Unknown command 'mmc' - try 'help' > > no USB devices available > > no IDE devices available > Unknown command 'mmc' - try 'help' > running scan_disk ... > Scan device usb > device usb 0:1 > ** Bad device usb 0 ** > device usb 1:1 > ** Bad device usb 1 ** > device usb 2:1 > ** Bad device usb 2 ** > device usb 3:1 > ** Bad device usb 3 ** > Scan device ide > > Reset IDE: ide_preinit failed > device ide 0:1 > ** Bad device size - ide 0 ** > device ide 1:1 > ** Bad device size - ide 1 ** > device ide 2:1 > ** Bad device ide 2 ** > device ide 3:1 > ** Bad device ide 3 ** > Scan device mmc > Unknown command 'mmc' - try 'help' > device mmc 0:1 > ** Bad device mmc 0 ** > device mmc 1:1 > ** Bad device mmc 1 ** > device mmc 2:1 > ** Bad device mmc 2 ** > device mmc 3:1 > ** Bad device mmc 3 ** > loading uImage ... > ** Bad device usb 0 ** > loading uInitrd ... > ** Bad device usb 0 ** > loading DTB /boot/dts/kirkwood-goflexnet.dtb ... > ** Bad device usb 0 ** > Wrong Image Format for bootm command > ERROR: can't get kernel image! > > NAND read: device 0 offset 0x100000, size > 0x400000 > 4194304 bytes read: OK > ## Booting kernel from Legacy Image at 00800000 > ... > Image Name: Linux-2.6.32.18-dockstar > Created: 2011-02-17 8:10:10 UTC > Image Type: ARM Linux Kernel Image > (uncompressed) > Data Size: 3236180 Bytes = 3.1 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > > > Starting kernel ... > >>
> I think the IDE and USB related errors are of
> course, becaus there's no drive plugged in atm.
> But what about the 'Unknown command 'mmc' - try
> 'help'' error and the other mcc related errors?
Yes. They are all scanned by u-boot envs, so the errors are expected. Since this box has no MMC you can set the devices to USB and IDE only. That will reduce the noise.
setenv devices 'usb ide'
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 26, 2017 07:50PM |
Registered: 7 years ago Posts: 90 |
bodhi's edit with responses:
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.
No need to. The rescue system should be OK. Just the envs are not.
:))
Edited 6 time(s). Last edit at 09/26/2017 10:55PM by bodhi.
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.
Quote
This message appers, no matter if I boot from USB or rescue system.
Both are booting, though..
My guess would be, that the rescue system partitions are partially crippled, because of the garbage that was stored in 'mtdparts' while I installed rescue system.. So reflashing rescue system v2 now could help; does this sound reasonable?
No need to. The rescue system should be OK. Just the envs are not.
Quote
OK, one donation to MSF is your beer? So you are drinking blood? :)
:))
Edited 6 time(s). Last edit at 09/26/2017 10:55PM by bodhi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 26, 2017 10:58PM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
Sorry I hit the wrong button. Instead of a new post, I've edited your post with my responses!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Sorry I hit the wrong button. Instead of a new post, I've edited your post with my responses!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 28, 2017 06:37PM |
Registered: 7 years ago Posts: 90 |
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.
The remaining differences are:
From my little understanding it's all looking good, right now. I compared everything, and all differences seem legit, as they have been done due to hardware and configuration specifics, netconsole and rescue system. machid isn't needed on the GoFlexNET and the additional lines are for the rescue system and I also compared those additional lines to those in the rescue system v2 tutorial.
I now understand, that the error comes from this line:
I learned about UBoot's nand command, that it's basically working like:
So it's loading 4 Megabytes from flash address 0x100000(start of mtd1/uImage) into the RAM at address 0x800000.
Subsequently bootm is supposed to run code from the same address on.
So I compared these parameters to the partitions, and it fits:
I believe that uImage (microimage?) is working like the initrd on my usual Linux systems, so it should be working, unless there was corrupt data in mtd1... shouldn't it?
I tried issuing the nand read and bootm commands manually, and they worked, so I examined the line:
Next I tried understanding the variables used by load_uimage, such as 'bootdev' and 'device'. But I couldn't go on from there, because I don't know, what this part is actually supposed to do.., Is it for loading the rescue system at all? Is it for trying to load a system from USB/SATA before loading the rescue system anyway? But then there needed to be an 'if'-block, checking for the existence of any other file system before executing the command, for avoiding that error, and I would have noticed such a big part missing from my configuration.. I don't know what to do next anymore...
Or: Is it just normal that this error ocurrs, if there's an USB or SATA device available?
PS:
Sorry for all that text :)
Edited 25 time(s). Last edit at 09/28/2017 10:00PM by ElMariachi.
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.
The remaining differences are:
admin@elite:~/Downloads$ colordiff uboot.2016.05-tld-1.environment envs.txt 1,2c1,2 < arcNumber=2097 < bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec --- > arcNumber=3089 > bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset 4c4,6 < bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi --- > bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3 > bootcmd_pogo=run bootcmd_rescue > bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 8c10 < devices=usb ide mmc --- > devices=usb ide 10c12 < dtb_file=/boot/dts/kirkwood-pogo_e02.dtb --- > dtb_file=/boot/dts/kirkwood-goflexnet.dtb 12c14 < ethaddr=52:3b:20:9c:11:51 --- > ethaddr=00:50:43:00:02:02 14c16 < ipaddr=192.168.0.231 --- > ipaddr=192.168.1.15 24d25 < machid=0x831 27a29,30 > nc_ready=0 > ncip=192.168.1.35 29c32,34 < preboot_nc=run if_netconsole start_netconsole --- > preboot=run preboot_nc > preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi > rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params 31c36 < serverip=192.168.0.220 --- > serverip=192.168.1.35 32a38,39 > set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts > set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts 36a44 > ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params 43a52 > usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
From my little understanding it's all looking good, right now. I compared everything, and all differences seem legit, as they have been done due to hardware and configuration specifics, netconsole and rescue system. machid isn't needed on the GoFlexNET and the additional lines are for the rescue system and I also compared those additional lines to those in the rescue system v2 tutorial.
I now understand, that the error comes from this line:
setenv bootcmd_rescue 'run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
I learned about UBoot's nand command, that it's basically working like:
nand read.oob addr ofs|partition size(Couldn't find anything related to 'nand read.e', though.)
So it's loading 4 Megabytes from flash address 0x100000(start of mtd1/uImage) into the RAM at address 0x800000.
Subsequently bootm is supposed to run code from the same address on.
So I compared these parameters to the partitions, and it fits:
rescue:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 02000000 00020000 "root" mtd3: 0db00000 00020000 "data"
I believe that uImage (microimage?) is working like the initrd on my usual Linux systems, so it should be working, unless there was corrupt data in mtd1... shouldn't it?
I tried issuing the nand read and bootm commands manually, and they worked, so I examined the line:
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr;If the direct bootm line is working, then MTD1 is okay, and the above line seems to be the only possibility, where this error could come from. (And the direct bootm command from before probably is the reason, that it's booting into the rescue system anyways in the end, isn't it?)
Next I tried understanding the variables used by load_uimage, such as 'bootdev' and 'device'. But I couldn't go on from there, because I don't know, what this part is actually supposed to do.., Is it for loading the rescue system at all? Is it for trying to load a system from USB/SATA before loading the rescue system anyway? But then there needed to be an 'if'-block, checking for the existence of any other file system before executing the command, for avoiding that error, and I would have noticed such a big part missing from my configuration.. I don't know what to do next anymore...
Or: Is it just normal that this error ocurrs, if there's an USB or SATA device available?
PS:
Sorry for all that text :)
Edited 25 time(s). Last edit at 09/28/2017 10:00PM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 29, 2017 09:27PM |
Admin Registered: 13 years ago Posts: 18,548 |
It is a lot to digest :) let me read it carefully and suggest a solution.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net September 30, 2017 12:05AM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi,
Thank you for your contribution to good cause :) It does not matter whether it is a little or a lot.
> nand read.e 0x800000 0x100000 0x400000; bootm
> 0x800000'
> (Couldn't find anything related to 'nand read.e',
> though.)
The above is a rescue setup to work with much older u-boot versions. But it should work fine with new u-boot.
> So it's loading 4 Megabytes from flash address
> 0x100000(start of mtd1/uImage) into the RAM at
> address 0x800000.
> Subsequently bootm is supposed to run code from
> the same address on.
Correct.
> I believe that uImage (microimage?) is working
> like the initrd on my usual Linux systems, so it
> should be working, unless there was corrupt data
> in mtd1... shouldn't it?
Incorrect. uImage is the kernel image (vmlinuz-x.xx.xx) that has been wrapped with a Marvell u-boot header. The rescue system uImage is similar to a normal Linux rootfs, where we have uImage in /boot. The uInitrd file is the ram disk image (initrd.img-x.xx.xx) that has been wrapped with Marvell u-boot header. Rescue system V2 does not use uInitrd.
We need to have these files in u-boot image format, so u-boot can read the headers and determine where to load, and whether the checksum is correct.
> I tried issuing the nand read and bootm commands
> manually, and they worked,
This means the automatic execution of all these envs somehow did inadvertenly execute an env that we don't want it to. When you execute that directly and it works, then it means the bootargs was set up correctly, but other envs in the calling chain were not. Or a failure during finding the USB drive has inadvertenly caused the calling sequence to abort.
> If the direct bootm line is working, then MTD1 is
> okay, and the above line seems to be the only
> possibility, where this error could come from.
> (And the direct bootm command from before probably
> is the reason, that it's booting into the rescue
> system anyways in the end, isn't it?)
When you see this rescue login prompt as shown the log above, then it did boot to rescue system
Let's see what the rescue envs are.
Here is the revised bootcmd (so that it will be more resilient to the failure previously in bootcmd_exec):
WIth no USB drive plugged in, power up, interrupt console, and:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thank you for your contribution to good cause :) It does not matter whether it is a little or a lot.
> nand read.e 0x800000 0x100000 0x400000; bootm
> 0x800000'
> (Couldn't find anything related to 'nand read.e',
> though.)
The above is a rescue setup to work with much older u-boot versions. But it should work fine with new u-boot.
> So it's loading 4 Megabytes from flash address
> 0x100000(start of mtd1/uImage) into the RAM at
> address 0x800000.
> Subsequently bootm is supposed to run code from
> the same address on.
Correct.
> I believe that uImage (microimage?) is working
> like the initrd on my usual Linux systems, so it
> should be working, unless there was corrupt data
> in mtd1... shouldn't it?
Incorrect. uImage is the kernel image (vmlinuz-x.xx.xx) that has been wrapped with a Marvell u-boot header. The rescue system uImage is similar to a normal Linux rootfs, where we have uImage in /boot. The uInitrd file is the ram disk image (initrd.img-x.xx.xx) that has been wrapped with Marvell u-boot header. Rescue system V2 does not use uInitrd.
We need to have these files in u-boot image format, so u-boot can read the headers and determine where to load, and whether the checksum is correct.
> I tried issuing the nand read and bootm commands
> manually, and they worked,
This means the automatic execution of all these envs somehow did inadvertenly execute an env that we don't want it to. When you execute that directly and it works, then it means the bootargs was set up correctly, but other envs in the calling chain were not. Or a failure during finding the USB drive has inadvertenly caused the calling sequence to abort.
> If the direct bootm line is working, then MTD1 is
> okay, and the above line seems to be the only
> possibility, where this error could come from.
> (And the direct bootm command from before probably
> is the reason, that it's booting into the rescue
> system anyways in the end, isn't it?)
When you see this rescue login prompt as shown the log above, then it did boot to rescue system
rescue:/tmp#
Let's see what the rescue envs are.
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset bootcmd_pogo=run bootcmd_rescue bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
Here is the revised bootcmd (so that it will be more resilient to the failure previously in bootcmd_exec):
WIth no USB drive plugged in, power up, interrupt console, and:
setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; if run bootcmd_exec; then; else run bootcmd_pogo; fi; reset' boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 01, 2017 03:12PM |
Registered: 7 years ago Posts: 90 |
>bodhi Wrote:
>---
> When you see this rescue login prompt as shown the
> log above, then it did boot to rescue system
>
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?
>
I tried your suggested patch, but this problem remains:
The error wont show, if I boot from USB instead. I don't want to bother you with meaningless problems. The reason why I'm asking about this, is, that I fear this error might make it more critical or even impossible to recover the system in case there's some new trouble in future..
Edited 2 time(s). Last edit at 10/01/2017 05:01PM by ElMariachi.
>---
> 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?
>
> setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; if run bootcmd_exec; then; else run bootcmd_pogo; fi; reset' > boot >
I tried your suggested patch, but this problem remains:
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot: 10
0
GoFlexNet> setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; if run bootcmd_exec; then; else run bootcmd_pogo; fi; reset'
setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; if run bootcmd_exec; then; else run bootcmd_pogo; fi; reset'
GoFlexNet> boot
boot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Reset IDE: ide_preinit failed
no USB devices available
no IDE devices available
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide
Reset IDE: ide_preinit failed
device ide 0:1
** Bad device size - ide 0 **
device ide 1:1
** Bad device size - ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-goflexnet.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
NAND read: device 0 offset 0x100000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2-kirkwide
Created: 2012-10-29 22:52:12 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3627768 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Starting kernel ...
The error wont show, if I boot from USB instead. I don't want to bother you with meaningless problems. The reason why I'm asking about this, is, that I fear this error might make it more critical or even impossible to recover the system in case there's some new trouble in future..
Edited 2 time(s). Last edit at 10/01/2017 05:01PM by ElMariachi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 04, 2017 03:00AM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi ,
With no USB drive plugged in, power up, interrupt console, and:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
With no USB drive plugged in, power up, interrupt console, and:
setenv bootcmd_exec 'if run load_uimage; then if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi; fi' setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; if run bootcmd_exec; then; else run bootcmd_pogo; fi; reset' boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 04, 2017 08:36AM |
Registered: 7 years ago Posts: 90 |
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 04, 2017 04:24PM |
Admin Registered: 13 years ago Posts: 18,548 |
ElMariachi Wrote:
-------------------------------------------------------
> That did the trick!
>
> I'll try understanding this tomorrow, I'm to tired
> right now. :)
That solution is quite easy, but too busy so I forgot this thread for the last a few days:)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> That did the trick!
>
> I'll try understanding this tomorrow, I'm to tired
> right now. :)
That solution is quite easy, but too busy so I forgot this thread for the last a few days:)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 04, 2017 04:36PM |
Admin Registered: 13 years ago Posts: 18,548 |
And btw, that was a really good question. It helps reminding me to revise the default envs. I did not pay enough attention to the Rescue system booting setup in my current uboot releases.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 06, 2017 05:01PM |
Registered: 6 years ago Posts: 11 |
Hello, Bodhi!
can you also help me? I have also a Goflex Net with a serial connection. the version of u-bott is this
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
when i boot without a device i got this
can you help me????
---------
mod edit: please use code tags
Edited 1 time(s). Last edit at 10/06/2017 05:27PM by bodhi.
can you also help me? I have also a Goflex Net with a serial connection. the version of u-bott is this
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
when i boot without a device i got this
NAND read: device 0 offset 0x100000, size 0x300000 3145728 bytes read: OK ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.22.18 Created: 2010-10-19 23:05:02 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1979140 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK Using machid 0xc11 from environment Starting kernel ... Uncompressing Linux............................................................................................................................ done, booting the kernel. I can't automatic boot from USB. I made a Device like https://forum.doozan.com/read.php?2,12096 this instruction but i wont boot. When i make a manuel boot I became this Information GoFlexNet> usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... Use USB retry period from the environment: 15 second(s) 1 Storage Device(s) found GoFlexNet> ext2load usb 0:1 0x800000 /boot/uImage 3833487 bytes read in 419 ms (8.7 MiB/s) GoFlexNet> ext2load usb 0:1 0x1100000 /boot/uInitrd 7245696 bytes read in 505 ms (13.7 MiB/s) GoFlexNet> bootm 0x800000 0x1100000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.12.1-kirkwood-tld-1 Created: 2017-10-06 21:28:43 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3833423 Bytes = 3.7 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: initramfs-4.12.1-kirkwood-tld-1 Created: 2017-07-24 0:18:23 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7245632 Bytes = 6.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK Using machid 0xc11 from environment Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.12.1-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] OF: fdt: Machine model: Seagate GoFlex Net [ 0.000000] bootconsole [earlycon0] enabled [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: console=ttyS0,115200n8 earlyprintk root=/dev/sda1 rootdelay=10 [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Memory: 109436K/131072K available (8192K kernel code, 716K rwdata, 1972K rodata, 1024K init, 288K bss, 21636K reserved, 0K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xc8800000 - 0xff800000 ( 880 MB) [ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc0900000 (9184 kB) [ 0.000000] .init : 0xc0c00000 - 0xc0d00000 (1024 kB) [ 0.000000] .data : 0xc0d00000 - 0xc0db3274 ( 717 kB) [ 0.000000] .bss : 0xc0db9b9c - 0xc0e01e60 ( 289 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns [ 0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [ 0.007980] Switching to timer-based delay loop, resolution 5ns [ 0.014481] Console: colour dummy device 80x30 [ 0.019108] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000) [ 0.029813] pid_max: default: 32768 minimum: 301 [ 0.034726] Security Framework initialized [ 0.039088] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.045825] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.053892] CPU: Testing write buffer coherency: ok [ 0.059961] Setting up static identity map for 0x100000 - 0x100058 [ 0.066513] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2 [ 0.075100] devtmpfs: initialized [ 0.082948] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.093000] futex hash table entries: 256 (order: -1, 3072 bytes) [ 0.099654] prandom: seed boundary self test passed [ 0.108434] prandom: 100 self tests passed [ 0.112644] pinctrl core: initialized pinctrl subsystem [ 0.119176] NET: Registered protocol family 16 [ 0.124188] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.132817] cpuidle: using governor ladder [ 0.137083] cpuidle: using governor menu [ 0.141588] Feroceon L2: Enabling L2 [ 0.145300] Feroceon L2: Cache support initialised. [ 0.150685] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set [ 0.166045] No ATAGs? [ 0.175341] vgaarb: loaded [ 0.180884] SCSI subsystem initialized [ 0.185202] usbcore: registered new interface driver usbfs [ 0.190915] usbcore: registered new interface driver hub [ 0.196409] usbcore: registered new device driver usb [ 0.202699] clocksource: Switched to clocksource orion_clocksource [ 0.298756] VFS: Disk quotas dquot_6.6.0 [ 0.302932] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.320612] NET: Registered protocol family 2 [ 0.325871] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [ 0.333003] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 0.339485] TCP: Hash tables configured (established 1024 bind 1024) [ 0.346059] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.352018] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.358596] NET: Registered protocol family 1 [ 0.363496] RPC: Registered named UNIX socket transport module. [ 0.369531] RPC: Registered udp transport module. [ 0.374410] RPC: Registered tcp transport module. [ 0.379219] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.386040] Unpacking initramfs... [ 0.389547] Initramfs unpacking failed: junk in compressed archive [ 0.415817] Freeing initrd memory: 7076K [ 0.419969] NetWinder Floating Point Emulator V0.97 (double precision) [ 0.427586] audit: initializing netlink subsys (disabled) [ 0.433627] Initialise system trusted keyrings [ 0.438225] Key type blacklist registered [ 0.442411] audit: type=2000 audit(0.420:1): state=initialized audit_enabled=0 res=1 [ 0.450421] workingset: timestamp_bits=30 max_order=15 bucket_order=0 [ 0.450482] zbud: loaded [ 0.458082] NFS: Registering the id_resolver key type [ 0.458099] Key type id_resolver registered [ 0.458103] Key type id_legacy registered [ 0.458116] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.458121] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 0.458312] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 0.458503] fuse init (API version 7.26) [ 0.458867] orangefs_debugfs_init: called with debug mask: :none: :0: [ 0.459133] orangefs_init: module version upstream loaded [ 0.459138] SGI XFS with ACLs, security attributes, realtime, no debug enabled [ 2.562706] random: fast init done [ 6.388691] Key type asymmetric registered [ 6.393168] Asymmetric key parser 'x509' registered [ 6.398216] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 6.405886] io scheduler noop registered [ 6.409910] io scheduler deadline registered [ 6.414420] io scheduler cfq registered (default) [ 6.420308] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 6.435896] loop: module loaded [ 6.440777] libphy: Fixed MDIO Bus: probed [ 6.445782] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 6.452444] ehci-pci: EHCI PCI platform driver [ 6.457088] ehci-orion: EHCI orion driver [ 6.461391] usbcore: registered new interface driver usb-storage [ 6.467870] mousedev: PS/2 mouse device common for all mice [ 6.473894] i2c /dev entries driver [ 6.477840] kirkwood-cpufreq kirkwood-cpufreq: Unable to get cpuclk [ 6.484312] kirkwood-cpufreq: probe of kirkwood-cpufreq failed with error -22 [ 6.491964] hidraw: raw HID events driver (C) Jiri Kosina [ 6.497880] drop_monitor: Initializing network drop monitor service [ 6.504530] NET: Registered protocol family 17 [ 6.509170] Key type dns_resolver registered [ 6.514331] registered taskstats version 1 [ 6.518535] Loading compiled-in X.509 certificates [ 6.523521] zswap: loaded using pool lzo/zbud [ 6.530407] Key type big_key registered [ 6.536300] Key type encrypted registered [ 6.541680] hctosys: unable to open rtc device (rtc0) [ 7.645681] Unable to handle kernel paging request at virtual address c8000000 [ 7.653026] pgd = c0004000 [ 7.655831] [c8000000] *pgd=00000000 [ 7.659518] Internal error: Oops: 5 [#1] PREEMPT ARM [ 7.664587] Modules linked in: [ 7.667747] CPU: 0 PID: 1 Comm: swapper Not tainted 4.12.1-kirkwood-tld-1 #1 [ 7.674911] Hardware name: Marvell Kirkwood (Flattened Device Tree) [ 7.681287] task: c7832e00 task.stack: c7834000 [ 7.685935] PC is at crc32_be+0x6c/0x160 [ 7.689962] LR is at 0xc0950bd0 [ 7.693201] pc : [<c0584814>] lr : [<c0950bd0>] psr: 20000053 [ 7.693201] sp : c7835ef0 ip : c09521e0 fp : 00000000 [ 7.704900] r10: c0db9ba0 r9 : c0c4b838 r8 : 628de917 [ 7.710228] r7 : 00000000 r6 : c7fffffc r5 : 1d3e9e27 r4 : 00000007 [ 7.716864] r3 : 330f6bc9 r2 : 1e1bdfbc r1 : c115f354 r0 : 865e9fec [ 7.723510] Flags: nzCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment none [ 7.730851] Control: 0005397f Table: 00004000 DAC: 00000053 [ 7.736702] Process swapper (pid: 1, stack limit = 0xc7834190) [ 7.742640] Stack: (0xc7835ef0 to 0xc7836000) [ 7.747099] 5ee0: c115f358 f0defde7 ae106ff1 c0c59544 [ 7.755403] 5f00: 00000000 c0c3f8f0 00000007 c0c3f8bc 000000b8 c010178c 00000000 c01334d0 [ 7.763704] 5f20: 00000000 c0299eec 00000000 c0aeb5e0 000000b8 00000007 00000007 c0aec440 [ 7.772006] 5f40: 000000b7 c0aec440 c7ffced2 c7ffcedc c0d0bc24 00000007 c0c4b830 000000b8 [ 7.780307] 5f60: 00000007 c0c4b834 000000b8 c0c59544 c0db9ba0 c0c00e18 00000007 00000007 [ 7.788608] 5f80: 00000000 c0c005ac 00000000 c08331f8 00000000 00000000 00000000 00000000 [ 7.796909] 5fa0: 00000000 c0833200 00000000 c01070f0 00000000 00000000 00000000 00000000 [ 7.805210] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 7.813512] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 [ 7.821830] [<c0584814>] (crc32_be) from [<c0c3f8f0>] (of_fdt_raw_init+0x34/0x78) [ 7.829440] [<c0c3f8f0>] (of_fdt_raw_init) from [<c010178c>] (do_one_initcall+0xa8/0x158) [ 7.837750] [<c010178c>] (do_one_initcall) from [<c0c00e18>] (kernel_init_freeable+0x198/0x260) [ 7.846587] [<c0c00e18>] (kernel_init_freeable) from [<c0833200>] (kernel_init+0x8/0x10c) [ 7.854895] [<c0833200>] (kernel_init) from [<c01070f0>] (ret_from_fork+0x14/0x24) [ 7.862590] Code: e1a05002 e59fe0f4 e3550000 0a00002b (e5963004) [ 7.868798] ---[ end trace 469eb1fe1050d71f ]--- [ 7.873606] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 7.873606] [ 7.882961] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 7.882961]
can you help me????
---------
mod edit: please use code tags
Edited 1 time(s). Last edit at 10/06/2017 05:27PM by bodhi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 06, 2017 05:26PM |
Admin Registered: 13 years ago Posts: 18,548 |
lexa,
When you create the rootfs to boot with this new U-Boot 2016.05-tld-1, you should not do step 4:
So mount the drive on another box and reverse the uImage back to the original. Assuming it is mounted as /media/sdb1 on that box.
Power up, and let it boot automatically, post serial console log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/06/2017 05:30PM by bodhi.
When you create the rootfs to boot with this new U-Boot 2016.05-tld-1, you should not do step 4:
Quote
https://forum.doozan.com/read.php?2,12096
4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).
Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for the exact spelling of your Kirkwood box name).
Generate the uImage with DTB embedded inside:
cd /media/sdb1/boot
cp -a zImage-4.12.1-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.12.1-kirkwood-tld-1 -d zImage.fdt uImage
sync
So mount the drive on another box and reverse the uImage back to the original. Assuming it is mounted as /media/sdb1 on that box.
cd /media/sdb1/boot mv uImage uImage.goflexnet cp -a uImage.orig uImage sync
Power up, and let it boot automatically, post serial console log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/06/2017 05:30PM by bodhi.
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 07, 2017 04:15AM |
Registered: 6 years ago Posts: 11 |
hello bodhi,
thanks for the fast reply, i made the steps, automatic boot don't work, with manuel i got this informations
here the output of printenv
thanks for the fast reply, i made the steps, automatic boot don't work, with manuel i got this informations
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
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
GoFlexNet> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
GoFlexNet> ext2load usb 0:1 0x800000 /boot/uImage
3821592 bytes read in 406 ms (9 MiB/s)
GoFlexNet> ext2load usb 0:1 0x1100000 /boot/uInitrd
7245696 bytes read in 504 ms (13.7 MiB/s)
GoFlexNet> bootm 0x800000 0x1100000
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.12.1-kirkwood-tld-1
Created: 2017-07-20 8:11:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3821528 Bytes = 3.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.12.1-kirkwood-tld-1
Created: 2017-07-24 0:18:23 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7245632 Bytes = 6.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Using machid 0xc11 from environment
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Error: unrecognized/unsupported machine ID (r1 = 0x00000c11).
Available machine support:
ID (hex) NAME
ffffffff Generic DT based system
ffffffff Marvell Kirkwood (Flattened Device Tree)
Please check your kernel config and/or bootloader.
here the output of printenv
arcNumber=3089 baudrate=115200 bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000 bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot; bootdelay=10 bootm_sduf=usb stop; usb start; bootm 0x800000 0x1100000 0x1c00000 console=ttyS0,115200 device=0:1 ethact=egiga0 ethaddr=00:10:75:26:18:CE ipaddr=192.168.170.10 led_error=orange blinking led_exit=green off led_init=green blinking machid=c11 mainlineLinux=yes mtdids=nand0=orion_nand mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) partition=nand0,2 rootdelay=10 rootfstype=ext2 serverip=192.168.170.71 set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts stderr=serial stdin=serial stdout=serial uenv_import=echo importing envs ...; env import -t 0x810000 uenv_load=usb start; ide reset; setenv uenv_loaded 0; for devtype in usb ide; do for disknum in 0; do run uenv_read_disk; done; done uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi uenv_read_disk=if $devtype part $disknum; then run uenv_read; fi usb_boot=run load_dtb; run load_uimage; if run load_initrd; then run bootm_sduf; else bootm 0x800000 - 0x1c00000; fi usb_init=usb start usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd usb_ready_retry=15 usb_root=/dev/sda1 x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),4M@1M(kernel),32M@5M(rootfs),-(data) rw x_bootargs_root=ubi.mtd=2 rootfstype=ubifs x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000 x_bootcmd_usb=usb start Environment size: 1882/131068 bytes
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 07, 2017 04:52PM |
Admin Registered: 13 years ago Posts: 18,548 |
lexa,
> automatic boot don't work,
Understood, that's why I wanted to see the console log!
> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19
> -0700)
> Seagate GoFlex Net
You have the latest u-boot, but the envs are older. You did not flash the default envs image in step 8
So to reset your envs to a good default set:
https://forum.doozan.com/read.php?3,29362,29390#msg-29390
These default envs are set up to boot with the rootfs (uImage is original, does not have the DTB embedded inside).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> automatic boot don't work,
Understood, that's why I wanted to see the console log!
> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19
> -0700)
> Seagate GoFlex Net
You have the latest u-boot, but the envs are older. You did not flash the default envs image in step 8
Quote
8. Flashing default u-boot envs image:
As described in step 1, u-boot envs must be defined in etc/fw_env.config as
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000
A special section (B. Flashing default u-boot envs image) about flashing default u-boot envs is included at the end of this installation procedure. Please follow the instruction in this section B to perform this step before continuing with step 9.
So to reset your envs to a good default set:
https://forum.doozan.com/read.php?3,29362,29390#msg-29390
These default envs are set up to boot with the rootfs (uImage is original, does not have the DTB embedded inside).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Everything gone wrong Cannot boot anything on GoFlex Net October 08, 2017 03:26AM |
Registered: 6 years ago Posts: 11 |
