F2-220 internal usb image
Posted: 31 Aug 2020, 01:41
I tried to re-initialize my F2-220 over the weekend only for it to fail repeatedly.
The HDD LEDs never changed from red and the NAS started beeping in constant intervals.
I've read through the FAQs and tried the steps listed with different HDDs and SSDs without any success.
The NAS just kept beeping and the HDD LEDs stayed red no matter which drives were being used.
The beeping also continued if the drives were removed and there was no way to access the NAS over the network.
After a few more trials I've come across GitHub repository which contained an old Backup of the internal usb drive of an F4-220.
So I've downloaded and wrote the image to an empty usb drive and replaced the internal usb drive with the new one.
And to my surprise during the next trial the beeping stopped, the HDD LEDs went from red to green and the device was reachable over the network.
So I assume the reason is either the original stick going bad (or it might be the drive being full? 98% of the 62 MB were being used with only 1.8 MB of free space according to the disk manager).
While I am now able to reach the NAS, I am still unable to install TOS (4.1.30) on the NAS.
Automatic download fails and while manually downloading the Installer from the website works, the installation crashes at 55%.
A possible reason might be the outdated usb image (I think the Web interface during the first initialization looked cleaner and more refined than the current one with the new drive).
Another reason might be that the image is not 100% compatible with the F2-220 since it originally came from an F4-220.
Is it possible to get an official and hopefully up-to-date boot image to try again?
Otherwise if it continues to fail I most likely will have to return the device.
The HDD LEDs never changed from red and the NAS started beeping in constant intervals.
I've read through the FAQs and tried the steps listed with different HDDs and SSDs without any success.
The NAS just kept beeping and the HDD LEDs stayed red no matter which drives were being used.
The beeping also continued if the drives were removed and there was no way to access the NAS over the network.
After a few more trials I've come across GitHub repository which contained an old Backup of the internal usb drive of an F4-220.
So I've downloaded and wrote the image to an empty usb drive and replaced the internal usb drive with the new one.
And to my surprise during the next trial the beeping stopped, the HDD LEDs went from red to green and the device was reachable over the network.
So I assume the reason is either the original stick going bad (or it might be the drive being full? 98% of the 62 MB were being used with only 1.8 MB of free space according to the disk manager).
While I am now able to reach the NAS, I am still unable to install TOS (4.1.30) on the NAS.
Automatic download fails and while manually downloading the Installer from the website works, the installation crashes at 55%.
A possible reason might be the outdated usb image (I think the Web interface during the first initialization looked cleaner and more refined than the current one with the new drive).
Another reason might be that the image is not 100% compatible with the F2-220 since it originally came from an F4-220.
Is it possible to get an official and hopefully up-to-date boot image to try again?
Otherwise if it continues to fail I most likely will have to return the device.