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

clefranc wrote:

Back to my first post, same errors...

Which firmware version I must use?

Bah! Sorry, I guess I haven't been much help.

I'd suggest using the latest firmware. 1.09 is out.

clefranc wrote:

Everything after this line go bad:
Bad inode number on dev mtdblock0: 65535 is out of range

Anyone have a clue? Bad memory, flash, hardware, etc.?

Possibly bad flash, I guess.

That said, you never made a new filesystem on /dev/mtdblock0, which may be part of the problem.

First, check the sizes of the partitions, and make a backup of them at the same time:

for i in 0 1 2 3 4; do
  dd if=/dev/mtdblock${i} of=/mnt/HD_a2/mtdblock${i}
done
ls -l /mnt/HD_a2/mtdblock*

The settings are in two 64kB Minix filesystems, which should be mtdblock0 and mtdblock1. Check the size in the listing above, they should be 65536 bytes.

If they are, then make a minix filesystem on them:

mkfs.minix /dev/mtdblock0
mkfs.minix /dev/mtdblock1

Try mount the filesystems:

mkdir /mnt/mtdblock0
mkdir /mnt/mtdblock1
mount /dev/mtdblock0 /mnt/mtdblock0
mount /dev/mtdblock1 /mnt/mtdblock1

Check for any files on them:

find /mnt/mtdblock0
find /mnt/mtdblock1

Check for errors:

dmesg

This is the most extensive unbrick thread I have found. Ill extend it some more.


I seems to be a limit on the ramdisk size of 0x005e0000 = 6 160 384 bytes in the uboot loadb r command (see below*). If I understand correct others in this thread has also suffered from it and solved it by loading a smaller ramdisk and later booted in a richer environment overwrite the mtdblock3 with raw write dd or cat.

I tried to find a firmware which fits this limit, alt-f dns 1.06 and 1.04 they all exceed it. The native debian firmware however fits the limit. I have successfully recoved into native debian (http://www.cyrius.com/debian/orion/d-li … overy.html). My plan is to do a default install of debian then somehow download my backups of the last good state of mdblock2/3 and write them back raw using cat. I am currently running the install. Lets see how my plan works out.


*
u-boot complains about ramdisk size.....

------------------------------
Erased 1 sectors
..................................... done
Erased 1 sectors
....................................... done
Erased 1 sectors
Ramdisk Size = 6389748
error,Ramdisk size > 005e0000 byesMarvell>>

Last edited by bjby (2011-07-08 21:17:19)

bhouse wrote:

Dear Sharp Rock,

I have un-bricked my DNS -323

It seems that loadb r and loadb k always load to address 0x10000.
Hence your trick with the cp command helped me. Thanks

I did the following:
- loadb r (sending kernel from firmware 1.7)
- cp ramdisk to a higher address for example 0x2000000 (by the way, this address seems out of the 8 MB Flash ROM. I do not understand where it is. Do you ?)
- loadb k
- bootm 100000 2000000

Then the DNS 323 boots alright, but hangs at "ehci_platform ehci_platform.20865: EHCI Host Controller" for 31 mn. You just have to wait that long!

I was then able to update the firmware using the standard web interface!!!

Hi Sharp Rock - Was this the C1 that you were able to do this with?

If so would you mind giving me more instructions on how to do this?  I made a serial cable and can see that it stops at booting Kernal - never goes past.

How do I do these steps.

- loadb r (sending kernel from firmware 1.7)
- cp ramdisk to a higher address for example 0x2000000 (by the way, this address seems out of the 8 MB Flash ROM. I do not understand where it is. Do you ?)
- loadb k
- bootm 100000 2000000