Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hey,
i was replacing a small disc(180GB) for a new 1TB disk.
i am running seperate volumes so i thought, pull out the disc put in the new one let it format en continue working.
guess what, both my discs are formatted and lost data from volume1(still the old disk i had in there) gone funplug gone videos and all.
Shit happens i know, the only good thing about this is that i can replace volume 1 with a new disc for it as welll that i have laying around.
so Bad things:
lost 180gb of data.
Good things:
i know have 2TB of storage in there instead of 360GB
greetings
HighWater
p.s. im now gonna convert them from ext2 to ext3.
Offline
This is actually not uncommon and is well documented on the forum. A reason I do not use the web gui to format my drives, and anyone who wants to do it that way, I reccommend taking out any drive that has data you want to same.
Offline
bq041, would you be willing to outline here or maybe in the Wiki some of the commands needed to maintain the RAID via telnet.? I'm sure I could crib stuff together from various places but if you're actually experienced with this particular product it would help immensely.
Offline
What do you want to know? I have a few scripts out there I wrote for creating and breaking raid 1 arrays, as well as updating the partition information when upgrading from 1.03 to 1.04 or 1.05 FW.
mdadm is the program used to work with the arrays. (mdadm stands for md administration) md is the device for an array. For example, the raid 1 on a DNS would contain block devices /dev/sda2 and /dev/sdb2, which would be joined into the array /dev/md0. Likewise, and leftover space setup as JBOD would be assembled into block device /dev/md1.
What I have found is that the biggest trouble comes from how DLink monitors the drives in the system. DLink uses configuration files that are stored on both hard drives and in 2 places in the flash. This is what makes manual administration difficult. The format is relatively simple, it is just making sure all of the files (12 of them) are all configured properly. To add to this, the physical serial numbers of the drives are stored in these files. These are what the DNS uses to invoke the ever famous "you must format" message. This is why you cannot just start swapping drives around. There also flaws in their script files. One example is the 94% error. I have done some testing and this usually happens when the DNS does not actually invoke the formatting of the drive. That is why data is still available after reboot. Formatting manually has resulted in 100% sucess.
Offline
I'm sure those scripts would be a good start. Are they in a forum thread somewhere?
If the web interface is to be avoided one would want to know how to setup/take down RAID 0 and 1 as well as replace a drive when it fails.
Offline
They are, just search the forum for upgrade 1.03, or click on my name and scroll though the posts I have done.
As for how to do simple things, google "man mdadm" and read up on mdadm. This will get you to be able to create and remove arrays, replace bad disks, etc. I have written out complete instructions on this forum in some of the threads, and you can find my scripst as well. Best to do is download the scripts and then go through them to see what is going on. I tried to remark them often, so people could tell what was going on step-by-step. My scripts are for running ffp on the hdd, so it involves rebooting. This is because I cannot unmount the primary boot disk. If ffp was running on a USB drive, or from RAM, then work could be done directly, as both drives could then be unmounted. I just have naot had time to sit down and modify them. I did make the upgrade one in a modular format so it can be pieced together in a variety ways.
Offline