Welcome! Log In Create A New Profile

Advanced

Pogoplug PRO Bootloader no start with flash disk

Posted by Emil 
Hi

I`m install debian in Pogoplug Pro from this instruction http://blog.qnology.com/2015/04/hacking-pogoplug-v3oxnas-proclassic.html?showComment=1464198116974#c7190902143829429000 .
- I untar debian package in flash disk on pogoplug device and restart.
- Pogoplug don`t boot, don`t see flash drive ....
- I connect serial cable and see this :

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
  Boot device: NAND
Attempting to set PLLA to 850 MHz ...
  plla_ctrl0 : 0000020a
  plla_ctrl1 : 00330000
  plla_ctrl2 : 0065008b
  plla_ctrl3 : 000000f1

PLLA Set
Please help to fix this problem.
Re: Pogoplug PRO Bootloader no start with flash disk
May 25, 2016 06:45PM
Emil Wrote:
-------------------------------------------------------
> Hi
>
> I`m install debian in Pogoplug Pro from this
> instruction
> http://blog.qnology.com/2015/04/hacking-pogoplug-v
> 3oxnas-proclassic.html?showComment=1464198116974#c
> 7190902143829429000 .
> - I untar debian package in flash disk on pogoplug
> device and restart.
> - Pogoplug don`t boot, don`t see flash drive ....
> - I connect serial cable and see this :
>
>
> U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
>   Boot device: NAND
> Attempting to set PLLA to 850 MHz ...
>   plla_ctrl0 : 0000020a
>   plla_ctrl1 : 00330000
>   plla_ctrl2 : 0065008b
>   plla_ctrl3 : 000000f1
> 
> PLLA Set
> 
>
> Please help to fix this problem.

