vendredi 12 septembre 2025, 20:01 UTC+2
Vous n’êtes pas connecté.
Bonjour, visiteur, bienvenue sur les forums NAS Forum. Si c’est votre première visite, nous vous invitons à consulter l’Aide. Elle vous expliquera le fonctionnement de cette page. Pour avoir accès à toutes les fonctionnalités, vous devez vous inscrire. Pour cela, veuillez utiliser le formulaire d’enregistrement, ou bien lisez plus d’informations sur la procédure d’enregistrement. Si vous êtes déjà enregistré, veuillez vous connecter.
mardi 6 avril 2021, 21:52
Trying to bring openWRT master to IB-NAS4210-B
Hi,
my plan is to bring a current openWRT to IB-NAS4210-B.
At first, I installed an old firmware based on openWRT Chaos Calmer (15.05), found here: http://openwrt.dtech.hu/firmware/chaos_c…5/IB-NAS4210-B/. You can use the firmware upgrade function of the stock firmware for this. It boots and runs just fine, but it is too old. The page shows some usefull information, including serial console layout.
Next try, I installed the firmware for IB-NAS4220-B from current snapshot on my device. I used the serial console and the tftp server method for this, read this thread. The systems boots up and runs, but network is not working. So this is useless.
I did some research. The IB-NAS4210-B uses SoC SL3512, IB-NAS4220-B has SL-3516, both Gemini platform. As much as I can say, this makes the difference. Info on this. The Gemini platform is supported by the Linux kernel and openWRT. There is a target device for IB-NAS4220-B in openWRT. Another device that uses the SL3512 SoC ist D-Link DNS-313. This has openWRT support.
I think, most of the stuff needed is there. All we need is such a target device entry for IB-NAS4120-B. I found it on this file. Copy the section for IB-NAS4220-B and change the values.
That was the easy part. Next, a device tree file in the kernel needs to be created, similar to this. I would edit the dts for IB-NAS4220-B and mix it with some parts from D-Link DNS-313. I can edit all kinds of files in my local clone of openWRT git, but I have no idea where and how to create the required device tree file.
Any idea?
Live long and prosper!
Cpt. Spcok
my plan is to bring a current openWRT to IB-NAS4210-B.
At first, I installed an old firmware based on openWRT Chaos Calmer (15.05), found here: http://openwrt.dtech.hu/firmware/chaos_c…5/IB-NAS4210-B/. You can use the firmware upgrade function of the stock firmware for this. It boots and runs just fine, but it is too old. The page shows some usefull information, including serial console layout.
Next try, I installed the firmware for IB-NAS4220-B from current snapshot on my device. I used the serial console and the tftp server method for this, read this thread. The systems boots up and runs, but network is not working. So this is useless.
I did some research. The IB-NAS4210-B uses SoC SL3512, IB-NAS4220-B has SL-3516, both Gemini platform. As much as I can say, this makes the difference. Info on this. The Gemini platform is supported by the Linux kernel and openWRT. There is a target device for IB-NAS4220-B in openWRT. Another device that uses the SL3512 SoC ist D-Link DNS-313. This has openWRT support.
I think, most of the stuff needed is there. All we need is such a target device entry for IB-NAS4120-B. I found it on this file. Copy the section for IB-NAS4220-B and change the values.
|
Code source |
1 2 3 4 5 6 7 |
define Device/raidsonic_ib-4210-b $(Device/storlink-reference) DEVICE_VENDOR := Raidsonic DEVICE_MODEL := NAS IB-4210-B DEVICE_DTS := gemini-nas4210b endef TARGET_DEVICES += raidsonic_ib-4210-b |
That was the easy part. Next, a device tree file in the kernel needs to be created, similar to this. I would edit the dts for IB-NAS4220-B and mix it with some parts from D-Link DNS-313. I can edit all kinds of files in my local clone of openWRT git, but I have no idea where and how to create the required device tree file.
Any idea?
Live long and prosper!
Cpt. Spcok
Live long and prosper!
RaidSonic IB-NAS4210-B, trying to bring openWRT snapshot on this device
RaidSonic IB-NAS4210-B, trying to bring openWRT snapshot on this device
jeudi 15 avril 2021, 16:11
Partial sucess!
Hi!
Thank you for your feedback.
I had some partial success in building a firmware for IB-NAS4210-B. I managed to create a new device tree file and some other files and the compile process can use it. Details will follow as soon as I am home again.
Problem for now: after booting the new firmware, the file system is read only. The kernel does not find the JFFS2 part in the flash. As you can read here, openWRT searches for a partition "rootfs" in flash. But there is no partition with this name on IB-NAS4210-B.
This is the flash layout on my device:
openWRT uses only 3 parts of the flash:
Kern - for storing first 2 MiB of the kernel
Ramdisk - for the rest of the kernel
Application - for the root file system
source: https://github.com/openwrt/openwrt/blob/…/image/Makefile
This changed in snapshot compared to 18.06.
I'm still looking for a way to tell the lernel where to look for this JFFS2 data.
There are other things that doesn't work for now, but I think the read-only filesystem is the reason.
The attached log file shows install and boot process of my new firmware.
Live long and prosper!
Cpt. Spock
Thank you for your feedback.
I had some partial success in building a firmware for IB-NAS4210-B. I managed to create a new device tree file and some other files and the compile process can use it. Details will follow as soon as I am home again.
Problem for now: after booting the new firmware, the file system is read only. The kernel does not find the JFFS2 part in the flash. As you can read here, openWRT searches for a partition "rootfs" in flash. But there is no partition with this name on IB-NAS4210-B.
This is the flash layout on my device:
|
|
Code source |
1 2 3 4 5 6 7 8 9 |
[ 4.689742] 7 RedBoot partitions found on MTD device 30000000.flash [ 4.757069] Creating 7 MTD partitions on "30000000.flash": [ 4.845257] 0x000000000000-0x000000020000 : "BOOT" [ 4.886683] 0x000000020000-0x000000220000 : "Kern" [ 4.957432] 0x000000320000-0x0000003d92cd : "Ramdisk" [ 5.037796] 0x000000920000-0x000000f20000 : "Application" [ 5.087129] 0x000000f20000-0x000000f40000 : "VCTL" [ 5.127570] 0x000000f40000-0x000000fe0000 : "CurConf" [ 5.176821] 0x000000fe0000-0x000001000000 : "FIS directory" |
openWRT uses only 3 parts of the flash:
Kern - for storing first 2 MiB of the kernel
Ramdisk - for the rest of the kernel
Application - for the root file system
source: https://github.com/openwrt/openwrt/blob/…/image/Makefile
This changed in snapshot compared to 18.06.
I'm still looking for a way to tell the lernel where to look for this JFFS2 data.
There are other things that doesn't work for now, but I think the read-only filesystem is the reason.
The attached log file shows install and boot process of my new firmware.
Live long and prosper!
Cpt. Spock
Live long and prosper!
RaidSonic IB-NAS4210-B, trying to bring openWRT snapshot on this device
RaidSonic IB-NAS4210-B, trying to bring openWRT snapshot on this device
samedi 17 avril 2021, 14:05
Hidiho,
my first idea about the file system was, that you pointed to the wrong mtd partition and does a temporary one. but that is obviously not the problem.I ckecked now your install log and the only thing I could find is the lookup for fstab entry. Maybe you can put mount information there in your build tree. Did you ever try to remount it writable? To be honest i am not sure if it is even possible.
BTW: I am a little jealous that your ethernet works with 1Gb, mine does not for what reason ever. I am still hanging on how to flash the image, due to my FIS layout is originally like this:
One more hint when I started out I got the suggestion to load an initramfs image through the bootloader. Therefore you take the load command like: load -m tftp -b 0x80000, and then go to start from that RAM address go 0x80000. That way you can load a lot of times without wearing the flash.
my first idea about the file system was, that you pointed to the wrong mtd partition and does a temporary one. but that is obviously not the problem.I ckecked now your install log and the only thing I could find is the lookup for fstab entry. Maybe you can put mount information there in your build tree. Did you ever try to remount it writable? To be honest i am not sure if it is even possible.
BTW: I am a little jealous that your ethernet works with 1Gb, mine does not for what reason ever. I am still hanging on how to flash the image, due to my FIS layout is originally like this:
|
|
Code source |
1 2 3 4 5 6 7 |
#Default Layout Danelec myditto: #Name FLASH addr Mem addr Datalen Entry point #BOOT 0x30000000-3001FFFF 0x00000000 0x00020000 0x00000000 #FIS directory 0x307E0000-307FFFFF 0x307E0000 0x00001400 0x00000000 #Kern 0x30020000-3071FFFF 0x00800000 0x00700000 0x00800014 #CurConf 0x30740000-3075FFFF 0x00000000 0x00020000 0x00000000 #VCTL 0x30720000-3073FFFF 0x00000000 0x00020000 0x00000000 |
One more hint when I started out I got the suggestion to load an initramfs image through the bootloader. Therefore you take the load command like: load -m tftp -b 0x80000, and then go to start from that RAM address go 0x80000. That way you can load a lot of times without wearing the flash.
dimanche 2 mai 2021, 23:37
Success!! with openWRT v19.07.7 / kernel 4.14
Yes, you're right. The suqashfs ist readonly, and the jffs2 partition is created in the free space. File size was OK.
I think the NAS-4210-B and NAS-4220-B have the same flash layout, as posted before. My problem is kind of openWRT specific.
While booting the kernel, openWRT looks for a partition named 'rootfs' within it looks for the jffs2 special marker. But in the partition table of the NAS-4210-B, there is no partition with this name. The mechanism ist not working.
In previous openWRT releases, there was some kind of workaround. The flash layout was hard coded, the one or the other way. At the end, 2 more partitions were added, only to make openWRT detect the right one. This is what I expext:
Have a look at the start and end addresses of the partitions firmware and rootfs. They overlay some of the other partitions.
In openWRT v19.07.7 / kernel 4.14, there was a patch that added this to partitions to the device tree (dts) file.
There was a ticket to a similar problem, but no solution.
In openWRT master / kernel 5.4, the fixed partitions in the device tree file have been replaced by an autodetect mechnism, see this patch. This makes the two special entries missing and the magic doesn't work anymore.
I restarted my tests with openWRT v19.07.7 and created a working firmware for IB-NAS4210-B. I'll give a link as soon as I can. This nightly version is still not perfect, but it boots. Missing is hard disk access (mistake in device tree, I think) and the luci (webinterface) packages.
That's it for now. Live long and prosper!
Cpt. Spock
I think the NAS-4210-B and NAS-4220-B have the same flash layout, as posted before. My problem is kind of openWRT specific.
While booting the kernel, openWRT looks for a partition named 'rootfs' within it looks for the jffs2 special marker. But in the partition table of the NAS-4210-B, there is no partition with this name. The mechanism ist not working.
In previous openWRT releases, there was some kind of workaround. The flash layout was hard coded, the one or the other way. At the end, 2 more partitions were added, only to make openWRT detect the right one. This is what I expext:
|
|
Code source |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
[ 4.643675] of-flash 30000000.flash: initialized Gemini-specific physmap control [ 4.688220] 30000000.flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x002101 [ 4.749261] Amd/Fujitsu Extended Query Table at 0x0040 [ 4.780211] Amd/Fujitsu Extended Query version 1.3. [ 4.810546] number of CFI chips: 1 [ 4.832623] 9 fixed-partitions partitions found on MTD device 30000000.flash [ 4.875064] Creating 9 MTD partitions on "30000000.flash": [ 4.908117] 0x000000000000-0x000000020000 : "RedBoot" [ 4.943509] 0x000000020000-0x000000320000 : "Kernel" [ 4.978906] 0x000000320000-0x000000920000 : "Ramdisk" [ 5.015124] 0x000000920000-0x000000f20000 : "Application" [ 5.053883] 0x000000f20000-0x000000f40000 : "VCTL" [ 5.088507] 0x000000f40000-0x000000fe0000 : "CurConf" [ 5.124837] 0x000000fe0000-0x000001000000 : "FIS directory" [ 5.164787] 0x000000020000-0x000000f20000 : "firmware" [ 5.202466] 0x000000320000-0x000000f20000 : "rootfs" [ 5.237494] mtd: device 8 (rootfs) set to be root filesystem [ 5.272959] 1 squashfs-split partitions found on MTD device rootfs [ 5.310424] 0x000000740000-0x000000f20000 : "rootfs_data" |
Have a look at the start and end addresses of the partitions firmware and rootfs. They overlay some of the other partitions.
In openWRT v19.07.7 / kernel 4.14, there was a patch that added this to partitions to the device tree (dts) file.
There was a ticket to a similar problem, but no solution.
In openWRT master / kernel 5.4, the fixed partitions in the device tree file have been replaced by an autodetect mechnism, see this patch. This makes the two special entries missing and the magic doesn't work anymore.
I restarted my tests with openWRT v19.07.7 and created a working firmware for IB-NAS4210-B. I'll give a link as soon as I can. This nightly version is still not perfect, but it boots. Missing is hard disk access (mistake in device tree, I think) and the luci (webinterface) packages.
That's it for now. Live long and prosper!
Cpt. Spock
Live long and prosper!
RaidSonic IB-NAS4210-B, trying to bring openWRT snapshot on this device
RaidSonic IB-NAS4210-B, trying to bring openWRT snapshot on this device
samedi 29 mai 2021, 02:09
Hey Cpt.
I tried the things with the partitions and do honestley not understand how to use the additional ones. I have the partition for the rootfs in the kernel path and that works for me.
For the number you count from zero to where your partition is. My partition layout in the *.dts file is:
Did you ever succeed with using the "FIS directory"; to read out the prtition information in the device tree?
I tried the things with the partitions and do honestley not understand how to use the additional ones. I have the partition for the rootfs in the kernel path and that works for me.
|
|
Code source |
1 2 |
bootargs = "console=ttyS0,19200n8 root=/dev/mtdblock2 rw rootfstype=squashfs,jffs2 rootwait noinitrd init=/etc/preinit"; stdout-path = &uart0; |
For the number you count from zero to where your partition is. My partition layout in the *.dts file is:
|
|
Code source |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
partition@0 {
label = "RedBoot";
reg = <0x00000000 0x00020000>;
read-only;
};
partition@20000 {
label = "Kernel";
reg = <0x00020000 0x00280000>;
};
partition@280000 {
label = "rootfs";
reg = <0x002A0000 0x00480000>;
};
partition@720000 {
label = "VCTL";
reg = <0x00720000 0x00020000>;
read-only;
};
partition@740000 {
label = "CurConf";
reg = <0x00740000 0x00020000>;
read-only;
};
partition@7E0000 {
label = "FIS directory";
reg = <0x007E000 0x00001400>;
read-only;
};
|
Did you ever succeed with using the "FIS directory"; to read out the prtition information in the device tree?
Ce message a été modifié 1 fois. Dernière modification effectuée par "hendi060" (29 mai 2021, 13:03)
dimanche 28 novembre 2021, 15:01
Leute ohne Laster haben oft wenige Tugenden...
NAS2000 2.3.2.IB.2.RS.1+Lüfterabschaltung+SSH+do_it+zusätzliche commandline tools+changed root password
1. suchen - lesen - Google - lesen - 1. Fragen gehören ins Forum, dann profitieren alle davon!
NAS2000 2.3.2.IB.2.RS.1+Lüfterabschaltung+SSH+do_it+zusätzliche commandline tools+changed root password
1. suchen - lesen - Google - lesen - 1. Fragen gehören ins Forum, dann profitieren alle davon!
Discussions similaires
-
OpenWRT port for MvixBOX and Clones »-
build an actual Open WRT for a myDitto NAS
(16 janvier 2020, 22:48)
-
- Software openWRT, misc »
-
Raidsonic Icy Box IB-NAS4210-B serial port guide and openwrt
(24 février 2021, 17:39)
-
- Hardware JTAG, RS232, misc »
-
IB-NAS 4210-B zugang über Winscp
(1 janvier 2021, 18:34)
-
- OpenWRT port for MvixBOX and Clones »
-
Firmware upgrade and crash
(27 novembre 2013, 19:44)