IB-4220-B: Upgrade to OpenWRT: Where to start?

Anfänger

Montag, 22. Januar 2024, 11:40

Hi everybody!
Greez from a total noob.
I just stumbled into my old IB-4220-B this weekend and I was wondering whether I can get new life into that device. Luckily I found this wonderful forum and recognized, that it seems to be possible to upgrade the box with some OpenWRT image to get a decent OS on it.
Unfortunately, I can't really get a hold on the steps to perform and I didn't really understand whether a recent OpenWRT-version would run or whether it's necessary to use some older version (which would of course still be a giant leap forward wrt. the last official Raidsonic firmware).

Which version of OpenWRT works on the IB4220-B?

Can I use the web-based firmware update?
What Image do I have to use?
==> Any help is very much appreciated. (Also in German, if that's more convenient for You great people out there.)
Cheers,Felix

Current situation:

I have the IB and it still works:

I can log in using the Web-Interface (yes I recognized my password)
[img]https://nas-forum.org/index.php?page=Attachment&attachmentID=325&h=7fd5ccdcb6af20ccc9d54535da27ce6126858235[/img]
I can access it using Samba v1
i can login to SSH using some old obscure key-exchange algos
The spindown of the disks works by means of a USB stick on the rear side. (However, I have no idea what I did to achive that 15 years ago)

In the web-interface all the entries for user managment are gone. I can only manage the users by means of SSH.
I cannot unraid my disks. They are currently coupled in RAID1 (mirrored).
I don't manage to get access to the telnet console on startup. Neither by trying to establish a manual telnet connection nor by means of the FlashTool from the database.

What I'd like to get:

Install some modern OS like OpenWRT
unraid my disks and either use JBOD or just two independent disks
understand how to do this.
Just use the Box again

»opt12« hat folgende Datei angehängt:

2024-01-22 11_36_11-Clipboard.jpg (63,62 kB - 11 mal heruntergeladen - zuletzt: 1. Februar 2026, 20:36)

Zum Seitenanfang

SmartSmurf

Anfänger

Beiträge: 3

2

Dienstag, 13. Februar 2024, 10:43

Hi opt12,
I run the latest kernel 6.1 on my NAS4220. Since I did not want to mess around with the original Redboot flash layout I decided to implement some patches. You find them in the repo below.

Would be great if you want to give it a try.

1.) clone the repo

	Quellcode
1 2	git clone https://github.com/Smartsmurf/openwrt-ib4220.git cd openwrt-ib4220

2.) update feeds

	Quellcode
1 2	./scripts/feeds update -a ./scripts/feeds install -a

3.) copy config-default to .config

	Quellcode
1	cp config-default to .config

4.) make menuconfig
-> select packages

5.) make

finally you find the update under

./bin/targets/gemini/generic

and you find all the nice packages under
./bin/packages/arm_fa526

To install the packages I recommend to insert USB flash drive (4 GB are more than sufficient) and configure this as overlay. All installations will be put on the drive since flash memory is spare. Then configure the software sources to point to the arm_fa526 (or copy it locally on the HDD somewhere).The main benefit is that my fork is flash layout compatible with the original Raidsonic firmware. So when you want to revert you can just install the original FW.

Good luck SM
PS: the default root password is "welcome" (without quotes), but you can put any hash you want into the template "target/linux/gemini/base-files/etc/passwd"

Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von »SmartSmurf« (13. Februar 2024, 11:02)

Zum Seitenanfang

oliv75

Anfänger

Beiträge: 4

3

Montag, 15. Dezember 2025, 21:15

Zitat von »SmartSmurf«
Hi opt12,
I run the latest kernel 6.1 on my NAS4220. Since I did not want to mess around with the original Redboot flash layout I decided to implement some patches. You find them in the repo below.

Would be great if you want to give it a try.

1.) clone the repo
Quellcode
1
2
git clone https://github.com/Smartsmurf/openwrt-ib4220.git
cd openwrt-ib4220
2.) update feeds
Quellcode
1
2
./scripts/feeds update -a
./scripts/feeds install -a
3.) copy config-default to .config
Quellcode
1
cp config-default to .config
4.) make menuconfig
-> select packages

5.) make

finally you find the update under

./bin/targets/gemini/generic

and you find all the nice packages under
./bin/packages/arm_fa526

To install the packages I recommend to insert USB flash drive (4 GB are more than sufficient) and configure this as overlay. All installations will be put on the drive since flash memory is spare. Then configure the software sources to point to the arm_fa526 (or copy it locally on the HDD somewhere).The main benefit is that my fork is flash layout compatible with the original Raidsonic firmware. So when you want to revert you can just install the original FW.

