Pogoplug Multimedia Sharing Device (Model B01 Pink or P21 Black) $17 + Free Shipping (Ebay Daily Deal)

Quote from blunty : Are you booting Arch off a single USB disk drive or do you have Arch booting off an usb flash drive and another usb disk drive for your data? If you have two drives, try booting with just your boot flash drive connected, then connect the hard drive.

i have a separate usb drive with arch on it.

i just re-installed again, and it seems to work as long as there is no external drive plugged in when it is rebooting or turning on.

is that how it is for everyone?

also, what is the default mount point? i tried copy/pasting backforwardback's smb.conf but it doesn't mount the data drive there by default, so i think i need to modify the path.

what can i do with this if not so techi ? lol

Quote from heiNey : i have a separate usb drive with arch on it. i just re-installed again, and it seems to work as long as there is no external drive plugged in when it is rebooting or turning on. is that how it is for everyone? also, what is the default mount point? i tried copy/pasting backforwardback's smb.conf but it doesn't mount the data drive there by default, so i think i need to modify the path.

I think it has to do with which usb drive gets mounted first. If it mounts the data drive, then it can't find the system to boot. I was digging around on archlinux forum and they seem to indicate to use fstab to label your root drive and media drive.

Quote from blunty : I think it has to do with which usb drive gets mounted first. If it mounts the data drive, then it can't find the system to boot. I was digging around on archlinux forum and they seem to indicate to use fstab to label your root drive and media drive.

use fstab even for the / drive? i'm normally used to adding external drives with fstab, but not sure how to edit fstab for the usb stick with arch on it.

Quote from heiNey : use fstab even for the / drive? i'm normally used to adding external drives with fstab, but not sure how to edit fstab for the usb stick with arch on it.

http://archlinuxarm.org/platforms...provideov3
In "Installation" tab:

Quote : Unlike it's Marvell based brethren, a modern U-Boot has not been created for the OXNAS line as of this time. As such, our available method is the use of /dev/sda1. The selection of a particular usb drive as sda is not perfect, and thus can sometimes come up in the wrong order based on drive response times at boot. (e.g. first to respond gets sda). As a result, you may need to test for yourself to see the pattern in which your drives "spin up". USB flash drives tend to come up faster than spinning hard drives in many cases. There is a special exception to this rule, because the OXNAS kernel initializes the SATA code first, so this problem never exists on systems with a SATA boot drive.

the /dev/sda1 is determined at boot process (before any services are started or rootfs is mounted). I don't think pointing the / to the correct UUID in fstab will be helpful (well I have tried but failed). Unplugging all but the system drive before reboot is the only way I can get my pogoplugs to boot properly. In other words no automount at boot, the nfs, sabnzbd, sickbeard, and any other services that requires the large-to-huge external storage drives will have to be manually started after the drives are all plugged in and recognized.

and this is not just for ARMv6 pogo (oxnas kernel) but also ARMv5 (e02 pogo) behaves the same. Actually lack of BIOS to assign which drive to be the 1st boot drive is the cause of the problem but as a always on server as long as it's reliable, chance for having to reboot remotely frequently is slim.

For P21 and B01 (oxnas) I guess the best way is to provide a SATA drive (and the SATA power) and tinker with u-boot code to boot from SATA first.

Quote from teetee1 : http://archlinuxarm.org/platforms...provideov3 In "Installation" tab: the /dev/sda1 is determined at boot process (before any services are started or rootfs is mounted). I don't think pointing the / to the correct UUID in fstab will be helpful (well I have tried but failed). Unplugging all but the system drive before reboot is the only way I can get my pogoplugs to boot properly. In other words no automount at boot, the nfs, sabnzbd, sickbeard, and any other services that requires the large-to-huge external storage drives will have to be manually started after the drives are all plugged in and recognized. and this is not just for ARMv6 pogo (oxnas kernel) but also ARMv5 (e02 pogo) behaves the same. Actually lack of BIOS to assign which drive to be the 1st boot drive is the cause of the problem but as a always on server as long as it's reliable, chance for having to reboot remotely frequently is slim. For P21 and B01 (oxnas) I guess the best way is to provide a SATA drive (and the SATA power) and tinker with u-boot code to boot from SATA first.

