Welcome! Log In Create A New Profile

Advanced

GoFlexHome Maybe Bricked

Posted by MacKenzie 
Forum List Message List New Topic
MacKenzie
GoFlexHome Maybe Bricked
November 19, 2016 08:13PM
So first thank you for these forums seems like a lot of good info and was enough to think I could follow along and migrate from Arch to Debian.

My setup had been to boot Arch off of the HD mounted on the GoFlexHome. But Debian seemed like a better choice so I dug out an old Arch bootable USB drive and went to work modifying the GoFlex rootfs on the hard drive.

First I followed http://forum.doozan.com/read.php?3,12381 it seemed rather straight forward other than having to install a few additional tools but everything went smoothly.

Next I followed the Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 install instructions.

After reboot everything seems to go normal from a link light and front light POV but the system does not grab an IP from the DHCP server on the router and so I have no way back into the GoFlex. But I have a green link light on the Ethernet port, and the front lights cycle from flashing green, to orange, to solid green.

Thinking maybe I'd messed up the rootfs install I made a bootable USB following the instructions here http://forum.doozan.com/read.php3,30890 Unfortunately it has the same light activity as with the hard drive.

I feel like I must be missing something obvious but I'm not sure what. I don't have a serial cable for this unit so I can't play that way.

Thanks for the help.

-MacKenzie
Reply Quote
bodhi
Re: GoFlexHome Maybe Bricked
November 20, 2016 12:56AM
MacKenzie,

> Next I followed the
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> install instructions.
>
> After reboot everything seems to go normal from a
> link light and front light POV but the system does
> not grab an IP from the DHCP server on the router
> and so I have no way back into the GoFlex. But I
> have a green link light on the Ethernet port, and
> the front lights cycle from flashing green, to
> orange, to solid green.
>

This indicated that the kernel has booted OK. But the rootfs was not mounted successfully.

> Thinking maybe I'd messed up the rootfs install

> I feel like I must be missing something obvious
> but I'm not sure what. I don't have a serial
> cable for this unit so I can't play that way.
>

You must have missed a crucial step in creating the rootfs on USB. Go back to the instruction to create Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on USB. It is very important to follow the steps verbatim (copy and paste if you can).

- Are you the root user while doing this? (sudo will not work).
- Does the USB drive contain a single Ext3 partition?
- Is the rootfs partition labeled rootfs ?

And

- What u-boot are you running? if it is Arch u-boot, then did you follow this instruction to use the uEnv.txt to adjust the u-boot envs during booting?:
http://forum.doozan.com/read.php?3,23727

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/20/2016 12:57AM by bodhi.
Reply Quote
MacKenzie
Re: GoFlexHome Maybe Bricked
November 20, 2016 05:14PM
So I have 2 GoFlex homes:

For one I followed the instructions here : http://forum.doozan.com/read.php?3,12381 to update the U-boot. I'm unable to get back into this one so I can't recheck what is actually running.

On the 2nd that I have not tried to move from Arch here is what it says: 

[root@alarm ~]# grep -a --null-data U-Boot /dev/mtd0ro
Warning: U-Boot configured device %s at address %llx,
 but the device tree has it address %llx.
U-Boot** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!
U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:05) Arch Linux ARM


After attempting to make a bootable rootfs USB I can't get either goFlex to boot from the rootfs drive (with the HDs removed to keep things simple).

Here is the steps I took to build the bootable USB maybe I screwed something up? 

pi@raspberrypi ~ $ su root
Password: 
root@raspberrypi:/home/pi# fdisk -l

Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mmcblk0: 7.3 GiB, 7860125696 bytes, 15351808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000da055

Device         Boot    Start      End  Sectors  Size Id Type
/dev/mmcblk0p1          8192  2121093  2112902    1G  e W95 FAT16 (LBA)
/dev/mmcblk0p2       2121728 15286271 13164544  6.3G 85 Linux extended
/dev/mmcblk0p3      15286272 15351807    65536   32M 83 Linux
/dev/mmcblk0p5       2129920  3178495  1048576  512M 83 Linux
/dev/mmcblk0p6       3186688  3309567   122880   60M  c W95 FAT32 (LBA)
/dev/mmcblk0p7       3317760 15286271 11968512  5.7G 83 Linux

Partition table entries are not in disk order.
Disk /dev/sda: 15 GiB, 16079781888 bytes, 31405824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd1888880

Device     Boot Start      End  Sectors Size Id Type
/dev/sda1        2048 31404031 31401984  15G 83 Linux

root@raspberrypi:/media/pi# umount rootfs
root@raspberrypi:/media/pi# mkfs.ext3 /dev/sda1
mke2fs 1.42.12 (29-Aug-2014)
/dev/sda1 contains a ext3 file system labelled 'rootfs'
	last mounted on /media/pi/rootfs on Mon Nov 21 09:43:51 2016
Proceed anyway? (y,n) y
Creating filesystem with 3925248 4k blocks and 983040 inodes
Filesystem UUID: 6b66842c-3726-4965-b19d-b8651334f0e1
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done   

root@raspberrypi:/media/pi# e2label /dev/sda1 rootfs
root@raspberrypi:/media/pi# mkdir rootfs
root@raspberrypi:/media/pi# ls
data0  rootfs  SETTINGS
root@raspberrypi:/media/pi# mount /dev/sda1 /media/pi/rootfs
root@raspberrypi:/media/pi# cd rootfs
root@raspberrypi:/media/pi/rootfs# wget https://www.dropbox.com/s/qt2v378sm3j0loe/Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2#
--2016-11-21 10:38:45--  https://www.dropbox.com/s/qt2v378sm3j0loe/Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
Resolving www.dropbox.com (www.dropbox.com)... 162.125.4.1
Connecting to www.dropbox.com (www.dropbox.com)|162.125.4.1|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.dropboxusercontent.com/content_link/gOnu01fFLRnw7W4UNQTk9cB3iTuCxHrsKUBoSscETbXrHElYmqnynFEVuMgCQYWD/file [following]
--2016-11-21 10:38:46--  https://dl.dropboxusercontent.com/content_link/gOnu01fFLRnw7W4UNQTk9cB3iTuCxHrsKUBoSscETbXrHElYmqnynFEVuMgCQYWD/file
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 45.58.75.165
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|45.58.75.165|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 143314034 (137M) [application/octet-stream]
Saving to: ‘Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2’

Debian-4.4.0-kirkwo 100%[=====================>] 136.67M  3.31MB/s   in 47s    

2016-11-21 10:39:34 (2.90 MB/s) - ‘Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2’ saved [143314034/143314034]