Good luck SM
PS: the default root password is "welcome" (without quotes), but you can put any hash you want into the template "target/linux/gemini/base-files/etc/passwd"

Hello.
I have been runing the smartsmurf release for a long time. The ethernet driver is not optimal, sometimes, I seem to see glitches in the network whenver i read/send data to/from the nas.
Still, the nas itself is enough even for day to day stuff and I would like to keep it running like this as it is mostly ok for normal home related activities.
I tried to build the openwrt release but I get an error on the the ethernet patch:

Any idea regarding how to fix that?:
(meanwhile, i wanted to add a usb wifi card driver in the process, but the outcome is identical even if i dont add the driver to the build)Applying /home/olivier/openwrt-ib4220/target/linux/gemini/patches-6.6/970-net-ethernet-cortina.patch using plaintext:
patching file drivers/net/ethernet/cortina/gemini.c
Hunk #1 succeeded at 82 with fuzz 2 (offset -1 lines).
Hunk #2 succeeded at 149 (offset -1 lines).
Hunk #3 succeeded at 209 (offset -1 lines).
Hunk #4 succeeded at 610 (offset -3 lines).
Hunk #5 succeeded at 713 (offset -3 lines).
Hunk #6 succeeded at 740 (offset -3 lines).
Hunk #7 succeeded at 765 (offset -3 lines).
Hunk #8 succeeded at 778 (offset -3 lines).
Hunk #9 succeeded at 801 (offset -3 lines).
Hunk #10 succeeded at 833 (offset -3 lines).
Hunk #11 succeeded at 847 (offset -3 lines).
Hunk #12 succeeded at 881 (offset -3 lines).
Hunk #13 succeeded at 915 (offset -3 lines).
Hunk #14 succeeded at 923 (offset -3 lines).
Hunk #15 succeeded at 938 (offset -3 lines).
Hunk #16 succeeded at 963 (offset -3 lines).
Hunk #17 succeeded at 972 (offset -3 lines).
Hunk #18 succeeded at 1200 (offset 45 lines).
Hunk #19 succeeded at 1407 (offset 45 lines).
Hunk #20 succeeded at 1441 (offset 49 lines).
Hunk #21 succeeded at 1510 (offset 49 lines).
Hunk #22 succeeded at 1777 (offset 48 lines).
Hunk #23 FAILED at 2037.
Hunk #24 succeeded at 2528 (offset 60 lines).
Hunk #25 succeeded at 2595 (offset 52 lines).
1 out of 25 hunks FAILED -- saving rejects to file drivers/net/ethernet/cortina/gemini.c.rej
Patch failed! Please fix /home/olivier/openwrt-ib4220/target/linux/gemini/patches-6.6/970-net-ethernet-cortina.patch!
make[4]: *** [Makefile:40: /home/olivier/openwrt-ib4220/build_dir/target-arm_fa526_musl_eabi/linux-gemini_generic/linux-6.6.58/.prepared_bc6c7b9cfb5f3af425403e45de205b97] Error 1
make[4]: Leaving directory '/home/olivier/openwrt-ib4220/target/linux/gemini'
make[3]: *** [Makefile:11: compile] Error 2
make[3]: Leaving directory '/home/olivier/openwrt-ib4220/target/linux'
time: target/linux/compile#10.15#6.23#12.29
ERROR: target/linux failed to build.
make[2]: *** [target/Makefile:32: target/linux/compile] Error 1
make[2]: Leaving directory '/home/olivier/openwrt-ib4220'
make[1]: *** [target/Makefile:25: /home/olivier/openwrt-ib4220/staging_dir/target-arm_fa526_musl_eabi/stamp/.target_compile] Error 2
make[1]: Leaving directory '/home/olivier/openwrt-ib4220'
make: *** [/home/olivier/openwrt-ib4220/include/toplevel.mk:248: world] Error 2

olivier@debnascompil:~/openwrt-ib4220$
$ cat ./build_dir/target-arm_fa526_musl_eabi/linux-gemini_generic/linux-6.6.58/drivers/net/ethernet/cortina/gemini.c.rej
--- drivers/net/ethernet/cortina/gemini.c 2019-03-15 14:28:50.689390331 +0100
+++ drivers/net/ethernet/cortina/gemini.c 2019-03-15 15:31:34.009462305 +0100
@@ -2037,7 +2012,8 @@
}
*values++ = port->tx_frags_linearized;
*values++ = port->tx_hw_csummed;
-
+ *values++ = port->geth->freeq_replaced;
+ *values++ = port->geth->freeq_lost;
} while (u64_stats_fetch_retry_irq(&port->tx_stats_syncp, start));
}

