Categories: Pogoplug v1, v2, and PRO
I would like to mount image files on the Pogoplug.
As I saw the /dev/loopX files, I thought the loop module was included in the kernel, but apparently this is not the case.
Could anybody confirm what is the status of this module in the kernel?
If not included in the kernel, is there a way to access a pre-built loop module to load it on a Pogoplug?
Just tried it. "mount --help" says there is a loop device and "losetup" is there but when I try to mount a loop device I get
-bash-3.2# mkdir /tmp/mount_loop
-bash-3.2# dd bs=512 count=2880 if=/dev/zero of=imagefile.img
2880+0 records in
2880+0 records out
-bash-3.2# mkfs.minix imagefile.img
480 inodes
1440 blocks
Firstdatazone=19 (19)
Zonesize=1024
Maxsize=268966912
-bash-3.2# mount -o loop /tmp/imagefile.img /tmp/mount_loop
mount: cannot setup loop device: No such file or directory
Yes, exactly, that is what happens to me, which leads me to the conclussion that the kernel has been built without support for a loop block device.
Here is the applicable section of the pogoplug 2.6.22.18 .config file.
#
# Block devices
#
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
Yup.
This whole thing started as I wanted to port slimserver to my pogoplug installation. my drive is NTFS formatted, which in the pogoplug world means that only root can write to it (at least as far as I know). I cannot run slimserver as root...
I wanted to mount an ext2/3 filesystem backed up y a file on the USB drive I have, but what I thought was going to be simple, has got to be quite complicated, thanks to the unavailability of the loop block device driver.
Back to looking for alternatives, unless I can find a kernel module for the pogoplug kernel providing the loop driver functionality.
Well,
I have tried loading a couple of different loop.ko kernel modules from kernels which seemed close enough to the one in the pogoplug, but I get the following result in both cases:
| -bash-3.2# insmod -f loop.ko insmod: cannot insert 'loop.ko': Invalid module format (-1): Exec format error -bash-3.2# |
The kernels from which I took the modules were built for arm, one was from the NSLU2 dist and the other from debian lenny.
Copyright © 2012
Capable Networks LLC.. All Rights Reserved.
RSS |
Privacy Policy |
Advertise With Us |
Terms of Use |
About Us |
Contact Us |
Site Map
Our Capable Community Network:
DVR playground |
Explore3DTV |
MediaSmart Home |
MotoDash |
My Open Router |
Pogoplugged |
DijitCommunity |
Robo Community |
Sansa Community |
TechLore |
TiVo Community |
TouchSmartDevZone
Pogoplug™ is a trademark of CloudEngines, Inc. PogoPlugged.com is not affiliated with CloudEngines, Inc.
Did you forget your password?
You can also log in using OpenID.
Previous Thread
