Current Position:Home > Had operational Goflex - plugged in USB WD MyBook, cannot boot & no IP

Had operational Goflex - plugged in USB WD MyBook, cannot boot & no IP

Update:10-11Source: network consolidation
Advertisement
Hello Archers!
Situation;
Arch Linux Seagate Goflex Home (SG-GFH) was fully operational but now not getting IP address after plugging in USB Western Digital My Book Essentials (USB-WD-MBE) and restarting.
Environment;
1 NetGear WND3700 v2 router.
1 Laptop computer running Ubuntu Linux 12.04 .
1 Seagate GoFlex Home (SG-GFH) with Arch Linux) connected directly to router.
1 USB Western Digital My Book Esstentials (USB-WD-MBE)
Events;
Recently installed Arch Linux on SG-GFH.
Setup 3 partitions - 1st partition for system, 2nd for swap and 3rd for data.
Create mount point for 3rd partition.
Setup NFS.
Installed some additional packages, Webmin, etc.
Everything seemed to be working fine.
Connected USB-WD-MBE to laptop.
Used Filezilla to successfully copy 150 GBs of data from laptop with USB-WD-MBE to the SG-GFH. Transfer rate was very slow.
To see if I could get better transfer speed I plugged in the USB-WD-MBE into the USB port on the SG-GFH.
I verified that the SG-GFH was seeing the USB-WD-MBE (/dev/sdc). I did not setup any mount points or modify fstab, etc.
I restarted the SG-GFH with the USB-WD-MBE plugged in and now not getting IP address.
So, I shutdown everything and powered up again, still no ip.
Then, I disconnected the USB-WD-MBE and powered up, still no ip.
I shutdown everything again and pulled the disk from the SG-GFH.
I placed a bootable USB (SanDisz Cruiser) into USP port on SG-GFH.
Upon restart, I could see that the router assigned 192.168.1.2 to the device named "ALARM".
I can ping successfully 192.168.1.2 *** BUT *** I cannot ssh into it "Connection refused".
$ ssh -v [email protected]
OpenSSH_5.9p1 Debian-5ubuntu1.1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.1.2 [192.168.1.2] port 22.
debug1: connect to address 192.168.1.2 port 22: Connection refused
ssh: connect to host 192.168.1.2 port 22: Connection refused
Ran port scan (Network Tools) nothing returned.
So what can I do. Is it possible to get it back?
I am not sure if the USB-WD-MBE had anything to do with this.
I cannot ssh in and not even sure if I can do a complete re-install.
Any assistance much appreciated!
Max...
Last edited by maxmcbyte (2013-11-09 06:16:30)

The Best Answer

Advertisement
Frustrated but determined, I decided to try one more time with Arch Linux. I went ahead and *** re-created *** another bootable USB with Arch Linux on it and this time the SG-GFH booted up with IP and I can ssh into it! Something must have happened to my other USB with Arch Linux on it. With the original bootable USB/Arch Linux that I created I could get an IP address but *** could not ssh (connection refused) ***, weird!!!
After booting up with the new bootable USB/Arch Linux, I placed the SATA drive in the craddle and mounted the partitions on sdb and they all (sdb1 - system, sdb2 - swap, sdb3 - large partition for data) appear normal.
THE PROBLEM
I want to be able to boot like before.
I want to boot using Arch Linux with the SATA drive in the craddle. I do not want to boot with the USB/Flash/Arch Linux.
How can I accomplish this?
REVIEW
Currently, the boot flag is set on the existing sdb1 partiton. But, if I remove the bootable USB/Arch Linux and starting with the SATA drive in the craddle (SATA now becomes sda1) is the same as it was before, have a green light but no IP.
If I use the bootable USB/Arch Linux I get IP, can ssh and see the existing partitons on the SATA drive.
Any tips greatly appreciated!
Max...