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

Grant29 · 2008-08-19 03:52:41

Hi,

I'm having a problem and hope someone on this forum can help. I just got a DNS-323 and 2 1TB Western Digital hard drives. When I got this hardware, I went through these steps:

1. Upgraded the firmware to 1.05 before installing the hard drives.
2. Inserted both drives and formatted as RAID 1.
3. At this point, the Sync Time Remaining said normal. The format process resulted in a success message.
4. I copied about 750G of data to the drive.
5. The copy took quite a while, and now when I check it says "Sync Time Remaining:Degraded".

What does Sync Time Remaining:Degraded mean? Is this normal? Do I simply need to wait for the data to get mirrored to the other drive? I don't see any indication that one drive failed and haven't gotten an email that indicates a drive failure either. Was copying 750G at one time too much? Do I need to adjust any of the Config Inactivity Timer settings?

This is what I see on the status page:

HARD DRIVE INFO :

Total Drive(s):    2
Volume Name:    Volume_1
Volume Type:    RAID 1
Sync Time Remaining:    Degraded
Total Hard Drive Capacity:    981858 MB
Used Space:    730853 MB
Unused Space:    251004 MB

Any ideas?

Thanks!

ChamPro · 2008-08-19 20:37:54

I'm having the same issue and I've tried using the wizard (*gasp*) twice.

I have two WD7500aaks-00rba0. Once already has 576 GB of data and it's in the right hand slot (since it seems that that is the first slot). I have an unformatted empty drive in the left slot. I start the DNS-323 with 1.05 firmware. The wizard comes up, formats the drive, I reboot, and get the degraded status for RAID 1. No syncing occurs after this.

Looking at the new drive on a different computer, it looks like it copied 10 GB or so of data over to the new drive. But stopped the sync for some reason.

I read a lot of posts in the forum about resyncing RAID 1 using console commands (mdadm), but it would be nice to know why the firmware can't rebuild the RAID like it's supposed to.

bq041 · 2008-08-20 05:24:52

Degraded is not normal.

I read a lot of posts in the forum about resyncing RAID 1 using console commands (mdadm), but it would be nice to know why the firmware can't rebuild the RAID like it's supposed to.

Who ever said the F/W was supposed to resync the RAID array? As long as there are no errors it will keep it in sync, but once it is degraded, there is nothing in the F/W to resync the array. The question to ask is "What is the problem with the array?", not "...why the firmware can't rebuild the RAID...?"

Anyway, since you have aleady found the threads on using mdadm, I won't repeat the commands here unless you really need them.

fordem · 2008-08-20 16:00:54

bq041 wrote:
Who ever said the F/W was supposed to resync the RAID array?

That is an interesting statement - not that I'm disagreeing with it.

The thing is this, a degraded array offers no protection, and provision needs to be made to deal with this, either automatically or manually. A failed drive will typically result in an email (if configured) or an error indication on the LEDs - the original poster has indicated that he received neither.

I'm not certain that my experiences have been identical, as I have had a number of LED indications - those pink/purple/white ones - that were definitely not disk failures, but could not be explained to my satisfaction.

ChamPro · 2008-08-20 21:27:30

bq041 wrote:
Degraded is not normal.
I read a lot of posts in the forum about resyncing RAID 1 using console commands (mdadm), but it would be nice to know why the firmware can't rebuild the RAID like it's supposed to.
Who ever said the F/W was supposed to resync the RAID array? As long as there are no errors it will keep it in sync, but once it is degraded, there is nothing in the F/W to resync the array. The question to ask is "What is the problem with the array?", not "...why the firmware can't rebuild the RAID...?"

Anyway, since you have aleady found the threads on using mdadm, I won't repeat the commands here unless you really need them.

I followed the instructions in the last mdadm thread (with swapping sda2 with sdb2) but I ran into issues.

Code:

