[Solved] Flashing Green Light PogoPlug v4
5 posts
• Page 1 of 1
[Solved] Flashing Green Light PogoPlug v4
by vnangia » Wed Jan 29, 2014 3:42 pm
I followed the instructions on http://archlinuxarm.org/platforms/armv5 ... g-series-4 precisely to the letter using an Amazon-bought SanDisk 16gb drive. However, on /sbin/reboot, the device started flashing a green light - it did so overnight. I power-cycled the drive as well, and it doesn't appear to have worked - it's still flashing green. How long should I give it to boot? An hour? Couple of hours?
Last edited by vnangia on Wed Feb 05, 2014 3:02 pm, edited 1 time in total.
- vnangia
- Posts: 3
- Joined: Wed Jan 29, 2014 3:39 pm
- WarheadsSE
- Developer
- Posts: 6807
- Joined: Mon Oct 18, 2010 2:12 pm
Re: Flashing Green Light PogoPlug v4
by Sergeanter » Wed Jan 29, 2014 5:39 pm
I suggest you plug your drive in a different linux machine ( a laptop with livecd or whatever you have ) and run a file system check on it. Unmount USB stick on that machine before running e2fsck -f /dev/sdb1 ( or whatever device gets assigned to USB stick).
Tell us your story. I still have similar problems even after the kernel upgrade.
Also, I believe there were suggestions to use flash memory with not more than 4GB capacity as boot drive.
Tell us your story. I still have similar problems even after the kernel upgrade.
Also, I believe there were suggestions to use flash memory with not more than 4GB capacity as boot drive.
- Sergeanter
- Posts: 87
- Joined: Wed Oct 02, 2013 5:14 am
Re: Flashing Green Light PogoPlug v4
by vnangia » Wed Feb 05, 2014 1:51 pm
$this->bbcode_second_pass_quote('WarheadsSE', 'W')hich "16gb drive"
Sandisk Cruzer 16GB, bought from Amazon (not marketplace) in September 2013.
$this->bbcode_second_pass_quote('Sergeanter', 'I') suggest you plug your drive in a different linux machine ( a laptop with livecd or whatever you have ) and run a file system check on it. Unmount USB stick on that machine before running e2fsck -f /dev/sdb1 ( or whatever device gets assigned to USB stick).
Tell us your story. I still have similar problems even after the kernel upgrade.
Also, I believe there were suggestions to use flash memory with not more than 4GB capacity as boot drive.
File system appears to have cleanly unmounted with no errors. I have not seen the suggestions to use less than 4GB drives anywhere in the instructions provided, but if that is the case, then I would appreciate a specific disk recommendation. I have no small drives that are not generics and cannot vouch for their reliability for boot purposes on ARM, though they have been used successfully to start x86 and AMD64 machines.
More information:
A friend of mine also has an identical Pogoplug v4 which he installed ALARM to several months ago (roughly May 2013). That drive DOES boot my Pogoplug correctly and I am able to ssh in, suggesting that uboot has the correct parameters. A dd of the drive does successfully boot the device, but ssh does not come up even after an hour. I am at a loss to explain why this is so.
However, attempting a fresh installation on my drive using the reinstallation instructions provided fails. This suggests there is a problem in the current configuration that prevents bootup. Is there a way to get an archived release (say from mid-year last year) and then use pacman to update all packages on the system? Alternatively, is there a clean known working disk image one can dd?
- vnangia
- Posts: 3
- Joined: Wed Jan 29, 2014 3:39 pm