Did you keep the log of the entired installation? And do you have the log of dmesg output? Any error occurred during installation of u-boot?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
No, nothing :-(
Re: Pogoplug PRO Bootloader no start with flash disk
May 26, 2016 03:36AM
If it stops right here then your u-boot was not flashed successfully (usually because of bad blocks in the first 2MB ).

> U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
>   Boot device: NAND
> Attempting to set PLLA to 850 MHz ...
>   plla_ctrl0 : 0000020a
>   plla_ctrl1 : 00330000
>   plla_ctrl2 : 0065008b
>   plla_ctrl3 : 000000f1
> 
> PLLA Set
>

The Pogo V3 does not have UART booting. So the only way you can recover this semi-bricked Pogo V3 is to boot with a special prepared SATA connected hardisk which contains u-boot image, u-boot envs, and Debian rootfs.

I'll have to find the thread that talk about this SATA booting. The idea is you need to open up the box and connect an HDD using the SATA port inside. And then format a partition and a boot sector on this disk.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
How create bootable hdd with u-boot in MBR on another machine ?
I must have bootloader, when i downloaded u-boot image, u-boot envs, and Debian rootfs?
Please solution.
Re: Pogoplug PRO Bootloader no start with flash disk
May 26, 2016 03:37PM
This is WarheadsSE's instruction (the original) (using Arch):
https://archlinuxarm.org/forum/viewtopic.php?f=55&t=2146&sid=f4dc4863e3a93822a4f9e925b3cbda45

And here shv's post showing how it was done with Debian rootfs:
http://forum.doozan.com/read.php?3,16017,17297#msg-17297

Some of the download links no longer work, it's been a while. But I have a tarball from Leggo that I think you can use with that the instruction. I'll upload the tarball when you have read these instruction and let me know if you ready.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 05/26/2016 03:52PM by bodhi.
Re: Pogoplug PRO Bootloader no start with flash disk
May 29, 2016 06:21PM
bodhi Wrote:
-------------------------------------------------------
> And here shv's post showing how it was done with
> Debian rootfs:
> http://forum.doozan.com/read.php?3,16017,17297#msg
> -17297
>

I will have to peruse the above link to learn how it gets done for my Seagate GoFLEX Home/Net devices. Many thanks Bodhi.
Re: Pogoplug PRO Bootloader no start with flash disk
May 29, 2016 06:41PM
habibie Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > And here shv's post showing how it was done
> with
> > Debian rootfs:
> >
> http://forum.doozan.com/read.php?3,16017,17297#msg
>
> > -17297
> >
>
> I will have to peruse the above link to learn how
> it gets done for my Seagate GoFLEX Home/Net
> devices. Many thanks Bodhi.

Why bother? if you have netconsole/serial console then it recovery is always possible. And you can already boot from SATA rootfs using u-boot.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Pogoplug PRO Bootloader no start with flash disk
May 30, 2016 07:56AM
bodhi Wrote:
-------------------------------------------------------
> habibie Wrote:
> --------------------------------------------------
> -----
> > bodhi Wrote:
> >
> --------------------------------------------------
>
> > -----
> > > And here shv's post showing how it was done
> > with
> > > Debian rootfs:
> > >
> >
> http://forum.doozan.com/read.php?3,16017,17297#msg
>
> >
> > > -17297
> > >
> >
> > I will have to peruse the above link to learn
> how
> > it gets done for my Seagate GoFLEX Home/Net
> > devices. Many thanks Bodhi.
>
> Why bother? if you have netconsole/serial console
> then it recovery is always possible. And you can
> already boot from SATA rootfs using u-boot.

Here is the idea why. With a Seagate GoFlex Home/NET still configured to use its original/stock uboot+firmware, I want it to be able to boot off other OS, i.e. LEDE, OpenWRT, etc., when a SATA HDD (installed with either OSes) is inserted. This way, I don't have to replace its original/stock uboot.
Re: Pogoplug PRO Bootloader no start with flash disk
May 30, 2016 04:33PM
I've maded a separate subject for this Kirkwood SATA booting:
http://forum.doozan.com/read.php?3,28224

Please continue posting on that thread if it is not related to the Pogo Pro/Classic V3.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Pogoplug PRO Bootloader no start with flash disk
May 31, 2016 03:36AM
Done and thank you Bodhi.
Ok Bohdi i`m ready please working links
Re: Pogoplug PRO Bootloader no start with flash disk
June 02, 2016 01:44AM
This is courtesy of LeggoMyEggo. I've upload the tarball Leggo sent me to Dropbox.

There are 2 tarballs in it. One from shv, one from WarheadsSE. It's easier to use the shv's: ox820-sata-uboot.tar.gz.

ox820-sata-uboot.tar.gz
oxnas_sata_boot.tgz

Dropbox download link:
oxnasboottarball.zip
md5
8e016437146f40cdb51ad9dbd63b1bdd

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 06/02/2016 01:45AM by bodhi.
hI

I connected hdd via sata. I have this :

ATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: FUJITSU MHV2080BH PL Firm: 892C Ser#: NW9ZT682HSW9
Type: Hard Disk
Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
Device 1: not available
Failed to read valid environment from disk, using built-in default


U-Boot 1.1.2 (Dec 31 2011 - 15:24:45)

U-Boot code: 60E00000 -> 60E1FB34 BSS: -> 60E5435C
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:128 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value

IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 0

Loading from IDE device 0, partition 1: Name: hda1
Type: U-Boot
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2132260 Bytes = 2 MB
Load Address: 60008000
Entry Point: 60008000
## Booting image at 60500000 ...
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2132260 Bytes = 2 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... Bad Data CRC
Unknown command 'lightled' - try 'help'
$

Whats now??

emilw11

Posts: 3
Joined: Wed May 25, 2016 5:11 pm
I create new hdd and system booting but halted. see log :
Quote

[ 6.350000] usb usb1: Product: OXNAS EHCI Host Controller
[ 6.360000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
[ 6.370000] usb usb1: SerialNumber: usb
[ 6.370000] usb usb1: configuration #1 chosen from 1 choice
[ 6.380000] hub 1-0:1.0: USB hub found
[ 6.380000] hub 1-0:1.0: 2 ports detected
[ 6.390000] Initializing USB Mass Storage driver...
[ 6.390000] usbcore: registered new interface driver usb-storage
[ 6.400000] USB Mass Storage support registered.
[ 6.400000] mice: PS/2 mouse device common for all mice
[ 6.410000] TCP cubic registered
[ 6.410000] NET: Registered protocol family 10
[ 6.420000] NET: Registered protocol family 17
[ 6.420000] RPC: Registered udp transport module.
[ 6.420000] RPC: Registered tcp transport module.
[ 6.430000] VFS: Cannot open root device "sda2" or unknown-block(8,2)
[ 6.440000] Please append a correct "root=" boot option; here are the available partitions:
[ 6.450000] 0800 78150744 sda driver: sd
[ 6.450000] 0801 78149632 sda1
[ 6.450000] 1f00 131072 mtdblock0 (driver?)
[ 6.460000] 1f01 14336 mtdblock1 (driver?)
[ 6.460000] 1f02 116736 mtdblock2 (driver?)
[ 6.470000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
[ 6.480000] [<c002e1fc>] (unwind_backtrace+0x0/0xe0) from [<c02e628c>] (panic+0x44/0x108)
[ 6.490000] [<c02e628c>] (panic+0x44/0x108) from [<c0008f3c>] (mount_block_root+0x1d4/0x294)
[ 6.490000] [<c0008f3c>] (mount_block_root+0x1d4/0x294) from [<c00092c0>] (prepare_namespace+0x164/0x1bc)
[ 6.500000] [<c00092c0>] (prepare_namespace+0x164/0x1bc) from [<c0008c20>] (kernel_init+0x1a8/0x1e8)
[ 6.510000] [<c0008c20>] (kernel_init+0x1a8/0x1e8) from [<c00299c4>] (kernel_thread_exit+0x0/0x8)
[ 6.520000] CPU0: stopping
[ 6.520000] [<c002e1fc>] (unwind_backtrace+0x0/0xe0) from [<c0028398>] (do_IPI+0xec/0x160)
[ 6.520000] [<c0028398>] (do_IPI+0xec/0x160) from [<c0028af8>] (__irq_svc+0x38/0xc0)
[ 6.540000] Exception stack(0xc03cff50 to 0xc03cff98)
[ 6.540000] ff40: 00000001 00000000 c03cff98 00000000
[ 6.540000] ff60: c03ce000 c03f5664 c03d40c4 c03ce000 c0022000 c0023180 c03d3e08 c03f53e0
[ 6.540000] ff80: 7fffffff c03cff98 c0029a1c c0029a20 60000013 ffffffff
[ 6.540000] [<c0028af8>] (__irq_svc+0x38/0xc0) from [<c0029a20>] (default_idle+0x24/0x28)
[ 6.580000] [<c0029a20>] (default_idle+0x24/0x28) from [<c0029be8>] (cpu_idle+0x6c/0xa4)
[ 6.580000] [<c0029be8>] (cpu_idle+0x6c/0xa4) from [<c0008a10>] (start_kernel+0x31c/0x384)
[ 6.580000] [<c0008a10>] (start_kernel+0x31c/0x384) from [<60008084>] (0x60008084)
I do 2 partitions and in log see
Quote

Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: ST3160815AS Firm: 3.CHF Ser#: 6RX3HPSK
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
Device 1: not available
Failed to read valid environment from disk, using built-in default


U-Boot 1.1.2 (Dec 31 2011 - 15:24:45)

U-Boot code: 60E00000 -> 60E1FB34 BSS: -> 60E5435C
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:128 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value

IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 0

Loading from IDE device 0, partition 1: Name: hda1
Type: U-Boot

** Bad Magic Number **

Loading from IDE device 0, partition 2: Name: hda2
Type: U-Boot

** Bad Magic Number **
Unknown command 'lightled' - try 'help'
$
$
$

What is ** Bad Magic Number ** ???
Re: Pogoplug PRO Bootloader no start with flash disk
June 12, 2016 04:56PM
Emilw11,

Once you see this prompt

Quote

> $

You are in the shell. So boot back this way, and verify at the prompt that you are in stock OS:

uname -a
mount
cat /proc/cmdline

Then if you are actually inside stock OS, follow the instruction to flash new u-boot again:
http://forum.doozan.com/read.php?3,16017

If you would like, post your entire log of how you install u-boot and its env image here.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Pogoplug PRO Bootloader no start with flash disk
March 12, 2017 10:45AM
thanks. reserver this files
shv
Re: Pogoplug PRO Bootloader no start with flash disk
March 13, 2017 03:56PM
Sorry, I posted in a wrong thread.

-shv



Edited 2 time(s). Last edit at 03/13/2017 04:01PM by shv.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: