Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
i was running a raid mirror on my dns-323 and now it's gone and mounting the two disks. they're out of sync now and although i'm pretty comfortable with linux, i've got no experience using the md tools for software raid management.
any advice on rebuilding this raid and getting it back in order. the admin interface threatens to reformat (thanks d-link).
cheers.
.z
Offline
looks like you updated from v 1.01 to 1.03 straight away and did format your drives with ext3. this format is not supported since v1.02 anymore. It really shows a great disrespect from D-Link not to inform you that you gonna loose your data by changing the firmware. I had the same when I updated from 1.01 to 1.02. fortunatly I haven't had any data on the drives than.
Maybe, change back to v1.01 and live with it or save all data while running v1.01 and than change firmware.
Last edited by elch (2007-04-11 01:08:11)
Offline
I know it's too late to say this now, but after reading some posts in these forums I realized that I should NAS always backup everything before a firmware update.
Offline
i was running 1.02b with ext2fs and upgraded to 1.03. it might have been the downgrade to 1.02b that broke it. but i think it was showing up as two seperate volumes on 1.03. can't be sure now.
it's not a big deal, i can rebuild it as long as all the raid tools are on disk. i just thought someone with linux raid experience could help me out. i'll get back to you here if no one steps up.
Offline
Anyone know how the DNS-323 checks to see if you are running RAID 0, RAID 1 or JBOD on boot up? I rebuild my RAID, but lose it on every reboot. i combed the startup script and web interface but there's some binaries involved and setting it through the web interface threatens to reformat my disks. i'm in a bind here. i'm trying to manually get the RAID1 back without reformating.
Offline
Here´s what I did.....
Drives in place. Goto set "RAID type reformat" chose RAID 1. Set size of RAID1. REMOVE drives!!!
Start format. It will go up to around 94%... Power off the DNS-323. Put drives back in place. Power On. Voila!! Now you should be happy :-)
Offline
awesome. crude, but that did the trick.
Offline
What I find scary is that the unit never detects that the drives are missing.
Offline
I'm reading a lot about RAID 1 issues in this forum. What's the benefit of RAID 1 if it is so sensitive to any firmware upgrade and re-synching of disks? Sounds like RAID is a bit "overraided" ;-)
Given the relative failure rate of disks being rather low anyway, I find that a standard setup (2 independent drives) with a primary disk that I use to access all my data which is backed up on the second disk with a daily/weekly rsynch cron-job would be more robust. Since I'm using the NAS mostly as a datastore and not as a replacement for my laptop's hard drive, I still get enough data protection in case of a hard drive failure. I'm curious to hear other opinions on this, but so far I'm satisfied with my low-tech RAID alternative.
Offline
valid point. i am disappointed in the stability of raid on this device.
i like RAID 1 and my thinking has always been, as cheap as disks are now days, double the cost of the storage for a more than double increase in data security. i also can't really be bothered trying to piece out data to backup and maintain and monitor backup scripts. my laziness and perception of more important things in my life is a point of failure for my data security. as i think it is for most people.
all this and the growth of digital media in our lives (hello digital cameras), i've been waiting for an affordable RAID 1 NAS for a while.
Offline
Let's just say that properly implemented RAID works and works well.
I've been very disappointed in the DNS-323 - at least as far as it relates to RAID and disk failure - I installed my first RAID array back in 1996 and I would not consider any server implementation without some form of redundant disks. I have lost track of how many disks I have changed over the years, but, it's usually a matter of walking up to the system, looking for the disk with the amber light on, pulling it out and putting the new one in it's place.
Sitting in my rack about 2U below my DNS-323 is my IBM xSeries server - it cost me just a little more ($470) than the DNS-323 plus disks ($428) - it's got RAID, and it works - it knows when I yank a drive out and when I put one back. Sometimes a power outage will knock the mirrors out of sync, the RAID controller knows when it happens and fixes it.
On the other hand - the D-Link DNS-323 is smaller, sleeker & quieter - it probably costs less to run. If a disk fails - I haven't actually had a disk fail, I yanked one out to simulate a failure - you get no warning at all, at least prior to 1.03 - I put a couple of disks in with bad sectors, it doesn't know that the disks have bad sectors - I put in a disk that worked but failed SMART, the D-Link never warned me - my IBM would.
Don't put down RAID because D-Link's implementation sucks - the problems are all in how this particular unit implements RAID and detects disk errors
Offline
Fordem,
I would be nice if you could restest with the latest firmware. If I recall correctly the kernel is upgraded in the 1.03 to 2.6.12 or something. Previous version of the kernel was 2.6.6 which has less support for smart on sata drives. So it might work with firmware 1.03.
I haven't upgraded myself yet so I can't test and I don't have any disks with broken sectors.
Offline
Will do.
Actually - I've stuck at least two drives that were supposed to be defective in it since upgrading to 1.03, and both times it sat with the led corresponding to the drive flashing blue - it didn't appear to detect the drives, as there was no change in the status screens, and no emails - and it most certainly didn't flash amber which I think is what it is supposed to do.
I didn't install the drives in a PC to see what the PC would tell me, but, I'll do that within the next week or so and repoart back.
Last edited by fordem (2007-04-22 03:24:58)
Offline