HELP! NETGEAR R6300 V1 kernel panic and reboots

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
rejuas
DD-WRT Novice


Joined: 29 Nov 2018
Posts: 3

PostPosted: Fri Nov 30, 2018 1:50    Post subject: HELP! NETGEAR R6300 V1 kernel panic and reboots Reply with quote
My router Netgear R6300 V1 have has installed V1.0.2.80_1.0.59 like used in the wiki https://wiki.dd-wrt.com/wiki/index.php/Netgear_R6300

Original OEM FW: Boots well

Tomato shibby: boot OK, I dont like it

DD-WRT :boots , but reboots by kernel panic, here are the logs taked by serial port

I dont know why reboots if is compatible model ?

tested builts: r33555, r33772, r35927, r37837, r37860 , same issue. all of them installed from OEM firmware in .chk

saludos !!



original.log.txt
 Description:
bootlog by serial port

Download
 Filename:  original.log.txt
 Filesize:  8.98 KB
 Downloaded:  186 Time(s)


DDWRT.log.txt
 Description:
bootlog by serial port

Download
 Filename:  DDWRT.log.txt
 Filesize:  7.48 KB
 Downloaded:  210 Time(s)


Tomato.log.txt
 Description:
bootlog by serial port

Download
 Filename:  Tomato.log.txt
 Filesize:  5.78 KB
 Downloaded:  205 Time(s)



Last edited by rejuas on Tue Dec 04, 2018 21:18; edited 1 time in total
Sponsor
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2616
Location: Indy

PostPosted: Fri Nov 30, 2018 15:52    Post subject: Reply with quote
I would guess it's due to this, right from your boot log:
    Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
    Bad block table found at page 65472, version 0x01
    Bad block table found at page 65408, version 0x01
    nand_read_bbt: bad block at 0x000000080000
    nand_read_bbt: bad block at 0x000002200000
    nand_read_bbt: bad block at 0x0000033e0000
    Creating 2 MTD partitions on "brcmnand":
    0x000000000000-0x000002000000 : "linux"
    0x000002000000-0x000007f00000 : "ddwrt"
    lookup_nflash_rootfs_offset: offset = 0x0
    found trx at 0, len =27607040
    scan filesys at 161000
    Creating 2 MTD partitions on "nflash":
    0x000000000000-0x000002000000 : "nandimage"
    0x000002000000-0x000008000000 : "rootfs"
    mtd: partition "rootfs" set to be root filesystem
    [...]
    No filesystem could mount root, tried: squashfs
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
    Creating 3 MTD partitions on "brcmnand":
    0x00000000-0x02000000 : "trx"
    0x02000000-0x04000000 : "jffs2"
    0x04000000-0x07f00000 : "brcmnand"

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 20.7.6|FT2020.6: EA6900v1.1@1GHz, F7D8302@532|DD 45036: DIR-810L, WNDR4500v2 & 4000@533,
R6300v1, RT-N66U@663, E1500@353, WRT54G{Lv1.1,Sv6}@250
|OpenWRT 19.7.5: RT-ACRH13, R6220, WNDR3700v4
rejuas
DD-WRT Novice


Joined: 29 Nov 2018
Posts: 3

PostPosted: Sun Dec 02, 2018 0:54    Post subject: Reply with quote
jwh7 wrote:
I would guess it's due to this, right from your boot log:
    Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
    Bad block table found at page 65472, version 0x01
    Bad block table found at page 65408, version 0x01
    nand_read_bbt: bad block at 0x000000080000
    nand_read_bbt: bad block at 0x000002200000
    nand_read_bbt: bad block at 0x0000033e0000
    Creating 2 MTD partitions on "brcmnand":
    0x000000000000-0x000002000000 : "linux"
    0x000002000000-0x000007f00000 : "ddwrt"
    lookup_nflash_rootfs_offset: offset = 0x0
    found trx at 0, len =27607040
    scan filesys at 161000
    Creating 2 MTD partitions on "nflash":
    0x000000000000-0x000002000000 : "nandimage"
    0x000002000000-0x000008000000 : "rootfs"
    mtd: partition "rootfs" set to be root filesystem
    [...]
    No filesystem could mount root, tried: squashfs
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
    Creating 3 MTD partitions on "brcmnand":
    0x00000000-0x02000000 : "trx"
    0x02000000-0x04000000 : "jffs2"
    0x04000000-0x07f00000 : "brcmnand"