olivier@debnascompil:~/openwrt-ib4220$
thanks !!!

Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »oliv75« (15. Dezember 2025, 23:14)

Zum Seitenanfang

linusw

Anfänger

Beiträge: 6

Wohnort: Sweden

4

Samstag, 24. Januar 2026, 14:13

Hi, I'm the OpenWrt maintainer for the Gemini systems, including the IB-4220-B.
I got this device sent to me in 2019 and only now did I start to try to fix it up to run the latest OpenWrt.
I wil try to get it going and also write some installation and upgrading instructions. Right now I'm booting the kernel over TFTP.
The flash is differently partitioned on the 4220 compared to sibling devices, which is why the mainline OpenWrt has not been working so far.
Stay tuned!

Zum Seitenanfang

oliv75

Anfänger

Beiträge: 4

5

Dienstag, 27. Januar 2026, 09:20

WOW, this is rgeat news. Really looking forward to having a somewhat updated and well working release for the nas4220!.

Zum Seitenanfang

linusw

Anfänger

Beiträge: 6

Wohnort: Sweden

6

Sonntag, 1. Februar 2026, 13:53

I have gotten ahead with this and OpenWrt is now booting nicely on this device, and you can test it, it is already better than previous OpenWrt versions for the IB-4220-B I think:
https://dflund.se/~triad/krad/raidsonic/
What works:

Flashing from UART
It boots correctly despite the kernel is now bigger than 3072KB
Mounts root from squashfs and writeable rootfs from JFFS2 overlay (current OpenWrt standard)
Maybe installing the factory image from the original software or with different TFTP-on-boot tricks? I don't know how people actually do this... I haven't tried
Sysupgrade works using standard OpenWrt sysupgrade procedures after the first install so after this no UART or tricks are needed, and this should be safe for future versions of OpenWrt as well

What remains:

Upstreaming all the patches to OpenWrt and some minor ones to Linux
Create a bogus (OpenWrt-only) driver for the fan control: what is happening is that the IB-4220-B is using an SSP (synchronous serial port) to generate a PWM signal and that is kind of an abuse of that hardware, but it works. This needs to have temperature zones defined as well.
Bump to kernel v6.18 (all of Gemini)
Wait for the next OpenWrt release to get proper support so you can install packages (with apt now!) and have some long term support

If you have UART mounted in your IB-4220-B this is a good time to give it a try!

Zum Seitenanfang

linusw

Anfänger

Beiträge: 6

Wohnort: Sweden

7

Montag, 16. Februar 2026, 01:14

I've updated the snapshot files on the page, working IB-4220-B support will also be in the OpenWrt 25.12 release.

Zum Seitenanfang

oliv75

Anfänger

Beiträge: 4

8

Montag, 23. Februar 2026, 07:38

Zitat von »linusw«

I've updated the snapshot files on the page, working IB-4220-B support will also be in the OpenWrt 25.12 release.

Hello.
I have been testing this for a few days now.
Install using tftp with serial console.
It boots fine, ethernet and overlayfs work, which is good.
However, I notice something about sata. There seems to be something wrong. I tried to isolate the issue by trying one drive at a time as I have 2 in the 4220 and both lead to this error:

Quellcode

