Pogoplug v2 doesn't show up on LAN after Archlinux install

[Waynosan]

Hi,
I performed the steps on this page on my Pink POGO-E02:
http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray#qt-platform_tabs-ui-tabs2

Aside from having to use tar instead of bsdtar to extract the distro everything worked fine up to step 9. I received a success message after flashing u-boot. Unfortunately after reboot the drive does not show up on my network (looking for the MAC address under connected devices). I also cannot SSH into it at the old IP address and there is no PING reply there either.

The pogoplug light on the front of the unit does not light. I do see the USB drive activity light flash for some time but then it stops. I tried rebooting without the USB drive inserted and the same thing happens. Is it bricked? Everything seemed to work fine until reboot.

I know the unit is not completely dead because the green LED (and only the green LED) on the network plug flashes when I plug it in.

Full disclosure: I'm a linux noob

Please advise and thank you.

Update: I tried creating another USB stick per this post http://archlinuxarm.org/forum/viewtopic.php?p=19207&sid=9735a59351f36c508aa0596fac33952d#p19207
With that USB drive the pogoplug light turned green but still no network activity...

[Socaltom]

USB sticks can be finicky, some work, some don't. How many times did you try rebooting?
Tom

also , how big were the USB sticks?

[Waynosan]

Hi Tom,
Tried rebooting about a half-dozen times between the two sticks. Sticks were 4GB and 16GB. Speaking of which, is there noticeable advantage to using a fast USB stick? I don't want to put ALARM on the attached HD because I will physically detach it and connect it to the PC if I need to move huge amounts of data.

From the research I've done it seems that uboot got messed up?

Also, I had archlinux on this box in the past, but I finally got around to trying to use it after installing it on a year+ ago. Since I didn't know how to update the files I decided to start over. I do have a second identical Pogoplug but I don't want to mess with it since I actually use that one as intended.

One thing I realized is that I never ran the 'sync' command after untarring the distro... perhaps that was the source of this issue...

I believe a friend of mine has a USB to serial TTL cable but I'm not sure if that is the next logical step or if there are other troubleshooting steps that I should take first. If it's reading off of the USB drive, is there a way set it up to reflash the uboot automatically from that?

[Socaltom]

Yes, there is an advantage to a fast USB stick. Was 2nd hard drive connected when you tried to boot? If so that could be the problem. The faster drive will be the one that it tries to boot, and spinning rust almost always beats a USB stick.

If you don't plug in any drives what happens?
Tom

[Waynosan]

I only tried powering the Pogoplug up with either just a USB drive or no drives connected. I did not connect any hard-drives.

To summarize:
1) with no drives connected it just sits there and never shows up on the network. The only reason I know it's on is because the green ethernet LED is on solid.
2) With the original USB drive I can see drive activity for a while (flashing LED on the stick), but it ends up in the same state as without any drives connected. No network, solid green ethernet LED.
3) When I boot it up with the "rootfs" USB drive connected, behaviour is like in item 2 BUT this time the front Pogoplug LED turns solid green. No network, solid green ethernet LED.

From other posts it looks like there may be some log files written to the USB stick? I'm just not sure where to find them. I do have LInux Mint installed on a PC (using it right now in fact), so I can read the filesystem on the USB stick... just not sure what to look for...

In case worse comes to worst, I ordered one of these on ebay...

1 PC OF A , USB TO UART TTL , CP2102 (chipset) SERIAL MODULE ADAPTER 5V,3.3V OUTPUT , 6 PINS 3.3V , RST , TXD , RXD , GND & 5V ,BAUD RATE 300 BPS TO 1.5 MBPS , INTERNAL BYTE RECEIVE BUFFER , 640 BYTE TRANSMIT BUFFER ,SILICON LABS MAKES THE CHIP SET

[Socaltom]

Its using systemd, so the journal can be read with journalctl
Here is the manpage. I'm not sure if you have that with mint

http://man7.org/linux/man-pages/man1/journalctl.1.html

a V2 pogoplug should still boot to the pogoplug linux prompt with no drive attached, so that's odd behaviour.

the cable maybe what you need, but that goes beyond my expertise, so hopefully someone else can help you out.
Tom

[Waynosan]

Any recommendations on where I can ask for more help with this?

[bodhi]

$this->bbcode_second_pass_quote('Waynosan', 'A')ny recommendations on where I can ask for more help with this

[Waynosan]

Got the serial cable earlier than expected. Here is the output when I try running a USB stick with rootfs. Network setup issue of some sort? Please let me know what I need to do to proceed to restore the box and start over....

$this->bbcode_second_pass_code('', '
U-Boot 2014.04.R3-1 (May 26 2014 - 19:45:55) Arch Linux ARM
Pogo E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 2048 7825408 00057ae5-01 83
Attempting to boot from usb 0:1...
** File not found /boot/uEnv.txt **
Checking if uenvcmd is set ...
Running default loadzimage ...
** File not found /boot/zImage **
Running default loaduimage ...
3124168 bytes read in 437 ms (6.8 MiB/s)
Booting from 0 ...
## Booting kernel from Legacy Image at 00810000 ...
Image Name: Linux-3.1.10-34-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3124104 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 14.998111] rtc-mv rtc-mv: internal RTC not ticking
[ 15.005906] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 15.953080] sd 0:0:0:0: [sda] No Caching mode page present
[ 15.958644] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 15.967206] sd 0:0:0:0: [sda] No Caching mode page present
[ 15.972878] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 16.305582] sd 0:0:0:0: [sda] No Caching mode page present
[ 16.311130] sd 0:0:0:0: [sda] Assuming drive cache: write through


U-Boot 2014.04.R3-1 (May 26 2014 - 19:45:55) Arch Linux ARM
Pogo E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 2048 7825408 00057ae5-01 83
Attempting to boot from usb 0:1...
** File not found /boot/uEnv.txt **
Checking if uenvcmd is set ...
Running default loadzimage ...
** File not found /boot/zImage **
Running default loaduimage ...
3124168 bytes read in 451 ms (6.6 MiB/s)
Booting from 0 ...
## Booting kernel from Legacy Image at 00810000 ...
Image Name: Linux-3.1.10-34-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3124104 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 15.087249] rtc-mv rtc-mv: internal RTC not ticking
[ 15.095048] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 16.042221] sd 0:0:0:0: [sda] No Caching mode page present
[ 16.047780] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 16.056221] sd 0:0:0:0: [sda] No Caching mode page present
[ 16.061901] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 16.292222] sd 0:0:0:0: [sda] No Caching mode page present
[ 16.297773] sd 0:0:0:0: [sda] Assuming drive cache: write through

Welcome to Arch Linux ARM!

[ OK ] Created slice Root Slice.
[ OK ] Listening on Journal Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Listening on Journal Audit Socket.
[ OK ] Created slice User and Session Slice.
Expecting device dev-ttyS0.device...
[ OK ] Reached target Encrypted Volumes.
[ OK ] Listening on LVM2 metadata daemon socket.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ OK ] Reached target Paths.
[ OK ] Reached target Remote File Systems.
[ OK ] Reached target Swap.
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Created slice System Slice.
Starting Setup Virtual Console...
[ OK ] Reached target Slices.
Starting Create list of required st... nodes for the current kernel...
Mounting Temporary Directory...
Mounting POSIX Message Queue File System...
[ OK ] Created slice system-getty.slice.
Starting Apply Kernel Variables...
Starting Journal Service...
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on udev Kernel Socket.
Starting udev Coldplug all Devices...
Starting Remount Root and Kernel File Systems...
Mounting Debug File System...
[ OK ] Created slice system-serial\x2dgetty.slice.
[ OK ] Set up automount Arbitrary Executab...ats File System Automount Point.
[ OK ] Mounted Debug File System.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Temporary Directory.
[ OK ] Started Setup Virtual Console.
[ OK ] Started Create list of required sta...ce nodes for the current kernel.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started Journal Service.
[ OK ] Started udev Coldplug all Devices.
Starting Flush Journal to Persistent Storage...
Starting Load/Save Random Seed...
Starting Create Static Device Nodes in /dev...
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Flush Journal to Persistent Storage.
Starting Create Volatile Files and Directories...
[ OK ] Found device /dev/ttyS0.
[ OK ] Started Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
[ OK ] Reached target System Time Synchronized.
[ OK ] Reached target System Initialization.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Login Service...
Starting Entropy Harvesting Daemon...
Starting D-Bus System Message Bus...
[ OK ] Started D-Bus System Message Bus.
Starting Network Service...
Starting Permit User Sessions...
[ OK ] Reached target Timers.
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
[ OK ] Started Entropy Harvesting Daemon.
[ OK ] Started Permit User Sessions.
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
Starting Serial Getty on ttyS0...
[ OK ] Started Serial Getty on ttyS0.
Starting Getty on tty1...
[ OK ] Started Getty on tty1.
[ OK ] Reached target Login Prompts.
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
[ OK ] Started Login Service.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
[ OK ] Reached target Network.
Starting OpenSSH Daemon...
[ OK ] Started OpenSSH Daemon.
Starting Network Name Resolution...

Arch Linux 3.1.10-34-ARCH (ttyS0)

alarm login:
')

[WarheadsSE]

Log in, and check the mount options on /