Green Led Blinking

[gigigunner]

OK now I am perfectly able to update after deleting the files that you have shown me, thanks!

Tests continue

[slycat]

Figured that was it, happened to the lot of us.

Make sure to run

Code: Select all

pacman -Syyuu
pacman -S udev-oxnas

udev might have been causing problems and dumping errors in the logs.

For the LED: http://archlinuxarm.org/forum/viewtopic.php?f=29&t=1362
As far as I am concerned the newest rootfs has the proled script already there?
I may be mistaken. If I am check here for a way to get the proper files to make it work.

[gigigunner]

[root@alarm ~]# pacman -Syyuu
:: Synchronizing package databases...
core 4.1K 5.3K/s 00:00:01 [######################] 100%
extra 4.1K 5.8M/s 00:00:00 [######################] 100%
community 4.1K 22.5K/s 00:00:00 [######################] 100%
aur 4.1K 11.4K/s 00:00:00 [######################] 100%
:: Starting full system upgrade...
there is nothing to do

[root@alarm ~]# pacman -S udev-oxnas
error: target not found: udev-oxnas

For the led I read the thread that you reported.

For the rest, unfortunately, I did not understand much... both for my bad English that my preparation for the very basic matter

[slycat]

Looks like your plug is up-to-date then.

Code: Select all

[root@AtomAnt ~]# pacman -Q udev-oxnas
udev-oxnas 171-2
[root@AtomAnt ~]# pacman -S udev-oxnas
warning: udev-oxnas-171-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Targets (1): udev-oxnas-171-2

Total Download Size:    0.18 MB
Total Installed Size:   1.74 MB

Proceed with installation? [Y/n]

I found it just fine not sure what happened.

If you'd like try joining the IRC: http://archlinuxarm.org/support/irc
Most of the people there are a little more hands-on and can probably walk you through on how to fix the LED (and the udev-oxnas).

EDIT: Try this:

Code: Select all

pacman -U http://archlinuxarm.org/arm/core/udev-oxnas-171-2-arm.pkg.tar.xz
##the -U flag lets you manually locate the package (local or internet)

[gigigunner]

[root@alarm ~]# pacman -Q udev-oxnas
udev-oxnas 171-2
[root@alarm ~]# pacman -S udev-oxnas
error: target not found: udev-oxnas

Tomorrow I try to get on IRC channel

[WarheadsSE]

pacman -Scc
pacman -Syy

Clear cache & force re-download of package indexes.

[pearldiver]

[root@alarm ~]# pacman -Q udev-oxnas
udev-oxnas 171-2
[root@alarm ~]# pacman -S udev-oxnas
error: target not found: udev-oxnas

Tomorrow I try to get on IRC channel

Hi Gigigunner,

I have got the same thing. First i had a bad flash. Performed "Help! It stopped working! instructions".
Now the PogoPlug boots up and i am able to logon (SSH). However my Led continues to blink and does not stop.

Have you resolved your problem? Please post solution if so!

Regards,
Pearldiver

[WarheadsSE]

From here:viewtopic.php?f=29&t=1551&p=8868#p8868

Code: Select all

mkdir -p /usr/local/cloudengines/bin
mkdir /tmp/ce
mount -t ubifs -o ro ubi0:rootfs /tmp/ce

cp /tmp/ce/usr/local/cloudengines/bin/xce.ko /usr/local/cloudengines/bin/
cp /tmp/ce/usr/local/cloudengines/bin/blparam /usr/local/cloudengines/bin/
cd /
umount /tmp/ce

Also

Now create a new file and add the mac address

touch /usr/local/mac_addr
echo "XX:XX:XX:XX:XX:XX" > /usr/local/mac_addr

#replace x's with your mac address, should be on bottom of your pogo

[pearldiver]

From here:viewtopic.php?f=29&t=1551&p=8868#p8868

Code: Select all

mkdir -p /usr/local/cloudengines/bin
mkdir /tmp/ce
mount -t ubifs -o ro ubi0:rootfs /tmp/ce

cp /tmp/ce/usr/local/cloudengines/bin/xce.ko /usr/local/cloudengines/bin/
cp /tmp/ce/usr/local/cloudengines/bin/blparam /usr/local/cloudengines/bin/
cd /
umount /tmp/ce

Also

Now create a new file and add the mac address

touch /usr/local/mac_addr
echo "XX:XX:XX:XX:XX:XX" > /usr/local/mac_addr

#replace x's with your mac address, should be on bottom of your pogo

Thanks WarheadsSE, that did the trick. Now i have a nice orange LED.

[aelfwyne]

If the pogoplug is working fine, reboots fine, etc... Then suddenly one day on reboot it is blinking green and won't boot, when no changes have been made, does that indicate a drive failure? I'm incredibly disappointed, I've only been running it for about a week and had a lot of things configured, files on drives, etc... the files are available from the external drives, but the configuration I assume is blasted away due to a bad thumb drive?

I avoided using a 2.5" sata (which I have) because I wanted it to be portable, and having a bare hard drive sticking out the top isn't very portable in my book.... but apparently it's a thumb drive eater....