/ # mdadm --misc -D /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Wed Aug 20 12:42:03 2008
     Raid Level : raid1
     Array Size : 731832960 (697.93 GiB 749.40 GB)
    Device Size : 731832960 (697.93 GiB 749.40 GB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Aug 20 14:18:27 2008
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           UUID : 8713c761:22dd0d8c:4b0bf891:ef01dd01
         Events : 0.66

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

So I tried clearing the zero-block

Code:

/ # mdadm --zero-superblock /dev/sdb2
mdadm: Unrecognised md component device - /dev/sdb2

Hmmm... format anyways.

Code:

/ # mke2fs -m 0 /dev/sdb2
mke2fs 1.40.6 (09-Feb-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
45727744 inodes, 182881951 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
5582 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
        102400000

Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

Then add the partition to the RAID.

Code:

/ # mdadm /dev/md0 -a /dev/sdb2
mdadm: hot add failed for /dev/sdb2: No space left on device

Seems like the formatter in the wizard made the partitions the wrong size... even though the drives are exactly the same.

Code:

/ # df
Filesystem           1k-blocks      Used Available Use% Mounted on
rootfs                    9911      7544      1855  80% /
/dev/root                 9911      7544      1855  80% /
/dev/md0             720349096 563011060 157338036  78% /mnt/HD_a2
/dev/sda4               202226     10972    191254   5% /mnt/HD_a4
/dev/sdb4               497861         5    497856   0% /mnt/HD_b4
/ # cat /proc/mdstat 
Personalities : [linear] [raid0] [raid1] 
md0 : active raid1 sda2[0]
      731832960 blocks [2/1] [U_]
      
unused devices: <none>
/ # dmesg|grep sd
SCSI device sda: 1465149168 512-byte hdwr sectors (750156 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 1465149168 512-byte hdwr sectors (750156 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB)
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb4
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Adding 530104k swap on /dev/sda1.  Priority:-1 extents:1
Adding 530104k swap on /dev/sdb1.  Priority:-2 extents:1
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4
ext3: No journal on filesystem on sda2
ext3: No journal on filesystem on sdb2
md: bind<sda2>
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4
md: export_rdev(sdb2)
md: export_rdev(sdb2)

bq041 · 2008-08-20 21:55:45

Use fdisk to set partition 1 from blocks 1 to 66, partition 4 from 67 to 130 and partition 2 from 131 to the end. This is the standard way the DNS sets up the partitons. Also, partition 1 needs to be set to swap space. Once that is done, you can format 2 and 4 using mke2fs and mkswap for partition 1.

Actually, before you do this, run:

Code:

fdisk -l /dev/sda

This will show you how the first disk is set-up. It should be set-up as above, but you have definately experienced an anomoly, so it may not be. Use fdisk to set /dev/sdb the same. After you format it, then use mdadm to add the disk.

Note, don't forget to use swapoff on /dev/sdb1 before you use fdisk, then swapon /dev/sdb1 to enable it after you format it.

ChamPro · 2008-08-20 23:11:34

Did everything you said... oddly enough, /dev/sda was not setup normally. The drive was setup by the DNS wizard back when it was by itself.

Code:

/ # fdisk -l /dev/sda

Disk /dev/sda: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          66      530113+ 82 Linux swap
/dev/sda2              93       91201   731833042+ 83 Linux
/dev/sda4              67          92      208845  83 Linux

Partition table entries are not in disk order

But now sda and sdb match, and the spare is rebuilding. The web GUI says it will take 140 minutes. Thanks for your help!

Code:

/ # mdadm --misc -D /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Wed Aug 20 12:42:03 2008
     Raid Level : raid1
     Array Size : 731832960 (697.93 GiB 749.40 GB)
    Device Size : 731832960 (697.93 GiB 749.40 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Aug 20 16:08:03 2008
          State : clean, degraded, recovering
 Active Devices : 1
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 1

 Rebuild Status : 0% complete

           UUID : 8713c761:22dd0d8c:4b0bf891:ef01dd01
         Events : 0.5890

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

bq041 · 2008-08-20 23:13:50

Once it is finished the sync, run do_reboot. There are configuration files that need to be updated this way. Do not reboot from the GUI.

ChamPro · 2008-08-21 04:44:44

bq041 wrote:
Once it is finished the sync, run do_reboot. There are configuration files that need to be updated this way. Do not reboot from the GUI.

So the sync went well. And I did the do_reboot. When login to the DNS web GUI now, everytime it brings up "Hard Drive Configuration" dialog. I can click skip and it'll go on and everything checks out in the Status screen for RAID 1.

Any ideas on why the web GUI is out of whack?

Code:

/ # mdadm --misc -D /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Wed Aug 20 12:42:03 2008
     Raid Level : raid1
     Array Size : 731832960 (697.93 GiB 749.40 GB)
    Device Size : 731832960 (697.93 GiB 749.40 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Aug 20 20:28:17 2008
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 8713c761:22dd0d8c:4b0bf891:ef01dd01
         Events : 0.5929

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

Last edited by ChamPro (2008-08-21 04:45:28)

bq041 · 2008-08-21 05:59:44

Yes, you now need to set the configuration files correctly. I will set-up a script to do this for you tomorrow. I cannot do it now as it is late at night. It involves 12 files between the 2 hard drives and the flash.

Just continue to skip the config at the GUI, the unit will continue to function fine. If you really want, I can show you how to do this manually, but it can get pretty confusing In theory, if the files on the flash are okay, it only involves creating the 3 files on the "new" hard drive (the one you formatted). If you want, we can check that out, but if you are unsure of your skills, I can give you a script to completely rewrite all 12 of them.

If you want to try it out, you can do the following just to see if it is okay:

Code:

/ # mount -t minix /dev/mtdblock0 /sys/mtd1
/ # mount -t minix /dev/mtdblock1 /sys/mtd2
/ # cat /sys/mtd1/hd_magic_num
/ # cat /sys/mtd2/hd_magic_num
/ # cat /sys/mtd1/raidtab2web 
/ # cat /sys/mtd2/raidtab2web
/ # cat /sys/mtd1/raidtab
/ # cat /sys/mtd2/raidtab
/ # cat /mnt/HD_a4/.systemfile/hd_magic_num 
/ # cat /mnt/HD_b4/.systemfile/hd_magic_num 
/ # cat /mnt/HD_a4/.systemfile/raidtab2web 
/ # cat /mnt/HD_b4/.systemfile/raidtab2web
/ # cat /mnt/HD_a4/.systemfile/raidtab
/ # cat /mnt/HD_b4/.systemfile/raidtab
/ # umount /sys/mtd1
/ # umount /sys/mtd2

MOST IMPORTANT -- Unmount the /sys/mtd1 and /sys/mtd2 -- These are the flash and you do not want to corrupt them by rebooting or shutting down the device with them mounted.

Anyway, if you post the results of each of those commands, I can tell you if it will be a quick copy or if it will require a complete rebuild of the config files. Rest assured, the disks are currently working fine, it is just the files that allow the DNS's web GUI to know what's happening need updating.

Lastly, don't worry if there are no files on the /mnt/HD_b4. This is probably where the problem lies.

Last edited by bq041 (2008-08-21 06:01:44)

bq041 · 2008-08-22 01:55:13

Put this script on the DNS and then execute it from telnet. It will create the proper RAID 1 configuration files on the DNS so the GUI will work.

CAUTION: THIS ONLY WORKS WITH ARRAYS THAT ARE ON THE F/W 1.04 or 1.05 CONFIGURATION FORMAT.

Last edited by bq041 (2008-09-04 18:44:22)

ChamPro · 2008-08-28 19:45:43

bq041 wrote:
Put this script on the DNS and then execute it from telnet. It will create the proper RAID 1 configuration files on the DNS so the GUI will work.

CAUTION: THIS ONLY WORKS WITH ARRAYS THAT ARE ON THE F/W 1.04 or 1.05 CONFIGURATION FORMAT.

Unfortunately, the script did not work. Here's the output from those commands.

Code:

/ # mount -t minix /dev/mtdblock0 /sys/mtd1
/ # mount -t minix /dev/mtdblock1 /sys/mtd2
/ # cat /sys/mtd1/hd_magic_num
62405
52584
WD-WCAPT0293543
WD-WCAPT0257654
/ # cat /sys/mtd2/hd_magic_num
62405
52584
WD-WCAPT0293543
WD-WCAPT0257654
/ # cat /sys/mtd1/raidtab2web 
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   2
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   1
SatamountFlag   1
SatamountFlag0  1
raidsize        697
filesystem      EXT2
parti3  1
Version 1.5
/ # cat /sys/mtd2/raidtab2web 
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   2
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   1
SatamountFlag   1
SatamountFlag0  1
raidsize        697
filesystem      EXT2
parti3  1
Version 1.5
/ # cat /sys/mtd1/raidtab
raiddev /dev/md0
        raid-level      raid1
        nr-raid-disks   2
        chunk-size      64
        persistent-superblock   1
        device          /dev/sda2
        raid-disk       0
        device          /dev/sdb2
        raid-disk       1

raiddev null
        raid-level      null
        nr-raid-disks   0
        chunk-size      64
        persistent-superblock   1
        device          null
        raid-disk       null
        device          null
        raid-disk       null
        Version 1.3

/ # cat /sys/mtd2/raidtab
raiddev /dev/md0
        raid-level      raid1
        nr-raid-disks   2
        chunk-size      64
        persistent-superblock   1
        device          /dev/sda2
        raid-disk       0
        device          /dev/sdb2
        raid-disk       1

raiddev null
        raid-level      null
        nr-raid-disks   0
        chunk-size      64
        persistent-superblock   1
        device          null
        raid-disk       null
        device          null
        raid-disk       null
        Version 1.3
/ # cat /mnt/HD_a4/.systemfile/hd_magic_num 
62405
52584
/ # cat /mnt/HD_b4/.systemfile/hd_magic_num 
cat: can't open '/mnt/HD_b4/.systemfile/hd_magic_num': Not a directory
/ # cat /mnt/HD_a4/.systemfile/raidtab2web 
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   2
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   1
SatamountFlag   1
SatamountFlag0  1
raidsize        697
filesystem      EXT2
parti3  1
Version 1.5
/ # cat /mnt/HD_b4/.systemfile/raidtab2web 
cat: can't open '/mnt/HD_b4/.systemfile/raidtab2web': Not a directory
/ # cat /mnt/HD_a4/.systemfile/raidtab     
raiddev /dev/md0
        raid-level      raid1
        nr-raid-disks   2
        chunk-size      64
        persistent-superblock   1
        device          /dev/sda2
        raid-disk       0
        device          /dev/sdb2
        raid-disk       1

raiddev null
        raid-level      null
        nr-raid-disks   0
        chunk-size      64
        persistent-superblock   1
        device          null
        raid-disk       null
        device          null
        raid-disk       null
        Version 1.3

/ # cat /mnt/HD_b4/.systemfile/raidtab
cat: can't open '/mnt/HD_b4/.systemfile/raidtab': Not a directory
/ # umount /sys/mtd1/
/ # umount /sys/mtd2/

bq041 · 2008-08-28 23:09:10

There is your problem. It looks like HD_b4 is not in existance or not mounted or something. The web does not like that. You first need to find out if you have an HD_b4.

Code:

cat /proc/partitions
mount
ls -al /mnt
ls -al /mnt/HD_b4
ls -al /mnt/HD_b4/.systemfile

Post the output of those. Once we determine if you indeed have the correct partitions and have them mounted, we will need to copy everything from /mnt/HD_a4/.systemfile to it.

The script set-up all areas correct except the HD_b4, which leads me to believe it is not correctly there. The script was not designed to set up the partitions, it assumes they are already there. This was the reason for the disclamer about the F/W level. Did you happen to have one of the drives in (left one) with F/W 1.03 or below at any time? Once you post the results from above, I will evaluate it and respond.

Last edited by bq041 (2008-08-28 23:10:19)

ChamPro · 2008-09-03 22:04:58

Code:

/ # cat /proc/partitions 
major minor  #blocks  name

   7     0       5484 loop0
  31     0         64 mtdblock0
  31     1         64 mtdblock1
  31     2       1536 mtdblock2
  31     3       6336 mtdblock3
  31     4        192 mtdblock4
   9     0  731832960 md0
   8     0  732574584 sda
   8     1     530113 sda1
   8     2  731833042 sda2
   8     4     208845 sda4
   8    16  732574584 sdb
   8    17     530113 sdb1
   8    18  731833042 sdb2
   8    20     208845 sdb4
/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
proc on /proc type proc (rw,nodiratime)
/dev/loop0 on /sys/crfs type cramfs (ro)
/dev/md0 on /mnt/HD_a2 type ext2 (rw)
/dev/sda4 on /mnt/HD_a4 type ext2 (rw)
/dev/sdb4 on /mnt/HD_b4 type ext2 (rw)
none on /proc/bus/usb type usbfs (rw)
devpts on /dev/pts type devpts (rw)
/ # ls -al /mnt
drwxr-xr-x    6 root     root         1024 Sep  3 13:26 .
drwxr-xr-x   18 root     root         1024 Sep  3 14:27 ..
drwxrwxrwx   16 root     root         4096 Aug 27 18:46 HD_a2
drwxrwxrwx    5 root     root         1024 Sep  1 01:24 HD_a4
drwxrwxrwx    2 root     root         1024 Aug 30 21:35 HD_b4
drwxr-xr-x    2 root     root         1024 Feb 16  2007 web_page
/ # ls -al /mnt/HD_b4/
drwxrwxrwx    2 root     root         1024 Aug 30 21:35 .
drwxr-xr-x    6 root     root         1024 Sep  3 13:26 ..
-rwx------    1 root     root           12 Aug 27 18:48 .systemfile
/ # ls -al /mnt/HD_b4/.systemfile 
-rwx------    1 root     root           12 Aug 27 18:48 /mnt/HD_b4/.systemfile

And odd thing is that in the web interface, it talks about Volume_1. But when I access the DNS from SMB, it lists Volume_2.

bq041 · 2008-09-03 22:47:27

There is the problem. In /mnt/HD_b4 the file .systemfile is supposed to be a directory and it is not. Here is it:

Code:

rm  /mnt/HD_b4/.systemfile
mkdir /mnt/HD_b4/.systemfile
chmod 700 /mnt/HD_b4/.systemfile
cp -dprf /mnt/HD_a4/.systemfile/*  /mnt/HD_b4/.systemfile
do_reboot

Try that and see how it fairs.

Last edited by bq041 (2008-09-03 22:48:24)

ChamPro · 2008-09-04 02:32:47

Code:

/ # mdadm --misc -D /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Wed Aug 20 12:42:03 2008
     Raid Level : raid1
     Array Size : 731832960 (697.93 GiB 749.40 GB)
    Device Size : 731832960 (697.93 GiB 749.40 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Sep  3 19:29:07 2008
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 8713c761:22dd0d8c:4b0bf891:ef01dd01
         Events : 0.15213

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

Looks good from the standpoint of the CLI and from the GUI.

Code:

HARD DRIVE INFO :

Total Drive(s):     2
Volume Name:     Volume_1
Volume Type:     RAID 1
Sync Time Remaining:     Completed
Total Hard Drive Capacity:     737637 MB
Used Space:     599878 MB
Unused Space:     137758 MB

Thanks so much for your time. Seems like I finally have a working RAID 1 setup.

bq041 · 2008-09-04 03:09:52

No problem. It looks like I made an error in the script and it coppied the config files into a file called .systemfiles instead of a directory called .systemfiles--sorry about that.

Anyway, I hope you learned a little about it and had fun trying something new. Any more questions, feel free to ask.

cdk · 2008-10-15 03:13:10

Hi there,

first of all - thank you very, very much for the information posted here. I've got a similar problem and hope you can help me too.
After restarting my NAS these days the Web-UI suggested to reformat both HDDs. Didn't knew why, but since my shares were still accessible I skipped the formatting procedure and went on as if nothing happened. Now Web-UI stated that my RAID1 was degraded.
Switching to Telnet I could hotadd the deaktivated sda1 (don't know what could have happened to it) and succeeded in recovering the RAID without any data loss by the mdadm -a command. But after restarting the Web-UI still insisted on reformating although the status was now on completed.

So I followed the instructions given here and I think I spotted the ultimate cause: The raidtab2web tables in the Flash seem to have strange entries and additionally they do not match the tables on harddisk.

Code:

/ # cat /sys/mtd1/raidtab2web
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   0
SatamountFlag   1
SatamountFlag1  1
raidsize        913
filesystem      EXT2
parti3  0
/ #
/ # cat /sys/mtd2/raidtab2web
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   0
SatamountFlag   1
SatamountFlag1  1
raidsize        913
filesystem      EXT2
parti3  0

They show up the raidsize of 913 MiB instead of 922 MiB - and shouldn't the nr-raid-disks be set to 2 and the FormatwebFlag set to 1?

The raidtab tables look ok:

Code:

/ # cat /sys/mtd1/raidtab
raiddev /dev/md0
        raid-level      raid1
        nr-raid-disks   2
        chunk-size      64
        persistent-superblock   1
        device          /dev/sda2
        raid-disk       0
        device          /dev/sdb2
        raid-disk       1

raiddev null
        raid-level      null
        nr-raid-disks   0
        chunk-size      64
        persistent-superblock   1
        device          null
        raid-disk       null
        device          null
        raid-disk       null
        Version 1.3

/ #
/ # cat /sys/mtd2/raidtab
raiddev /dev/md0
        raid-level      raid1
        nr-raid-disks   2
        chunk-size      64
        persistent-superblock   1
        device          /dev/sda2
        raid-disk       0
        device          /dev/sdb2
        raid-disk       1

raiddev null
        raid-level      null
        nr-raid-disks   0
        chunk-size      64
        persistent-superblock   1
        device          null
        raid-disk       null
        device          null
        raid-disk       null
        Version 1.3

The raidtab2web tables on harddrive differ from each other in a lot of settings: The raiddev tag, the raidsize, the SatamountFlag1 and the FormatwebFlag:

Code:

/ # cat /mnt/HD_a4/.systemfile/raidtab2web
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   0
SatamountFlag   1
SatamountFlag1  1
raidsize        922
filesystem      EXT2
parti3  0
/ #
/ # cat /mnt/HD_b4/.systemfile/raidtab2web
raiddev null
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      0
FormatwebFlag   1
SatamountFlag   1
SatamountFlag1  0
raidsize        186
filesystem      EXT2
parti3  0

This is the mdadm -D output:

Code:

/ # mdadm -D /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Thu Sep 18 23:21:08 2008
     Raid Level : raid1
     Array Size : 966791616 (922.00 GiB 989.99 GB)
    Device Size : 966791616 (922.00 GiB 989.99 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Oct 15 00:09:02 2008
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : c781c972:507b22c3:3d84f4af:ec43b77c
         Events : 0.252918

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

Btw the only thing that looks really healthy to me. 922GiB is definitely the correct size.

Now - what should I do and in what order? The day before yesterday I didn't know how to spell the word Linux, so I'm a bit scared of acting just at discretion...

Please help!

Last edited by cdk (2008-10-15 03:19:23)

bq041 · 2008-10-15 14:58:28

Okay, all 4 raidtab and raidtab2web files (2 flash 1 on each hard drive) should be identical. This is one very likely cause of the problem. Next check the hd_magic number files. The 2 on the hard drives should have just the 2 numbers in them, and the 2 in flash should have the numbers (same order) followed by the serial numbers of the drives (separet lines). If any of these files veries, the web will always prompt for reformat.

Yes, 922 looks good for raid size.

cdk · 2008-10-15 18:51:11

Hello bq041, I'm glad you're still there and "active"...

I checked the magic numbers before (I completely checked your script mentioned above) - they exist, they are identical and additionally the drive-s/n's are listed in the files on flash. Every output of your script commands looked fine, except of those raidtab and raidtab2web tables I posted before.

But if you need these outputs anyway I can post'em when I come home soon...

Last edited by cdk (2008-10-15 18:51:46)

cdk · 2008-10-15 19:50:25

Oh no, stop - I was wrong! The magic numbers do differ!

Code:

/ # cat /sys/mtd1/hd_magic_num
127078
353512
6QJ011CR
9QJ1TCL6
/ #
/ # cat /sys/mtd2/hd_magic_num
127078
353512
6QJ011CR
9QJ1TCL6

Code:

/ # cat /mnt/HD_a4/.systemfile/hd_magic_num
4858
791700/ #
/ #
/ # cat /mnt/HD_b4/.systemfile/hd_magic_num
173274
791700/ #
/ #

Sorry, it was rather late last night...

Perhaps I should tell you some more background and the presumable origin of these problems: Yesterday I used another set of harddisks for experimental purposes in my NAS. After finishing my trials I removed them both and reassembled my current disks with the "real" data stored on it. After that the NAS started up with those problems mentioned.
And btw, this is not a DNS323, but it's clone CH3SNAS with the most recent firmware (1.04RC6)...

Last edited by cdk (2008-10-15 20:03:13)

bq041 · 2008-10-15 21:56:42

You have to be VERY careful about swapping drives around in the DNS (CH3NAS). Since flash stores teh drive serial numbers, it know about the different drives and has problems. This is whay you cannot play drive swap to make backups. Anyway, according to your last post, the HD_magic number files are wrong, also. This is a guarantee that the unit will ask to format. Copy the ones from flash over onto both drives, then erase the last 2 lines (serial numbers) of each. The ones in flash look good.

cdk · 2008-10-15 22:41:50

You have to be VERY careful about swapping drives around in the DNS (CH3NAS)

Oh yeah!
I guess I was a really lucky man that I did not loose any data yet, even if I didn't know about that, isn't it?

Copy the ones from flash over onto both drives, then erase the last 2 lines (serial numbers) of each. The ones in flash look good.

Replacing the content of both files on disk and then restart the NAS? Shouldn't the raidtab and the raidtab2web files be corrected before as well?

cdk · 2008-10-16 01:50:52

One ridiculous hour later I finally succeeded in copying 2 files and editing them in my first ever vi-session. Damn I'm good...

Code:

/ # cat /sys/mtd1/hd_magic_num
127078
353512
6QJ011CR
9QJ1TCL6
/ # cat /sys/mtd2/hd_magic_num
127078
353512
6QJ011CR
9QJ1TCL6
/ # cat /mnt/HD_a4/.systemfile/hd_magic_num
127078
353512
/ # cat /mnt/HD_b4/.systemfile/hd_magic_num
127078
353512

Ok - mdadm still finds the RAID in sync, all data is accessible and Web-UI says "completed", but it still wants to format both disks when I start it.

cdk · 2008-10-16 02:04:21

(Please excuse my multi-postings - I try to get a better overview of the different chapters of my problem)

So, what's next? Correcting the raidtab2web files, I think. You said all of them should be identical. This is the current siutation:

Code:

/ # cat /sys/mtd1/raidtab2web
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   0
SatamountFlag   1
SatamountFlag1  1
raidsize        913
filesystem      EXT2
parti3  0
/ #
/ # cat /sys/mtd2/raidtab2web
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   0
SatamountFlag   1
SatamountFlag1  1
raidsize        913
filesystem      EXT2
parti3  0
/ #
/ # cat /mnt/HD_a4/.systemfile/raidtab2web
raiddev /dev/md0
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      1
FormatwebFlag   0
SatamountFlag   1
SatamountFlag1  1
raidsize        922
filesystem      EXT2
parti3  0
/ #
/ # cat /mnt/HD_b4/.systemfile/raidtab2web
raiddev null
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
FirstStart      0
FormatwebFlag   1
SatamountFlag   1
SatamountFlag1  0
raidsize        186
filesystem      EXT2
parti3  0

My stomach says this would be the right configuration for all of these 4 Tables:

Code:

___raiddev /dev/md0___
raid-level      raid1
nr-raid-disks   1
chunk-size      32
persistent-superblock   1
device  /dev/sda2
raid-disk       0
device  /dev/sdb2
raid-disk       1
Status  Start
raid-masterdisk /dev/sda2
___FirstStart      1___
___FormatwebFlag   1___
SatamountFlag   1
___SatamountFlag1  1___
___raidsize        922___
filesystem      EXT2
parti3  0

Last edited by cdk (2008-10-16 02:05:24)

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

Announcement

#1 2008-08-19 03:52:41

Sync Time Remaining:Degraded. Normal?

#2 2008-08-19 20:37:54

Re: Sync Time Remaining:Degraded. Normal?

#3 2008-08-20 05:24:52

Re: Sync Time Remaining:Degraded. Normal?

#4 2008-08-20 16:00:54

Re: Sync Time Remaining:Degraded. Normal?

bq041 wrote:

#5 2008-08-20 21:27:30

Re: Sync Time Remaining:Degraded. Normal?

bq041 wrote:

Code:

Code:

Code:

Code:

Code:

#6 2008-08-20 21:55:45

Re: Sync Time Remaining:Degraded. Normal?

Code:

#7 2008-08-20 23:11:34

Re: Sync Time Remaining:Degraded. Normal?

Code:

Code:

#8 2008-08-20 23:13:50

Re: Sync Time Remaining:Degraded. Normal?

#9 2008-08-21 04:44:44

Re: Sync Time Remaining:Degraded. Normal?

bq041 wrote:

Code:

#10 2008-08-21 05:59:44

Re: Sync Time Remaining:Degraded. Normal?

Code:

#11 2008-08-22 01:55:13

Re: Sync Time Remaining:Degraded. Normal?

#12 2008-08-28 19:45:43

Re: Sync Time Remaining:Degraded. Normal?

bq041 wrote:

Code:

#13 2008-08-28 23:09:10

Re: Sync Time Remaining:Degraded. Normal?

Code:

#14 2008-09-03 22:04:58

Re: Sync Time Remaining:Degraded. Normal?

Code:

#15 2008-09-03 22:47:27

Re: Sync Time Remaining:Degraded. Normal?

Code:

#16 2008-09-04 02:32:47

Re: Sync Time Remaining:Degraded. Normal?

Code:

Code:

#17 2008-09-04 03:09:52

Re: Sync Time Remaining:Degraded. Normal?

#18 2008-10-15 03:13:10

Re: Sync Time Remaining:Degraded. Normal?

Code:

Code:

Code:

Code:

#19 2008-10-15 14:58:28

Re: Sync Time Remaining:Degraded. Normal?

#20 2008-10-15 18:51:11

Re: Sync Time Remaining:Degraded. Normal?

#21 2008-10-15 19:50:25

Re: Sync Time Remaining:Degraded. Normal?

Code:

Code:

#22 2008-10-15 21:56:42

Re: Sync Time Remaining:Degraded. Normal?

#23 2008-10-15 22:41:50

Re: Sync Time Remaining:Degraded. Normal?

#24 2008-10-16 01:50:52

Re: Sync Time Remaining:Degraded. Normal?

Code:

#25 2008-10-16 02:04:21

Re: Sync Time Remaining:Degraded. Normal?

Code: