goflex home - don't start from harddisk

[hdhwx42]

Hello all,
Arch Linux doesn't start from harddisk.

I installed ArchLinux on my GoFlexHome for a few years. At that time the installation from scratch worked fine.
I've used my GoFlex Home as backup-server.
For a few days the harddisk dies. Now I try to install Archlinux on a new harddisk -- 3TB.

I created a RescueUSB:
* the Goflex home boots with the flashdrive (with or without harddrive plugged in)
* LED is green
* ssh works fine

1) I used this instruction: http://archlinuxarm.org/support/reinstallation
2) I installed ArchLinux: http://archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz more than one time - but archlinux doesn't boot from the harddisk -- LED ist green blinking
3) unfortunately -- my frustiating level arised and I did the installation documented here: http://archlinuxarm.org/platforms/armv5/seagate-goflex-home and downloaded and flashed the U-Boot again.
4) but nothing changes -- LED ist still blinking.

I have no serial hardware -- and I'm not firm enough to setup netconsole -- I don't want brick my Goflex Home.
May someone can help.
Thanks in advance

[wobble]

I don't own a GFH, but the TLDR of what I understand from this thread is: The installation instructions install an old version of uboot that can't handle disks > 2 TB so you have to upgrade uboot before it will boot from the hd.

[hdhwx42]

Hi wobble,

thanks for your info.

Due to this I updated to U-Boot 2015.10-1: http://www.luthiano.com/Instalando-Arch-Linux-ARM-no-Seagate-GoFlex-Home/.

After reboot the LED switched to solid GREEN.
But I cannot find the GoFlexHome in my LAN.

The boot process looks like this:
a) LED flashes GREEN
b) after a while LED ist ORANGE (approx. 1sec)
c) then LED is solid GREEN
d) and the WHITE LED flashes a little bit and goes out

The boot process is the same either harddrive or USBstick is inserted.

My situation is more bad, isn't it?

Thanks for help.

[hecatae]

@hdhwx42

can you install the rescue system, see viewtopic.php?f=30&t=8383

Hello all,

sorry for my late reply. Ich ordered a serial cable and got it last friday.
Now I have access to the serial interface. I can see the boot process but have no idea what is going wrong (see ERRORs) and how I can solve the problem -- hope somebody can help.

Regards
hdhwx42

a) First the info about the firmware:
$this->bbcode_second_pass_quote('', '
')U-Boot 2015.10-1 (Nov 28 2015 - 01:54:16 -0700) Arch Linux ARM
Seagate GoFlex Home

SoC: Kirkwood 88F6281_A1
DRAM: 128 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
IDE: Bus 0: ..OK Bus 1: not available
Device 0: Model: HGST HDN724030ALE640 Firm: MJ8OA5E0 Ser#: PK1234P9J6PJEX
Type: Hard Disk
Supports 48-bit addressing
Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
No link on egiga0
ping failed; host 10.10.10.5 is not alive
Hit any key to stop autoboot: 0
GoFlexHome>

[moonman]

Fix PARTUUID on your bootable media.

[hdhwx42]

Hello moonman,
yes you are right -- but how does it work?

I found this https://archlinuxarm.org/forum/viewtopic.php?f=58&t=9798&p=50505&hilit=PARTUUID#p50455.

Does this work on the recovery shell?
$this->bbcode_second_pass_code('', 'rootfs=`mount | sed -n 's/^\([^ ]*\).* \/ .*/\1/p'`
rootuuid=`blkid $rootfs | sed -n 's/^.*\(PARTUUID=\)\"\(.*\)\"$/\1\2/p'`
echo root=${rootuuid} > /boot/uEnv.txt')

Thanks for your advice.

Regards
hdhwx42

[hdhwx42]

And I found this:

http://thedaneshproject.com/posts/find-partition-uuid-arch-linux/

I'll try this and will give feedback.

Regards

[moonman]

There was a thread on this forum somewhere. PARTUUID is not the same thing as UUID. Your PARTUUID is messed up as it cannot be all zeroes. One way to fix is to fix PARTUUID by using fdisk advanced menu, second is to add UUID in uEnv.txt
e.g.
$this->bbcode_second_pass_quote('', 'r')oot=UUID=xxxxxxxxxxxxx

[summers]

Woah, my code apearing else where My command will typically only work once you have got inside a linux os ... or more specifically it sets up root to be the root file system of the linux you are currently in. So its only useful if you have found a way of booting into the standard arch linux os ... mind you, if you know your root partition, and just set the first line to that, the second will give what you need in uEnv.txt

As you have access to the uart, you should (I think) be able to do:

set root /dev/sdan

Where n is is your root parition, so probably

set root /dev/sda1
or
set root /dev/sda2

You'll need to interupt uboot to type it.

Then to boot - hmm tries to remeber what it set to on your uboot, probably bootcmd, or maybe startboot.