Search found 4 matches
- 06 Aug 2025, 11:12
- Forum: System Update
- Topic: [Help] F4-424 not accessible after update to 6.0.530
- Replies: 6
- Views: 828

Re: [Help] F4-424 not accessible after update to 6.0.530
Upgrading from version 5.1.145 to 6.0.530 typically requires two reboots. It seems that it has only rebooted once and is stuck on the initialization page. Please manually perform a second reboot, which should allow you to successfully start the newly upgraded TOS6 system. If the new TOS6 system sti...
- 06 Aug 2025, 11:09
- Forum: System Update
- Topic: [Help] F4-424 not accessible after update to 6.0.530
- Replies: 6
- Views: 828

Re: [Help] F4-424 not accessible after update to 6.0.530
Also, I have a m.2 nvme coming tomorrow, was thinking of installing the OS on that. Should I run the initialization with only that installed first and then insert the remaining disks, or have it all installed at the same time, then only select the NVME for the OS install?
- 06 Aug 2025, 11:07
- Forum: System Update
- Topic: [Help] F4-424 not accessible after update to 6.0.530
- Replies: 6
- Views: 828

Re: [Help] F4-424 not accessible after update to 6.0.530
So when I get the selection screen about it doing it automatically in 60 seconds, does that mean it will overwrite my pools/storage? Should I use the custom method? Also, why does it have up to two disks that the OS can be installed on, why would it need to be on two?
- 06 Aug 2025, 01:31
- Forum: System Update
- Topic: [Help] F4-424 not accessible after update to 6.0.530
- Replies: 6
- Views: 828

[Help] F4-424 not accessible after update to 6.0.530
I was finally looking forward to updating my F4-424. I was coming from 5.1.145, which came with the device when I bought it new last November. I looked at the upgrade information, and it showed that it should be a straight upgrade to 6.0.530. I downloaded the bin file, backed up my configuration, an...