New Pink Pogoplug B04 bricked

This forum is for all other ARMv5 devices
Topic locked

Re: New Pink Pogoplug B04 bricked

Postby redsquare » Wed Aug 17, 2011 8:00 pm

Were you able to put the old one back in then?, mine had errors.
redsquare
 
Posts: 18
Joined: Tue Aug 02, 2011 6:37 pm
Top

Re: New Pink Pogoplug B04 bricked

Postby WarheadsSE » Wed Aug 17, 2011 8:06 pm

Originally I had errors too. I can try again tonight.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: New Pink Pogoplug B04 bricked

Postby WarheadsSE » Thu Aug 18, 2011 12:56 am

So far: Stage1 on nand, copied from pogoplug, ok.

Successfully booting.. not so much. errors reading.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: New Pink Pogoplug B04 bricked

Postby Taker » Sun Oct 02, 2011 11:28 am

$this->bbcode_second_pass_quote('WarheadsSE', 'O')k, I've bundled up the entire mtd0, with and without oob (out of band data). It's 44MB compacted with tar cjvf (so use tar xjvf to extract).

Once it is extracted, and you have are booted into an ALARM OS, get the mtd-utils package and you should be able to flash_eraseall and then dd the non-oob. If that doesn't work we'll have to do it from uboot off the sata drive.

http://my.pogoplug.com/share/vArHUudFPhMW8MZGCEDcIA/

Look for oxnas-mtd0.tar.xz, and I apologize for the speed of my current internet connection.


$this->bbcode_second_pass_quote('redsquare', 'T')his is not (Yet) a recovery mechanism, just an attempt to get to one.

So in order to get some sort of U-Boot running you need a SATA disk, create a partition on it (Just so an MBR is created). From there, extract the attached tarball, and edit the script to point to the correct drive you want to use. You'll need to change the kernel if you don't have PCI on your board.

Connect it up to the Pogoplug and you should see on the serial that the board now runs U-Boot and attempts to boot Linux from the HDD. I use the following U-Boot variables to boot into my setup:

