Pogoplug stuck after usb boot

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Pogoplug stuck after usb boot

Postby frankzan » Wed Jul 11, 2012 5:28 pm

Hi all, I installed many times on many usb sticks archlinux as it is discribed here. But every time I'm not able to access the box. The front led is orange and the network port is blinking green. The yellow led is out. My router shows the mac and ip address, but I can't connect.

Is there any log? Nc does not work.

many thanks upfront.

Frank
frankzan
 
Posts: 7
Joined: Wed Jul 11, 2012 4:58 pm

Re: Pogoplug stuck after usb boot

Postby WarheadsSE » Wed Jul 11, 2012 7:09 pm

Which device do you have, exactly?

Try adding this to rc.local, so that it will boot, then shut down safely. Then you can read the logs.
$this->bbcode_second_pass_code('', '
sleep 5
/sbin/halt
')
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pogoplug stuck after usb boot

Postby frankzan » Wed Jul 11, 2012 7:22 pm

it's a Pogoplug v2 POGO-E02.
I did not get you. I have no access to the box if I boot it with a usb stick. Is there any log on the stick?
frankzan
 
Posts: 7
Joined: Wed Jul 11, 2012 4:58 pm

Re: Pogoplug stuck after usb boot

Postby WarheadsSE » Wed Jul 11, 2012 8:31 pm

Yes, that is what I was referring to.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pogoplug stuck after usb boot

Postby frankzan » Wed Jul 11, 2012 8:59 pm

I did it. No change - no log. I changed /etc/rc.local on my usb stick and included "sleep 5 /sbin/halt".
frankzan
 
Posts: 7
Joined: Wed Jul 11, 2012 4:58 pm

Re: Pogoplug stuck after usb boot

Postby frankzan » Thu Jul 12, 2012 5:05 pm

okay I found all logs. I attached them below. Two issues I do not understand:

1. Why ist the listener do not have a ip-address?
2. Why do I got the following message : "eth0: no IPv6 routers present"

$this->bbcode_second_pass_code('', 'auth.log
Dec 31 18:00:56 alarm sshd[237]: Server listening on 0.0.0.0 port 22.
Dec 31 18:00:56 alarm sshd[237]: Server listening on :: port 22.

boot
Wed Dec 31 18:00:56 1969: :: Setting Hostname: alarm [BUSY] [DONE]
Wed Dec 31 18:00:56 1969: :: Saving dmesg Log [BUSY] [DONE]
Wed Dec 31 18:00:56 1969: INIT: Entering runlevel: 3
Wed Dec 31 18:00:56 1969: :: Starting Syslog-NG [BUSY] [DONE]
Wed Dec 31 18:00:56 1969: :: Starting Network [BUSY] [DONE]
Wed Dec 31 18:00:56 1969: :: Mounting Network Filesystems [BUSY] [DONE]
Wed Dec 31 18:00:56 1969: :: Starting crond daemon [BUSY] [DONE]
Wed Dec 31 18:00:56 1969: :: Starting Secure Shell Daemon [BUSY] ssh-keygen: generating new host keys: RSA1 RSA DSA ECDSA
Wed Dec 31 18:00:56 1969: [DONE]

crond.log
Dec 31 18:00:26 alarm /usr/sbin/crond[216]: (CRON) STARTUP (1.4.8)
Dec 31 18:00:26 alarm /usr/sbin/crond[216]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Dec 31 18:00:26 alarm /usr/sbin/crond[216]: (CRON) INFO (running with inotify support)

daemon.log
Dec 31 18:00:14 alarm [ 18.361149] udevd[73]: starting version 185
Dec 31 18:00:15 alarm dhcpcd[172]: version 5.5.6 starting
Dec 31 18:00:15 alarm dhcpcd[172]: all: not configured to accept IPv6 RAs
Dec 31 18:00:15 alarm dhcpcd[172]: eth0: broadcasting for a lease
Dec 31 18:00:20 alarm dhcpcd[172]: eth0: offered 192.168.178.38 from 192.168.178.1
Dec 31 18:00:20 alarm dhcpcd[172]: eth0: acknowledged 192.168.178.38 from 192.168.178.1
Dec 31 18:00:21 alarm dhcpcd[172]: eth0: checking for 192.168.178.38
Dec 31 18:00:26 alarm dhcpcd[172]: eth0: leased 192.168.178.38 for 864000 seconds
Dec 31 18:00:26 alarm dhcpcd[172]: forked to background, child pid 201

dmesg.log
[ 6.862637] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 6.869247] Waiting 10sec before mounting root device...
[ 7.705199] scsi 0:0:0:0: Direct-Access hp v115w 0.00 PQ: 0 ANSI: 2
[ 7.705950] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 7.708009] sd 0:0:0:0: [sda] 7892992 512-byte logical blocks: (4.04 GB/3.76 GiB)
[ 7.708497] sd 0:0:0:0: [sda] Write Protect is off
[ 7.708511] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[ 7.708870] sd 0:0:0:0: [sda] Asking for cache data failed
[ 7.714417] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7.723244] sd 0:0:0:0: [sda] Asking for cache data failed
[ 7.728798] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7.736085] sda: sda1
[ 7.738370] sd 0:0:0:0: [sda] Asking for cache data failed
[ 7.743885] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7.750042] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 16.878145] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
[ 16.880907] VFS: Mounted root (ext2 filesystem) on device 8:1.
[ 16.883162] devtmpfs: mounted
[ 16.883692] Freeing init memory: 168K
[ 18.361149] udevd[73]: starting version 185
[ 19.416614] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended

errors.log
Dec 31 18:00:14 alarm kernel: [ 6.854261] rtc-mv rtc-mv: internal RTC not ticking
Dec 31 18:00:14 alarm kernel: [ 6.862637] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Dec 31 18:00:14 alarm kernel: [ 7.708870] sd 0:0:0:0: [sda] Asking for cache data failed
Dec 31 18:00:14 alarm kernel: [ 7.714417] sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 18:00:14 alarm kernel: [ 7.723244] sd 0:0:0:0: [sda] Asking for cache data failed
Dec 31 18:00:14 alarm kernel: [ 7.728798] sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 18:00:14 alarm kernel: [ 7.738370] sd 0:0:0:0: [sda] Asking for cache data failed
Dec 31 18:00:14 alarm kernel: [ 7.743885] sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 18:00:26 alarm /usr/sbin/crond[216]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory

everything.log
Dec 31 18:00:14 alarm kernel: [ 16.883162] devtmpfs: mounted
Dec 31 18:00:14 alarm kernel: [ 16.883692] Freeing init memory: 168K
Dec 31 18:00:14 alarm [ 18.361149] udevd[73]: starting version 185
Dec 31 18:00:14 alarm kernel: [ 19.416614] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
Dec 31 18:00:15 alarm dhcpcd[172]: version 5.5.6 starting
Dec 31 18:00:15 alarm dhcpcd[172]: all: not configured to accept IPv6 RAs
Dec 31 18:00:15 alarm dhcpcd[172]: eth0: broadcasting for a lease
Dec 31 18:00:17 alarm kernel: [ 22.679554] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Dec 31 18:00:20 alarm dhcpcd[172]: eth0: offered 192.168.178.38 from 192.168.178.1
Dec 31 18:00:20 alarm dhcpcd[172]: eth0: acknowledged 192.168.178.38 from 192.168.178.1
Dec 31 18:00:21 alarm dhcpcd[172]: eth0: checking for 192.168.178.38
Dec 31 18:00:26 alarm dhcpcd[172]: eth0: leased 192.168.178.38 for 864000 seconds
Dec 31 18:00:26 alarm dhcpcd[172]: forked to background, child pid 201
Dec 31 18:00:26 alarm /usr/sbin/crond[216]: (CRON) STARTUP (1.4.8)
Dec 31 18:00:26 alarm /usr/sbin/crond[216]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Dec 31 18:00:26 alarm /usr/sbin/crond[216]: (CRON) INFO (running with inotify support)
Dec 31 18:00:56 alarm kernel: [ 61.308368] NET: Registered protocol family 10
Dec 31 18:01:06 alarm kernel: [ 72.284250] eth0: no IPv6 routers present

