No Network Access on GoFlex

[ignignokt]

Hello. I did my weekly update as usual and shut it down. Started it up the next day and it was no longer showing up on my network. Two days later and I'm still at a loss as to what's wrong. I had a thumb drive previously setup from last year so I decided to boot from it. Same exact problem. Solid green light, but no ip address was registering. I then read about the new systemd causing these problems, but why would my thumb drive not register an ip if it hadn't been touched in over a year? I decided the drive must be corrupt and reformatted the drive and put a fresh copy of arch (Kirkwood) back on it. I was able to get an ip this time and began getting the files I'd need to fix my GoFlex. I mounted the drive and followed some of the fixes I'd read about. Here's what's confusing me. If I mount and unmount the drive and reboot, I loose network access through the thumb drive. Even if I make no modifications. I then have to format the thumb drive and put arch on it again in order to get an ip. It's looking like I'm going to have to do a clean install of arch, but just mounting and unmounting the 3 TB drive shouldn't be causing this. I guess I'll search the logs on the thumb drive, but I don't have much of a clue as to what I'm looking for.

[ignignokt]

I'm still not having any luck. I'd appreciate any help in trying to diagnose it. I mainly want to get network connectivity back. Thanks in advance and I apologize for being a newbie. If I should be posting under software instead just let me know and I'll close the thread and post there. Thanks.

It's possible my problem is the same as this: viewtopic.php?f=53&t=6695

My install isn't new. It's at least 18 months old, but my symptoms are the same.

[WarheadsSE]

Use a spare USB, and a chroot, to upgrade your kernel to linux-kirkwood, and tray again.

[ignignokt]

Thanks for the reply. I've got the thumb drive ready, but I need help installing kirkland onto the sata drive using the thumbdrive. Basically I'm going to use wget to get the file and direct it to extracxt the .tar on the sata drive i.e sda1 or sdb1 (whichever it shows up as). Overwriting the old files and then rebooting without the thumb drive and hope all goes well. Correct? Do I use chroot like this: arch-chroot /mnt/arch /bin/bash I've never had to use it before. I know that I'm changing the root directory to the sata. Just unsure of the correct command, I'm basically a newbie and I'm not afraid to admit it.

[WarheadsSE]

If you have devtools(-alarm) installed, then you can use arch-chroot, yes.

$this->bbcode_second_pass_code('', '
[root@usb}# mount /dev/sda1 /mnt
[root@usb}# arch-chroot /mnt /bin/bash -l
[root@sata}# pacman -S linux-kirkwood
')

You can also use -U *.pkg.tar.xz

[ignignokt]

I had problems getting the file for some reason:

[root@alarm ~]# arch-chroot /mnt /bin/bash -l
[root@alarm /]# pacman -S linux-kirkwood
resolving dependencies...
looking for inter-conflicts...
:: linux-kirkwood and linux are in conflict. Remove linux? [y/N] y

Packages (2): linux-3.1.10-33 [removal] linux-kirkwood-3.14.5-1

Total Download Size: 17.63 MiB
Total Installed Size: 19.94 MiB
Net Upgrade Size: 3.37 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
error: failed retrieving file 'linux-kirkwood-3.14.5-1-arm.pkg.tar.xz' from or.archlinuxarm.org : The requested URL returned error: 404 Not Found
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.
synchronizing filesystem...
[root@alarm /]#


I had to install arch-install-scripts in order to use the chroot command. Here's what I did prior to that I wanted to make sure I had the correct drive partition:

[root@alarm ~]# /sbin/fdisk /dev/sdb1

Welcome to fdisk (util-linux 2.24.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.

Created a new DOS disklabel with disk identifier 0xf6f693b1.

Command (m for help): p
Disk /dev/sdb1: 20 GiB, 21474836480 bytes, 41943040 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
Disklabel type: dos
Disk identifier: 0xf6f693b1


Command (m for help): q

[root@alarm ~]# mount /dev/sdb1 /mnt
[root@alarm ~]# arch-chroot /mnt /bin/bash -l
-bash: arch-chroot: command not found
[root@alarm ~]# pacman -S arch-chroot
error: target not found: arch-chroot
[root@alarm ~]# pacman -S chroot
error: target not found: chroot
[root@alarm ~]# pacman -S arch-install-scripts
resolving dependencies...
looking for inter-conflicts...

Packages (1): arch-install-scripts-13-1

Total Download Size: 0.01 MiB
Total Installed Size: 0.05 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
arch-install-script... 6.1 KiB 512K/s 00:00 [######################]
(1/1) checking keys in keyring [######################]
(1/1) checking package integrity [######################]
(1/1) loading package files [######################]
(1/1) checking for file conflicts [######################]
(1/1) checking available disk space [######################]
(1/1) installing arch-install-scripts [######################]
synchronizing filesystem...
[root@alarm ~]# arch-chroot /mnt /bin/bash -l

[ignignokt]

I may have found out why I can't retrieve it:

Updated 29 May 2014:

I've removed kernel linux-3.14.0-kirkwood-tld-2 temporarily, to investigate possible missconfiguration regarding the NSAxxx boxes sensors. Since then it was tested to be working OK, if you're already running kernel linux-3.14.0-kirkwood-tld-2 there is no need to do anything.

Should I update my uboot as the person in the other thread I linked to suggested? I don't have a serial connection and I'd hate to brick it.

[WarheadsSE]

$this->bbcode_second_pass_quote('ignignokt', 'l')inux-3.14.0-kirkwood-tld-2

[ignignokt]

K. My bad. I see up in the forum tree it does says debian. Once again I really appreciate your help. I'll just keep trying. Hopefully the file will be back up soon.

[ignignokt]

I decided to try -Sy instead of -S and it found a newer version and installed. Still a no go goflex. I don't have a light anymore and still no ippp. It suggested that some older pogo users update their uboot. I'll include everything I did in case I royally ... u know:


pacman -Sy linux-kirkwood
:: Synchronizing package databases...
core 166.9 KiB 293K/s 00:01 [######################] 100%
extra 1983.6 KiB 311K/s 00:06 [######################] 100%
community 2.3 MiB 360K/s 00:07 [######################] 100%
alarm 27.6 KiB 384K/s 00:00 [######################] 100%
aur 63.9 KiB 64.3K/s 00:01 [######################] 100%
resolving dependencies...
looking for inter-conflicts...
:: linux-kirkwood and linux are in conflict. Remove linux? [y/N] y

Packages (2): linux-3.1.10-33 [removal] linux-kirkwood-3.14.6-1

Total Download Size: 17.63 MiB
Total Installed Size: 19.95 MiB
Net Upgrade Size: 3.38 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
linux-kirkwood-3.14... 17.6 MiB 364K/s 00:50 [######################] 100%
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(2/2) checking available disk space [######################] 100%
(1/1) removing linux [######################] 100%
(1/1) installing linux-kirkwood [######################] 100%
>>> Updating module dependencies. Please wait ...
**********************************************************************
WARNING! This kernel requires a newer U-Boot than many devices such as
the Dockstar and Pogoplug v2 originally came with. If you do
not have an updated version, your system WILL NOT BOOT.
**********************************************************************
Optional dependencies for linux-kirkwood
crda: to set the correct wireless channels of your country
synchronizing filesystem...
[root@alarm /]# umount /dev/sdb1
[root@alarm /]# shutdown -h now
Running in chroot, ignoring request.
[root@alarm /]# exit
logout
[root@alarm ~]# shutdown -h now