Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I suspected my system file is not clean. I saw this message on the status web admin:
Hard Disk Info:
Volume Name: Volume_1 Volume Type: RAID 1 Sync Time Remaining: Degraded Total Hard Drive Capacity: 490402 MB Used Space: 268675 MB Unused Space: 221727 MB
The Sync Time shows Degraded. what does it mean actually?
How to actually perform e2fsck for my RAID 1 Volume_1 hard disk? I just have no idea how to begin with...
Offline
A degraded status means that the DNS-323 thinks the two drives that form the RAID1 array are not in sync - e2fsck will not fix it.
Start by backing up your data - if you're running firmware prior to 1.06 I'd suggest you hold on, there's another forum member who has written scripts to deal with this, he'll respond to you at some point, if you're running 1.06 or later, there's a manual rebuild feature in the webGUI that will fix it.
Offline
Please post the contents of
mdadm --detail /dev/md0
Offline
You may force an array resync. You may want to backup your data first, as suggested by fordem. You also need telnet built into the firmware, *or* load a telnet server into a USB flash stick by loading the usb-storage module, and modify the fun_plug script accordingly.
You will have to unmount and disassemble the RAID.
umount /dev/md0 mdadm --stop /dev/md0
then re-assemble it adding a forced resync:
mdadm --assemble /dev/md0 --update=resync
I strongly recommend _not_ to remount the array while it resyncs. You _can_ remount and access it while it is resyncing, but _personally_ I would not recommend to do so.
I always walked these steps and I never had any sort of problem. Though, other users may have better suggestions.
Offline
masterz3d wrote:
You may force an array resync. You may want to backup your data first, as suggested by fordem. You also need telnet built into the firmware, *or* load a telnet server into a USB flash stick by loading the usb-storage module, and modify the fun_plug script accordingly.
You will have to unmount and disassemble the RAID.Code:
umount /dev/md0 mdadm --stop /dev/md0then re-assemble it adding a forced resync:
Code:
mdadm --assemble /dev/md0 --update=resyncI strongly recommend _not_ to remount the array while it resyncs. You _can_ remount and access it while it is resyncing, but _personally_ I would not recommend to do so.
I always walked these steps and I never had any sort of problem. Though, other users may have better suggestions.
Thank you very much for your tips., though I could not test it right now. Just to share, my right HDD was sent back to the computer shop last weekend (the maxtor apparently give me 3 year warranty!). So right now, my DNS-323 is not running although it still can run perfectly with single HDD (Seagate Barracuda).
Just to ask anyone, if later when I receive the replacement/repaired, how to reconstruct those two HDD back to RAID 1 config without deleting/reformatting both of the HDD. Does your steps above can be used?
How to manually reattached the new empty HDD with an existing HDD back to RAID 1 configuration?
Offline
By the way, you will not be able to unmount the array, as it is in use by the system without going through the proccess above of USB or other ways. If you post the results from the detail, we will know which drive is the issue. Once we know that, you can remove it from the array and add it back in. It will sync start automatically, and you can do this with out worrying about data loss and without having to have telnet running from USB or any of that.
However, since you are getting a new drive, there are some serious complecations to manually reconfiguring. First you have to form the correct partition structure and format them. Next, you have to copy / modify the configuration files in several locations. finally, you just need to add the drive to the array. Most likely, you will want to insert it and let the web GUI take care of this for you. In a perfect world, this will work, but the DLink web GUI has been known to format the wrong drive. I STRONGLY suggest that you back-up the data you have on it before attempting to put the new drive back in. Better to be safe than sorry.
Last edited by bq041 (2009-05-01 21:07:16)
Offline