[ 71.542872] ata1: lost interrupt (Status 0x51)
[ 71.569660] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 71.612030] ata1.00: failed command: READ DMA EXT
[ 71.640294] ata1.00: cmd 25/00:08:20:6a:70/00:00:74:00:00/e0 tag 0 dma 4096 n
[ 71.640294] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 71.727989] ata1.00: status: { DRDY }
[ 71.750091] ata1: soft resetting link
[ 72.103834] ata1.00: revalidation failed (errno=-2)
[ 77.127132] ata1: soft resetting link
[ 77.314027] ata1.00: configured for UDMA/133
[ 77.339876] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 drs
[ 77.397869] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current]
[ 77.432920] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
[ 77.463328] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 74 70 6a 20 00 000
[ 77.508791] I/O error, dev sda, sector 1953524256 op 0x0:(READ) flags 0x80702
[ 77.564230] ata1: EH complete
[ 108.007315] ata1: lost interrupt (Status 0x51)
[ 108.034096] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 108.076474] ata1.00: failed command: READ DMA
[ 108.102670] ata1.00: cmd c8/00:08:00:10:00/00:00:00:00:00/e0 tag 0 dma 4096 n
[ 108.102670] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 108.190370] ata1.00: status: { DRDY }
[ 108.212450] ata1: soft resetting link
[ 108.394112] ata1.00: configured for UDMA/133
[ 108.419957] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 drs
[ 108.477956] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current]
[ 108.513010] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
[ 108.543421] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 10 00 00 000
[ 108.588926] I/O error, dev sda, sector 4096 op 0x0:(READ) flags 0x80700 phys2
[ 108.641245] ata1: EH complete
[ 139.367298] ata1: lost interrupt (Status 0x51)
[ 139.394125] ata1.00: limiting speed to UDMA/100:PIO4
[ 139.423970] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 139.466336] ata1.00: failed command: READ DMA
[ 139.492509] ata1.00: cmd c8/00:08:18:00:00/00:00:00:00:00/e0 tag 0 dma 4096 n
[ 139.492509] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 139.580193] ata1.00: status: { DRDY }
[ 139.602274] ata1: soft resetting link
[ 139.784128] ata1.00: configured for UDMA/100
[ 139.810023] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 drs
[ 139.868046] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current]
[ 139.903103] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
[ 139.933512] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 00 18 00 000
[ 139.978976] I/O error, dev sda, sector 24 op 0x0:(READ) flags 0x80700 phys_s2
[ 140.030295] ata1: EH complete
[ 170.087315] ata1: lost interrupt (Status 0x51)
[ 170.114124] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 170.156528] ata1.00: failed command: READ DMA
[ 170.182726] ata1.00: cmd c8/00:f8:08:01:00/00:00:00:00:00/e0 tag 0 dma 12697n
[ 170.182726] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 170.271435] ata1.00: status: { DRDY }
[ 170.293534] ata1: soft resetting link
[ 170.474136] ata1.00: configured for UDMA/100
[ 170.500085] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 drs
[ 170.558085] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current]
[ 170.593161] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
[ 170.623584] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 01 08 00 000
[ 170.669016] I/O error, dev sda, sector 264 op 0x0:(READ) flags 0x80700 phys_2
[ 170.721377] ata1: EH complete
[ 200.807315] ata1: lost interrupt (Status 0x51)
[ 200.834120] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 200.876487] ata1.00: failed command: READ DMA
[ 200.902720] ata1.00: cmd c8/00:08:90:01:00/00:00:00:00:00/e0 tag 0 dma 4096 n
[ 200.902720] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 200.990436] ata1.00: status: { DRDY }
[ 201.012536] ata1: soft resetting link
[ 201.194150] ata1.00: configured for UDMA/100
[ 201.219988] ata1: EH complete
[ 231.527302] ata1: lost interrupt (Status 0x51)
[ 231.554096] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 231.596472] ata1.00: failed command: READ DMA
[ 231.622678] ata1.00: cmd c8/00:e0:20:02:00/00:00:00:00:00/e0 tag 0 dma 11468n
[ 231.622678] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 231.711412] ata1.00: status: { DRDY }
[ 231.733508] ata1: soft resetting link
[ 231.914139] ata1.00: configured for UDMA/100
[ 231.940064] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 drs
[ 231.998076] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current]
[ 232.033152] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
[ 232.063555] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 02 20 00 000
[ 232.109017] I/O error, dev sda, sector 544 op 0x0:(READ) flags 0x80700 phys_2
[ 232.161369] ata1: EH complete
[ 262.247323] ata1: lost interrupt (Status 0x51)
[ 262.274115] ata1.00: limiting speed to UDMA/33:PIO4
[ 262.303451] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 262.345786] ata1.00: failed command: READ DMA
[ 262.372013] ata1.00: cmd c8/00:08:78:02:00/00:00:00:00:00/e0 tag 0 dma 4096 n
[ 262.372013] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 262.459722] ata1.00: status: { DRDY }
[ 262.481820] ata1: soft resetting link
[ 262.659968] ata1.00: revalidation failed (errno=-2)
[ 267.687135] ata1: soft resetting link
[ 267.874144] ata1.00: configured for UDMA/33
[ 267.899467] ata1: EH complete
[ 298.087311] ata1: lost interrupt (Status 0x51)
[ 298.114114] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 298.156497] ata1.00: failed command: READ DMA
[ 298.182675] ata1.00: cmd c8/00:08:a0:02:00/00:00:00:00:00/e0 tag 0 dma 4096 n
[ 298.182675] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 298.270369] ata1.00: status: { DRDY }
[ 298.292452] ata1: soft resetting link
[ 298.474149] ata1.00: configured for UDMA/33
[ 298.499464] ata1: EH complete
[ 328.807315] ata1: lost interrupt (Status 0x51)
[ 328.834096] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 328.876476] ata1.00: failed command: READ DMA
[ 328.902651] ata1.00: cmd c8/00:08:c8:02:00/00:00:00:00:00/e0 tag 0 dma 4096 n
[ 328.902651] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 328.990387] ata1.00: status: { DRDY }
[ 329.012474] ata1: soft resetting link
[ 329.194859] ata1.00: configured for UDMA/33
[ 329.220187] ata1: EH complete
[ 359.527312] ata1: lost interrupt (Status 0x51)
[ 359.554116] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 359.596511] ata1.00: failed command: READ DMA EXT
[ 359.624799] ata1.00: cmd 25/00:e0:20:68:70/00:00:74:00:00/e0 tag 0 dma 11468n
[ 359.624799] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 359.713547] ata1.00: status: { DRDY }
[ 359.735647] ata1: soft resetting link
[ 359.924136] ata1.00: configured for UDMA/33
[ 359.949551] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 drs
[ 360.007549] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current]
[ 360.042635] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
[ 360.073049] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 74 70 68 20 00 000
[ 360.118503] I/O error, dev sda, sector 1953523744 op 0x0:(READ) flags 0x80702
[ 360.174518] ata1: EH complete
[ 390.247347] ata1: lost interrupt (Status 0x51)
[ 390.274132] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 390.316493] ata1.00: failed command: READ DMA EXT
[ 390.344769] ata1.00: cmd 25/00:08:48:68:70/00:00:74:00:00/e0 tag 0 dma 4096 n
[ 390.344769] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 390.432493] ata1.00: status: { DRDY }
[ 390.454593] ata1: soft resetting link
[ 390.634117] ata1.00: configured for UDMA/33
[ 390.659432] ata1: EH complete
[ 420.967315] ata1: lost interrupt (Status 0x51)
[ 420.994101] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 421.036489] ata1.00: failed command: READ DMA
[ 421.062699] ata1.00: cmd c8/00:40:5f:00:00/00:00:00:00:00/e0 tag 0 dma 32768n
[ 421.062699] res 40/00:0c:00:00:00/00:00:00:00:00/00 Emask 0x4 (time)
[ 421.150916] ata1.00: status: { DRDY }
[ 421.173009] ata1: soft resetting link
[ 421.354126] ata1.00: configured for UDMA/33
[ 421.379461] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 drs
[ 421.437456] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current]
[ 421.472531] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
[ 421.502932] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 00 5f 00 000
[ 421.548426] I/O error, dev sda, sector 95 op 0x0:(READ) flags 0x80700 phys_s2
[ 421.599715] ata1: EH complete

