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

Like I said in the other thread, I'm no linux guru - but I do have a little working knowledge.

1 - I have no idea if you do need it, but if you do, just put another insmod line directly below the first one - insmod $DIR/lnx_bin/ntfs.ko
2 - I think you're right, they need to be the same - they are names, making the name the same as the size makes then easier to remember.
3 - I don't think you can hot swap like you can with Windows, you might need to unmount, swap and then remount to avoid corruption.
4 - Not certain, but I'd call it fun_plug.
5 - There are a couple of possible trouble spots

Here's where I think you could get into trouble...

The command "mount /dev/sdd1" - is an instruction to mount the first partition on the fourth disk drive, and assuming you have two drives in the DNS-323, it is going to be incorrect, it will need to be "mount /dev/sdc1", if you have only one internal disk, it might have to be "mount /dev/sdb1"

If you do any reading - you may discover that "sda" refers to the first SCSI disk, and sdb the second SCSI disk - this can be slightly confusing when you consider that you have no SCSI disks, but SATA and USB - don't let it confuse you, linux thinks SATA and USB are SCSI.  If the drives are ATA, they will be hda, hdb and so on.

By the way - you can also do this interactively once you have telnet access and the necessary kernel modules loaded, before you create the script.

The heart of the script are these lines

===========================
insmod $DIR/lnx_bin/usb-storage.ko
  dmesg > $DIR/lnx_bin/logs/dmesg.out
  mkdir $DIR/usb_200 
  mount /dev/sdd1 $DIR/usb_200
===========================

Line 1 - insmod etc. is an instruction to install the usb-storage.ko kernel module
Line 2 - dmesg etc. is an instruction to output the device messages tp a log file called dmesg.out in a folder called /lnx_bin/logs/dmesg.out,
Line 3 - creates a directory or mount point called usb_200
Line 4 - mounts the first partition on the fourth disk to the previously created mount point.

I'm guessing that the DNS-323 specifically looks for a script named fun_plug - but I could be wrong.  Either incorporate the additional lines into the existing fun_plug or create a second script with a name of your choice and call it from fun_plug.

Well, no joy.  Tried running it via fun plug and that didn't work...tried typing the commands from the wiki manually in a telnet session and it seemed like the disc finally mounted, (had to insmod the ntfs.ko) but nothing ever showed up in My Comptuer...oh well...read more, try more...

fordem wrote:

where did you find it?  That and the the ntfs.ko kernel module?

http://dev.skcserver.de/dns323/

DNS-323 Talker - here's what I came up with so far - and I'm working interactively from the telnet prompt, with a USB flash drive.

insmod /mnt/HD_a2/lnx_bin/usb-storage.ko - this installs the kernal module
mkdir /mnt/HD_a2/lnx_bin/usb_test - this creates a folder in lnx_bin that serves as a mount point
mount /dev/sdc1 /mnt/HD_a2/lnx_bin/usb_test - this mounts the USB flash drive at the mount pointed created above

I then attempted to display the files on the flash drive

ls /mnt/HD_a2/lnx_bin/usb_test

and all were visible - I could also navigate to the usb_test folder using Windows Explorer and see my files and open them etc.

I did not use ntfs.ko which may just be because my flash drive is probably formated fat32 - I don't have a USB external drive hand to test with an NTFS formatted volume, perhaps in a day or two I'll get around to that.

If you compare my commands to yours , you'll realise that I skipped some of the shortcuts used - DIR=/mnt/HD_a2 - and typed the entire string in each command, and also did not perform some of the tests - if [ ! -d lnx_bin ] etc. - a properly written script will test to ensure specific conditions are met, where as I was just interested in a quick and dirty "proof of concept".

before disconnecting you need to issue an unmount command - for safety sake

umount /dev/sdc1

Hopefully my results will get you a little further in your quest - let me know how it goes.

Gave your short steps a quick try...didn't work, the mount fails for some reason.  "Mounting /dev/sdc1 on /mnt/HD_a2/lnx_bin/usb_1 failed." 

When I tried the insmod commands again this AM, it reported that the file already existed (I assume due to previous insmod commands).  Tried rmmod to remove it to start over, but got a "REsource temporarily unavailable" response.  don't know if this even matters...I presume once inserted I can leave those modules alone. 

So: #1 below said it was already there...#2 worked fine (creating directory) and #3 failed.

fordem wrote:

1. insmod /mnt/HD_a2/lnx_bin/usb-storage.ko - this installs the kernal module
2. mkdir /mnt/HD_a2/lnx_bin/usb_test - this creates a folder in lnx_bin that serves as a mount point
3. mount /dev/sdc1 /mnt/HD_a2/lnx_bin/usb_test - this mounts the USB flash drive at the mount pointed created above

Next step is to format a drive in my USB enclosure to FAT32 so I can see if NTFS is the problem.  My son took my only USB key to school recently and lost it, so the quick and easy way isn't availble at the moment...

Thanks for the help, I'll keep plugging away.  Fonz...if you know whether the ntfs issue is the key reason, appreciate any comments.  I got nfts.ko from http://dev.skcserver.de/dns323/

I was looking at dmesg and found this noting maximum mount count reached...anything to worry about?  Is each mount attempt failing because of this error?  umount doesn't allow me to unmount anything...the /dev/sdc1 syntax above fails with error ("invalid argument").  A umount command pointed at the mount point rather than device tells me the mount point doesn't exist even though it does and I can do an "ls" on it...strange.

dmesg wrote:

BusyBox v1.5.0 (2007-05-06 16:42:17 CEST) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ # mount /dev/sdc1 /mnt/HD_a2/lnx_bin/usb_1
mount: mounting /dev/sdc1 on /mnt/HD_a2/lnx_bin/usb_1 failed
/ # dmesg
<snip>
raid1: raid set md0 active with 2 out of 2 mirrors
EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
Link Layer Topology Discovery Protocol, version 1.05.1223.2005
dev is  <NULL>
usb 1-1: new high speed USB device using ehci_platform and address 2
/ #

Mount is also failing w/a 15gig FAT 32 drive in the USB enclosure attached to the DNS-323....arghhhh

Fordem...thanks.  I've rebooted to clear things out and start fresh.  Commands are not in my fun_plug, as I'm still not quite sure how to add them to it...another path to figure out. 

Fonz...I'll try proc/partitions now and see what I get. 

With the USB drive off I get the following, the same as in the post you pointed me at:

proc/partitions wrote:

/ # cat /proc/partitions
major minor  #blocks  name

   7     0       5120 loop0
  31     0         64 mtdblock0
  31     1         64 mtdblock1
  31     2       1536 mtdblock2
  31     3       6336 mtdblock3
  31     4        192 mtdblock4
   8     0  488386584 sda
   8     1     530113 sda1
   8     2  487853887 sda2
   8    16  488386584 sdb
   8    17     530113 sdb1
   8    18  487853887 sdb2

When I insmod usb-storage.ko and ntfs.ko and then connect the usb drive the cat /proc/partitions adds two entries!!

8   32  78150744  sdc
8   33  78148161  sdc1

Yay!!  Progress...

Trying mount command: 

mount /dev/sdc1 /mnt/HD_a2/lnx_bin/usb_1

No error!!!

Uh oh...new problem.  When I try to browse (from telnet or Windows GUI) I get errors. 

- ls lnx_bin/usb_1   -  I get "System Volume Information" in blue, but nothing else displays
- Browsing from Windows GUI:  when I double-click on the usb_1 directory I get error message - "G:\lnx_bin\usb_1 is not accessible"  Access is denied.

I checked properties and the usb_1 directory CHMOD is 500...read/execute for owner, no write for owner, no access for group or public.  I tried to change properties using CHMOD (CHMOD a+wx usb_1) but got error message:  CHMOD: usb_1: Read-only file system

I tried umoun to unmount and then created a new directory (usb_80) and mounted to that directory with the same results. 

So I think I'm closer, but still no cigar....but at least I'm a little more optimistic now... 

Mounting ntfs is a bit tricky. Also, there's no ntfs write support until very recent linux kernels. Since I don't have any ntfs drives/sticks, I haven't tested the following (umount, first):

mount -o umask=0222 /dev/sdc1 /mnt/HD_a2/lnx_bin/usb_1

This should adjust permissions to dr-xr-xr-x.

1

I think, ntfs write support was added around 2.6.16. So either D-Link upgrades the kernel or someone else make a recent kernel work on the box... we'll see what happens first :-)

Better create a new script /mnt/HD_a2/fun_plug.d/start/mount-sdc1.sh:

#!/bin/sh
insmod /..../usb-storage.ko
insmod /..../ntfs.ko
mount -o umask=0222 /dev/sdc1 /mnt/HD_a2/lnx_bin/usb_80

Though I don't think you want it this way....
- you need to umount the drive before you detach it from the dns323
- you don't want to reboot after re-attaching it, right?