323 firmware 1.06 not detecting fun_plug on reboot - wtf?
Published February 11th, 2009 in dns-323, hacksHey all… Just wanted to write a quick post asking if anyone else has had issues with firmware 1.06 not loading the ffp modules after a reboot? I’m not sure if it’s 1.06 or if I broke something while tinkering, but I simply cannot get the 323 to pick up the fun_plug on the reboot. Anyone else experienced this? I’ve troubleshooted to absolutely no avail. I can get in via SMB and the normal admin interface, but cannot telnet or ssh and none of my custom scripts are running. Basically, the fun_plug is not being picked up after I reboot. Volume_1 and Volume_2 are still the same and haven’t been swapped.
Figured I would ask before I hose my /ffp directory and start over again :) Let me know in the comments!
Update: Dropping the fun_plug back in along fun_plug.tgz seems to have done the trick! No swapping of drives required. Kept all my scripts in the same place, everything now works as expected. Strange.
Try swapping the drives. I know they haven’t been swapped but it worked for me.
I didn’t install fun_plug until I had upgraded to v1.06, and no problems rebooting so far. Mind you, I think you’re talking about the fun_plug “installation”, which would have only occurred once on my system.
That sucks man. Hope you get it figured out! I’m eagerly awaiting the conclusion to your USB article! =)
I upgrade to 1.06 and had no issues fun_plug worked fine. Although I did notice after the first reboot it took a few minutes for SSH to actually come up.
Ok need some help here. Just picked up the 323 along with two 1.5 TB drives. Right away I had to update the firmware to 1.06 in order for it to even see the 1.5TB drives correctly. Now I’m trying to setup ffp but am not have any luck. I’m using an iMac (in case it makes a difference). I’m setup as Raid 1, I can go to finder and mount the drive (smb://ip) fine and see Volume_1 as the drive on my desktop. I went and got the two files fun_plus.sh and fun_plus.tgz and copied them to the drive (actually I went to the website, right clicked the files and did download liked file as and saved directly to the 323. I then reboot the 323 by holding the power button down. It comes up and the tgz file is still there, no new directories created, nothing. Even after waiting about 10 minutes. Any idea why this isn’t being run? Anyway to manually kick it off or force it?
Thanks
Jamie
I too have the same problem. After reboot, I can’t telnet to it. I tried ssh into the NAS but after entering my root login and password, it shows
“login as: root
root@192.168.11.196’s password:
BusyBox v1.00-pre1 (2008.09.02-11:43 0000) Built-in shell (ash)
Enter ‘help’ for a list of built-in commands.”
I can’t do anything. Then I drop fun_plug and fun_plug.tgz and reboot the unit.
Everything back to normal as of nothing changed except I need to setup my root login credentials again.
It did not work for me either Firmware 1.0.7
But I found out why
Actually, the problem was so simple. Lost several hours googling and almost gave up. lol
Once you got the 2 files: fun_plug without any extension (no .sh) and the other tgz file.
You do need to download cygwin in my case for windows, map the drive of the nas 323 to any letter.
eg. L: drive map to the nas Volume_1 file where the files are. You need to to that for cygwin to access
Next, install cygwin (remote install takes a little bit longer) be patient.
Launch cygwin
cd L: drive
Run : chmod 777 fun_plug to make it executable
That was the problem why it was never executed!
Hope it helps!
I have the same problem as Jamie. Except that i run it on 1.07 firmware. The two files are still there after reboot, and nothing happens.
You must place the fun_plug and fun_plug.tgz files on the drive sitting in the right slot
regardless of Volume.
I have firmware 1.07 and am also encountering this issue, however when i do chmod 777 on the file its says permission denied? When I figure out the issue I will post again.
so what i did was go into the NAS HTTP management interface (192.168.0.253 - for me anyway) clicked on advance then Network Access and I noticed the user I created ‘Phil’ was on read only, so I deleted that permission and created a new one for the entire volume_1 and made sure it has read/write access, saved. Then I tried rebooting again just for the heck of it and it worked!! I was using fun plug 0.5, hope this helps someone
Having similar problems, just can’t get the DNS-323 to access the fun_plug.sh (and then respectively the fun_plug_tgz) to setup telnet or else. The files just sit there and nothing happens. Copied those with FTP inside the Volume_1 root directory, permissions are 0777 and all. What could be wrong?
The setup is:
- fun_plug v0.5
- only single WD 2TB HDD in the _left_ slot (as instructed by the manual for single HDD setup)
- 1.08 firmware for the DNS-323
- browser access, ftp and accessing the drive via smb work fine (well some problems loosing the drive occasionally)
- using Macbook Pro
Any ideas?
Got it working… my Macbook renamed the fun_plug to fun_plug.sh and thus it was not found by DNS-323…. now it works perfect