kernel.log
Dec 31 18:00:14 alarm kernel: [ 7.708511] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
Dec 31 18:00:14 alarm kernel: [ 7.708870] sd 0:0:0:0: [sda] Asking for cache data failed
Dec 31 18:00:14 alarm kernel: [ 7.714417] sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 18:00:14 alarm kernel: [ 7.723244] sd 0:0:0:0: [sda] Asking for cache data failed
Dec 31 18:00:14 alarm kernel: [ 7.728798] sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 18:00:14 alarm kernel: [ 7.736085] sda: sda1
Dec 31 18:00:14 alarm kernel: [ 7.738370] sd 0:0:0:0: [sda] Asking for cache data failed
Dec 31 18:00:14 alarm kernel: [ 7.743885] sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 18:00:14 alarm kernel: [ 7.750042] sd 0:0:0:0: [sda] Attached SCSI removable disk
Dec 31 18:00:14 alarm kernel: [ 16.878145] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
Dec 31 18:00:14 alarm kernel: [ 16.880907] VFS: Mounted root (ext2 filesystem) on device 8:1.
Dec 31 18:00:14 alarm kernel: [ 16.883162] devtmpfs: mounted
Dec 31 18:00:14 alarm kernel: [ 16.883692] Freeing init memory: 168K
Dec 31 18:00:14 alarm kernel: [ 19.416614] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
Dec 31 18:00:17 alarm kernel: [ 22.679554] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Dec 31 18:00:56 alarm kernel: [ 61.308368] NET: Registered protocol family 10
Dec 31 18:01:06 alarm kernel: [ 72.284250] eth0: no IPv6 routers present

messages.log
Dec 31 18:00:14 alarm kernel: [ 19.416614] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
Dec 31 18:00:15 alarm dhcpcd[172]: version 5.5.6 starting
Dec 31 18:00:15 alarm dhcpcd[172]: all: not configured to accept IPv6 RAs
Dec 31 18:00:15 alarm dhcpcd[172]: eth0: broadcasting for a lease
Dec 31 18:00:17 alarm kernel: [ 22.679554] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Dec 31 18:00:20 alarm dhcpcd[172]: eth0: offered 192.168.178.38 from 192.168.178.1
Dec 31 18:00:20 alarm dhcpcd[172]: eth0: acknowledged 192.168.178.38 from 192.168.178.1
Dec 31 18:00:21 alarm dhcpcd[172]: eth0: checking for 192.168.178.38
Dec 31 18:00:26 alarm dhcpcd[172]: eth0: leased 192.168.178.38 for 864000 seconds
Dec 31 18:00:26 alarm dhcpcd[172]: forked to background, child pid 201
Dec 31 18:00:56 alarm kernel: [ 61.308368] NET: Registered protocol family 10

syslog.log
Dec 31 18:00:14 alarm syslog-ng[165]: syslog-ng starting up; version='3.3.5'
')
frankzan
 
Posts: 7
Joined: Wed Jul 11, 2012 4:58 pm

Re: Pogoplug stuck after usb boot

Postby frankzan » Thu Jul 12, 2012 5:36 pm

hi all, I don't know why - but it's working now. But never the less. Front led is orange und orange network is off.
frankzan
 
Posts: 7
Joined: Wed Jul 11, 2012 4:58 pm

Re: Pogoplug stuck after usb boot

Postby moonman » Fri Jul 13, 2012 6:49 am

Front led will be orange unless you change the u-boot variable (forgot what it is) to tell kernel that your device is Pogoplug E02. LAN Orange led is barely lit on mine as well, it's almost not noticeable. As for ipv6, your router doesn't support ipv6 and/or your ISP doesn't support ipv6. This is normal and not a big deal. You still have same old ipv4.
Edit: U-Boot variable name is arcNumber and it should be set to 3542 for proper led colors and behavior.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 3 guests