yet, the drives still mount and I can access the files.
It could also be both my drive have issues, which is a possibility. I need to double check the drives, they are 2.5i, so not the best in terms of reliability.

Zum Seitenanfang

HWguru

NAS2000-Team

Beiträge: 1 040

Wohnort: Wien

9

Mittwoch, 25. Februar 2026, 10:25

Hi,
I don't exactly remember - it was long time ago while the nas-portal was online.
People there reported problems with some combination of SATA disks and the 4220, especially Seagate disks I believe.
It could be some kind of hardware issue or incompatibility.

HWguru

P.S. If you use the "CODE" feature there will be no formatting and no smileys appear in the log

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!

Zum Seitenanfang

AQUAR

Schüler

Beiträge: 117

Wohnort: Australia

10

Mittwoch, 25. Februar 2026, 13:33

My old QNAP NAS is very picky as to HDD compatibility.
4Kn HDD don't work at all and 512e HDD is hit and miss.

Old second hand HDDs work great though (typically non shingled).
Maybe the case for IB-4220 NAS boxes?

Zum Seitenanfang

linusw

Anfänger

Beiträge: 6

Wohnort: Sweden

11

Montag, 2. März 2026, 23:50

I did pick up and send this patch from this forum:
https://marc.info/?l=linux-ide&m=177011713121213&w=2
However it is not included in the images I made.
This patch has been applied for the next relase of the the stable v6.12 kernel, so I will wait for that to land in OpenWrt and regenerate the images based on v6.12.75.
Does this work or are you in great hurry?

Zum Seitenanfang

NAS Forum