Arch Installation on Pogoplug E02 ...no space left

[Orki]

I am trying to install arch on my pogoplug e02 which i did successfully 2 times before. Same setup, same usb stick and usb slot i am stuck with a no space left error message.

$this->bbcode_second_pass_code('', '
Pogoplug:~$ killall hbwd
killall: hbwd: no process killed
Pogoplug:~$ /sbin/fdisk /dev/sda

Command (m for help): o
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.

Warning: invalid flag 0x00,0x00 of partition table 4 will be corrected by w(rite )

Command (m for help): p

Disk /dev/sda: 8032 MB, 8032092160 bytes
248 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15376 * 512 = 7872512 bytes

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1020, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1020, default 1020): Using default value 1020

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table
Pogoplug:~$ cd /tmp
Pogoplug:/tmp$ wget http://archlinuxarm.org/os/pogoplug/mke2fs
Connecting to archlinuxarm.org (50.116.36.110:80)
mke2fs 100% |*******************************| 799k --:--:-- ETA
Pogoplug:/tmp$ chmod +x mke2fs
Pogoplug:/tmp$ ./mke2fs -j /dev/sda1
mke2fs 1.41.9 (22-Aug-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
490560 inodes, 1960432 blocks
98021 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2009071616
60 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Pogoplug:/tmp$ mkdir alarm
Pogoplug:/tmp$ mount /dev/sda1 alarm
<archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz
Connecting to archlinuxarm.org (50.116.36.110:80)
ArchLinuxARM-kirkwoo 73% |********************* | 122M 00:00:27 ETAw get: write error: No space left on device
Pogoplug:/tmp$
')



$this->bbcode_second_pass_code('', '
Pogoplug:/tmp$ df -h
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 32.0M 13.6M 18.4M 42% /
none 125.0M 125.0M 0 100% /tmp
/dev/sda1 7.4G 145.0M 6.8G 2% /tmp/alarm
Pogoplug:/tmp$
')

[WarheadsSE]

$this->bbcode_second_pass_code('', 'cd /tmp/alarm') before downloading. Your RAM based tmpfs is filling up.

Then for step six, skip the `-C alarm`

[Orki]

Thanks for your help WarheadSE, installation succeeded with both the Archlinux Image and the Uboot loader BUT now i can´t SSH via putty which never happend before.

The Pogo is showing up as Alarm with a IP address in my router but when trying to connect via PuTTy with that address connection is refused. I already tried to change the usb ports, different router LAN ports, reboot....

[Orki]

Ok now its getting strange to me.
- Booting with USB stick, the pogo led becomes green and showing up in my router with alarm (but can´t SSh)
- Booting without USB stick the pogo doesn´t even boot, led stays dark, no alarm and IP in the router.

From installing Arch on the E02 the first few times i remember that the pogo gave me always an IP to SSH, with or without usb stick. And the Uboot install was different this time. Could it be that it installed a new Uboot version, but its only one week between the installs ?

[moonman]

It won't boot into stock with the new uboot so no ip.

[Orki]

So whats the benefits in the new Uboot as right now i only see downsides when i have to replace my usb stick if its damaged, or if i decide to setup arch from ground up? Everytime then i will have to access the pogo via serial?

[kmihelich]

http://archlinuxarm.org/support/reinstallation

[moonman]

Benefits:
Gpt support for large hdds (> 2tb)
Booting from ext4
UEnv file on hdd (you can modify uenvironment without touching the one it nand)
FDT support

You should'have never used installation instructions for RE-installation anyway.

[tedm]

installed to usb stick from a linux machine using the reinstall instructions as my dockstar has 128MB

umounted stick from host, inserted in dockstar, router says dockstar has an ip, but can't ssh to it.

[hydro]

Try using a static IP or/and examine the journal as described here. Did you execute steps 7 & 8 in the installation instructions? You don't necessarily have to, if U-Boot was updated from stock during an earlier ALARM installation - I'm mostly asking out of curiosity and because netconsole setup is a bit different.