there is a way to force to flash ddwrt ?
deslatha
DD-WRT User


Joined: 12 Jul 2016
Posts: 190

PostPosted: Sun Dec 02, 2018 6:26    Post subject: Reply with quote
rejuas wrote:
jwh7 wrote:
I would guess it's due to this, right from your boot log:
    Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
    Bad block table found at page 65472, version 0x01
    Bad block table found at page 65408, version 0x01
    nand_read_bbt: bad block at 0x000000080000
    nand_read_bbt: bad block at 0x000002200000
    nand_read_bbt: bad block at 0x0000033e0000
    Creating 2 MTD partitions on "brcmnand":
    0x000000000000-0x000002000000 : "linux"
    0x000002000000-0x000007f00000 : "ddwrt"
    lookup_nflash_rootfs_offset: offset = 0x0
    found trx at 0, len =27607040
    scan filesys at 161000
    Creating 2 MTD partitions on "nflash":
    0x000000000000-0x000002000000 : "nandimage"
    0x000002000000-0x000008000000 : "rootfs"
    mtd: partition "rootfs" set to be root filesystem
    [...]
    No filesystem could mount root, tried: squashfs
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
    Creating 3 MTD partitions on "brcmnand":
    0x00000000-0x02000000 : "trx"
    0x02000000-0x04000000 : "jffs2"
    0x04000000-0x07f00000 : "brcmnand"


there is a way to force to flash ddwrt ?


you can flash through download fw to /tmp by wget command
Or copy fw to usb and flash to dd or mtd write command.

Due to your router log ...too may 3rd fw, you need erase jffs2 and brcmnand partitions, also due many btt badblocks then fw also backup in ddwrt partition or nandimage. If you able landing on cfe promt then :
flash -noheader...........to nflash1.trx.

Here my log so long time, some nvram mod,back up and compare before adjust.also i see no data_board partition leading kong fw miss detecting correct fw.

check: cat /proc/mtd // to see full partitions



r6300v1_info.rar
 Description:

Download
 Filename:  r6300v1_info.rar
 Filesize:  4.69 KB
 Downloaded:  23 Time(s)

rejuas
DD-WRT Novice


Joined: 29 Nov 2018
Posts: 3

PostPosted: Thu Dec 06, 2018 0:22    Post subject: I cant flash it Reply with quote
deslatha wrote:
rejuas wrote:
jwh7 wrote:
I would guess it's due to this, right from your boot log:
    Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
    Bad block table found at page 65472, version 0x01
    Bad block table found at page 65408, version 0x01
    nand_read_bbt: bad block at 0x000000080000
    nand_read_bbt: bad block at 0x000002200000
    nand_read_bbt: bad block at 0x0000033e0000
    Creating 2 MTD partitions on "brcmnand":
    0x000000000000-0x000002000000 : "linux"
    0x000002000000-0x000007f00000 : "ddwrt"
    lookup_nflash_rootfs_offset: offset = 0x0
    found trx at 0, len =27607040
    scan filesys at 161000
    Creating 2 MTD partitions on "nflash":
    0x000000000000-0x000002000000 : "nandimage"
    0x000002000000-0x000008000000 : "rootfs"
    mtd: partition "rootfs" set to be root filesystem
    [...]
    No filesystem could mount root, tried: squashfs
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
OEM and Tomato probably don't reach those bad blocks. In the Tomato log, that bad region is part of JFFS2...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
    Creating 3 MTD partitions on "brcmnand":
    0x00000000-0x02000000 : "trx"
    0x02000000-0x04000000 : "jffs2"
    0x04000000-0x07f00000 : "brcmnand"


there is a way to force to flash ddwrt ?


you can flash through download fw to /tmp by wget command
Or copy fw to usb and flash to dd or mtd write command.

Due to your router log ...too may 3rd fw, you need erase jffs2 and brcmnand partitions, also due many btt badblocks then fw also backup in ddwrt partition or nandimage. If you able landing on cfe promt then :
flash -noheader...........to nflash1.trx.

Here my log so long time, some nvram mod,back up and compare before adjust.also i see no data_board partition leading kong fw miss detecting correct fw.

check: cat /proc/mtd // to see full partitions


i cannot flash it!
how to make an smaller image?
even better, can you build a smaller image for me?
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum