It's not only the wear issue, but writes are generally slow to flash media, so using journaling can also slow down the 'o' in i/o. On the other hand, the downside of ext2 is that this file system is more fragile.by restamp - Debian
You disable the Pogo service (hbmgr.sh) to prevent it from downloading updates which may turn off your ssh access to the OS. However, if you've already disabled this manually, you should answer 'no' when prompted in Jeff's script. If you want to leave it enabled and use the media serving software, you can do so, but you should probably not allow the Pogoplug on the greaterby restamp - Debian
Wow! I don't have an immediate need to do this, but I'm definitely bookmarking this thread. Thanks for taking the time to do that masterful job of documenting your work, Vlad!by restamp - Debian
Thanks, davidnewton. This seems to have done the trick for now and gotten my Asterisk happily connecting with Google Voice once again, but I wonder if Asterisk is going to eventually add some additional code to their GV to make future such changes bulletproof.by restamp - Debian
My guess is that it's mounted as ext3. An ext3 file system can be explicitly mounted as ext2. It just means that logging will not be used. But normally, if you just execute a "mount", it will defer to the primary type specified in the fs. What does /proc/commandline show ("cat /proc/commandline"). Is rootfstype set to anything? Does /etc/fstab not have an explicby restamp - Debian
I am reasonably certain you could write something other than the rescue image to the NAND. I'm less certain you could actually succeed at booting the default uImage off of a thumb drive, as you'd probably get bitten by something along the lines of the default kernel not having the proper drivers built into it to interact with the root partition on the thumb drive. But, it would be anby restamp - Rescue System
@bodhi: Well, Jeff Doozan showed us how to replace the firmware on these Plug boxes using only the OS that was initially loaded on them (along with downloadable executables compiled to run on it), so if it is possible to craft an external device which boots into this environment, then yes, it follows that that setup could be used to restore the initial OS onto the device's internal NAND memby restamp - Rescue System
Just curious: The original *nix that comes with the Dockstar (and its associated devices) doesn't require an arcNumber. (Does it?) I wonder if you could put that kernel on a thumb drive and boot that up, at least far enough to log in and reset the arcNumber. And, when you get it booting again, make sure you set up netconsole if you don't have to wire up the serial connection.by restamp - Rescue System
Great news indeed! Thanks for being the guinea pig in this experiment, bodhi, but hey, being a successful guinea pig ain't all that bad, is it! Hope you get many years of use out of your Pogoplug.by restamp - uBoot
Bodhi, kraqh3d is correct about setting the ethaddr to the correct MAC address. Here is the diff of my Pogoplug's environment and the one you posted:4a4 > arcNumber=2097 40,46d39 < ethaddr=00:25:31:00:AB:CD < arcNumber=2097 < serverip=192.168.2.1 < ipaddr=192.168.2.2 < if_netconsole=ping $serverip < start_netconsole=setenv ncip $serverip; setenv bootdelay 10; sby restamp - uBoot
Actually, this looks promising, bodhi. It appears that the nandwrite caught the bad block and correctly shifted the last block of data to the next good block. Look, I'm no expert, but here's what I'd do: First, and foremost, I don't think the new uBoot environment was ever written to the NAND. (Jeff's script bails out without doing that after it thought the uBootby restamp - uBoot
If the uBoot winds up becoming corrupted during the install and you then reboot out of the running OS, I think your Pogoplug is toast. The only way to recover from that would be to open it up, connect a JTAG board, and reprogram it that way. (FWIW, I understand the JTAG unit for the Guruplug will work for this.) OTOH, I suspect your Pogoplug is not very useful to you in its current state, so iby restamp - uBoot
Hi bodhi. It's late, and I don't have a lot of time to spend online tonight. (It's 3 AM here.) On my "bad" Dockstar, the problem turned out to be an incorrectly flashed original uBoot. Jeff's installer does a hash of the existing uBoot and if one bit is different, it produces an entirely different hash sum. That was the case here. Jeff had me send him a copyby restamp - uBoot
Thanks for the observations, folks. Looks like the original Pogoplug software isn't worth messing with.by restamp - Debian
Thanks, bodhi. Nope, I just booted the Pogoplug on an isolated LAN (but one with a DHCP server), sshed in and deactivated hbmgr.sh, and never bothered with registering at the Pogoplug website. With the Dockstar, I was even cruder -- I just plugged an X/O cable between it and a laptop and used its MAC address to find it. In all honesty, I've got a second Pogoplug, and have been thinkingby restamp - Debian
Switching an ext2 fs to ext3 is fairly straightforward: 1. Make sure the fs is unmounted and fscked 2. As root, add a journal: tune2fs -j /dev/whatever 3. If the fs is automounted from /etc/fstab, change its entry from ext2 to ext3 there Technically, you can run the "tune2fs -j" command on a mounted fs, and this is necessary if you want to convert the root file system in place.by restamp - Debian
Here, using Ubuntu 10.04 for the netconsole capture machine, I've found the following works best:nc -klu 6666 Good luck with it.by restamp - uBoot
I just purchased a 2 TB GoFlex drive from Staples for $90, minus a 20% off coupon I had, the total came to about $77 with tax. It's a good deal if the drive proves to be reliable. So far, it has been working well hanging off my SheevaPlug. By default, it automatically spins down after 15 minutes of inactivity, which is about where I'd set it if I were tuning it, so I've left thaby restamp - Debian
Let me try this again. For some reason, my original post is being adjudicated to be spam. I'll keep it short: Google Voice has changed the chan_gtalk.c argument back to what it was before. See: https://issues.asterisk.org/jira/browse/ASTERISK-18301 So, you'll need to recompile again, until the Asterisk folks find a better workaround.by restamp - Debian
The fix did not work because Google changed the nodename once again -- this time back to what it was originally. See: https://issues.asterisk.org/jira/browse/ASTERISK-18301 Apparently, the Asterisk folks need a more robust solution, and they are working on it. In the meantime, I've changed the chan_gtalk.c file back to what it was before. If this happens again, I'll hack the fiby restamp - Debian
I compiled it from scratch initially. To make this change, I went to the directory I had initially had compiled asterisk in, and (1) modified channels/chan_gtalk.c as described above (2) did a "make" As root: (3) /etc/init.d/asterisk stop (4) make install (5) /etc/init.d/asterisk start No need to do another ./configure as it has already been done prior to the initial build.by restamp - Debian
Hi bodhi, erez was complaining that, after a power failure, his Pogoplug would not boot from his flash drive, but "boots pogoplug" instead (which I take to mean it boots the OS on its internal NAND filesystem). I've never seen this happen as a result of file system corruption (although I suppose if the file system was *so* corrupt that the uBoot couldn't find the uImage or uby restamp - Debian
Forgive me if I'm missing something, but if you were only messing with the fstab, then the problem should be confined to the OS, and not to the uBoot loader. In that case, if you provide a pristine OS, the Dockstar should be able to boot it. If you swap your two Dockstars, does your fileserver run on the original hardware? (Make sure you apply the Ethernet fixes to the appropriate filesby restamp - Debian
If you are consistently booting into the PogoPlug OS on a cold boot, it is not likely due to file system corruption. A power failure is a "cold boot", as opposed to a warm boot where you instruct the device to reboot without removing power. Some flash drives cold boot fine, but won't warm boot. Others, perhaps like yours, do the opposite. Some will not boot at all. What you woby restamp - Debian
I must confess up front that I am not well versed in this area. I am currently using a Dockstar to stream OTA programming to a hard drive from an HDHomeRun digital tuner. I then serve this content to a PC over my local LAN and watch it using VLC or Windows Media Player. Realistically, this approach works well for me. I rarely sit down just to watch TV. Rather, I typically scale down the videby restamp - Debian
The patch worked like a champ -- Google Voice lives again on my Dockstar! Thanks!by restamp - Debian
Yesterday evening, I noticed that outgoing Google Voice calls, using an Asterisk server on my Dockstar which I had put together some months ago using this thread (thanks!), stopped working for me. Incoming calls to my Google Voice number still ring through Asterisk to my Linksys ATA. Outgoing calls placed from my computer still work. But, outgoing calls through Asterisk appear to ring foreverby restamp - Debian
Frankly, all my computers here are attached to an UPS, so I have not had much trouble with corruption caused by power glitches. I have inadvertently crashed my Dockstar on a couple of occasions (with its root drive on a Seagate GO drive) by jostling the drive on its pedestal atop the Dockstar body. (It doesn't seem to like this.) But, if I recall, in all cases, it rebooted OK. When I lby restamp - Debian
(I think the question about the Free Agent GO HDD was directed at me. In any event, I'll take a stab at it, but I'll answer in the other thread that bodhi points to above.)by restamp - Debian
Does your Windows box respond to a ping?by restamp - uBoot