Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I had my DNS323 set up with two 1 terabyte drives. All was well until I turned the D-link on this week to do some backups. I configured the system to run Raid 1 mirroring. For the most part I keep the system powered down, I turn it on to do backups only. I don't believe there is more than 20 hours of use on the system over the last year.
I looked at the Admin pages, it shows one drive 'degraded'. I looked around the forum , found this link -->http://inreto.de/dns323/fsck/ and followed the instructions. No problem installing. When I ran the command 'mdadm -A /dev/md0 /dev/sd[ab]2' i i got this response...
"mdadm -A /dev/md0 /dev/sd[ab]2
mdadm: /dev/md0 has been started with 1 drive (out of 2) and 1 spare."
It took about an hour for the command 'e2fsck /dev/md0' to complete. I rebooted, and the one drive is still pink.
The Raid Tool menu shows one drive at 1000 GB and the other at 0GB.
If I run Scan DIsk, it runs in a few seconds, and shows Failed as the results.
I did remove, and re-insert the drive on the side that is pink, I have Enabled auto-rebuild, however the status of the one drive never changes.
Not sure what to do next. Some questions I'm not sure on.
The failed drive is on the side with the pink disk light. Is this correct?
I'm guessing the drive has bit the dust. Is there any other solution other than buying a new drive and inserting it?
Is there a way to format the failed drive in the D-link? I want to be sure not to destroy the data on the working drive.
Offline
Well, I have dug the hole way deeper. This is very frustrating.
O.K. i d did a lot of reading in this web site. I have tried many things, nothing is helping.
I have fun_plug 0.5 installed, I installed it shortly after I installed the DNS323. Reading through the forums, I saw others having trouble running scan disk on the Tools menu. That is failing on my system. I saw one solution was to disable fun_plug, so I did. I renamed the fun_plug script on /mnt/HD_a2 and re-booted.
I wanted to see if scan disk would work then, it still fails, only a second or two after startup. Its like it never looks at the disk ( 1 Tera byte disks ) at all.
Then I realized I could not either telnet or ssh into the dlink anymore, since I had re-named fun_plug script.
Is there a way out of this mess?
Next, the Status panel shows Vulume_1 as a Volume Type - Standard. I had the two drives set up as mirrored originally. I can find any way to talk to the second drive. The system shows in the log it was removed, Yes, i pulled it out.
I did run fsck on the drives before I disabled fun_plug, and got the message it ran on one disk only ( see the above post for exact wording ).
The one disk seems O.K.
I have disabled 'Auto-rebuild'. I wanted to see if I could format the drive on the right side, the one showing the pink light. I get a warning "All data will be erased" so there doesn't seem to be any way to recover this drive.
Please, anyone, suggestions???
Offline
Enable the stock FTP server and rename the script.
Offline
FunFiler,
Thank-you for your reply. This is what I did. Once done, it took some more poking with the gui interface, and the Dlink finally gave me the opportunity to re-build the mirrored drive. It took some time, I left it alone to do its thing. The Status page now shows two drives. From what I can tell all looks well again.
It took me some time to find out how to re-connect and re-name the fun_plug script. For what ever reason I do not understand, my user ID's password was mucked up, I did not change it. I had used it many times, so I knew what it was. I could not connect with FTP until I created a new password for myself. Once I did, I re-named fun_plug script. Then I saw my user was back to the ash , I set that to bash, and now things are normal again.
I will see how this goes, if mirrored config fails again, I think I will abandon it and go with two separate volumes. We will see.
Offline
The mirror config has failed, again. I did some investigating, and found out I have the drives with 4k problem. It is ( apparently ) fixed by installing 1.10 firmware. I still have the 1.10b7 file installed.
1.10b7 would not format the failed drive, no matter what I tried. I installed the drive in my main system, and formatted the drive with ext3 file system. The disk has been back in the DNS323 for over a month, and is working normally. The config is as two separate drives, no mirroring.
For now, all is well.
Last edited by camorri (2012-01-19 18:46:49)
Offline