root@raspberrypi:/media/pi/rootfs# tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@raspberrypi:/media/pi/rootfs# ls
bin						  etc	      media  root  sys
boot						  home	      mnt    run   tmp
Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2  lib	      opt    sbin  usr
dev						  lost+found  proc   srv   var
root@raspberrypi:/media/pi/rootfs# cd boot
root@raspberrypi:/media/pi/rootfs/boot# cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
root@raspberrypi:/media/pi/rootfs/boot# cat dts/kirkwood-goflexhome.dtb >> zImage.fdt
root@raspberrypi:/media/pi/rootfs/boot# mv uImage uImage.orig
root@raspberrypi:/media/pi/rootfs/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
bash: mkimage: command not found
root@raspberrypi:/media/pi/rootfs/boot# apt-get install u-boot-tools
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  u-boot-tools
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 69.8 kB of archives.
After this operation, 202 kB of additional disk space will be used.
Get:1 http://mirrordirector.raspbian.org/raspbian/ jessie/main u-boot-tools armhf 2014.10+dfsg1-5+rpi1 [69.8 kB]
Fetched 69.8 kB in 0s (74.8 kB/s)     
Selecting previously unselected package u-boot-tools.
(Reading database ... 116795 files and directories currently installed.)
Preparing to unpack .../u-boot-tools_2014.10+dfsg1-5+rpi1_armhf.deb ...
Unpacking u-boot-tools (2014.10+dfsg1-5+rpi1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up u-boot-tools (2014.10+dfsg1-5+rpi1) ...
root@raspberrypi:/media/pi/rootfs/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
Image Name:   Linux-4.4.0-kirkwood-tld-1
Created:      Mon Nov 21 11:05:50 2016
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3165437 Bytes = 3091.25 kB = 3.02 MB
Load Address: 00008000
Entry Point:  00008000
root@raspberrypi:/media/pi/rootfs/boot# sync




I then also updated the uEnv.txt as you suggested to see if I could get it to work on my goFlex with the @old@ uboot. No joy for either.

-------
Mod edit: added code tags



Edited 2 time(s). Last edit at 11/20/2016 06:16PM by bodhi.
Reply Quote
bodhi
Re: GoFlexHome Maybe Bricked
November 20, 2016 06:26PM
Quote

I then also updated the uEnv.txt as you suggested to see if I could get it to work on my goFlex with the @old@ uboot. No joy for either.

The above only works with Arch u-boot.

Quote

root@raspberrypi:/media/pi/rootfs# cd boot
root@raspberrypi:/media/pi/rootfs/boot# cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
root@raspberrypi:/media/pi/rootfs/boot# cat dts/kirkwood-goflexhome.dtb >> zImage.fdt
root@raspberrypi:/media/pi/rootfs/boot# mv uImage uImage.orig
root@raspberrypi:/media/pi/rootfs/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
bash: mkimage: command not found
root@raspberrypi:/media/pi/rootfs/boot# apt-get install u-boot-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
u-boot-tools
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 69.8 kB of archives.
After this operation, 202 kB of additional disk space will be used.
Get:1 http://mirrordirector.raspbian.org/raspbian/ jessie/main u-boot-tools armhf 2014.10+dfsg1-5+rpi1 [69.8 kB]
Fetched 69.8 kB in 0s (74.8 kB/s)
Selecting previously unselected package u-boot-tools.
(Reading database ... 116795 files and directories currently installed.)
Preparing to unpack .../u-boot-tools_2014.10+dfsg1-5+rpi1_armhf.deb ...
Unpacking u-boot-tools (2014.10+dfsg1-5+rpi1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up u-boot-tools (2014.10+dfsg1-5+rpi1) ...
root@raspberrypi:/media/pi/rootfs/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
Image Name: Linux-4.4.0-kirkwood-tld-1
Created: Mon Nov 21 11:05:50 2016
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3165437 Bytes = 3091.25 kB = 3.02 MB
Load Address: 00008000
Entry Point: 00008000
root@raspberrypi:/media/pi/rootfs/boot# sync

The above is wrong. Since Arch u-boot look for FDT kernel, so you can't append the DTB.

---------------

Let's pick one and work on it. It is rather confusing if you go back and forth between the 2.

---------------


Take this one with Arch u-boot 

U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:05) Arch Linux ARM

Use the rootfs that you have created, it looks OK until the DTB appending steps. So reverse it

1. mount it on rPi like before, and then restore original uImage 

cd /media/pi/rootfs/boot
cp -a uImage uImage.goflex_home
mv uImage.orig uImage
sync

2. Do the uEnv step:
http://forum.doozan.com/read.php?3,23727

3. Boot with this USB rootfs on the box with Arch u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
MacKenzie
Re: GoFlexHome Maybe Bricked
November 21, 2016 09:48PM
Thank you that got the Arch one to boot with the USB rootfs.

Any suggestions on how to get the unit that I flashed with the uboot.2016.05-tld-1.goflexhome.bodhi.tar to work. Is there some tweak I can make to the rootfs drive that should work with that one?

Thanks
Reply Quote
bodhi
Re: GoFlexHome Maybe Bricked
November 21, 2016 11:02PM
MacKenzie Wrote:
-------------------------------------------------------
> Thank you that got the Arch one to boot with the
> USB rootfs.
>
> Any suggestions on how to get the unit that I
> flashed with the
> uboot.2016.05-tld-1.goflexhome.bodhi.tar to work.
> Is there some tweak I can make to the rootfs drive
> that should work with that one?
>
> Thanks


For the one with uboot.2016.05-tld-1.goflexhome.bodhi.tar installed.

1. Create the USB rootfs as before. And don't append DTB to uImage. We are booting with the separate DTB like Arch u-boot.

2. Copy the uboot.2016.05-tld-1.environment (the content of the default envs in text format) in the u-boot tarball that you've downloaded to the uEnv.txt location in this rootfs. Assuming it is mounted at /media/sdb1. 

cp -a uboot.2016.05-tld-1.environment /media/sdb1/boot/uEnv.txt
3. Modify this uEnv.txt to set the DTB to goflexHome to have the following settings: 

arcNumber=3338
dtb_file=/boot/dts/kirkwood-goflexhome.dtb
ethaddr=xxxxx
ipaddr=yyyyyy
serverip=zzzzz
where xxxx is the GoFlexHome MAC address, yyyyy is the GoFlexHome IP address, zzzzz is your laptop/PC/another-Linux-box IP address.

4. sync and take this to the GoflexHome and boot with it. This USB drive should be the only drive plugged in.

5. After booted into Debian, flash the default envs as instructed in section B in the u-boot installation instruction. 
B. Flashing default u-boot envs image

And do the adjustment similar to step 3 using fw_setenv (note the values are in single quotes): 
fw_setenv arcNumber '3338'
fw_setenv dtb_file '/boot/dts/kirkwood-goflexhome.dtb'
fw_setenv ethaddr 'xxxxx'
fw_setenv ipaddr 'yyyyyy'
fw_setenv serverip 'zzzzz'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: