Potential brick on pogo v2. Looking for confirmation.

[chriso]

Hello,

My pogo v2 has been running happily since initial install. I wanted to move it to a new location so i did a 'systemctl poweroff'. After this, I cannot access the device, with our without USB devices plugged in. Without removing any of my drives, I plugged it back in but what I get now is a solid green light, no ssh, and no IP assignment. With all USB devices UNPLUGGED, I get no green light, and no IP assignment. I've done lots and lots of reading and it seems that uboot might be messed up? Am I correct that uboot is something on the pogo device itself?

One solution I've tried is running "fsck -f" from another system. There were no errors/issues detected, and the results were the same.

Short of getting the serial cable and reflashing (?) the pogo, is there anything else I can try?

Thanks for any help.

[grayman4hire]

You can not brick your Pogoplug by moving it.

Most likely you just have a bad USB drive. Try reloading a new rootfs on a new USB drive.

[chriso]

I didn't mean that physically moving it caused this, but something with my config and the 3 USB devices (2 external hard drives and arch on a thumb drive) has become so corrupt, I don't know how to proceed. Ultimately, I'm having a difficult time getting the armv5 arch on my pogo.

As you suggested, I attempted to get a new rootfs on it. Here is what I tried:h

1) first tried following the directions here: https://wiki.archlinux.org/index.php/Installation_guide#Installation
This worked and I was able to boot to my thumb drive. However, when I tried plugging it into the pogo, no luck. The instructions had me use pacstrap to put on a base install. I wasn't sure if this "base" install was compatible with the pogo, so I started over.

2) My next attempt was following the arch pogo instructions http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray. I couldn't follow the instructions exactly since I was running from an arch live cd and not the pogo(can't ssh to it). I got as far as step 8 where u-boot is installed. In this step I download the pogo_e02.sh script which installs and flashes u-boot. This is where I stopped. I figured that running pogo_e02.sh would not work since I'm running from an arch live cd and not the alarm rootfs(from the armv5 package above). I attempted to chroot/arch-chroot onto the other file system but got an error that indicated that the architecture between the live cd and arch on the flash drive were different.
I then tried installing syslinux manually, but this also failed as I couldn't chroot on to my pogo rootfs.

Thanks for any help. I've spent a good 6 hours on this today.

[chriso]

Update. Well, after all that, I started the pogo with my last arch install and it worked. The thing is, I didn't install or configure a bootloader. There must be some default with arch?

Now, to figure out how a new Sandisk drive became so corrupt in such a short period. Or, I light this pogo on fire, save myself some time and just buy a Synology.

[hydro]

$this->bbcode_second_pass_quote('chriso', 'T')he thing is, I didn't install or configure a bootloader. There must be some default with arch?

[chriso]

Hydro/grayman - first, thanks a lot for your time in replying. It's very much appreciated.

You are correct that I had arch installed on this pogo e02 from a year ago, prior to mainline u-boot. I'm almost positive I didn't update u-boot on the pogo myself, but perhaps it was done using the arch pogo instructions at that time?

I'm now at the point of trying to figure out what happened. I have ran journactl against the original journal logs on my non-bootable thumb drive. I'm not experienced enough to exactly tell what is wrong. If it is obvious to you, please let me know. Here is the link (wish I knew how to create actual html links)https://dl.dropboxusercontent.com/u/313398/journal.txt.txt

The last thing I see before things start shutting down is a failed dependency on my usb hard drives: "Dependency failed for /media". /media is my mount point for one of my drives. Even if the drives are present, the system still doesn't boot. Could it be that these "dependency" mounts are causing the system to fail?

[moonman]

You can't use x86 binaries on the pogo, and thats what you did by following arch wiki. Use the official reinstall instructions on archlinuxarm.org or a simplified version in my signature. After you get it to boot you really should update to mainline uboot with instructions on the forum here. The second thing you should do is bring your system up to date with pacman -Suy

http://archlinuxarm.org/support/reinstallation
viewtopic.php?f=53&t=7290

As for the log i really dont see anything out of ordinary

[hydro]

$this->bbcode_second_pass_code('', '
Timed out waiting for device dev-sdb1.device.
Timed out waiting for device dev-sdc1.device.
Starting Emergency Shell...
')
You created entries in /etc/fstab for devices that were not present at boot time or have different block device naming, hence, after waiting 90 seconds, systemd switches to emergency mode. On a serial console you would see that you are prompted for the root password to clean up the mess. Just mount the USB drive elsewhere and remove those entries from /etc/fstab or add the mount option nofail or use Labels or UUIDs instead of device names in case the other drives are always connected.

[chriso]

Hydro - you nailed it. Removing those entries from fstab did it. Thanks! Now, I need to educate myself on how to configure persistent/static naming of devices.

Thanks all!

[hydro]

Arch Linux Wiki is your friend.