newbie bricks GoFlex Home

[beausoleil]

Well, I'm embarrassed to say that even as an experienced Linux user, I managed to brick my GoFlex Home when following the instructions to the letter (I think). After a seemingly successful install, I shutdown and rebooted the GoFlex. However, I didn't first configure my laptop with pseudo ethernet ports for use with nc (perhaps the advanced tab should explicitly say to do that first?). So I didn't see any of the console messages upon first reboot of the GoFlex with Arch and UBIT installed. I installed them to a 2GB flash USB drive.

I even tried wireshark to look for any traffic generated by the GoFlex while booting, but didn't see anything.

Any suggestions besides getting a USB-TTY adapter?

[moonman]

does the front led flash at all? if it does it isn't bricked.. netconsole should work regardless if it is first boot or not, also it wont generate any traffic if there is noone to send the messages to.

[beausoleil]

Hmm.... when I tried to quote moonman's reply, I got a forum error "This topic is too old to reply, so, it's locked now. Thanks."


Anyway, the green LED flickers for about 45 seconds on boot, then glows solid green. The GoFlex is plugged into one 100Mb Ethernet port on an AT&T/Motorola DSL/WiFi router', model NVG510. The local IPv4 subnet is private, and the router is also supplying IPv6 connectivity. The laptop I'm using to config and manage the GoFlex from is attached via WiFi.

Today I rebooted the GoFlex, then checked the router's known device list, and found that the GoFlex is on the same private subnet, 192.168.1.0. I guess I was assuming that Arch Linux starts up with a default addresses starting with 10.10.10.1, .2, .3, and .5 according to the Advanced tab of the GoFlex Home page here. But I guess it tries using the dhcp client first...

Anyway, I'm in - the GoFlex isn't bricked just yet . I'll report back on my progress in this same thread.

[moonman]

Only netconsole is on a separate subnet.