DSM-G600, DNS-3xx and NSA-220 Hack Forum

What firmware version was the RAID array created with?

There is another thread in here that suggests that this message results from the disk partition structure being created by an older firmware revision not being recognized by the new firmware.

You are missing the configuration partitions required for F/W 1.04 and 1.05.  I've walked a couple of people through converting.  It can be done without losing your data, but it takes a little bit of time.  Essentially, these would take place:

1) Break array
2) Repartition  and format 1 disk
3) Copy data over to fresh disk
4) Repartition and format other disk
5) Recreate the array

It's not too dificult to do, and you will not lose your data (though I always recommend a backup anyway).
Let me know if you are interested, and I can walk you through it.

The missing partitions are partition 4 on each drive and physically are located from blocks 67-130.

hi bq041,
I have seen several posts where you refer to your array repair (break & recreate) scripts, and one sayng you are near ready to release them.  How near are you to this as I would like to have a look, can you put them up on the wiki?  Brief comments in the scripts outlining what they do and a couple of words explaining each script 'section' would be useful for linux newbies (like me) too!
thanks
lu

bq041 wrote:

It comes down to until I can make it idiot proof, I don't want them on the wiki.  I certainly do not want to be blamed for someone losing their data.

Just a suggestion - when you're through idiot proofing them (I prefer the term making them "layer 8 compatible"), be sure to include a disclaimer.

bq041 wrote:

I will let people use them (you can download them from some of the posts) on an individual basis as they need them, but I do not want them up on the wiki until I have some safeguards in place. ...

It comes down to until I can make it idiot proof, I don't want them on the wiki.  I certainly do not want to be blamed for someone losing their data.

Sure that is fair enough, safeguards will save some users from making a catastrophic mistake, but I agree a disclaimer is a good idea too).

What I am actually looking for is a script to rebuild a raid1 array (without data loss) after factory reset.  IN my case the raid was created on f/w 1.04 then upgraded to 1.05 then downgraded to 1.04.  I haven't reset the 323 yet though!

One problem I find with this (really fantastic) forum is having to search multiple threads on different topics to find the latest version of a script or file - that is why I mentioned putting them up on the wiki.  Obviously this is not a 'fault' and not something unique to this forum, I just find it much easier to find what I am looking for in the wiki (just a personal opinion).
thanks
lu

Almost there.  I'm going through the last stages of testing now.  I should post it tomorrow if everything finishes well with the tests.  Sorry it took so long, but each test lasts a couple of hours.

A strange thing happened to me, it seems to be working now.

Below are what I did:-

1. Shutdown my DNS 323.
2. Remove drive 0 (the leftmost drive) and connect it to an external 3.5" enclosure.
3. Started Fedora9 Live on my notebook with 2. above connected to it.
4. Mounted the drive with the command " mount -t ext2 /dev/<path>".
5. I can see the contents of my files in the drive. Copied one file over to a tmp directory and verified that I can see the file.
6. Shutdown my notebook.
7. Remove HDD from 3.5" enclosure and put it back to original location in DNS 323.
8. Turn on my DNS 323.
9. SFTP over the script raid_upgrade_1.03_1.04-5.sh to /mnt/HD_a2
10. Ran the script but chose (x) instead to exit out of the script because I wanted to kill the bittorent process (/mnt/HD_a2/Nas_Prog/BT/bt) myself as the script does not kill this process.
11. Log into web interface. The wizard does not prompt anymore to set up RAID configuration.

Below is the status from the web interface (previously the total drives was 0 but now it shows 2):-

HARD DRIVE INFO :
Total Drive(s):     2

Volume Name:     Volume_1
Volume Type:     RAID 1
Sync Time Remaining:     Completed
Total Hard Drive Capacity:     490402 MB
Used Space:     380874 MB
Unused Space:     109527 MB

Running mdadm --detail /dev/md0 gave me almost the same output as in my first post:-

/ # mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Thu Jan 24 07:53:58 2008
     Raid Level : raid1
     Array Size : 486544512 (464.01 GiB 498.22 GB)
    Device Size : 486544512 (464.01 GiB 498.22 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Mon Jun 23 01:01:12 2008
          State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
  Spare Devices : 0

           UUID : 60fbd487:5d4425ca:f1babd8e:f8b4583c
         Events : 0.1763295

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2


/ # cat /proc/mdstat also indicated that my RAID1 is up and running properly.

Personalities : [linear] [raid0] [raid1]
md0 : active raid1 sda2[0] sdb2[1]
      486544512 blocks [2/2] [UU]
     
unused devices: <none>




How can I verify that this is indeed working properly? I rebooted a few more times and from the web interface, it all seems ok now.

bq041, thanks for the awesome upgrade script. Ran it on my DNS323 which I'd upgraded from 1.03 to 1.05 without reformatting. Worked a treat and the web interface is much happier.

No problem.  Sometime when I get time, I will work on a version to do it without the reboots, but it will be a while.  I was pressed on time for this one, as I knew you guys wanted to get your machines going.

It may, but would require some modification, as it was written specifically for RAID 1.  What you first need to find out is why the drive is not showing up.  do you have any fun_plug installed?  Your drives, what position are they in? (i.e. - the drive that was volume_2 and is now Volume_1, what bay is it in, left or right?)  Second, which wizard are you getting?  The reformat wizard?  What happens if you boot up the unit with only the drive that does not work in it?

As far as the problem, I would guess that you magic numbers and/or the raidtab files have been messed up.  They are not too hard to fix.  If you can try out the things abouve, that would be great.  The next thing to do after that would be to boot the unit with only the "good" drive in it with ffp on it, then install the "bad" drive with the power on.  The you can telnet in an see what shape the drive is in.

That is correct.  F/W 1.04 and 1.05 require the 4th partition of each drive to store configuration files on.