PogoPlug unrechable after copying file system tarball

This forum is for all other ARMv5 devices

PogoPlug unrechable after copying file system tarball

Postby pogoschorsch » Fri Feb 22, 2013 5:29 am

I have a pogoplug B04 (pink version) with installed ArchLinux. On the plug, there was only a samba and NFS-server running. All was quite fine until I had a crash yesterday - the plug was not responding anymore and every boot attempt only resulted into a wild green blinking LED.

So, I saved my entire system from the stick and copied the root file system tarball to the system (including setting every file to root:root and 777 + entering the MAC address). Now, the pogoplug boots up, my fritzbox reports a IP-address, but the system is not responding to any SSH-connection-attempt.

What shall I do now? I have no clue how to access the plug without SSH-connection.

Any help would be very appreciated!
pogoschorsch
 
Posts: 8
Joined: Tue Feb 19, 2013 9:30 pm

Re: PogoPlug unrechable after copying file system tarball

Postby Socaltom » Fri Feb 22, 2013 8:49 am

Which tarball did you extract?
Did you save you old boot stick? If you did then I would put it in another Linux system computer and run fsck. That will probably fix it.
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: PogoPlug unrechable after copying file system tarball

Postby pogoschorsch » Fri Feb 22, 2013 9:33 am

I did perform a fsck on the original filesystem, but it didn't help (there were no errors). I also saved the original fs by using dd.

The tarball which i took is from this link: http://archlinuxarm.org/platforms/armv6 ... provideov3
pogoschorsch
 
Posts: 8
Joined: Tue Feb 19, 2013 9:30 pm

Re: PogoPlug unrechable after copying file system tarball

Postby Socaltom » Sun Feb 24, 2013 10:02 pm

Try the 2012.05 tar ball from here.
http://os.archlinuxarm.org/os/oxnas/

I beleive it predates the need for the kernel update.
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: PogoPlug unrechable after copying file system tarball

Postby pogoschorsch » Tue Feb 26, 2013 5:05 pm

thank you for the advice.

I tried the way you proposed, but:

-Plug-LED blinks green for ~20seconds, after that, it stays green
-I cannot see any IP in fritz.box Network overview.

After disconnecting, I put the stick into my Ubuntu-machine and copied the /var/log/messages. It dates from the 16th february, but I hope it is real data and not the copied one from the tarball:

$this->bbcode_second_pass_code('', 'ec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: carrier acquired
Dec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: broadcasting for a lease
Dec 31 18:00:17 alarm-oxnas dhcpcd[909]: eth0: offered 192.168.11.27 from 192.168.11.1
Dec 31 18:00:17 alarm-oxnas dhcpcd[909]: eth0: acknowledged 192.168.11.27 from 192.168.11.1
Dec 31 18:00:18 alarm-oxnas dhcpcd[909]: eth0: checking for 192.168.11.27
Dec 31 18:00:19 alarm-oxnas dhcpcd[909]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:23 alarm-oxnas dhcpcd[909]: eth0: leased 192.168.11.27 for 86400 seconds
Dec 31 18:00:23 alarm-oxnas dhcpcd[909]: forked to background, child pid 945
Dec 31 18:00:23 alarm-oxnas dhcpcd[945]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:27 alarm-oxnas dhcpcd[945]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:27 alarm-oxnas dhcpcd[945]: eth0: no IPv6 Routers available
Feb 16 19:48:53 alarm-oxnas ntpd[980]: set local clock to Thu Feb 16 19:48:53 CST 2012 (offset 1329443298.559166s)
Feb 16 19:50:48 alarm-oxnas kernel: [ 150.010000] Turning off blinking LED.
Feb 16 20:04:36 alarm-oxnas shutdown[1030]: shutting down for system halt
Feb 16 20:04:36 alarm-oxnas init: Switching to runlevel: 0
Feb 16 20:04:37 alarm-oxnas ntpd[982]: Terminating
Feb 16 20:04:38 alarm-oxnas dhcpcd[945]: eth0: removing IP address 192.168.11.27/24
Feb 16 20:04:38 alarm-oxnas dhcpcd[945]: eth0: carrier lost
Feb 16 20:04:38 alarm-oxnas kernel: [ 979.630000] Freeing CoPro parameters 36 bytes
Feb 16 20:04:38 alarm-oxnas kernel: [ 979.630000] Freeing ARM descs 8192 bytes
Feb 16 20:04:38 alarm-oxnas dhcpcd[945]: received SIGTERM, stopping
Feb 16 20:04:38 alarm-oxnas dhcpcd[945]: eth0: removing interface
')

Any advice? Did I brick my plug?

What I see is some IP-address in the 192.168.11-area, but I have a net in the 192.168.178-area. The DHCP-region is from 192.168.178.20 to .200.
pogoschorsch
 
Posts: 8
Joined: Tue Feb 19, 2013 9:30 pm

Re: PogoPlug unrechable after copying file system tarball

Postby Socaltom » Tue Feb 26, 2013 7:05 pm

Did you put your mac address in the mac_addr file as listed in the reinstall directions?

Create a file at /usr/local/mac_addr and place in it your Pro's MAC address (its on the bottom of the unit) in the format XX:XX:XX:XX:XX:XX. Safely umount the drive from the computer, plug it back in to the powered-off Pogoplug, and then plug in the Pogoplug.

The data is copied from the tarball.

Did you fdisk and create a dos table? using option"o"? its required to get the plug to boot the rootfs.

$this->bbcode_second_pass_code('', 'There are reinstall instructions on the installation page. basically you extract the rootfs tarball to you usb drive, then it should boot.

Link to install page ( reinstall instructions at the bottom)
http://archlinuxarm.org/platforms/armv6 ... provideov3


1) Format USB drive as follows ( it MUST use DOS partition table)
Start fdisk to partition the USB or SATA drive:
CODE: SELECT ALL
/sbin/fdisk /dev/sdX

At the fdisk prompt, delete old partitions and create a new one:
Type o. This will clear out any partitions on the drive.
Type p to list partitions. There should be no partitions left.
Now type n, then p for primary, 1 for the first partition on the drive, and then press ENTER, accepting default values.
Exit by typing w.

2)Create the ext3 filesystem:


