[FS#4137] OpenWRT 21.02.1 doesn't completely boot on RaidSonic IB-NAS4220-B

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Sun Nov 21 05:17:01 PST 2021


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#4137 - OpenWRT 21.02.1 doesn't completely boot on RaidSonic IB-NAS4220-B
User who did this - Christian Lamparter (chunkeey)

----------

   [    4.782402] physmap-flash 30000000.flash: no enabled pin control state
   [    4.825925] physmap-flash 30000000.flash: no disabled pin control state
   [    4.950469] physmap-flash 30000000.flash: initialized Gemini-specific physmap control
   [    5.022102] physmap-flash 30000000.flash: physmap platform flash device: [mem 0x30000000-0x30ffffff]
   [    5.121754] 30000000.flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x002101
   [    5.249280] Amd/Fujitsu Extended Query Table at 0x0040
   [    5.320148]   Amd/Fujitsu Extended Query version 1.3.
   [    5.351156] number of CFI chips: 1
   [    5.427677] Searching for RedBoot partition table in 30000000.flash at offset 0x0
   [    5.548038] No RedBoot partition table detected in 30000000.flash
   [    5.618553] Searching for RedBoot partition table in 30000000.flash at offset 0x0
   [    5.739093] No RedBoot partition table detected in 30000000.flash

Something is wrong here, the partition parser on your NAS4220-B doesn't seem to be able to find the RedBoot Partition table. What's odd is that according to the Device's dts, it should be located at offset "0xfe0000" and not "0x0".

The reason why OpenWrt 19.07 worked was that it had a static partition table
[[https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/gemini/patches-4.14/0900-arm-dts-gemini-add-openwrt-partitions-for-nas4220b.patch;h=0fae0af0e12f7845ab54228800b89a7e480554b2;hb=refs/heads/openwrt-19.07|0900-arm-dts-gemini-add-openwrt-partitions-for-nas4220b.patch]]

whereas now, the information should be coming from the RedBoot partition table:
[[https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts/gemini-nas4220b.dts?h=linux-5.10.y#n86|gemini-nas4220b.dts]]

(Maybe your flash has 64KiB/128KiB erase blocks? Maybe the table is located elsewhere? etc.)

To generate a flashdump (which would help locating the table, you could boot up 19.07 and run gzip -c /dev/mtd*ro > /tmp/flashdump.gz. This will produce a packed flashdump that can be copied over to a PC and inspected from there.

To check the flash erase size:
cat /sys/class/mtd/mtd0/erasesize (there might be more other "useful" information in that /sys/class/mtd/mtd0/)

Cheers,
Christian

(Let's hope this isn't eaten.)
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4137#comment10315

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the openwrt-bugs mailing list