Reverting to original firmware

Eric Klein

unread,

Mar 14, 2018, 3:20:28 PM3/14/18

to Alt-F

Hello,
I installed the latest release of Alt-F for my DNS320 REVA1 and wanted to go back quickly to the original firmware.
Unluckily, I thought I just could use the original firmware from Dlink and flash the NAS, but it didn'T work at all.

My NAS is now stuck in the network with the default name but remains unaccessbile. I suppose I am not the only one to have tried this.

Could anyone please give me some guidance on how I can return to the original system?
Thanks in advance,

Eric

João Cardoso

unread,

Mar 14, 2018, 8:58:33 PM3/14/18

to Alt-F

On Wednesday, 14 March 2018 19:20:28 UTC, Eric Klein wrote:

Hello,
I installed the latest release of Alt-F for my DNS320 REVA1 and wanted to go back quickly to the original firmware.
Unluckily, I thought I just could use the original firmware from Dlink and flash the NAS, but it didn'T work at all.

Please confirm the following:
You flashed Alt-F, tested it, didn't like it and flashed the Dlink firmware back using the Alt-F webUI, right?
And the Alt-F webUI accepted the fw file, and displayed messages like "Flashing kernel", "Flashing...", etc, without producing any error or warning, and suggesting you to reboot the box, right?
Using Chrome or Firefox, not IE, right?

That all is part of the standard test release procedure, and always performed fine on a DNS-323-rev-A1/B1, a DNS325-rev-A1, a DNS-320L-rev-A1 and on a DNS-327L-rev-A1.

My NAS is now stuck in the network with the default name

Alt-F or D-Link name?

but remains unaccessbile.

To what? MS-Windows file access or browser access?

Have you cleared the browser cache? Have you rebooted the Windows box (that will clear the MS-Wins cache)? Have you performed a network scan (using, e.g. Fing on Windows) to be sure the box name and IP has not changed? Or have you consulted your router's DHCP server leases or clients page instead?

Eric Klein

unread,

Mar 16, 2018, 12:30:37 PM3/16/18

to Alt-F

Dear Joao,

thank you for your reply.

Yes , I did the firmware update with Chrome - right now I am trying again. It is the default name of Alt-F

Meanwhile the box is responsive again and running Alt-F . I have tried all the above suggested.

The latest issue is that when performing the firmware upgrade, the process is stuck at the firmware updater and at this stage:

kernel: Erasing... flashing... verifying... OK

rootfs: Erasing... flashing... verifying... OK

sqimage: Erasing... flashing...

It hasn't changed since 20 minutes now - stuck at flashing sqimage and now it turned off and now the left + right + power led is blinking in sync. Sounds like a mess to me but I am thankful for any suggestion to get this solved!
Thtnaks,
Eric

Eric Klein

unread,

Mar 16, 2018, 12:40:05 PM3/16/18

to Alt-F

Update here: I hope this helps others.

After the above mentioned happening, I noticed that the leds were flashing like crazy. So I looked up the connected devices in the network and noticed that the NAS had the original DNS-320 again.

I accessed the IP directly (share name didn't work) and got this screen:

I uploaded the latest firmware again and now it seems to work like magic!

Generally, I tried at least 5 firmware updates in the Alt-F UI to get to this stage.
I hope this helps to others.

João Cardoso

unread,

Mar 17, 2018, 1:01:00 PM3/17/18

to Alt-F

On Friday, 16 March 2018 16:40:05 UTC, Eric Klein wrote:

Update here: I hope this helps others.

Thanks for the feedback, it's indeed useful.

Obviously there was an error while flashing, and on the reboot the bootloader noticed the error and loaded and executed the vendor's rescue/recovey image (which Alt-F don't use or touch).

Why Alt-F flash failed and the vendor's succeed I can't guess. The flashing fails at sqimage, which is not a vital component, it allows Alt-F to boot with a reduced set of functionalities, that's probably why you always returned to Alt-F.

It would be interesting for me to diagnose the problem, but unfortunately I don't have a 320-rev-A to test with, and you are no longer with us (if you are, can you provide a link to the D-Link firmware that failed the flashed?

Ioannis Katsaounis

unread,

May 31, 2021, 4:53:31 PM5/31/21

to Alt-F

Hi, did the update to ALt+f.

So wanted to go back to origin but right now I am facing follwing screenshot. Any help on this? Its A DLINK 320 Rev A.

Kid regards

Janni

João Cardoso

unread,

Jun 1, 2021, 11:41:02 AM6/1/21

to Alt-F

Have you unzipped the D-Link supplied fw and uploaded the biggest file on it to the box?

Ioannis Katsaounis

unread,

Jun 1, 2021, 12:16:07 PM6/1/21

to al...@googlegroups.com

Hello Joao,

Thank you for your response. Seems that I was to impatient, after leaving Alt+f the whole night running and recognizing the Harddisks, the next day with few configurations it ran. So I'll leave it as it is. And to answer your question, no i put the whole zip.

Kind regards

Janni

--
You received this message because you are subscribed to a topic in the Google Groups "Alt-F" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/alt-f/ix1VIS2G5WU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to alt-f+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/30d80a0d-4727-4e52-bc0e-fd6d48b74391n%40googlegroups.com.

João Cardoso

unread,

Jun 1, 2021, 2:18:53 PM6/1/21

to Alt-F

On Tuesday, June 1, 2021 at 5:16:07 PM UTC+1 i.kats...@gmail.com wrote:

Hello Joao,

Thank you for your response. Seems that I was to impatient, after leaving Alt+f the whole night running and recognizing the Harddisks,

checking the filesystems, actually.

Notice that if the FS is still ext2 (and not ext3 or ext4), such a lengthy check will be done every time there is an an-ordered shutdown, such as a power cut.

the next day with few configurations it ran. So I'll leave it as it is. And to answer your question, no i put the whole zip.