D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-343 => Topic started by: giftmugs on May 07, 2014, 12:31:12 PM
-
I updated my firmware from 1.04 to 1.05 and all went well, except that NOW my unit will no longer boot.
In other words: my NAS is no longer accessible nor pingable.
It constantly shows: System is booting.... yet it never does, and this is now going on for over 24 hours.
Now I am very worried since my backups are on this D-Llnk NAS 343
I desperately need some help on how to get my unit to boot again as a factory reset, unloading of all 4 HHDs did not help. No matter what I do do not get my unit to reboot.
Can you offer my any help? Thank you very much
.
-
How are the HDDs configured (Standard, RAID-1, RAID-5, etc.)?
Performing a factory reset will remove all user settings but should not impact your HDD configuration or stored data:
DNS ShareCenter - Restoring Factory Default Settings (http://forums.dlink.com/index.php?topic=51309.0)
Depending on how the HDDs are configured, there may be some other options as well...
-
The restore button does not respond at all at this time. Nor does the frontal power button. Only unplugging the unit will stop the continuous display of: System is booting......System is booting......, yet it does NOT.
I have no access to the unit as it will not boot any more. The firmware update must have corrupted my unit.
How would I install a new firmware without having access to the unit (as it's no longer accessible nor pingable)
???
-
Just curious, What browser are you using to mange the DNS and do the FW update?
Please ensure any 3rd party browser add-ons and PC security SW is disabled while doing FW updates on the DNS.
My 2 cents...
-
I'm using Firefox 28, with Win 8.1
-
I'm sure JavaLawyer has more information regarding this that he will be posting.
I do recommend using IE for any FW update evolutions on D-Link products. Most of the time FF and other browsers do work however we have seen some issues with them since they are constantly updated. Yes IE is updated as well however not to the extent that others are. I recommend use IE and setting compatibility mode with all add-ons disabled. I use IE for doing all of my FW and management when I used Windows platform, Safari when I'm on Mac. I like to keep it safe this way. I use other browsers for all other management and configurations.
I believe Javalawyer will be posting a bit later as he's headed home so please be patient. He'll post more information soon.
-
Hello FurryNutz,
Thanks for your post and info.
Of course I'll patiently wait for any postings as I really need to be able to access my 343 again with all my backups on it.
Again, many thanks for your help.
-
;) I'd leave the DNS OFF off for now until JavaLawyer posts.
Good Luck.
-
Yes, that's what I did now.
The unit is turned OFF (un-plugged) until further notice. Thanks.
-
How are the HDDs configured?
-
If I remember correctly, the 2x2TB are mirrored to the 2nd identical pair.
The drives are a simple copy made for backup from several HHD's.
-
two independent RAID-1 arrays? or a RAID-10?
-
One thing you can try is shutting down the DNS-343, removing all four HDDs, and then rebooting. See if that gets you to the web UI. Practically speaking, a RAID array created in one DNS-343 should be transferable to another identical unit, which would make this approach plausible.
Under normal circumstances, I would recommend that you backup your data before performing this type of activity, but that doesn't seem to be an option here.
-
I think it is One RAID-1.
I already had removed all 4 HHD's and then tried to reboot.
I also tried to reset the unit with and without HHD's in it, but to no avail.
Unfortunately, the text in the front panel of the NAS is always the same: System is booting.....
but does NOT
Since I am just a regular guy who has to work with PC's and does not know much about RAID's nor NAS's,
I think that as long as the 343 does NOT boot, nothing will happen, as I tried so many different things
and the unit just will not boot.....because of the firmware update that did not install as it should.
Before that with version 1.04 the NAS worked great without ever failing.
Is there a way to install firmware on a NAS that is not accessible?
-
I reached out to my contact at D-Link to validate whether or not an emergency firmware recovery procedure exists for the DNS-343 and will post back if I hear anything.
In the interim, there is software available that will enable you to mount the DNS-343 HDDs in a PC to access the data: DNS-343 - Data Recovery (Windows PCs) (http://forums.dlink.com/index.php?topic=41302.0)
-
I will also presume that you used the following method for the factory reset (if not, give this a shot):
DNS ShareCenter - Restoring Factory Default Settings (http://forums.dlink.com/index.php?topic=47707.0)
These procedures assume that the DNS-343 is already booted. For your situation, try unplugging the power cord for 30 seconds and then plug back in. Next, hold the Reset button while the DNS-343 is powered-down, and continue to keep the Reset button pressed while you power-up the device.
-
Hello JavaLawyer,
Thank you for your quick response and information.
Now I should at least be able to read/copy the 4 disks from the "un-bootable" 343 (by putting them into a USB caddy) and make appropriate straight copies to HHD's on my PC.
Before I do that I'll await news from you about any emergency firmware recovery procedure that may exist for the DNS-343.
Since my 343 does NOT boot at all, all attempts at restoring factory defaults have failed.
Again, many thanks for your efforts at helping me getting back into business.
.
-
Certain D-Link routers have emergency firmware recovery procedures, while many other D-Link devices do not. I don't think one exists for the DNS-343 as I believe I would have heard about it by now, but I've made the query nonetheless. This is the first time I've encountered a situation where the DNS-343 simply got stuck in a boot cycle.
I'm sure you've already looked at this (and it's a shot in the dark) but I'll ask anyway. . . What happens when you enter the DNS-343 IP address into a browser? Did you try IE and Firefox? I'll presume you received "Page Can't Be Displayed" messages because the unit was still booting.
-
Just curious, any chance of powering ON the DNS in a different wall out let? I'm also wondering if maybe the Power Supply could be at fault as well. Just a thought. :-\
-
Can't hurt trying another outlet. I thought that this might be the power supply, but I would think that removing the four HDDs should have lowered the load enough to support the DNS-343 if the power supply had degraded.
. . . but who knows. ???
-
Using IE and Win File Explorer, the following error message is displayed:
- An error occurred while reconnecting Z: to\\DLINK-622f58\Volume_01 OR
- This page can’t be displayed
• Make sure the web address http://192.168.1.195 is correct.
Using Opus Directory, this error message is displayed:
- An error occurred reading folder. The network path was not found (53)
In Google it says simply:
- Oops! Google Chrome could not connect to 192.168.1.195
In Firefox it says:
- The connection has timed out. The server at 192.168.1.195 is taking too long to respond.
The changing of electrical outlets did not show any change nor the number of disks in the 343.
The result is always the same: System is rebooting....
. ???.
-
I think it's time to get Ivan in here. ;D
-
Lets wait a day or so and see if someone gets back to us. I've also pinged a couple of forum members that are ShareCenter gurus and have experience repairing these devices.
-
Thank you for your offers of help and assistance.
I'll gladly wait for any response that may arrive.
I am extremely surprised about the responsiveness of this forum
and the amount of help that you both offer, JavaLawyer and FurryNutz.
It is astonishing your dedication, cooperation and assistance to help me out of this impas.
Again, many, many thanks. I am impressed!
:)
-
An interesting problem you have there giftmugs and sorry I didn't get to this sooner but the week has been rather busy.
Now I need a little information from you.
First, how confident do you feel about opening your unit and exposing the motherboard? I ask this because it appears that you will either have to use JTAG or the serial interface to re-flash the firmware. That will also require a little soldering on your part.
Second, make sure that your power supply is actually supplying 19volt under load. Failing power supplies may give the rated voltage at no load but the moment you put a load on them the voltage drops, in many cases to a level where the unit will not work even though the indicators do (they are generally not very voltage sensitive).
The easiest way to go is to use the serial port marked JP4 which requires a 3.3v to 5.0v serial translation module and a serial port on your PC as well as terminal software which will allow you to get into U-Boot and replace the firmware.
A few of observations.
1) Since the unit uses a 19v power supply you can do a test with a 19v laptop power supply that has the same, or higher, current rating.
2) It is essential that there be stable power during any flashing operation. In some cases where spikes appear on the mains it is necessary to use a UPS for power during flashing operations.
3) DO NOT attempt any of the above work on the circuits if you are not confident in your skill level. If necessary find a electronics repair shop or the electronics department of the local tech college ad see if they will do it for you.
I will try and help you if you decide to try and do it yourself (I own a company that repairs and maintains computer equipment for industry) but It will have to fit round work commitments and I can't 'borrow' a clients 343 to take it apart and take photographs to show you where things are (we no longer own a 343).
-
Here comes the cavalry. . .
Ivan thanks for lending a hand. :)
-
Hello Ivan,
Thank you very much for you post and suggestions and would like to say:
- I'm not too confident to execute the steps you describe;
- I now tried another power supply but the results are as before. No change...No booting...
- Before I attempt to locate a local electronics repair shop I can trust to be competent enough,
and since I am not under any time pressure, would it be possible I ship the
unit w/o disks to you for the repair?
I'd be happy to pay for your services and am aware that you have many previous commitments.
Maybe I could use the e-mail link in the forum page to contact you for further details?
I'm so happy that you could offer a way to get my unit back to work and hope that you'll
be able to help me.
Thank you very much, indeed, as well as JavaLawyer and FurryNutz.
.
-
Hi giftmugs,
For us to do the work is not a problem. The problem could be that we are in France and unless you are somewhere in Europe shipping and customs becomes a big problem.
To give you some idea of what might be involved go to http://dns323.kood.org/start (http://dns323.kood.org/start) and have a look round. This is for the DNS-323 but works much the same as the DNS-343 using the same equipment - there is a page for the 343 in the side menu. It is one of the best general information sites about this series of NAS boxes on the web, catering to people that have a little ability of a technical nature.
There was someone on the DNS-323 forum that used the information there to get his unit working again - he had a problem very similar to yours.
Another piece of information. If you use a USB caddy to read the data on your disks make sure it is one with its own external power supply. You can not reliably power up the disks using power from the USB port.
The other thing is to have the software for reading the Linux file system already installed on your windows computer before you plug in the USB caddy and DO NOT let windows write to those disks.
Here we use a Linux PC with a USB/SATA plug in adapter if we ever need to work on our or our clients disks because that way we don't have problems with disk file system formats.
-
Hello Ivan,
Thank you for your very quick reply and I'm so sorry that our geographical
differences will not permit to have this unit fixed by you.
Would you be able to give me some specific key points that I could show a local
electronic repair shop on how to best fix my DNS-343 as I am not sure that my
local shops will know what to do exactly even if I refer them to the web site you mentioned:
http://dns323.kood.org/start (http://dns323.kood.org/start)
(Or maybe JavaLawyer or FurryNutz know of some competent repair shops in the USA? or are they also located in Europe?)
Again I very much appreciate your help and am so sorry not to be able to overcome the distance problem.
Merci beaucoup
Roland
P.S.
I'll follow your other suggestions faithfully.
/
-
I presume JavaLawyer may have some info on possible repair shops, I don't know. We might be able to find some forum users that can help out as I believe I remember recently someone over here on this side of the pond was helped by Ivan to fix his.
I could probably do this as I do have a electronics repair back ground, however I don't have any parts necessary to do this repair. I'm not opposed to helping out however if we can find a user here in the forums that has done this already and has the parts and is willing, I suggest we try to make contact with that user first and lets go from there.
Maybe Ivan or Java can point us to the most recent user who did this?
-
Great,
let's give this matter a little time to simmer and we can then take it from there.
By the way, the way I read Ivan's suggestions there are no spare parts required so to speak of - just a soldering iron?? ???
However, I know nothing about these things and maybe Ivan knows the parts required.
Just a thought.
-
I do have a soldering iron. ;D
-
Great,
let's give this matter a little time to simmer and we can then take it from there.
By the way, the way I read Ivan's suggestions there are no spare parts required so to speak of - just a soldering iron?? ???
However, I know nothing about these things and maybe Ivan knows the parts required.
Just a thought.
Keep us posted, whichever way you decide to go.
-
Oh,
I am so sorry that I created the impression that I did not want to continue.
Au contraire. What I meant was that maybe, as FurryNuts pointed out,
JavaLawyer would know someone in the US who can repair the unit, and that
Ivan may be able to supply some details (beyond the link he has already indicated)
that can be shown to any electronics repair shop able of doing this kind of repair.
I'm sorry for my failure to express myself more clearly as I am very interested in
having my 343 unit fixed. I need and greatly appreciate any help. Thank you.
Of course I'll keep the forum posted of any and all developments.
-
Can JavaLawyer or Ivan find the most recent thread or the user whom recently went thru this? I don't remember if it was for this model or a different model. It was in the past few month I believe...
-
As I stated back in one of my original replies, this is the first time I've encountered a thread/user whose ShareCenter was rendered unusable by what seems to be a corrupt firmware upload. As far as repairs go, I don't personally know of anyone, nor know of any recommended repair center. Ivan's instructions appear to be straightforward (and simple) enough for an electrical engineer or someone familiar working with ICs to follow. If you're looking for an economical route, visit a local university's EE department and see if there is a grad or undergrad student willing to quickly knock this out. You can offer a flat fee with an small incentive if the project is successful. The quickest way to find someone is to knock on a professor's door and ask for some references.
-
The previous forum thread I was thinking about was http://forums.dlink.com/index.php?topic=57510.0 (http://forums.dlink.com/index.php?topic=57510.0) where there was a problem with U-Boot.
A little more information regarding the serial ports of the DNS-343 after I asked my head technician if he had any ideas (he likes to take things apart to see what makes them tick).
There are two of them, one at the front of the board and one at the back by the power connectors for the backplane. He thinks the front one is reserved for working with the O-LED display and the back one is the one to be used with this problem.
Another point, there MUST be a level converter used between the 3.3v ARM circuits and the higher voltage RS232 or USB of the PC. We have made our own but they can be purchased quite cheaply from Amazon or such like.
As JavaLawyer says, the best bet would be to find a grad student in electronics and ask if they would do it for you.
-
Hello Ivan,
Thank you for your post and suggestions which are very helpful to me.
I'll try to find a person capable of fixing my unit but that may take a while
as I live in the sticks.
To facilitate the task of reparing my DNS-343, I list below the links to serve as
repair reference points for any technician:
1.04 failed: http://forums.dlink.com/index.php?topic=38687.15 (http://forums.dlink.com/index.php?topic=38687.15)
Previous: http://forums.dlink.com/index.php?topic=57510.0 (http://forums.dlink.com/index.php?topic=57510.0)
DNS-323: http://dns323.kood.org/start (http://dns323.kood.org/start)
I'll not fail to post here any progress I may make.
Again, thank you Ivan, Javalawyer and FurryNutz, for all your help and suggestions.
:)
-
It's a bit after-the-fact, but I heard back from D-Link and unfortunately there is no procedure that would allow reloading firmware after a complete failure. The U-Boot utility used in the DNS-343 does not have the headers installed on the board, so the recovery process was not created in firmware.
-
What exactly did they say?
My tech guy says there are the two 4 pin headers on the board for com 1 and com 2 (at least there was on the 343 he opened).
Or do they mean there are missing hooks in the bios that prevent u-boot working on a failed system?
The other thing to ask them is, is there a JTAG header there somewhere? If there is can they supply the connection data because this should enable direct writing to the NVR which should lead to an unbricked unit.
-
Thank you very much for your post and effort in helping me recuperate an otherwise fully functioning NAS drive.....
Why did I have to update the firmware, why did I listen to the D-Link Blog? Yes, why, indeed??
There was nothing wrong with my 343.
So we now finally know that there is no hope for a DNS-343 recovery process and that means for me
that I will no longer be in the market for any D-Link products!!
-
Hello Ivan,
While writing my last post I got a message that a new post was available as I was responding to JavaLawyer's post.
Maybe there is still hope for my brick?
???
-
Could Ivan or Java look thru there recent history on posts they've done and see whom this users was that Ivan helped to do this repair. I believe this user was here in the U.S. and if we could get a hold of him we could maybe see if he's interested in doing it since he has the parts needed already. It would be worth checking.
I'd like to see if we can change giftmugs thoughts about D-Link products if possible. ::)
-
So are you saying that there may not be any recovery option work around for the 343 due to this info?
-
Hi giftmugs,
It is a pity that we sold our 343 to a client because it was exactly what he wanted, otherwise I'd take it apart to see exactly what was there.
One thing that should be noted, unless JavaLawyer actually got a response from someone that actually has hands on experience of working with the units I would question the response he got.
Reason for doubt.
Several years ago we became agents for some equipment produced by a manufacturer in LA. Part of the agency agreement required that I sent someone over to their offices 'for training', I was the one that went because I needed to arrange for spare parts and other things. The first morning of the training period ended up with me teaching their service department how to field service their equipment with minimum equipment and spare parts (all they did was replace suspect parts from the factory floor). It ended up with them sending their service manager and head technician over to us for training (hence my not naming the product or manufacturer).
It is possible that the information that JavaLawyer was given is incorrect from a field servicing point of view but not a manufacturer point of view where they just change parts. The real problem will be if there are missing software hooks in the bios to allow u-boot to operate and no JTAG connector pads on the board (although direct solder connections might be possible but that requires skill).
As for D-Link products, we find them reliable and recommend their use to our clients as well as using then ourselves. I will admit we don't update firmware unless there is some feature in the new firmware that we need. As far as I remember all of our NAS units are on the firmware they had when we got them but then they are used as either storage units or backup units with some being backup units to others.
-
In summing up, I would like to offer some observations on this matter, if I may, even though I do not understand anything technical about this, except common sens:
- There has to be a way to load the firmware into the DNS-343. How was it loaded into it at time of manufacture when the board was new/empty?
- Also, when a unit is still under warranty how does D-Link fix it? They must have a shop or know of a shop that does their repair work in the US as I am sure they do not sent it to Asia for repair purposes.
_ Mine is no longer under warranty and I offered to pay for repairing my unit - but maybe this is not a cost conscious observation
- Furthermore, in many forums sooner or later a factory rep joins into the fray and offers suggestions if not concrete help.
- Maybe D-Link is not interested in existing customers (my router is also a D-Link) as the response I received from them directly to my pleas were just boilerplate.
Again, as I write this, a new post arrived from JavaLawyer and that seems to be the final word on this
matter:
"Warning - while you were typing a new reply has been posted. You may wish to review your post."
Many thanks for all your effort in trying to help me fix a unit that used to work great for many years and only because I tried to update it lost my DNS343. What a pity!
???
-
Thank you very much for your post and effort in helping me recuperate an otherwise fully functioning NAS drive.....
Why did I have to update the firmware, why did I listen to the D-Link Blog? Yes, why, indeed??
There was nothing wrong with my 343.
I personally do not perform a firmware upgrade unless there's a substantial upside to be gained that offsets the potential risk. When it comes to storage products, I'm very skittish about taking the plunge as my data is irreplaceable. Conversely, I'm more easily swayed to upgrade the FW in my network cameras, even if the improvements are minor, since the risk of failure is one I can live with.
-
I only ran the update because D-Link sent me an e-mail blog suggesting it.
Otherwise I would not even have known that I can update.
NOW I KNOW!
-
This is the thing I was just talking about!
The DNS-343 uses the same chipset as the DNS323.
The serial headers are JP2 and JP4 with, I think JP2 being the one we want (the other is the port for the OLED controller)
Pinout: (pin one has the square solder pad)
pin 1 - +3.3v
pin 2 - RX
pin 3 - TX
pin 4 - GND
The signal levels at the NAS end are 3.3v which have to be level shifted to and from the PC (use a MAX232 based level shifter).
The terminal program should be set at 115200-8-N
That is the hardware defined
Now as per the dns323.kood.org/dns-343 wiki page the U-boot information is as follows:
U-Boot
** LOADER **
** MARVELL BOARD: DB-88F5X81-DDR1-A LE
U-Boot 1.1.1 (Apr 1 2009 - 18:02:07) Marvell version: 2.2.2.Gandolf.02
U-Boot code: 00200000 -> 0026FFF0 BSS: -> 0027BC8C
Soc: 88F5281 D0 (DDR1)
CPU running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz
DRAM CS[0] base 0x00000000 size 128MB
DRAM Total size 128MB
[16384kB@ff000000] Flash: 16 MB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done
CPU : ARM926 (Rev 0)
Streaming disabled
VFP initialized to Run Fast Mode.
USB 0: host mode
CPU: Write allocate enabled
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Marvell>> printenv
bootargs=root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none
bootcmd=bootm FF040000 FF1C0000
baudrate=115200
loads_echo=0
ipaddr=2.66.66.1
serverip=2.66.66.32
rootpath=/mnt/ARM_FS/
stdin=serial
stdout=serial
stderr=serial
cpuName=926
CASset=min
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
enaVFP=yes
enaWrAllo=yes
enaICPref=yes
enaDCPref=yes
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:egiga0:none
image_name=uImage
standalone=fsload 0x400000 $(image_name);setenv bootargs $(bootargs) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x400000;
bootdelay=3
disaMvPnp=no
ethaddr=00:00:00:00:51:81
eth1addr=00:00:00:00:51:82
mvNetConfig=mv_net_config=(eth0,00:aa:bb:cc:dd:ee,0)(eth1,00:11:22:33:44:55,1:2:3:4)
overEthAddr=no
pciMode=host
usb0Mode=host
ethact=egiga0
Environment size: 835/4092 bytes
Marvell>>
The other information provided by sysinfo is:
Sysinfo
/proc/cpuinfo
Processor : ARM926EJ-S rev 0 (v5l)
BogoMIPS : 498.07
Features : swp half thumb fastmult edsp
CPU implementer : 0x41
CPU architecture: 5TEJ
CPU variant : 0x0
CPU part : 0x926
CPU revision : 0
Cache type : write-back
Cache clean : cp15 c7 ops
Cache lockdown : format C
Cache format : Harvard
I size : 32768
I assoc : 1
I line length : 32
I sets : 1024
D size : 32768
D assoc : 4
D line length : 32
D sets : 256
Hardware : Feroceon
Revision : 0000
Serial : 0000000000000000
/proc/meminfo
MemTotal: 126836 kB
MemFree: 73700 kB
Buffers: 28108 kB
Cached: 11668 kB
SwapCached: 0 kB
Active: 9248 kB
Inactive: 35364 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 20 kB
Writeback: 0 kB
AnonPages: 4864 kB
Mapped: 1540 kB
Slab: 7140 kB
SReclaimable: 848 kB
SUnreclaim: 6292 kB
PageTables: 140 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 63416 kB
Committed_AS: 12168 kB
VmallocTotal: 385024 kB
VmallocUsed: 18016 kB
VmallocChunk: 360444 kB
DMESG Output
Linux version 2.6.22.7 (jack@SWTEST1) (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #4 Fri Jan 22 11:02:54 CST 2010
CPU: ARM926EJ-S [41069260] revision 0 (ARMv5TEJ), cr=00053177
Machine: Feroceon
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 32768
DMA zone: 256 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 32512 pages, LIFO batch:7
Normal zone: 0 pages used for memmap
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Built 1 zonelists. Total pages: 32512
Kernel command line: root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 117248KB available (2876K code, 193K data, 120K init)
Calibrating delay loop... 498.07 BogoMIPS (lpj=2490368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Sys Clk = 166666667, Tclk = 166666667
CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 128MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....base 20000000, size 256MB
SDRAM_CS3 ....base 30000000, size 256MB
PEX0_MEM ....base e0000000, size 128MB
PEX0_IO ....base f2000000, size 1MB
PCI0_MEM ....base e8000000, size 128MB
PCI0_IO ....base f2100000, size 1MB
INTER_REGS ....base f1000000, size 1MB
DEVICE_CS0 ....no such
DEVICE_CS1 ....no such
DEVICE_CS2 ....no such
DEV_BOOCS ....base ff000000, size 16MB
Marvell Development Board (LSP Version 3.0.5_NAS_GDP_p9)-- DB-88F5X81-DDR1-A Soc: 88F5281 D0
Detected Tclk 166666667 and SysClk 166666667
Marvell USB EHCI Host controller #0: c112c600
PCI: bus0: Fast back to back transfers disabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: orion_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 9328K
RTC registered
Use IDMA channels 2 and 3 for enhancing the following function:
o Copy From/To user space operations.
o memcpy() and memmove() operations.
o memzero() operations.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 3.3 (2007/10/31) Phillip Lougher
squashfs: LZMA suppport for slax.org by jro
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 25600K size 1024 blocksize
loop: module loaded
Marvell Ethernet Driver 'mv_ethernet':
o Uncached descriptors in DRAM
o DRAM SW cache-coherency
o TCP segmentation offload enabled
o Checksum offload enabled
o Marvell ethtool proc enabled
o Rx desc: 128
o Tx desc: 256
o Loading network interface 'egiga0'
PCI: enabling device 0000:00:01.0 (0140 -> 0143)
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi2 : Marvell SCSI to SATA adapter
scsi3 : Marvell SCSI to SATA adapter
flash VppMin = "0" , VppMax = "0"
cfi_flash_0: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
cfi_flash_0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "cfi_flash_0":
0x00000000-0x00020000 : "MTD1"
0x00020000-0x00040000 : "MTD2"
0x00040000-0x001c0000 : "Linux Kernel"
0x001c0000-0x00f80000 : "File System"
0x00f80000-0x01000000 : "u-boot"
ehci_marvell ehci_marvell.4523: Marvell Orion EHCI
ehci_marvell ehci_marvell.4523: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.4523: irq 17, io base 0xf1050100
ehci_marvell ehci_marvell.4523: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1 30 MB/s
raid6: int32x2 48 MB/s
raid6: int32x4 53 MB/s
raid6: int32x8 48 MB/s
raid6: using algorithm int32x4 (53 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 429.600 MB/sec
8regs : 330.000 MB/sec
32regs : 513.600 MB/sec
raid5: using function: 32regs (513.600 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 120K
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
egiga0: mac address changed
egiga0: Ilegal MTU value 9000, rounding MTU to: 9004
egiga0: change mtu 1500 (buffer-size 1520) to 9004 (buffer-size 9024)
egiga0: link down
egiga0: link up, full duplex, speed 1 Gbps
usbcore: deregistering interface driver usblp
No found HD
And the standard access to U-Boot is space + 1
Need I say more?
-
Ivan,
Thank you for the very detailed tech info as well as the previous post about tech service in general, both of which are greatly appreciated.
Since I am not able to do the actual fixing of my 343, would I be able to use the existing 4 HHD's just as they are (from the now dead 343 box) and insert them into a new 343 box and go on with my life?
I read everywhere that any disk inserted anew into a 343 box will automatically be formatted no matter what.
Is there a way around this automatic formatting or do I need to purchase new HHD disks and copy to them from the old disks via Ext2 to my PC and then back to the "New" 343?
???
-
From the beginning of this topic it appears as that you have two RAID 1 sets (this is how we setup our unit we sold).
If this is the case then you only need two new disks at the most and if one of the arrays was a backup of the other that can be reduced to one.
The above is based on the fact that the pair of disks in a RAID 1 array both carry the exact same information hence the rebuilding of the array if a disk dies is little more than the unit copying the contents of the remaining disk to the new one.
If that is indeed your setup then it will be a simple matter of plugging three of the original disks with the new one into the replacement unit. Try and keep one of the RAID arrays together just to check if it will accept it as a valid array, if it does you are up and running. If it doesn't just setup the two RAID 1 arrays put the reserved disk into a USB/SATA caddy or adapter, plug it into a PC that has been booted from a live Linux CD and start copying your data over.
Once the data transfer is complete setup the unit to backup the primary array to the secondary array and you are back to where you were before all this happened. You also have an added bonus if you used a USB/SATA caddy that you have have a third backup of your data (as an aside, we have three separate backup units for every primary unit and an off site storage array for backup as well, but then we have clients data to look after as well as our own).
-
Ivan, correct me if I'm wrong, but hypothetically speaking, wouldn't he also be able to "possibly" drop one of the RAID-1 arrays into a DNS-323 (if he can come across a unit) since the underlying architecture is the same?
-
Thanks for your reply.
Yes, Ivan, you're correct my "broken" unit had two RAID 1 sets.
However I am still puzzled and before I make any mistakes I would need to know if any disk that is inserted into the NS-343 will automatically be formatted.
Since any new 343 unit would have no disks installed at the beginning and if I now insert one disk, that disk will be automatically formatted. Then what happens if I insert one of the disk form my "broken" 343? It will be formatted before I can copy it.
Could you clarify this for my, please?
Thank you.
-
I will try and answer but please remember we no longer have a 343 to test this with.
For a start as JavaLawyer says, in theory it should be possible to just plug in the two RAID 1 arrays and they should work BUT, and this is a very large but, a lot depends on the firmware revision of the old unit and the replacement unit. If they are the same firmware level then there is a good chance that the raid array will be recognised but it might not because we do not know where the update firmware failed and what that failure did to the RAID information on the disks.
Now giftmugs, since you said earlier that you were using one of the arrays as a backup of the other I am assuming that backup was up to date. If that is the case you can then plug the two disks of that backup array into the slots of the replacement unit corresponding to the ones they were in in the old unit then power up the new unit and see if thy are recognised as a RAID 1 array. If they are then check that you can read your data. If you can do that then your problems are over and you can plug in the other two disks and check that they are recognised as a RAID 1 array and you can read your data.
Now this is what to do if the backup RAID array is not recognised.
First of all if you had any data on that array that was not the backup plug on of the disks into a USB/SATA caddy/adapter and copy it off that disk to a safe place as I described before. Once you have done that plug both disks into their corresponding slots on the replacement unit, power it up and create a RAID 1 array.
Once the array is formatted and ready use on of the remaining pair of disks mounted in the USB/SATA caddy/adapter and copy all the data on it over to the new RAID 1 array. when the copy is complete verify that the data is readable and what you expected, then copy the extra data if there was any.
Now you have a choice. You can either put the two original disks in the replacement unit and create the second RAID 1 array and then use it as the backup for the first array you created, or you can plug in one of the original disks and a new one, create an array and copy the data from the original disk you replaced with the new one - this gives you a remote backup of your data should you ever need it.
I hope this makes what you need to do a little more clear but it does require you to get a USB/SATA caddy or adapter that has its own power supply (USB ports generally do not supply enough power for the 3.5" disks). It also means that you need either the software mentioned in the windows recovery sticky or a bootable Linux CD or USB stick.
If you need more help or further explanations don't hesitate to ask.