tar: write error: Read-only file system

[capchap]

Hi all,
first post, please be gentle if I have violated posting rules.

I have pogoplug v2 e02 grey
I am trying to install archlinux i guess...I first saw this on another site that I could make it a LAMP server.

So anyway, I am following the instructions located at:
http://archlinuxarm.org/platforms/armv5 ... 2-pinkgray
I get to the tar command:
tar -zxvf ArchLinuxARM-kirkwood-latest.tar.gz -C /tmp/alarm
which seems to process a lot of files, but then I get the following error (showing last three lines):
./usr/share/gtk-doc/html/gudev/annotation-glossary.html
./usr/share/gtk-doc/html/gudev/GUdevDevice.html
tar: write error: Read-only file system
I am logged in as root and ls -la results as blank dir.
when I first mounted it it had lost+found, but now it has nothing.
I also cant unmount...the command
-bash-3.2# cd /tmp
-bash-3.2# unmount alarm
results in:
-bash: unmount: command not found

the only way around this seems to be to /sbin/reboot the device and start over.
But I cant get past the above read-only error.
I am using a 1gb USB -- didnt have any trouble deleting and creating the partition...at least not that I recognize.
When I set the partition I did get the following message:
The partition table has been altered!

Calling ioctl() to re-read partition table


as you know, I am logged in as root and root is the owner when ls -la

is it possible that usb is too small and is crashing? or maybe it is defective?
is there anyway I can test it?


History:
I tried installing uboot using another method:
http://lifehacker.com/5637092/turn-a-po ... web-server
and got past successful installation of uboot, but in the process somewhere it couldnt find
wget http://Arch Linux ARM.com/os/1.1/Plugbox-Linu ... tfs.tar.gz
so I googled for uboot for pogo and found a location that worked, I think it was from this site, but maybe not.
at any rate, at some point I ran into another error and couldnt complete process.
I was worried I had pricked my pogo, but when it rebooted pogoplug still sees it and it still seems to work even though instructions said it wouldnt.

anyway, I really could use some guidance.

thanks,
don

[moonman]

See if the flash drive got remounted for some reason because of errors by issuing "dmesg". 1GB seems awefully old is it still good? Try a different flash drive.

To unmount, the command is "umount", without 'n' after 'u'

[capchap]

Thanks,
any comment on the error messages or why the files seem to disappear in the 'alarm' dir?
I am guessing either I am doing something wrong, or there is a system issue I need to fix so I can write to dirs I own.

I thought tar had ability to over-write/create even if dir was read-ony (which it isnt)

[capchap]

OH, BTW,
I am currently trying to help by creating the usr dir in the /tmp/alarm dir so possibly the tar wont need to create it because it already exists...

[moonman]

My comment about your maybe failing flash drive was about the error message. If the filesystem is found to be with errors it might be remounted read-only. Also try without "-C /tmp/alarm". There is no need to create any folders by hand.

[capchap]

some information that might point the way to the problem
before mounting alarm I get this
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 32.0M 15.8M 16.2M 49% /
none 125.0M 12.0k 125.0M 0% /tmp
/tmp/.cemnt/sdb1 772.0M 185.2M 547.6M 25% /tmp/.cemnt/mnt_sdb1

after mounting alarm I get this:
-bash-3.2# df -h
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 32.0M 18.5M 13.5M 58% /
none 125.0M 820.0k 124.2M 1% /tmp
/dev/sda1 772.0M 185.2M 547.6M 25% /tmp/alarm
/tmp/.cemnt/sdb1 772.0M 185.2M 547.6M 25% /tmp/.cemnt/mnt_sdb1


after I run the tar command and cant see anything in the alarm dir and umount alarm
I run df -h again and get this.
-bash-3.2# df -h
Filesystem Size Used Available Use% Mounted on
/dev/mtdblock2 32.0M 15.8M 16.2M 49% /
none 125.0M 12.0k 125.0M 0% /tmp
/tmp/.cemnt/sda1 772.0M 185.2M 547.6M 25% /tmp/.cemnt/mnt_sda1

why is .cemnt moving from sdb1 to sda1.
is this normal behavior?
is it possible that Its changinging because I'm moving the USB device to different USB ports?

[moonman]

Did you kill hbwd?
As a last ditch resort If it does not work use alternative method in my signature (reinstallation) + follow the guide to install uboot starting with step 7 (cd /tmp first).

[capchap]

I'm trying a different thumb drive.
This one is an 8gb memorex.
maybe the thumbdrive is causing a problem....hopefully.

If same results I'll try your reinstallation.

thanks

[capchap]

lesson learned
use good equipment.

My 1GB thumbdrive was apparently not capable of keeping up.

Muy 8gb memorex completed the tar extraction without issue.
hopefully the rest goes as well as this did.