[SGVLUG] PogoPlug mount problem

[Rae Yip]

My only suggestion is do the usual shell environment debugging. Try adding
debugging flags to the rcS script, make sure PATH as inherited from init
includes where mount and mkdir is, verify script is executable, etc.

Good luck,

-Rae.

On Thu, Apr 4, 2013 at 9:11 PM, Matthew Campbell <dvdmatt at gmail.com> wrote:

> There is an Arch available for the Pogoplug as well as debian, but then
> you lose their web interface, anywhere access, cloud storage and mirroring
> features.  Darned closed source benefits!  If it wasn't for those the world
> would be open.
>
> # cat /etc/inittab
> ::sysinit:/etc/init.d/rcS
> ::respawn:-/bin/sh
> #::respawn:-/bin/sh
> #tty2::askfirst:-/bin/sh
> #::ctrlaltdel:/bin/umount -a -r
>
> #
>
> ---------
> *Matthew Campbell*
> Storage Solution Consultant
> Storage Design and Engineering
>
> *Kaiser Permanente*
> IMG-Systems Integration
> 99 S. Oakland
> Pasadena, CA 91101
>
> 626-564-7228 (office)
> 8-338-7228 (tie-line)
> 818-314-9897 (mobile phone)
> Green Center 3-North, 031W29
> ---------
> *kp.org/thrive*
>
>
> On Thu, Apr 4, 2013 at 9:42 AM, Rae Yip <rae.yip at gmail.com> wrote:
>
>> Is there an /etc/inittab? ArchLinux switched to systemd; any chance
>> that's what you're running?
>>
>> -Rae.
>>
>>
>> On Thu, Apr 4, 2013 at 9:17 AM, Matthew Campbell <dvdmatt at gmail.com>wrote:
>>
>>> Thank you John for your thoughtful answer.
>>>
>>> Unfortunately these are USB devices so I can't assume that they will be
>>> mounted as the same device from boot to boot which is why I started down
>>> the UUID route.
>>>
>>> # 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 2930266584 sda
>>>    8        1 2930265088 sda1
>>>    8       32 2930266584 sdc
>>>    8       33 2930265088 sdc1
>>>    8       48    3913696 sdd
>>>    8       49    3911680 sdd1
>>>    8       16 1953514582 sdb
>>>    8       17 1953512534 sdb1
>>>
>>> So it looks like they are showing up.  I can mount them once the boot
>>> sequence is complete by hand:
>>>
>>> # blkid
>>> /dev/sdc1: UUID="408d60e4-358b-450f-a6f0-4c3fdde4e8ed" TYPE="ext3"
>>> /dev/sda1: UUID="062801fe-7225-4834-b27d-104e375c1bbc" TYPE="ext3"
>>> /dev/sdb1: UUID="2858227358223FC4" LABEL="TOSHIBA EXT" TYPE="ntfs"
>>> /dev/sdd1: UUID="0d295fe2-b6b9-4d8e-b035-d68ec6c0843e" TYPE="ext3"
>>> /tmp/.cemnt/sdb1: UUID="2858227358223FC4" LABEL="TOSHIBA EXT"
>>> TYPE="ntfs"
>>>
>>> The question is:  On a Pogoplug Mobile device (arm/busybox) where in the
>>> boot sequence should I be attempting to mount the partitions?
>>>
>>> I am not a busybox expert.  Others had success adding the lines to
>>> /etc/init.d/rcS but this does not appear to be working in my case.  Any
>>> other suggestions of where to look?
>>>
>>> # uname -a
>>> Linux PogoplugMobile 2.6.31.8 #4 Tue Aug 23 13:00:50 PDT 2011 armv5tel
>>> GNU/Linux
>>>
>>> # busybox | head -n1
>>> BusyBox v1.16.1 (2011-08-23 13:02:26 PDT) multi-call binary.
>>>
>>> Look on the bottom of the unit:  Model POGO-V4-A1-01
>>>
>>> Matt
>>>
>>>
>>> ---------
>>> *Matthew Campbell*
>>> Storage Solution Consultant
>>> Storage Design and Engineering
>>>
>>> *Kaiser Permanente*
>>> IMG-Systems Integration
>>> 99 S. Oakland
>>> Pasadena, CA 91101
>>>
>>> 626-564-7228 (office)
>>> 8-338-7228 (tie-line)
>>> 818-314-9897 (mobile phone)
>>> Green Center 3-North, 031W29
>>> ---------
>>> *kp.org/thrive*
>>>
>>>
>>> On Thu, Apr 4, 2013 at 5:11 AM, John Kreznar <jek at ininx.com> wrote:
>>>
>>>> In a posting purporting to be from Matthew Campbell <dvdmatt at gmail.com>
>>>> but lacking a digital signature, it is written:
>>>>
>>>> > I am running into some problems trying to get my USB drives to mount
>>>> > automatically in a known location when my PogoPlug Mobile v4 boots.
>>>> ...
>>>>
>>>> > It seems that busybox doesn't understand mounting by UUID
>>>>
>>>> Would it be practical to mount by device name (e.g. /dev/sde1) instead
>>>> of UUID?
>>>>
>>>> Do those devices appear in /proc/partitions at that stage of the boot?
>>>> The mount man page says
>>>>
>>>> BUGS
>>>>        ...
>>>>
>>>>        Mount by label or uuid will work only if your devices have the
>>>>        names listed in /proc/partitions.  In particular, it may well
>>>>        fail if the kernel was compiled with devfs but devfs is not
>>>>        mounted.
>>>>
>>>> --
>>>> OpenPGP key: http://ininx.com
>>>>  John E. Kreznar jek at ininx.com 9F1148454619A5F08550
>>>> 705961A47CC541AFEF13
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sgvlug.net/pipermail/sgvlug/attachments/20130404/03612b39/attachment.html>