wow, thanks. and all this time i've been pulling my hair out trying to figure out why this thing kept dying on me after rebooting.

EDIT: got another question about miniDLNA. has anyone been able to install this successfully? i've got it installed and it's streaming to the PCs in my house, but for some reason none of my android phones can see the dlna server. my ps3 can see it, my logitech revue can see it, but i cant find an app that can see it on my phone. anyone have a suggestion?

Quote from teetee1 : http://archlinuxarm.org/platforms...provideov3 In "Installation" tab: the /dev/sda1 is determined at boot process (before any services are started or rootfs is mounted). I don't think pointing the / to the correct UUID in fstab will be helpful (well I have tried but failed). Unplugging all but the system drive before reboot is the only way I can get my pogoplugs to boot properly. In other words no automount at boot, the nfs, sabnzbd, sickbeard, and any other services that requires the large-to-huge external storage drives will have to be manually started after the drives are all plugged in and recognized. and this is not just for ARMv6 pogo (oxnas kernel) but also ARMv5 (e02 pogo) behaves the same. Actually lack of BIOS to assign which drive to be the 1st boot drive is the cause of the problem but as a always on server as long as it's reliable, chance for having to reboot remotely frequently is slim. For P21 and B01 (oxnas) I guess the best way is to provide a SATA drive (and the SATA power) and tinker with u-boot code to boot from SATA first.

Quote from heiNey : wow, thanks. and all this time i've been pulling my hair out trying to figure out why this thing kept dying on me after rebooting. EDIT: got another question about miniDLNA. has anyone been able to install this successfully? i've got it installed and it's streaming to the PCs in my house, but for some reason none of my android phones can see the dlna server. my ps3 can see it, my logitech revue can see it, but i cant find an app that can see it on my phone. anyone have a suggestion?

I haven't tried this yet but these writeups might help:
http://forum.doozan.com/read.php?2,5233,5957

http://mouhassan.wordpress.com/20...-usb-disk/

Quote from blunty : I haven't tried this yet but these writeups might help: http://forum.doozan.com/read.php?2,5233,5957 http://mouhassan.wordpress.com/20...-usb-disk/

interesting. i'll give it a try in a few hours.

Got mine today and the box indicated model P21 but the tag on the unit indicates model E02

Quote from pongoboy : Got mine today and the box indicated model P21 but the tag on the unit indicates model E02

Same here.
I tried to install arch on it yesterday and got an error. Can't install on an E02?

Quote from doctorwizz : Same here. I tried to install arch on it yesterday and got an error. Can't install on an E02?

Not sure I'm not a techie at all. Will try to pay someone to mod them.
Here is the link from the wiki though:

If you get a E02 instead (which has more RAM), follow this link instead
http://archlinuxarm.org/platforms...2-pinkgray

FYI the pink B01 is actually a B01 oxnas (not an E02 like the black P21 commonly is)

If you get an E02 the install instructions are here: http://archlinuxarm.org/platforms...2-pinkgray

Quote from blunty : I haven't tried this yet but these writeups might help: http://forum.doozan.com/read.php?2,5233,5957 http://mouhassan.wordpress.com/20...-usb-disk/

tried this. killed my arch install. gave me all sorts of permission problems after rebooting. for some reason sda and sdb got switched, so / became sdb and the data drive became sda...which ended up making the filesystem read-only, even for root.

tried to make it writable with:

which worked, but the system would go back to read-only after every reboot - something is wrong with it.

looked around to see if a simple kernel name swap could fix it, i.e. making it think sda was sdb and vice versa. made a 10-local.rules in /etc/udev/rules.d

which killed the system upon reboot.

had to re-install the whole thing.

i won't be doing it again, but someone else could give it a shot.

received mine. The box says P21, but the unit inside is an E02. Odd thing is that the macs match (the address printed on the box label and the actual address of the unit). I'll take it - 256MB :-).