Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I know everyone says it's impossible for fonz's fun_plug script to brick your NAS, but something happened to mine, although I'm not sure what would have caused it. I threw a few 1.5TB drives in mine, upgraded the firmware, then after it rebooted added a few movies. My PS3 saw them, so far, so good. Then, however, I added the fun_plug shell script and .tgz archive to the root level of the drive, made the script +777 from the CLI, and rebooted from the Web interface, after which the light just kept blinking and the 321 never came back up. Could have just been a bum unit, but it seems odd that it broke right after I tried to get fun_plug going. Does anyone have any suggestions? I had multiple partitions - could that have changed some mountpoints and had the script overwrite something in flash when it unpacked the archive?
Offline
fritter,
I have FFP running on my dns-321 with no problems.
From what I can see, the only thing that could happen with FFP that would come close to bricking the system would be a powerfailure during the store-passwd.sh step. This could leave the flash in a bad state. Otherwise, it does not touch the flash.
I'm not sure what you're experience level is with linux/computers, ... is, but here are some interesting things to try that should be possible at just about any level.
First, make sure power and ethernet are plugged in properly. (Since you have lights, power is probably ok.)
Second, remove both drives, carefully noting which came from the left and which from the right bay, as (originally left) and (originally right) and then reboot/ powercycle.
if you can see the web interface when it boots, whatever is causing the problem is quite likely to be on the drives. Furthermore it's likely to be on the (originally right) drive.
if you cannot see the web interface, try doing a hardware reset. There
is a procedure documented somewhere on this site involving the reset
button on the back. This restores the original firmware configuration,
but not the firmware itself. Try rebooting by powercycling. If this
doesn't work, your out of my range of expertise, but
something is messed up with the unit or firmware.
Assuming that (Second) ended up with a problem on the drives, place the drive from the Left bay into the Right bay, leaving the left bay empty. Try rebooting. If it works, the issue is on the (originally right drive). In this case, you should be able to bring up the system with both drives in place, but swapped from the original configuration. Using the basic SMB mounts or ftp, remove anything that looks like fun_plug on the (originally right) drive.
If none of that works, your best bet, if you care about preserving your data, is to find a running PC linux box with a SATA connector and see what's on the drive. It's just an ext2 filesystem that such a box can read.
If you don't care about the data and you can get any configuration going, you can always reformat.
Offline
talkingRock wrote:
It's just an ext2 filesystem that such a box can read.
Providing you are booting your pc with linux or have installed the ext2ifs driver for the ext2 FS.
Offline
Yes. I did mention linux, but forgot to mention the ext2 drivers for windows.
I have had decent luck using those in a read-only mode, but really mixed results for the rw mode.
Offline
RW mode has worked quite well for me - on the admittedly few occasions I have needed it.
Offline
fordem,
That's interesting. Which of the two tools and which version has worked well for you?
Which windows os and version are you running?
Offline
Windows XP Pro/SP2 & EXT2IFS Ver 1.11
Offline
I was using EXT2IFS on Win2k sp4+ I don't recall which ext2ifs version.
Offline