Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JavaLawyer]

I had to redo a full reset of my DNS-343. I was lucky that I had a full backup of it.

Now my big issue, because of 1.06 Firmware Im not able to change the Name of it
in the Device Settings. Everything else can be changed. But the name stays with the
random dlink name: dlink-14B096

Is it possible to rollback to 1.05. So I could change the device name...
Then upgrade to 1.06 again?
Or any plan to fix this issue? or any other way to change the device name??

You should be able to roll back to firmware v1.05 without issue and migrate back to v1.06. I don't know if v1.05 supports device name changes -- the names on my two DNS-343 were established in v1.04, and I haven't tried changing them since.

[hsantos]

Just did it... And 1.05 Supports Device Name change without any issue.

So Now im back to 1.06 Beta and Im about to restore my backup to it.

I was just afraid to create corruption by rolling back to 1.05 and then again to 1.06


Thanks

[JavaLawyer]

I'm glad everything worked out. The only published change from v1.05 to 1.06 was related to FTP, nothing that would impact HDD configuration.

[hsantos]

It worked yes.... But now I have some issues!!!

My slot1 is telling giving me a HDD status of Abnormal and my RAID is Degraded....

Lucky I have 2 other 2GB drives available.... But It did teh same for bith of them....

Something is wrong!!!! Could it be the Slot1 or the 1.06 Beta that is not working as designed??

Im planning on rolling back to 1.05 and Reset + Factory Default everything and restart my backup copy Again!

[JavaLawyer]

It's possible that a HDD is failing, as that would cause the Degraded message. You can go back to v1.05 and see if the message goes away. Rolling back shouldn't impact anything.

[hsantos]

3 HDD failing! 2 brand new... and 1 that I was using just before without any errors.... I find it strange!

[JavaLawyer]

3 HDD failing! 2 brand new... and 1 that I was using just before without any errors.... I find it strange!

Yes, odd. Changing the FW should have no impact on HDD configuration, especially a release as insubstantial as 1.06, which only touched on FTP.

[JavaLawyer]

Any update on this issue?

[hsantos]

Did a full reset.... seems to be ok and stable now... But on FW 1.05.
Was able to copy 100GB to it without any issue.

Redid a full reset... Upgraded to FW1.06B
While trying to copy the same 100GB the copy stopped and I had an error on Slot1
Something is fishy with FW1.06B!

Redid a full reset... Downgraded to FW1.05
Copied the same 100GB with success.
DNS-343 stable for the last 8hours

[JavaLawyer]

Thanks for your feedback. This begs the question as to whether v1.06b01 has some underlying changes that impacts RAID. My DNS-343s are configured as Standard Volumes, and I haven't had any issues. 

[doctormas]

i have a DNS-343 firmware r1.0. It has 4 2TB HDD installed and they are almost full of data. I don't have any backups of this data. i want to upgrade my firmware to r1.05. i am concerned about issues with the hard drives wanting to reformat after an upgrade. My question is can i safely upgrade my firmware from r1.0 -> r1.05 with HDDs installed without compatibility issues or the software wanting to reformat my HDDs. I should add that these drives are arranged as JBOD and accessed via Windows XP.

Thanks !

[JavaLawyer]

i have a DNS-343 firmware r1.0. It has 4 2TB HDD installed and they are almost full of data. I don't have any backups of this data. i want to upgrade my firmware to r1.05. i am concerned about issues with the hard drives wanting to reformat after an upgrade. My question is can i safely upgrade my firmware from r1.0 -> r1.05 with HDDs installed without compatibility issues or the software wanting to reformat my HDDs. I should add that these drives are arranged as JBOD and accessed via Windows XP.

Thanks !

Firmware version 1.0? Really? I can say from personal experience that migrating firmware version 1.03 and onward should not impact existing stored data or HDD configuration (e.g. v1.03 to v1.04 or v1.04 to 1.05). I've never dealt with (or read about) user experiences upgrading from version 1.0. You may want to try an incremental approach (e.g. 1.0 > 2.0; 2.0 > 3.0; etc).

Regardless of your approach, I can't stress how important it is for you to backup your data before performing any migration, especially from an older firmware version.  Please read the following thread DNS-343 - Data Backup vs. Redundancy

[doctormas]

my mistake...it's actually v1.01

I purchased it new in '09 , installed 4 seagate 2TB drives, and it has run flawless since. i never even thought about firmware upgrades until recently. i think i will just let sleeping dogs lay.

:-)

Thanks for the info!

[JavaLawyer]

my mistake...it's actually v1.01

I purchased it new in '09 , installed 4 seagate 2TB drives, and it has run flawless since. i never even thought about firmware upgrades until recently. i think i will just let sleeping dogs lay.

:-)

Thanks for the info!

If it's not broken, don't fix it
If your data is important to you, make a backup as soon as possible. There's no recovery from a hard drive failure.

[doctormas]

Oh i forgot to ask you. In the event that i do attempt to upgrade in the future, where can i d/l a copy of v1.01 firmware so i can rollback versions if need be. I didn't see anything that old on the D-Link site. Oldest version i seen was v1.02

Thanks again!