$this->bbcode_second_pass_code('', '
setenv bootargs "root=/dev/sdb1 console=ttyS0,115200 rootwait mem=128M"
run select0 load1

bootm 60500000
')

The problem I'm having now is that I'm not able to successfully burn and run from flash. I get errors as in my previous post, I wonder if my NAND is bad? I think I've tried all combinations of flash_eraseall and nandwrite with both the OOB and non OOB.


Missed off the file, try this:

https://rapidshare.com/files/4116281900/sata_update.tar.gz



@WarheadsSE / redsquare
I tried to follow your instructions on my bricked B04 but it still leads to a
$this->bbcode_second_pass_code('', '## Booting image at 60500000 ...
Bad Magic Number')

I did the following steps (may be it could grow to a short tutorial, if someone could help me to fix my problem):

1) Create a partition on a SATA-Device with filesystem ext2, marked as 'boot' (using GParted from Knoppix Linux Live Disc)

2) Copy the two archives to the new partition and extract them :
$this->bbcode_second_pass_code('', '
knoppix@Microknoppix:~$ sudo cp /media/sdd1/oxnas-mtd0.tar.xz /media/sdc1/
knoppix@Microknoppix:~$ sudo cp /media/sdd1/sata_update.tar.gz /media/sdc1/
knoppix@Microknoppix:~$ cd /media/sdc1/
knoppix@Microknoppix:/media/sdc1$ ls -la
insgesamt 45756
drwxr-xr-x 3 root root 4096 2. Okt 10:22 .
drwxr-xr-x 10 root root 0 2. Okt 10:19 ..
drwx------ 2 root root 16384 2. Okt 10:19 lost+found
-rwxr-xr-x 1 root root 44596609 2. Okt 10:22 oxnas-mtd0.tar.xz
-rwxr-xr-x 1 root root 2182170 2. Okt 10:22 sata_update.tar.gz
knoppix@Microknoppix:/media/sdc1$ sudo tar xjvf oxnas-mtd0.tar.xz
oxnas-mtd0/
oxnas-mtd0/mtd0.backup
oxnas-mtd0/mtd0.backup.oob
knoppix@Microknoppix:/media/sdc1$ sudo tar xvf sata_update.tar.gz
disk_create
stage1.wrapped
u-boot.wrapped
uImage.pci
')
3.) I used the disk_create-script, but here I'm really not sure if I have to use it:
$this->bbcode_second_pass_code('', '
knoppix@Microknoppix:/media/sdc1$ sudo ./disk_create
0+1 Datensätze ein
0+1 Datensätze aus
444 Bytes (444 B) kopiert, 0,873634 s, 0,5 kB/s
Writing stage 1
17+1 Datensätze ein
17+1 Datensätze aus
8716 Bytes (8,7 kB) kopiert, 0,0104861 s, 831 kB/s
Writing uboot
202+1 Datensätze ein
202+1 Datensätze aus
103572 Bytes (104 kB) kopiert, 0,0238891 s, 4,3 MB/s
Writing kernel
4164+1 Datensätze ein
4164+1 Datensätze aus
2132324 Bytes (2,1 MB) kopiert, 0,33064 s, 6,4 MB/s
4164+1 Datensätze ein
4164+1 Datensätze aus
2132324 Bytes (2,1 MB) kopiert, 0,2333 s, 9,1 MB/s
knoppix@Microknoppix:/media/sdc1$ cd ~
knoppix@Microknoppix:~$ umount /media/sdc1
knoppix@Microknoppix:~$
')
4.) After umount and connect to my pogoplug the full serial output is:
$this->bbcode_second_pass_code('', '
Stage-1 Bootloader Tue Jan 18 15:00:30 MST 2011
Attempting to set PLLA to 600MHz ...
plla_ctrl0 : 0x0000021A
plla_ctrl1 : 0x00480000
plla_ctrl2 : 0x008F008B
plla_ctrl3 : 0x00000154
PLLA Set

Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001948C
Hdr CRC: 0xA6FB1209
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: ST380013AS Firm: 8.12 Ser#: 5MR2TQPX
Type: Hard Disk
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
Device 1: not available
Failed to read valid environment from disk, using built-in default


U-Boot 1.1.2 (Aug 26 2010 - 14:02:09)

U-Boot code: 60D00000 -> 60D1948C BSS: -> 60D1D11C
RAM Configuration:
Bank #0: 60000000 256 MB
SRAM Configuration:
64KB at 0x50000000
*** 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

IDE device 0: Model: ST380013AS Firm: 8.12 Ser#: 5MR2TQPX
Type: Hard Disk
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
... is now current device

IDE read: device 0 block # 1290, count 5700 ... 5700 blocks read: OK

IDE read: device 0 block # 16674, count 5700 ... 5700 blocks read: OK
## 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
Light LED

IDE device 0: Model: ST380013AS Firm: 8.12 Ser#: 5MR2TQPX
Type: Hard Disk
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
... is now current device

IDE read: device 0 block # 58344, count 5700 ... 5700 blocks read: OK

IDE read: device 0 block # 16674, count 5700 ... 5700 blocks read: OK
Extinguish LED
## Booting image at 60500000 ...
Bad Magic Number
Unknown command 'lightled' - try 'help'
PLX>>
')
I'm really sure, that I misunderstood or did not understood some of your explanations, so please could you take a look at my steps above and give me a hint where something is wrong?

THX
Taker
 
Posts: 14
Joined: Mon May 30, 2011 9:46 am
Top

Re: New Pink Pogoplug B04 bricked

Postby redsquare » Mon Oct 03, 2011 7:29 pm

$this->bbcode_second_pass_quote('Taker', '
')I'm really sure, that I misunderstood or did not understood some of your explanations, so please could you take a look at my steps above and give me a hint where something is wrong?


Taker,

At the moment we can only use "bricked" pogos by booting from the SATA drive. No one has managed to successfully restore a boot loader back into flash.

Your problem seems to be related to the loading of the kernel image. You might want to try dding the image back to the disk again, failing that post you U-Boot env.
redsquare
 
Posts: 18
Joined: Tue Aug 02, 2011 6:37 pm
Top

Re: New Pink Pogoplug B04 bricked

Postby Taker » Sun Oct 09, 2011 9:19 pm

$this->bbcode_second_pass_quote('redsquare', '')$this->bbcode_second_pass_quote('Taker', '
')I'm really sure, that I misunderstood or did not understood some of your explanations, so please could you take a look at my steps above and give me a hint where something is wrong?


Taker,

At the moment we can only use "bricked" pogos by booting from the SATA drive. No one has managed to successfully restore a boot loader back into flash.

Your problem seems to be related to the loading of the kernel image. You might want to try dding the image back to the disk again, failing that post you U-Boot env.


Thanks a lot!
I did the procedure again with another SATA drive and made a progress with my "bricked" B04-Pogo.
I also changed the bootargs with 'setenv bootargs root=/dev/sdb1 console=ttyS0,115200 rootwait mem=128M', followed by the 'run select0 load1' & 'bootm 60500000' and kernel loading began:

$this->bbcode_second_pass_code('', 'U-Boot 1.1.2 (Aug 26 2010 - 14:02:09)

U-Boot code: 60D00000 -> 60D1948C BSS: -> 60D1D11C
RAM Configuration:
Bank #0: 60000000 256 MB
SRAM Configuration:
64KB at 0x50000000
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

PLX>>setenv bootargs root=/dev/sdb1 console=ttyS0,115200 rootwait mem=128M
PLX>>printenv
bootcmd=run select0 load1 load_rd boot || run lightled select0 load2 load_rd extinguishled boot || lightled
bootdelay=3
baudrate=115200
ethaddr=00:30:e0:00:00:01
ipaddr=172.31.0.128
serverip=172.31.0.100
autoload=n
netmask=255.255.0.0
bootfile="uImage"
select0=ide dev 0
load1=ide read 0x60500000 50a 1644
load2=ide read 0x60500000 e3e8 1644
load_rd=ide read 0x60800000 4122 1644
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000 60800000
stdin=serial
stdout=serial
stderr=serial
bootargs=root=/dev/sdb1 console=ttyS0,115200 rootwait mem=128M

Environment size: 556/8188 bytes
PLX>>run select0 load1

IDE device 0: Model: ST380013AS Firm: 8.12 Ser#: 5MR2TQPX
Type: Hard Disk
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
... is now current device

IDE read: device 0 block # 1290, count 5700 ... 5700 blocks read: OK
PLX>>bootm 60500000
## Booting image at 60500000 ...
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2159884 Bytes = 2.1 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux................................................................................................................................. done, booting the kernel.
[ 0.000000] Linux version 2.6.31.6_SMP_820 (root@ProDev) (gcc version 4.6.0 20110429 (prerelease) (GCC) ) #99 SMP Sun May 29 03:04:43 EDT 2011
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Oxsemi NAS
[ 0.000000] 1 memory region
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: root=/dev/sda1 console=ttyS0,115200 rootwait mem=128M
[ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 125524KB available (3636K code, 296K data, 128K init, 0K highmem)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:96
[ 0.000000] OX820_RPS_init_irq: interrupts 64 to 96
[ 0.010000] Console: colour dummy device 80x30
[ 0.010000] console [ttyS0] enabled
[ 0.020000] Calibrating delay loop... 239.20 BogoMIPS (lpj=1196032)
[ 0.260000] Security Framework initialized
[ 0.260000] Mount-cache hash table entries: 512
[ 0.270000] CPU: Testing write buffer coherency: ok
[ 0.270000] Calibrating local timer... 299.99MHz.
[ 0.340000] CPU1: Booted secondary processor
[ 0.440000] Calibrating delay loop... 239.20 BogoMIPS (lpj=1196032)
[ 0.680000] Brought up 2 CPUs
[ 0.690000] SMP: Total of 2 processors activated (478.41 BogoMIPS).
[ 0.700000] NET: Registered protocol family 16
[ 0.700000] Number of DMA channels = 4, version = 4
[ 0.710000] Reserving a DMA channel for DirectRAID
[ 0.710000] Allocating 389 SRAM generic DMA descriptors
')

Using your script without changing the default value for the kernel (uImage.pci) booting stops after these lines :roll: .
So I changed it to 'uImage.nopci' from
http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz.

Now with the 'uImage.nopci' it leads to:
$this->bbcode_second_pass_code('', 'PLX>>bootm 60500000
## Booting image at 60500000 ...
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2159884 Bytes = 2.1 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux................................................................................................................................... done, booting the kernel.
[ 0.000000] Linux version 2.6.31.6_SMP_820 (root@ProDev) (gcc version 4.6.0 20110429 (prerelease) (GCC) ) #100 SMP Sun May 29 04:53:45 EDT 2011
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Oxsemi NAS
[ 0.000000] 1 memory region
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: root=/dev/sdb1 console=ttyS0,115200 rootwait mem=128M
[ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 125496KB available (3692K code, 291K data, 124K init, 0K highmem)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:96
[ 0.000000] OX820_RPS_init_irq: interrupts 64 to 96
[ 0.010000] Console: colour dummy device 80x30
[ 0.010000] console [ttyS0] enabled
[ 0.020000] Calibrating delay loop... 239.20 BogoMIPS (lpj=1196032)
[ 0.260000] Security Framework initialized
[ 0.260000] Mount-cache hash table entries: 512
[ 0.270000] CPU: Testing write buffer coherency: ok
[ 0.270000] Calibrating local timer... 299.99MHz.
[ 0.340000] CPU1: Booted secondary processor
[ 0.440000] Calibrating delay loop... 239.20 BogoMIPS (lpj=1196032)
[ 0.680000] Brought up 2 CPUs
[ 0.690000] SMP: Total of 2 processors activated (478.41 BogoMIPS).
[ 0.700000] NET: Registered protocol family 16
[ 0.700000] Number of DMA channels = 4, version = 4
[ 0.710000] Reserving a DMA channel for DirectRAID
[ 0.710000] Allocating 389 SRAM generic DMA descriptors
[ 0.730000] bio: create slab <bio-0> at 0
[ 0.740000] SCSI subsystem initialized
[ 0.750000] usbcore: registered new interface driver usbfs
[ 0.750000] usbcore: registered new interface driver hub
[ 0.760000] usbcore: registered new device driver usb
[ 0.790000] NET: Registered protocol family 2
[ 0.790000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.800000] Switched to NOHz mode on CPU #0
[ 0.800000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.800000] Switched to NOHz mode on CPU #1
[ 0.810000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.820000] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.820000] TCP reno registered
[ 0.830000] NET: Registered protocol family 1
[ 0.830000] Create fragment cache
[ 0.840000] fuse init (API version 7.12)
[ 0.850000] msgmni has been set to 245
[ 0.850000] alg: No test for stdrng (krng)
[ 0.860000] io scheduler noop registered
[ 0.860000] io scheduler anticipatory registered (default)
[ 0.870000] io scheduler deadline registered
[ 0.870000] io scheduler cfq registered
[ 0.900000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.900000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
[ 0.920000] brd: module loaded
[ 0.930000] loop: module loaded
[ 0.940000] ox820sata: OX820 sata core.
[ 0.940000] scsi0 : oxnassata
[ 0.950000] scsi1 : oxnassata
[ 0.950000] ata1: SATA max UDMA/133 irq 50
[ 0.950000] ata2: SATA max UDMA/133 irq 50
[ 0.960000] ox820sata: reseting SATA core
[ 1.480000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.480000] ata1.00: ATA-6: ST380013AS, 8.12, max UDMA/133
[ 1.490000] ata1.00: 156250000 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 1.500000] ata1.00: configured for UDMA/133
[ 1.500000] ox820sata: reseting SATA core
[ 2.220000] ata2: SATA link down (SStatus 0 SControl 300)
[ 2.220000] scsi 0:0:0:0: Direct-Access ATA ST380013AS 8.12 PQ: 0 ANSI: 5
[ 2.230000] sd 0:0:0:0: [sda] 156250000 512-byte logical blocks: (80.0 GB/74.5 GiB)
[ 2.240000] sd 0:0:0:0: [sda] Write Protect is off
[ 2.240000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.250000] sda:
[ 2.260000] tun: Universal TUN/TAP device driver, 1.6
[ 2.260000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 2.270000] sda1
[ 2.270000] NAND: Page read time 40ms
[ 2.280000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[ 2.280000] Scanning device for bad blocks
[ 2.360000] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.360000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[ 2.360000] 0x000000000000-0x000000e00000 : "boot"
[ 2.360000] 0x000000e00000-0x000008000000 : "rootfs"
[ 2.380000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.390000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
[ 2.400000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
[ 2.440000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
[ 2.460000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
[ 2.460000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.470000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.480000] usb usb1: Product: OXNAS EHCI Host Controller
[ 2.480000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
[ 2.490000] usb usb1: SerialNumber: usb
[ 2.490000] usb usb1: configuration #1 chosen from 1 choice
[ 2.500000] hub 1-0:1.0: USB hub found
[ 2.500000] hub 1-0:1.0: 2 ports detected
[ 2.510000] Initializing USB Mass Storage driver...
[ 2.510000] usbcore: registered new interface driver usb-storage
[ 2.520000] USB Mass Storage support registered.
[ 2.520000] mice: PS/2 mouse device common for all mice
[ 2.530000] TCP cubic registered
[ 2.530000] NET: Registered protocol family 10
[ 2.540000] NET: Registered protocol family 17
[ 2.540000] RPC: Registered udp transport module.
[ 2.550000] RPC: Registered tcp transport module.
[ 2.550000] Waiting for root device /dev/sdb1...
[ 2.820000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
[ 2.970000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 2.970000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.980000] usb 1-1: Product: USB2.0 Hub
[ 2.990000] usb 1-1: configuration #1 chosen from 1 choice
[ 2.990000] hub 1-1:1.0: USB hub found
[ 3.000000] hub 1-1:1.0: 4 ports detected
')

Now I'm really unsure wich output I should expect after these lines, because serial output stops here and nothing else seems to happen. Did I forget something again?
Taker
 
Posts: 14
Joined: Mon May 30, 2011 9:46 am
Top

Re: New Pink Pogoplug B04 bricked

Postby timstegeman » Fri Oct 28, 2011 6:35 pm

After almost giving up I finally recovered my Pogoplug B03.
With all the hints you guys gave me I booted into ALARM OS.
There I installed the mtd-utils and flashed the uboot part of mtd0 back.
I attached my backup so you can use it to.

$this->bbcode_second_pass_code('', '
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot-mtd0-dump
')
After this I was possible to boot into uboot again without a SATA harddisk. Only it didn't booted the kernel.
Somehow the environment variable "bootcmd" was changed. Possibly by the wrong uboot version that bricked my device.

To correct this I used the following commands.
$this->bbcode_second_pass_code('', '
setenv bootcmd "run boot_nand"
saveenv
reset
')

And now it working again... :)
Attachments
uboot-mtd0-dump.tgz
the uboot part of mtd0 (Pogoplug B03)
(152.34 KiB) Downloaded 1291 times
timstegeman
 
Posts: 7
Joined: Sat May 28, 2011 11:36 am
Top

Re: New Pink Pogoplug B04 bricked

Postby Taker » Fri Oct 28, 2011 9:14 pm

$this->bbcode_second_pass_quote('timstegeman', '
')With all the hints you guys gave me I booted into ALARM OS.


Can you take a look at my last post, please? Am I already in the ALARM OS? Im really unsure at which step booting into ALARM OS was successful

$this->bbcode_second_pass_quote('timstegeman', '
')There I installed the mtd-utils and flashed the uboot part of mtd0 back.

Could describe which steps are necessary to install the mtd-utils?

Thanks
Taker
Taker
 
Posts: 14
Joined: Mon May 30, 2011 9:46 am
Top

Re: New Pink Pogoplug B04 bricked

Postby WarheadsSE » Sat Oct 29, 2011 8:49 pm

Taker, at that point it stopped and waited for the rootfs it expected as /dev/sdb1 .. you might want to change that to sda1
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: New Pink Pogoplug B04 bricked

Postby Taker » Sun Oct 30, 2011 8:42 am

$this->bbcode_second_pass_quote('WarheadsSE', 'T')aker, at that point it stopped and waited for the rootfs it expected as /dev/sdb1 .. you might want to change that to sda1


Changing bootargs to /dev/sda1 leads to Kernel panic:

$this->bbcode_second_pass_code('', '
...
[ 2.570000] NET: Registered protocol family 10
[ 2.580000] NET: Registered protocol family 17
[ 2.580000] RPC: Registered udp transport module.
[ 2.590000] RPC: Registered tcp transport module.
[ 2.590000] List of all partitions:
[ 2.600000] 0800 78125000 sda driver: sd
[ 2.600000] 0801 78123976 sda1
[ 2.610000] 1f00 131072 mtdblock0 (driver?)
[ 2.610000] 1f01 14336 mtdblock1 (driver?)
[ 2.620000] 1f02 116736 mtdblock2 (driver?)
[ 2.620000] No filesystem could mount root, tried: ext3 ext2 fuseblk
[ 2.630000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
[ 2.640000] [<c002cbc0>] (unwind_backtrace+0x0/0xe0) from [<c02f5b18>] (panic+0x44/0x108)
[ 2.640000] [<c02f5b18>] (panic+0x44/0x108) from [<c0008fac>] (mount_block_root+0x244/0x294)
[ 2.650000] [<c0008fac>] (mount_block_root+0x244/0x294) from [<c00092c0>] (prepare_namespace+0x164/0x1bc)
[ 2.660000] [<c00092c0>] (prepare_namespace+0x164/0x1bc) from [<c0008c20>] (kernel_init+0x1a8/0x1e8)
[ 2.670000] [<c0008c20>] (kernel_init+0x1a8/0x1e8) from [<c00289c4>] (kernel_thread_exit+0x0/0x8)
[ 2.680000] CPU1: stopping
[ 2.680000] [<c002cbc0>] (unwind_backtrace+0x0/0xe0) from [<c0027398>] (do_IPI+0xec/0x160)
[ 2.680000] [<c0027398>] (do_IPI+0xec/0x160) from [<c0027af8>] (__irq_svc+0x38/0xc0)
[ 2.680000] Exception stack(0xc7843f90 to 0xc7843fd8)
[ 2.680000] 3f80: 00000001 00000000 c7843fd8 00000000
[ 2.680000] 3fa0: c7842000 c04012c4 c03e203c c7842000 00000000 410fb025 6001fd74 00000000
[ 2.680000] 3fc0: 7fffffff c7843fd8 c0028a1c c0028a20 60000013 ffffffff
[ 2.680000] [<c0027af8>] (__irq_svc+0x38/0xc0) from [<c0028a20>] (default_idle+0x24/0x28)
[ 2.680000] [<c0028a20>] (default_idle+0x24/0x28) from [<c0028be8>] (cpu_idle+0x6c/0xa4)
[ 2.680000] [<c0028be8>] (cpu_idle+0x6c/0xa4) from [<60008084>] (0x60008084)
')(output stops after these lines)

Comparing it to /dev/sdb1:
$this->bbcode_second_pass_code('', '
...
[ 2.620000] NET: Registered protocol family 10
[ 2.630000] NET: Registered protocol family 17
[ 2.630000] RPC: Registered udp transport module.
[ 2.640000] RPC: Registered tcp transport module.
[ 2.640000] Waiting for root device /dev/sdb1...
[ 2.910000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
[ 3.060000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 3.060000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 3.070000] usb 1-1: Product: USB2.0 Hub
[ 3.080000] usb 1-1: configuration #1 chosen from 1 choice
[ 3.080000] hub 1-1:1.0: USB hub found
[ 3.090000] hub 1-1:1.0: 4 ports detected
')(output stops after these lines)

Do you agree, that /dev/sdb1 should be ok but there is another issue with my root fs on HDD?
Taker
 
Posts: 14
Joined: Mon May 30, 2011 9:46 am
Top
PreviousNext
Topic locked

Return to Community Supported

Who is online

Users browsing this forum: Google [Bot] and 74 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group    © Arch Linux ARM