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

Yes, it´s possible.

Take the file "system.tgz" from new firmware and put it in an folder on your linux PC.
Cut the imageheader away.   dd if=system.gz bs=8 skip=13 of=system_noh.gz
Unpack this:     tar -xzf system_noh.gz
You get 3 files, rootfs.tgz, rd.gz and zImage.
Connect the 313 over USB to your Linux-PC. Notice, as which device it is connected,
e.g. /dev/sda or /dev/sdb.
Mount the 3rd partition (ext2 filesystem). May be, if the filesystem on this partition is wrong, you can create a new.
mkfs.ext2 /dev/sda3 (or sdb3, sdc3...)
Mount this partition again.
Create a folder /.boot (don´t forget the dot before the "b"!)
Put the files  rootfs.tgz, rd.gz and zImage in this folder.
Unmount and disconnect the USB, connect network to the 313 and reboot.

Greatings,  the bear.

maple wrote:

Works like a charm!
Thank you very much for this detailed how to guide, I'm a Linux newbie and I have done it on a first attempt :-)

Regarding that samba - is there another way how to mount this NAS in Linux?

mount //<ipaddr>/<share> /mnt/nas -o uid=<local_uid>,username=<nas_user_name>
you'll be prompted for a password then. if you want to mount the share at the boot time, check /etc/samba/smbfstab

uid option will help you to set the owner of a files to the local regular user.

in the official install there is no other protocol support, aside from ftp. but you can install the dropbear ssh server, and mount a directory using the sshfs.

Last edited by pcp (2008-05-16 11:29:38)

CharminBaer wrote:

Yes, it´s possible.

Take the file "system.tgz" from new firmware and put it in an folder on your linux PC.
Cut the imageheader away.   dd if=system.gz bs=8 skip=13 of=system_noh.gz
Unpack this:     tar -xzf system_noh.gz
You get 3 files, rootfs.tgz, rd.gz and zImage.
Connect the 313 over USB to your Linux-PC. Notice, as which device it is connected,
e.g. /dev/sda or /dev/sdb.
Mount the 3rd partition (ext2 filesystem). May be, if the filesystem on this partition is wrong, you can create a new.
mkfs.ext2 /dev/sda3 (or sdb3, sdc3...)
Mount this partition again.
Create a folder /.boot (don´t forget the dot before the "b"!)
Put the files  rootfs.tgz, rd.gz and zImage in this folder.
Unmount and disconnect the USB, connect network to the 313 and reboot.

Greatings,  the bear.

Stupid question: what format rd.gz and rootfs.tgz are??? Invalid magic and not gzip format error messages I got only ...

Thanks.

pcp wrote:

radir wrote:

CharminBaer wrote:

Yes, it´s possible.

Cut the imageheader away.   dd if=system.gz bs=8 skip=13 of=system_noh.gz

Stupid question: what format rd.gz and rootfs.tgz are??? Invalid magic and not gzip format error messages I got only ...

Thanks.

there is a header containing some info for the bootloader. you must strip it off and then you can work with the file as with a regular gz archive.

Ok, how? How long is this header?

CharminBaer wrote:

104 byte.
You can change both, but re-packing is a lot more difficult.
You need an 386-Linux, a tool from Dlink and an corresponding config-file for this.

That sounds mystical :-) So if I don't want to get overwritten everything (except user space /mnt/HD_a2) during boot time, other than getting that very special dlink tool+config file, there is no chance? Btw this tool is public or proprietary?

mkimage tool will create system.gz including 3 items rd.gz, zImage, rootfs.tgz; or can i (de)pack any of the 3 components indiviudally?

Did you change rd.gz not to overwrite everything?

Thank you very much.

Thanks, I will try. If I am going to play with linuxrc anyway, any suggestion what else, other than samba, can cause continuous reading/writing to hdd prohibiting standby?

[global]
log level = 0

syslog is writing logs too, cron daemon is accessing disk frequently, as well the atd. you need to kill all of them to put the disk into the sleep state.

Try "apt-get install ia32-libs" before...

CharminBaer wrote:

@radir

Success?

Sorry, i was net-less ...

Yes, thank you very much everything worked fine!

Now my root partition is not cleaned everytime.
Though one more question pls: do I need to add/remove header for kernel as well? I compiled a kernel but it does not start with, was wondering if it is because kernel is bad (not for this CPU or something); or because not used header?

CharminBaer wrote:

Exactly this is the reason why....

Just to clarify: need to add header to zImage too, right? As my compiled kernel does not start neither with nor without header ...
May I ask you to please send me/upload your kernel config file, if you used a customized kernel for your etch package?

Last edited by radir (2008-06-03 22:20:35)

I checked: you were right, all 3 files using header. But still no luck with customized kernel :-( Keep trying ...