PogoPlug v4 install mounting failing: Invalid argument

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

PogoPlug v4 install mounting failing: Invalid argument

Postby caderoux » Sun Jul 08, 2012 12:15 am

What am I doing wrong? Is it something wrong with the 4GB USB drive (in top slot)? I just used that USB drive to transfer a 2GB image file from a Mac to a PC write an SD to set up my Raspberry Pi, so I think it's OK.

$this->bbcode_second_pass_code('', '/ # killall hbwd
/ # /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.


Command (m for help): p

Disk /dev/sda: 4026 MB, 4026531840 bytes
255 heads, 63 sectors/track, 489 cylinders
Units = cylinders of 16065 * 512 = 8225280 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-489, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-489, default 489): Using default value 489

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 (206.217.130.189: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)
245760 inodes, 981965 blocks
49098 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1006632960
30 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

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

This filesystem will be automatically checked every 35 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
/tmp # mkdir alarm
/tmp # mount /dev/sda1 alarm
mount: mounting /dev/sda1 on alarm failed: Invalid argument
/tmp #')
caderoux
 
Posts: 44
Joined: Sat Jun 30, 2012 3:46 am

Re: PogoPlug v4 install mounting failing: Invalid argument

Postby WarheadsSE » Sun Jul 08, 2012 1:48 am

cat /proc/partitions to be sure it is there. Then, try rebooting and proceeding from that point.
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 v4 install mounting failing: Invalid argument

Postby caderoux » Sun Jul 08, 2012 2:16 am

$this->bbcode_second_pass_code('', '~ # cat /proc/partitions
major minor #blocks name

31 0 2048 mtdblock0
31 1 3072 mtdblock1
31 2 3072 mtdblock2
31 3 8192 mtdblock3
31 4 114688 mtdblock4
8 0 3932160 sda
8 1 3927861 sda1
~ # /sbin/rebootConnection to 192.168.3.100 closed by remote host.
Connection to 192.168.3.100 closed.
cade-rouxs-mac-mini:~ caderoux$ ssh root@192.168.3.100
root@192.168.3.100's password:
~ # cd /tmp
/tmp # mkdir alarm
/tmp # mount /dev/sda1 alarm
mount: mounting /dev/sda1 on alarm failed: Invalid argument
/tmp #
')

I cleared it all out and tried again:


$this->bbcode_second_pass_code('', '/ # cd tmp
/tmp # mkdir alarm
/tmp # mount /dev/sda1 alarm
mount: mounting /dev/sda1 on alarm failed: Invalid argument
/tmp # mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,relatime)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
none on /tmp type tmpfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)
/tmp #
')
caderoux
 
Posts: 44
Joined: Sat Jun 30, 2012 3:46 am

Re: PogoPlug v4 install mounting failing: Invalid argument

Postby moonman » Sun Jul 08, 2012 4:42 am

i think it has to be "./alarm" and not just "alarm" or you can give a full path like "/tmp/alarm"
"mount /dev/sda1 /tmp/alarm". If it still fails, try specifying a fylesystem type "mount -t ext3 /dev/sda1 /tmp/alarm"
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

Re: PogoPlug v4 install mounting failing: Invalid argument

Postby caderoux » Sun Jul 08, 2012 1:09 pm

$this->bbcode_second_pass_quote('moonman', 'i') think it has to be "./alarm" and not just "alarm" or you can give a full path like "/tmp/alarm"
"mount /dev/sda1 /tmp/alarm". If it still fails, try specifying a fylesystem type "mount -t ext3 /dev/sda1 /tmp/alarm"


$this->bbcode_second_pass_code('', '/ # cd tmp
/tmp # mkdir alarm
/tmp # mount /dev/sda1 /tmp/alarm
mount: mounting /dev/sda1 on /tmp/alarm failed: Invalid argument
/tmp # mount -t ext3 /dev/sda1 /tmp/alarm
mount: mounting /dev/sda1 on /tmp/alarm failed: Invalid argument
/tmp #
')
caderoux
 
Posts: 44
Joined: Sat Jun 30, 2012 3:46 am

Re: PogoPlug v4 install mounting failing: Invalid argument

Postby WarheadsSE » Sun Jul 08, 2012 4:20 pm

try reformatting the partition.
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 v4 install mounting failing: Invalid argument

Postby caderoux » Sun Jul 08, 2012 6:00 pm

Went through all the instructions again - for perhaps the 10th time, and it got past the mount and finally booted off the USB (other times before I had got the filesystem mounted but it failed to boot and I had to use the revert)!
caderoux
 
Posts: 44
Joined: Sat Jun 30, 2012 3:46 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 5 guests