Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Well I bought one of these devices and put in two Seagate 200GB hard drives (ST3200820AS) and it went right up and started runnning. Upgraded to the new firmware 1.2 and this ran fine for 10 days. I went on a trip and when I came back it had locked up. It wouldn't even power down by holding the power button as instructed. The only thing I could do was ping the device, but i could not access any of my folders. Did a hard restart and then it never came up again. It would act like it was going to during the power on portion, but as soon as it was time to access the hard drives, the NAS would shut itself down abruptly. I finally got it going by pulling one of the drives out,then it would start fine. I had it on RAID 1 (mirroring) and EXT3 but when I upgraded never reformatted the disks to put it to EXT2. I thought this was it, but reformatting doesn't help. When I reboot it with one, i can go ahead and put the second one in and it will recognize it. That's how I did the reformat of both. I even tried at one point to downgrade back to 1b - that helped for a little while. however, after shutting down the system a few times, it started doing the same thing. Please let me know if anyone is having the same problems or if you think i am missing something.
Thanks.
Offline
Oh, one more thing. I think maybe nobody has noticed the problem because they have never shut down the system all the way (like power OFF). You can do this through the utility -> system area..shutdown if you have 1.2, or you can do it through the front button by holding it for a few seconds until it starts to blink. THEN turn it back on and see what happens. Remember, I am using RAID 1 and 2 disks. 1 disk will always work from what I have seen..
Offline
Hello Gazoo:
What did you see after power-on the unit??? Did you see the power led keep blinking without stopping???
Offline
You have probably hardware related problem here. Check your disks for bad sectors and try to swap bays if one disk works fine. Also maybe get telnet access and check dmesg.
Offline
If the firmware's anything like that of the DSM-G600, then fsck never gets run on start-up, so any file system problems which are almost bound to happen when the power is cut without shutting down properly will remain. Unless I've misread the original post, all the RAID controller does is to replicate the corrupted file system from one drive to another, so the drives don't really get reformatted.
As sala says, your best bet is to get telnet. I recommend you run fsck to repair the file system. I've had to do this a few times myself with the DSM-G600.
Offline
Lets assume you have telnet access and a RAID1 (mirror) /dev/md0 with v1.02 firmware,
what would be the procedure to run the fsck? (this has always confused me with a RAID)
1. telnet to DNS-323
do you unmount the RAID #umount /dev/md0
do you run fsck on /dev/md0 or /dev/sda1 or /dev/sda2 or /dev/sda3
how to you choose which disk to fsck or do you fsck both sda(1,2,3) and sdb(1,2,3)
do you fix one drive sda and re-sync sdb (not exactly sure how to re-sync?)
do you fix sda and copy to sdb (dd if=/dev/sda1 of=/dev/sdb1)
then remount the RAID #mount -a or # mount /dev/md0 /mnt/HD_a2
//Mig
Offline
The unit does the following when I try to power it up:
Lights blink as normal, but after 5 seconds or so when it's time to power up the hard drives, the whole thing shuts off completely - no power, no lights, like you pulled the plug. It does start if I take out one drive OR the other.
I've swapped them, reformatted them as raid, single, JBOD, etc. Doesn't stop doing this.
How do I reformat these? Is it worth downgrading to 1.01b and running the scandisk, defrag, etc.? Can I put them in a PC and reformat them and then try again?
I have a linux box, but it's an old P2 with no SATA drive support. Please, keep the comments coming - I am only a few days from returning it..
How do I get telnet running to this? And when/if I do, how do I run the checkdisk?
THANK YOU!
Offline
gazoo, it sounds like a power supply problem, could you get a replacement power supply from a friend to test?
Offline
Nope, I'm the first one to get one of these around here. It did work when I got it new AND it works if I boot with one drive, then put the other one in hot swap style..
Offline
gazoo the easiest thing is to try the disks in another DNS-323 but since this is not an option dmesg is your friend, you need to install telnet as explained elsewhere (the rar'd file is the best).
If the box dies after 5 sec's but you can still ping it the chances are that the telnet will be alive.
Perhaps destroy all partitions with fdisk on a PC, recreate them and fully format the drives (even NTFS is fine), this will check the drives for errors. It would be more elegant to use smartctl to run a full internal SMART test but this is way beyond this forum, you can read more about it on smartctl pages.
Destroy the partitions again and plug the disks back into DNS-323.
Offline
Gonna try that tonite. Thank you.
Offline
Reformatted the two drives in windows using ntfs, and then removed the partitions. STILL DID THE SAME THING - Starts up for 5-10 seconds, and when you here the two drives start to spin up the whole thing POWERS ITSELF OFF ABRUPTLY. I've sent this back as defective and will receive another one in 2 days and will let you know if it really was defective or if the DNS just stopped liking my drive model numbers.
Offline
Turns out I had a defective box. Just got my new one, used the same disks, and all seems well so far. I will let you know if it loses files on transfer or otherwise acts up but so far so good!
Offline