Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
Hello,
I am running a CH3SNAS for 2 years now. I run ffp from usb. Until today I had one hard disk (WD10EADS, left bay).
Running fine.
Today I inserted a new hard disk (WD15EARS, right bay). Turning the CH3SNAS on does succeed, but the fun_plug script is no longer triggered/started. No entries in fun_plug.log / ffp.log.
The default NAS functions do work like the web interface and samba. It does show the default shares (Volume_1, web_page, lp), so my custom shares are not loaded (which is logical because funplug hasn't been started at all).
The web interface does run, but is only accessible by IP (previously it worked by hostname (NAS)) also. Same for samba. The web interface detected the new hard disk and wants to format it. I skipped this step because I need a manual format due to 4K cluser size.
If I remove the new hard disk, eveything turns back to normal, funplug runs, custom samba ok, ssh ok, etc, etc.
What could be the issue?
Thanks for any info,
Opper
Offline
I would guess that you have the original drive in the left hand slot, where with a single drive it is Volume_1 and with two drives it becomes Volume_2. Even if you run ffp from a USB stick, I believe the initial call to start ffp comes from a script on Volume_1, so that when you insert the new drive which becomes Volume_1, the script is missing.
Swap the drives around or copy the script and related files to the new disk.
Offline
Thanks, I'll try swapping, but I am not sure it will help.
The Volume_1 that I am seeing via samba is the 'old' hard disk, containing all data and the previously working funplug stuff.
What is th official bay for Volume_1? I tend to think I checked that out when I got the NAS.
UPDATE: Just formatted the new disk from the web interface, and now I have Volume_1 (the existing drive) and Volume_2 (the new empty drive).
But funplug still doesn't start. No ffp.log, nothing.
Last edited by Opperpanter (2010-06-03 20:23:41)
Offline
Here's the first part of my fun_plug script:
#!/bin/sh # switch to safe working directory on ramdisk cd / # write a log, in case sth goes wrong FFP_LOG=/mnt/HD_a2/ffp.log #FFP_LOG=/dev/null exec >>$FFP_LOG 2>&1 # real path to ffp FFP_PATH=/mnt/HD_a2/ffp # where to search for the install tarball FFP_TARBALL=/mnt/HD_a2/fun_plug.tgz # setup script (used for ffp on USB disk) FFP_SETUP_SCRIPT=/mnt/HD_a2/.bootstrap/setup.sh # rc file path FFP_RC=/ffp/etc/rc echo "**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****" date
This means a ffp.log should be created with at least the last two lines in it!
Offline
Aha, just copied the fun_plug file and .bootstrap folder to Volume_2, and now I am seeing a log. So the new drive must have become HD_a2 now.
Offline
http://dns323.kood.org/howto:ffp#troubleshooting
This is a known issue. If you add a second disk, you better have the first in the right bay. Otherwise fun_plug will stop working unless you move it to Volume_2.
Offline
fonz wrote:
http://dns323.kood.org/howto:ffp#troubleshooting
This is a known issue. If you add a second disk, you better have the first in the right bay. Otherwise fun_plug will stop working unless you move it to Volume_2.
Must improve on my googling skills...
Thanks, I thought the left bay was the primary one.
Offline
Just to let any future visitors know: Fonz is right (as usual), and so is fordem.
Next challenge is to find out on which /dev/???? the usb stick is now.
EDIT: it's sdc1. I really need to change the usb loader to work by UUID instead of device name.
Last edited by Opperpanter (2010-06-03 21:07:49)
Offline
Pages: 1