VU+ Solo2 Kernel Panic

pip268

Vu+ Newbie
I've been searching the threads and reading up on problems with my box stuck on "Starting".
Image is BH (can't remember which version).
It was working fine until I accidently pulled the power plug out.
Now when I start it I get the BackHole logo on the TV screen and the box display just says "starting".
Having read up on how to connect a serial port I got the boot log.
The part where the error starts is :-


NAND device: Manufacturer ID: 0xad, Chip ID: 0xda (Hynix H27U2G8F2CTR-BC)


NAND device: 256MiB, SLC, page size: 2048, OOB size: 64


NAND device: Manufacturer ID: 0xad, Chip ID: 0xda (Hynix H27U2G8F2CTR-BC)


NAND device: 256MiB, SLC, page size: 2048, OOB size: 64


brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC


Bad block table found at page 131008, version 0x01


Bad block table found at page 130944, version 0x01


nand_read_bbt: bad block at 0x000004620000


nand_read_bbt: bad block at 0x000009640000


Creating 4 MTD partitions on "brcmnand.0":


0x000001f00000-0x000010000000 : "rootfs"


0x000001f00000-0x000010000000 : "rootfs(redundant)"


0x000000200000-0x000000900000 : "kernel"


0x000000900000-0x000000a00000 : "mac"


UBI: attaching mtd0 to ubi0


UBI error: check_corruption: PEB 25 contains corrupted VID header, and the data does not contain all 0xFF


UBI error: check_corruption: this may be a non-UBI PEB or a severe VID header corruption which requires manual inspection


Volume identifier header dump:


magic 55c241a1


version 1


vol_type 1


copy_flag 64


compat 32


vol_id 256


lnum 7


data_size 64


used_ebs 268435456


data_pad 16


sqnum 2305984021579956224


hdr_crc 947ddd7f


Volume identifier header hexdump:


hexdump of PEB 25 offset 4096, length 126976


UBI error: scan_peb: bad image sequence number 153896872 in PEB 92, expected 1030351679


Erase counter header dump:


magic 0x55424923


version 1


ec 3


vid_hdr_offset 2048


data_offset 4096


image_seq 153896872


hdr_crc 0xce46496d


erase counter header hexdump:


UBI error: ubi_attach_mtd_dev: failed to attach mtd0, error -22


UBI error: ubi_init: cannot attach mtd0


ALSA device list:


No soundcards found.


UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19


VFS: Cannot open root device "ubi0:rootfs" or unknown-block(8,1): error -19


Please append a correct "root=" boot option; here are the available partitions:


1f00 230400 mtdblock0 (driver?)


1f01 230400 mtdblock1 (driver?)


1f02 7168 mtdblock2 (driver?)


1f03 1024 mtdblock3 (driver?)


Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)


Rebooting in 180 seconds..random: nonblocking pool is initialized

It then proceeds to reboot after 180 seconds to give the same error.
Anybody know if it is bricked or can it be salvaged?
 

yura21

Vu+ User
@pip268
Just read your message and can find the answer...

brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x000004620000
nand_read_bbt: bad block at 0x000009640000
 
Top