DSM-G600, DNS-3xx and NSA-220 Hack Forum

usulsuspct wrote:

I think I have bricked my 323. In anattempt to update to latest firmware (just upgrading from
stock firmware to 1.04 the device is no longer accessible.). The device now boots and the power icon just continues to flash with a sporadic flash of the network light. The drive lights never turn on. Needless to say I can't ping or connect via http to the device.

Any ideas out there?

Pull out your drives and hold the reset button on the back of your unit for about 15 seconds. Give it a couple minutes and see if the light goes solid. Something on your drive could be causing it.

I had this issue while mucking around with mine the other day (installing too many things at once). If you're running Windows, have you tried mapping the drives? Even though I had all those blinky, blinky lights (scientific terminology) I was still able to map the drives and see my data. If you installed fun-plug, log in via puTTY and delete the FFP folder and re-boot (this worked for me). You can always re-install fun-plug from scratch, not a huge big deal <shrug>. If you didn't install any fun-plug stuff then backup your data to your PC. If you can't see the data, get yourself an external SATA drive case and install the Windows Linux driver (Ext2 IFS) on your PC (I had to do this when I went from RAID1 to 2 separate drives, it also worked). Backup your data from the external case, re-install drives to the DNS, re-format and xfer everything back. It's a PIA but your data is probably safe, it's getting to it that might be painful. Hope that works for you, the DNS makes an ugly paperweight...

Yo!Adrian, eh?
Toronto

Last edited by yo_adrian_eh (2008-11-11 14:35:30)

My "blinky, blinky" light experience was a failed Fun-Plug USB install. The script failed (maybe it was me who failed?) and kept the unit cycling in a black hole. Logging in via puTTY and deleting the FFP folder solved my problem. If your issue isn't from Fun Plug then I'd mount a drive in an external enclosure and start copying your data.

> So you feel the unit itself is a lost cause?

No. What I said is based on the info you've provided you have a device that you can't access. I'm suggesting that if you want to bring it back to life you should set about recovering, in this order:
a. your data
b. your drives
c. your device

Installing the drive(s) in an external enclosure will give you 2 things; 1.) most important in my books, your data, 2.) once the data has been recovered to another drive the ability to reformat those drives prior to re-installing them in the DNS. Just my opinion but if you take those steps and something on the drives themselves is preventing boot, that issue *may* be eliminated during that process. At least at that point even if the device is a brick (and I hope that's not the case for your sake) your data and drives are safe and in usable condition. After doing all that I'd again use the reset button on the device, if it was me I'd try it without and also with the drives installed <nothing to loose at that point, right?>

I'm not nearly clever enough to know why the firmware upgrade puked. Don't give up yet, but get your data...just in case. I had to copy data on to 2 home PC's because I didn't have enough space and it took hours, like overnight. Once done, I was free to melt the DNS and rebuild everything. I just did this last week, twice! 1st time because of un-explained constant activity on drive 1, I rebuilt and also swapped drive 1 & 2 positions on the DNS. 2nd time because of my failed FFP USB install.

Try booting up without the network cable plugged in.  A couple of people here have had the same symptoms and it was caused by a improper DHCP.  It successfully booted up without the network cable plugged in, then they could access it using the default ip address and chnge it to a static one on thier subnet.