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

hmm,I think I have the same problem - maybe we should "compare notes"

one HDD - always right in my case - is dropping out of RAID1 (while LED)

I first had to add it back manually via command:
mdadm -add /dev/md0  /dev/sda2
so I think it is safe for you to do it as well, but check you setup first! (in your case it may be: mdadm -add /dev/md0  /dev/sdb2)
at least you will have two disks in the array (even if they are resyncing on reboot)

(I did use tune2fs utility to schedule automatic disk checks - but I doubt that this is the cause.....)

the partition setup looks fine to me: (except the comment: Partition table entries are not in disk order)

It occured to me to check the message log:
/mnt/HD_a2/wspolny # dmesg
software to use new ictls.
md: mdadm(pid 1802) used obsolete MD ioctl, upgrade your software to use new ictls.
md: mdadm(pid 1808) used obsolete MD ioctl, upgrade your software to use new ictls.
md: mdadm(pid 1836) used obsolete MD ioctl, upgrade your software to use new ictls.
..... lots of messages

there is more about it here: http://dns323.kood.org/forum/t1476-DNS- … -2007.html
but I am not sure if this is directly relevant to the problem


/mnt/HD_a2/wspolny # fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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             131       60702   486544590  83 Linux
/dev/sda4              67         130      514080  83 Linux

Partition table entries are not in disk order

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1          66      530113+ 82 Linux swap
/dev/sdb2             131       60702   486544590  83 Linux
/dev/sdb4              67         130      514080  83 Linux

Partition table entries are not in disk order




but now after EVERY reboot the DNS is auto-forcing full raid resynch:
/mnt/HD_a2/wspolny # mdadm -D /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Sat Feb  9 13:53:03 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 : Wed Feb 13 08:50:44 2008
          State : active, resyncing
Active Devices : 2
Working Devices : 2
Failed Devices : 0
  Spare Devices : 0

Rebuild Status : 68% complete

           UUID : 6d1cd9f1:f568efed:4a8904db:e3086e15
         Events : 0.115361

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

Last edited by ahors (2008-02-13 13:25:10)

Wow fordem, mentioning possible faulty disks in a mirror without suggesting they make sure they have a complete backup? Are you feeling ok?? 

For the record - I doubt that the hard drive is faulty (they are new) - and did I run full fsck on it - no bad sectors.
As far as white color  --- hmmm not blue for sure the other drive is blue - maybe very,very light shade of amber (-;

I did have a problem initially  when creating the array - the formating stopped at 94% - it was there for a long time - so I rebooted the DNS. reformatted it for two single drives and back for RAID1

Also the RAID1 starts to operate correctly once the synchronization is complete (at least according to mdadm) albeit the while/amber LED stays on

To me it really seems white. Maybe an off-white, but I never thought of calling it 'amber': http://666kb.com/i/aw3akk7rexufpazfp.jpg (soory for the bad quality, but with flash it doesn't work... :-)

About backups: yes, I have the originals of all data on the drive on my desktop, and that one also has a Raid1... :-)

The funny thing is: it all works! If I didn't notice the white Led, I never would've known that there is something wrong. The Raid1 volume works, the JBOD volume also. No degrading in speed noticed, no other startup sounds than I am used to.
I am currently moving the contents of the JBOD-drive to the Raid1 volume, but after that I will pull the drive out and test it externally. After that; I will check the rebuild function...

Ardjan wrote:

To me it really seems white. Maybe an off-white

Interesting, mine are orange...  I was wondering what all you guys were talking about.  I'll have to take a photo of mine

Last edited by orbitaudio (2008-02-15 10:10:41)

Doesn't orange mean amber? And amber means the drive is failing / about to fail / failed?

I was able to make whitish colour on one of HD LED by doing some experiment.  It has two-colour LED and when both Blue and Amber parts are lit, whitish colour.

In my case, this is how I made that happen.  I pulled out one HD to simulate one HD failure while it is running.  The LED on the HD turned off immediately, but status page says I have two disks and sync completed.  Then couple of minutes later, the LED lit amber, although status page still says sync completed.
Push back the HD now the LED lit both blue and amber at the same time and show like whitish colour.  Power cycling let status page realize RAID1 is degraded, and the LED colour changed to blue, but re-building did not start.  Couple of minutes later, LED went back to white again, still no array rebuilding.

Power off, pull out the bad (?) HD, power on, wait for full reboot, power off, put back HD, power on.  Now I can see 323 is rebuilding array.  It seems white LED occur when it knows something is not right (amber) but also knows there is a healthy HD (blue) to play with, but not sure what to do or does not want to rebuild array whatever the reason.

I tried this with both side of HD, and the result was same.  Although the test was done with only 99GB of RAID 1 array out of two 1TB HDs, (Strangely, I cannot create bigger than 99GB RAID 1 array while I can create 2TB RAID 0 or two 1TB individual disks no problem.  But this issue should be on another thread.)  I am glad there were no data loss and array rebuild properly.


HW: 1A, FW:1.04, HD: WD10EACS x 2, No mod, yet.

How do you do when ou are daltonian ?

Personnaly, i have one LED which is less blue than the other one, during 1 month it was off, then i have updated the firmware with the new 1.04 and it is on now. it is just shining less (half than the other one) and my hard drives are both fine. I don't know what it is happening.
by seing your post with your "amber LED", i am quite happy with my problem

good luck

Last edited by bodbod (2008-02-19 01:45:46)