ARMv5 ppv4 failed install

[WyoDad]

First anomaly is the disk cylinders. I don't know if that is causing the errors near the end or not.

~ # killall hbwd
~ # /sbin/fdisk /dev/sda

The number of cylinders for this disk is set to 1936.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

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.


The number of cylinders for this disk is set to 1936.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 1998 MB, 1998519808 bytes
32 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 2016 * 512 = 1032192 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-1936, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1936, default 1936): Using default value 1936

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

Calling ioctl() to re-read partition table
~ # cd /tmp
/tmp # wget http://archlinuxarm.org/os/pogoplug/mke2fs
Connecting to archlinuxarm.org (50.116.36.110:80)
Connecting to os.archlinuxarm.org (181.41.198.161:80)
/tmp # chmod +x mke2fs
/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)
122160 inodes, 487864 blocks
24393 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=503316480
15 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912

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

This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
/tmp # mkdir alarm
/tmp # mount /dev/sda1 alarm
/tmp # wget http://archlinuxarm.org/os/pogoplug/bsdtar
Connecting to archlinuxarm.org (50.116.36.110:80)
Connecting to os.archlinuxarm.org (150.162.66.161:80)
/tmp # chmod +x bsdtar
/tmp # wget http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz
Connecting to archlinuxarm.org (50.116.36.110:80)
Connecting to os.archlinuxarm.org (181.41.198.161:80)
wget: short write
/tmp # ./bsdtar -xpf ArchLinuxARM-kirkwood-latest.tar.gz -C alarm
./usr/bin/ping6: Cannot restore extended attributes on this file system
./usr/bin/ping: (null)
./usr/bin/rlogin: (null)
./usr/bin/rsh: (null)
./usr/bin/rcp: (null)
./usr/share/man/man3/ldns_pkt2buffer_wire.3.gz: truncated gzip input
bsdtar: Error exit delayed from previous errors.

after this, none of the commands has any affect. The u-boot installer doesn't load, just goes back to /tmp #

[WyoDad]

I am using a 2 gb thumb drive. Is this too small?

[WarheadsSE]

wget: short write

[WyoDad]

"wget: short write" is system generated not something entered by me. It hangs on "Connecting to os.archlinuxarm.org (181.41.198.161:80)" for a time then goes to the "wget: short write". What is the significance? How to fix?

[moonman]

cd into alarm, then wget, then remove -C alarm from bsdtar command. You are downloading into /tmp right now which is mounted in ram and you run out of space there

[WyoDad]

/tmp # mkdir alarm
/tmp # mount /dev/sda1 alarm
/tmp # cd /alarm
-sh: cd: can't cd to /alarm
/tmp #

[moonman]

cd alarm or cd /tmp/alarm not cd /alarm

[WyoDad]

oops. syntax. 8-) cd \alarm worked.

wget http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz

still results in short write. is there an issue with the drive partition? or is the /alarm also created in the ram and not on the drive?

~/alarm # ls -alh
drwxr-xr-x 2 root root 256 Nov 1 02:52 .
drwxr-xr-x 3 root root 288 Nov 1 02:51 ..
-rw-r--r-- 1 root root 82.2M Nov 1 02:54 ArchLinuxARM-kirkwood-latest.tar.gz

this is the ppv4 portable, do the commands need to be changed?

[moonman]

No backslashes in UNIX paths.

It isn’t in ram unless you rebooted after last try and did not mount the drive.

And why is alarm dir in ~ and not in /tmp. You are clearly not following the installation guide.

[WyoDad]

the entire installation is in my first post. tell me where i went wrong.