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

Hi Fonz,

It is a great ida but it did not work for me on /mnt/HD_a2/fsck. The fsck instals fine, executes OK but still no telnet access after 5 minutes.....
DNS-323 can be shut down from the front panel and after restart the old system is back.

SD

Last edited by skydreamer (2008-07-20 22:23:31)

/mnt/HD_a2/fsck # ls -l
-rw-r--r--    1 1000     1000         2314 Jul 20 15:53 README.txt
-rwxr-xr-x    1 nobody   501          1620 Jul 21 00:17 debug-reload.sh
-rw-r--r--    1 1000     1000      2595046 Jul 20 15:31 fsck-initramfs.gz
lrwxrwxrwx    1 1000     1000           17 Jul 20 19:14 initramfs.gz -> fsck-initramfs.gz
-rwxr-xr-x    1 1000     1000         1606 Jul 20 15:44 reload.sh
-rw-r--r--    1 1000     1000        16746 Jul 13 14:50 reloaded-2.6.12.6-arm1-fonz.ko
-rw-r--r--    1 1000     1000        16746 Jul 13 14:50 reloaded-2.6.12.6-arm1.ko
-rw-r--r--    1 1000     1000        16427 Jul 13 14:50 reloaded-2.6.6-arm2.ko
lrwxrwxrwx    1 1000     1000           15 Jul 20 19:14 zImage -> zImage-2.6.25.1
-rw-r--r--    1 1000     1000      1974476 Jul 20 14:37 zImage-2.6.25.1
/mnt/HD_a2/fsck # ./debug-reload.sh
+ sync
+ mount -o remount -r /mnt/HD_a2
mount: mounting /dev/md0 on /mnt/HD_a2 failed: Device or resource busy
+ mount -o remount -r /mnt/HD_a4
+ mount -o remount -r /mnt/HD_b4
+ mount -o remount -r -a
mount: mounting rootfs on / failed: Invalid argument
mount: mounting /dev/root on / failed: No such file or directory
+ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
proc on /proc type proc (rw,nodiratime)
/dev/loop0 on /sys/crfs type cramfs (ro)
/dev/md0 on /mnt/HD_a2 type ext2 (rw)
/dev/sda4 on /mnt/HD_a4 type ext2 (ro)
/dev/sdb4 on /mnt/HD_b4 type ext2 (ro)
none on /proc/bus/usb type usbfs (rw)
devpts on /dev/pts type devpts (rw)
/dev/md0 on /opt type ext2 (rw)
+ sync
+ sleep 1
+ insmod /mnt/HD_a2/fsck/reloaded-2.6.12.6-arm1.ko machtype=1542 kernel=/mnt/HD_a2/fsck/zImage-2.6.25.1 initrd=/mnt/HD_a2/fsck/fsck-initramfs.gz cmdline=console=ttyS0,115200 ip=192.168.111.61::192.168.111.254:255.255.255.0:jumbo:eth0:none

skydreamer wrote:

It works with your modified script- I have broken the telnet connection and managed to reconnect again. The button is finally dead.

That's good news.

I think the shell is the problem. On my box /ffp/bin/sh was a link to bash. After changing it back to busybox, it stopped working like yours. For the moment, you should be able to run the original script (which I highly recommend, because it properly cleans up before booting) with

bash ./reload.sh

skydreamer wrote:

Thanks Fonz but where is bash? (ffp 0.5)

Come on, packages are at http://www.inreto.de/dns323/fun-plug/0.5/packages/

cd /some/temp/dir
wget http://www.inreto.de/dns323/fun-plug/0.5/packages/bash-3.2-3.tgz
funpkg -i bash-3.2-3.tgz

KyleK wrote:

I just tried it on my CH3SNAS, but when issuing the "free" command, there's no space reserved for swap. The complete line shows only zeros.
Also, when typing "mount", none of my hard drives show up. Shouldn't they be listed as ro, anyway?

Glad it's booting on a CH3SNAS, too.

What's the swap paritions on a CH3SNAS? fdisk -l should show.

On my DNS-323, it's:

root@bob:~# fdisk -l | grep swap
/dev/sda1               1          66      530113+ 82 Linux swap

After you found out, you can activate it manually with:

swapon /dev/sda1

KyleK wrote:

Also, when typing "mount", none of my hard drives show up. Shouldn't they be listed as ro, anyway?

No disks are mounted, not even ro. But it's simple enough to do: mount -r /dev/sda2 /mnt (-r for read-only)

I don't think it's a good idea to have them mounted, even ro. Although an ro-mount can't cause damage, e2fsck might change stuff on disk, making the filesystem caches inconsistent.

KyleK wrote:

But after using the reload.sh script and logging back into the CH3SNAS via telnet, "fdisk -l" has no output at all.
Looking at /dev, there are no sd* devices listed whatsoever.