3)Download and extract the root filesystem tarball onto the new ext3 partition as the root user, not just sudo.

4)Create a file at /usr/local/mac_addr and place in it your Pro's MAC address (its on the bottom of the unit) in the format XX:XX:XX:XX:XX:XX.

5)Safely umount the drive from the computer, plug it back in to the powered-off Pogoplug, and then plug in the Pogoplug.

')
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: PogoPlug unrechable after copying file system tarball

Postby pogoschorsch » Sat Mar 02, 2013 12:12 pm

Ok, first time, I didn´t use the "o" option in fdisk, but with completely following your instructions, it does not work.

The green LED on the ethernet jack is only blinking slow, the plug does not get any ethernet connection.
pogoschorsch
 
Posts: 8
Joined: Tue Feb 19, 2013 9:30 pm

Re: PogoPlug unrechable after copying file system tarball

Postby pogoschorsch » Tue Mar 05, 2013 4:02 pm

does anyone has an idea what I am doing wrong, or is the plug bricked?
pogoschorsch
 
Posts: 8
Joined: Tue Feb 19, 2013 9:30 pm

Re: PogoPlug unrechable after copying file system tarball

Postby Socaltom » Tue Mar 05, 2013 6:09 pm

Its not bricked. What are you using for a boot drive? Some usb sticks aren't compatible. A USB hard drive is much more reliable boot device.
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: PogoPlug unrechable after copying file system tarball

Postby pogoschorsch » Thu Apr 04, 2013 7:19 pm

Sorry for the late reply, the project pogoplug had to wait :-).

I use the identical USB-Stick I also had for the running system (before the crash). So I suggest, it "should" work. It is a Kingston Data Traveller 4GB, I also changed to a 16GB Noname-One, but it neither did not work.

Should I use a real hard disk? Only for the tarball-installation? Because, if I get the pogoplug back to working condition, I definetely want to use it with an usb-stick.

Maybe I did something wrong with the copy process?:
$this->bbcode_second_pass_code('', '
wget http://os.archlinuxarm.org/os/oxnas/ArchLinuxARM-2012.05-oxnas.tar.gz
tar xzf ArchLinuxARM-2012.05-oxnas.tar.gz -C /media/…. (actual folder, weird numbername)
')
pogoschorsch
 
Posts: 8
Joined: Tue Feb 19, 2013 9:30 pm

Next

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 8 guests