[RESOLVED] [Goflex Home] booting from HDD

[irq]

Hi everyone!

I was going to install archlinux on my goflex home device today, but it wasn't successful by now.

Using the installation guide http://archlinuxarm.org/platforms/armv5/seagate-goflex-home I followed the steps 1 to 20 without getting an error message from my goflex ssh console.

After rebooting the device i noticed that my dhcp server got a new MAC address and a new ip lease for this device.
So the MAC address of the goflex deviced had chanced after the setup process.

After connecting with SSH to the new leased IP address i was logged in to an alarm console as root.

So i proceeded trough the following "after first reboot" steps, running a full system update and installed the required packages.

After reboot i get a bit astonished because my ssh connect runs into the alarm console again.

So i'm not sure if this state of my goflex is correct now?

Uname's output:

$this->bbcode_second_pass_code('', '[root@alarm ~]# uname -a
Linux alarm 3.0-ARCH #1 PREEMPT Tue Oct 18 23:56:25 UTC 2011 armv5tel Feroceon 88FR131 rev 1 (v5l) Seagate GoFlex Home GNU/Linux
[root@alarm ~]#
')

Logging the boot procedure with nc drops the following lines:

$this->bbcode_second_pass_code('', 'U-Boot 2010.09 (Feb 16 2011 - 18:44:23)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(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
Hit any key to stop autoboot: 0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
** Block device usb 0 not supported
** Block device usb 0 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 1 not supported
** Block device usb 1 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 2 not supported
** Block device usb 2 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 3 not supported
** Block device usb 3 not supported

** Invalid boot device **

** Invalid boot device **

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: ST31000528AS Firm: CC46 Ser#: 6VP99WZJ
Type: Hard Disk
Supports 48-bit addressing
Capacity: 953868.6 MB = 931.5 GB (1953523055 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2675436 bytes read
Loading file "/uInitrd" from ide device 0:1 (hda1)
** File not found /uInitrd
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
2643862 bytes read
## Booting kernel from Legacy Image at 00680000 ...
Image Name: Linux-3.0-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2675372 Bytes = 2.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: UBIT-2010.11-00125-ga21bcca
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 2643798 Bytes = 2.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...
')

After "starting kernel" nothing more happend and my ssh connect runs into the alarm@root console as mentioned above.

Any hints or ideas?

Thx a lot!

[WarheadsSE]

Uboot: good, spot on even (notice hda1? that is the internal HDD )

kernel messages are on a different ip/port

You should always get the to root@alarm, unless you login as someone other than root

[irq]

yes i noticed that hda1 is tne internal HDD but i was not sure if i was at the end of the setup procedure and everything went fine

So i can feel free installing packages, daemons and adding users etc?

[WarheadsSE]

Should be, yes.

[irq]

thx a lot

"problem" solved and thread can be closed