I get the normal output:

root@bob:/sys# uname -a 
Linux bob 2.6.25.1-ffp #1 Sun Jul 20 15:37:41 CEST 2008 armv5tel unknown
root@bob:/sys# fdisk -l | grep swap
/dev/sda1               1          66      530113+ 82 Linux swap

Maybe the kernel doesn't detect the CH3SNAS SATA controller?
The DNS-323 rev A1 is a DB88F5181 SoC, I think the DNS-323 rev B1 and CH3SNAS have a different (but mostly compatible) SoC:
http://dns323.kood.org/forum/p5797-2007 … html#p5797

Can you post your output of (with Linux 2.6.25.1 running):

root@bob:~# dmesg | grep -i mv
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
Orion ID: MV88F5181-Rev-B1. TCLK=166666667.
MV-643xx 10/100/1000 Ethernet Driver
sata_mv 0000:00:01.0: version 1.20
sata_mv 0000:00:01.0: Applying 60X1C0 workarounds to unknown rev
sata_mv 0000:00:01.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
scsi0 : sata_mv
scsi1 : sata_mv
scsi2 : sata_mv
scsi3 : sata_mv

KyleK wrote:

I assumed the drives would be listed when issuing the "mount" command since the reload.sh script speaks of "remount file systems as read-only".

Purpose of reload.sh is to shutdown the current system, and then initiate the reboot. remounting filesystems read-only is part of the shutdown. The 'insmod' at the end triggers the reboot and does not not return, so the last line won't ever be executed if all goes well.

KyleK wrote:

I've attached the complete dmesg output, maybe it's of help to you.

Thanks. I found a recent commit in the orion kernel git tree that looks relevant:
http://git.kernel.org/?p=linux/kernel/g … 25a563f8db

I'll have a look and try to build a new kernel. For now, CH3SNAS won't work.

fonz wrote:

I've updated my filesystem check tools at http://inreto.de/dns323/fsck

fonz,

Following your excellent instruction bash and the latest fsck tool were installed and run. From what I understand of Linux (I'm still new at this!) and the messages that displayed during the operation, all worked well. I do have a couple of questions though;

1) Executing uname returns "Linux DNS323_NAS 2.6.25.1-ffp #1 Sun Jul 20 15:37:41 CEST 2008 armv5tel unknown". This is not what the README.txt indicates I'll see. Is the "unknown" part okay?

2) Executing e2fsck /dev/sda2 returns

 /dev/sda2: clean, 13321/38944768 files, 11556902/77881111 blocks

Can I assume the word "clean" in this statement means everything on sda2 is great?

3) Upon reboot dmesg showed the following;

RAMDISK: Compressed image found at block 0
usb 1-1: new high speed USB device using ehci_platform and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.2: new full speed USB device using ehci_platform and address 3
usb 1-1.4: new high speed USB device using ehci_platform and address 4
EXT2-fs warning: maximal mount count reached, running e2fsck is recommended

What does the warning on the last line mean?

Output from dmesg is attached for reference.

Bob Blackwell
Pickering, ON

Last edited by rcblackwell (2008-07-22 04:08:49)

---

Attachments:
dmesg.txt, Size: 7,427 bytes, Downloads: 940

KyleK wrote:

Apparently, no SATA hardware is detected by the kernel

I've uploaded a new kernel: linux-2.6_orion
This is the current development kernel. To use it, download the updated files, relink zImage, and boot:

cd /ffp
rsync -av --delete inreto.de::dns323/fsck .

cd fsck
rm zImage
ln -s zImage-2.6_orion zImage

./reload.sh

Please repeat the dmesg | grep mv step first. If it now detects the sata controller, do a read-only mount first and see if the files look ok.

KyleK wrote:

Unfortunately, with the orion 2.6 image, I'm not able to log in anymore via telnet. PuTTY tries to connect but closes after a couple of seconds.

You did also fetch the new fsck-initramfs.gz, didn't you? On my dns-323, the orion kernel doesn't acticate the nic properly, too. I had to modify the initramfs to 'reactivate' eth0.

KyleK wrote:

I did update via your rsync command, I assumed it would fetch all the necessary files?

Yes, sure. Please update again. There's another obvious option: use plain old 2.6.12.6.
I've added the 2.6.12.6 to the directory and made it the default for now. Since nobody complained about the 2007 version of fsck, I think that kernel will work for you, too.

KyleK wrote:

One thing I noticed though: I can't access fanspeed or temperature, as the directory /sys/class/i2c-adapter/ is empty (there's no i2c-0).

Only present in vanilla kernels. 2.6.12.6 is the D-Link kernel with a (strange) different interface for fancontrol. The tools needed for the old kernel are not yet included in the ramdisk...