[Help] F5-221 won't boot after online update 6.0.794 -> 7.0.0747, hangs even with no disks (not found by TNAS PC)
Posted: 29 Oct 2026, 12:07
Hello,
My F5-221 stopped booting after the online update from TOS 6.0.794 to TOS 7.0.0747. It hangs on every boot, even with all disks removed, and TNAS PC cannot find it. I emailed [email protected] on 28 Oct but have not received a reply yet.
Device
- F5-221, BIOS MAPL0304V22 (within the supported range for TOS 7)
- TOS 6.0.794-01324 before the update
- 4 x Seagate IronWolf 8 TB (bays 1-4), RAID 5, Btrfs, about 17 TB of data
- RAM: upgraded, about 10 GB in total. It worked without problems on TOS 6 for about a year
- BIOS boot order never changed. No USB devices were connected during the update
- Before the update: full Btrfs scrub with 0 errors, all disks SMART PASSED, RAID healthy
What happened (28 Oct 2026)
1. Control Panel > System offered TOS 7.0.0747 (TOS_X642.0_Update_7.0.0747_1247_2607310709.bz2). TOS downloaded it, and I clicked Update.
2. The NAS rebooted (one beep), and a few minutes later beeped a second time.
3. Its MAC address appeared on the LAN at the usual reserved IP for about a minute, but it did not answer ping, and no ports were open (80, 443, 5443, 8181, 9222). Then it disappeared from the network completely.
4. Front panel: power LED on, LAN LED blinking, HDD LEDs solid green with no activity at all, no disk sound.
5. A short press of the power button did nothing (the system was frozen). I held the button to turn it off.
6. Second boot: one beep only, no second beep, same LEDs, not on the network for 8+ hours.
7. Next morning: booted with ALL DISKS REMOVED. One beep, power on, LAN blinking, nothing else. TNAS PC does not find it, and no new device appears on the network (scanned the whole subnet for 25 minutes).
Since it hangs the same way with and without disks, I suspect the internal init-boot USB / bootloader was not written correctly during the update.
Questions
1. Is there an init-boot (USB) image and a procedure for the F5-221 to recover from this? Is it safe for the existing RAID 5 / Btrfs volume?
2. Once the device reaches the installation page, how do I reinstall TOS 7 while keeping the existing storage pool and volume?
3. Could the extra RAM matter with the TOS 7 kernel even though it worked with TOS 6? (I can test with the original configuration if needed.)
I have not done anything else to the disks and will wait for advice before any step that could affect the data.
Thank you.
My F5-221 stopped booting after the online update from TOS 6.0.794 to TOS 7.0.0747. It hangs on every boot, even with all disks removed, and TNAS PC cannot find it. I emailed [email protected] on 28 Oct but have not received a reply yet.
Device
- F5-221, BIOS MAPL0304V22 (within the supported range for TOS 7)
- TOS 6.0.794-01324 before the update
- 4 x Seagate IronWolf 8 TB (bays 1-4), RAID 5, Btrfs, about 17 TB of data
- RAM: upgraded, about 10 GB in total. It worked without problems on TOS 6 for about a year
- BIOS boot order never changed. No USB devices were connected during the update
- Before the update: full Btrfs scrub with 0 errors, all disks SMART PASSED, RAID healthy
What happened (28 Oct 2026)
1. Control Panel > System offered TOS 7.0.0747 (TOS_X642.0_Update_7.0.0747_1247_2607310709.bz2). TOS downloaded it, and I clicked Update.
2. The NAS rebooted (one beep), and a few minutes later beeped a second time.
3. Its MAC address appeared on the LAN at the usual reserved IP for about a minute, but it did not answer ping, and no ports were open (80, 443, 5443, 8181, 9222). Then it disappeared from the network completely.
4. Front panel: power LED on, LAN LED blinking, HDD LEDs solid green with no activity at all, no disk sound.
5. A short press of the power button did nothing (the system was frozen). I held the button to turn it off.
6. Second boot: one beep only, no second beep, same LEDs, not on the network for 8+ hours.
7. Next morning: booted with ALL DISKS REMOVED. One beep, power on, LAN blinking, nothing else. TNAS PC does not find it, and no new device appears on the network (scanned the whole subnet for 25 minutes).
Since it hangs the same way with and without disks, I suspect the internal init-boot USB / bootloader was not written correctly during the update.
Questions
1. Is there an init-boot (USB) image and a procedure for the F5-221 to recover from this? Is it safe for the existing RAID 5 / Btrfs volume?
2. Once the device reaches the installation page, how do I reinstall TOS 7 while keeping the existing storage pool and volume?
3. Could the extra RAM matter with the TOS 7 kernel even though it worked with TOS 6? (I can test with the original configuration if needed.)
I have not done anything else to the disks and will wait for advice before any step that could affect the data.
Thank you.