Aller au contenu


- - - - -

Ajouter Un Disque Dans Un Raid


Aucune réponse à ce sujet

#1 cris

    Administrateur

  • Administrateurs
  • 2 567 messages
  • LocationFernelmont
  • Matériel: TS-459 Pro, TS-419P, TS-409 Pro

Posté 22 mars 2011 - 10:13

Voici une procedure permettant de rajouter un disque dans un RAID quant la procédure automatique prévue par QNAP ne fonctionne pas:



I'm seem to be having the same issues expanding my TS 509 as described in this post:

http://forum.qnap.co...php?f=25&t=9083

Now the solution does look good but seems to be lacking some steps.

So this is what I think the process should be, please feel free to correct and expand any steps listed below. The only thing that isn't working is the RAID status in the Web Admin, as this still reports only 3 drives in the RAID - but does report the free disk space correctly.

** DISCLAIMER ** This worked for me, it might not work for you - backup first!!

-----------------------------------------------------------------------------------------------------------------------------
1.) ssh onto your TS box.

Use your favorite SSH client to log onto the TS*** and become the root user.

2.) Check RAID size.

[/etc/init.d] # df /dev/md0
Filesystem                Size      Used Available Use% Mounted on
/dev/md0                  2.7T      2.7T      4.7G 100% /share/MD0_DATA


Not a lot of space left :)

3.) Check to see if all disks are present with the mdadm command.

[/etc/init.d] # mdadm -D /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Tue Oct 21 22:34:19 2008
     Raid Level : raid5
     Array Size : 4390708800 (4187.31 GiB 4496.09 GB)
  Used Dev Size : 1463569600 (1395.77 GiB 1498.70 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Sat Feb 28 19:59:42 2009
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           UUID : b95bf024:8c1517d6:af35b4a1:c06378bd
         Events : 0.2441216

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3
       2       8       35        2      active sync   /dev/sdc3
       3       8       51        3      active sync   /dev/sdd3


For me the /dev/sdd line above indicates that I have my new 4th drive visible to the system.

4.) Check what type of filesystem the RAID is by checking mtab.

[/etc/init.d] # cat /etc/mtab 
/proc /proc proc rw 0 0
none /dev/pts devpts rw,gid=5,mode=620 0 0
sysfs /sys sysfs rw 0 0
tmpfs /tmp tmpfs rw,size=32M 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/sda4 /mnt/ext ext3 rw 0 0
/dev/md9 /mnt/HDA_ROOT ext3 rw 0 0
/dev/md0 /share/MD0_DATA ext3 rw,usrjquota=aquota.user,jqfmt=vfsv0,data=writeback 0 0


The last line shows that the current RAID is ext3.

5.) Turn off all network mounts.

From the Web Admin page go to the Network Settings and disable the following services:

    • Microsoft Networking
    • Apple Networking
    • NFS Service
    • Web File Manager
    • FTP Service
    • Multimedia Station
    • iTunes Service
    • Download Station
    • Web Server
    • MySQL Server

6.) Unmounting the volume.

From the command line run the following:

[/etc/init.d] # umount /dev/md0


If you see this message after running the above command stop, this means that you have not disabled all of the network services.

umount: /share/MD0_DATA: device is busy


7.) File system check.

Run the e2fsck command to check your filesystem for errors, this may take a while:

[/etc/init.d] # e2fsck -f /dev/md0
e2fsck 1.40.4 (31-Dec-2007)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/md0: 51686/365903872 files (11.0% non-contiguous), 730560098/731784800 blocks


8.) Turn ext3 journaling off

As step 4 showed that the RAID was using ext3 we need to turn off the journaling prior to expansion.

[/etc/init.d] # tune2fs -O ^has_journal /dev/md0


9.) Extend the RAID, this will take a while.

[/etc/init.d] # resize2fs /dev/md0
resize2fs 1.40.4 (31-Dec-2007)
Resizing the filesystem on /dev/md0 to 1097677200 (4k) blocks.
The filesystem on /dev/md0 is now 1097677200 blocks long.


10.) Recheck the filesystem - using the -n option so no changes are made.

[/etc/init.d] # e2fsck -n /dev/md0
e2fsck 1.40.4 (31-Dec-2007)
/dev/md0: clean, 51686/365903872 files, 730560098/731784800 blocks


This looks good as the number of blocks reported above has increased from what we saw in Step 7 above.

11.) Turn the journaling back on.

[/etc/init.d] # tune2fs -j /dev/md0
tune2fs 1.40.4 (31-Dec-2007)
Creating journal inode: done
This filesystem will be automatically checked every -1 mounts or
0 days, whichever comes first.  Use tune2fs -c or -i to override.


12.) Reboot the system.

Just to make sure everything is in order do a reboot to bring everything up cleanly:

[/etc/init.d] # reboot


13.) Check RAID size.

SSH back on and check your RAID has been expanded.

[/etc/init.d] # df /dev/md0
Filesystem                Size      Used Available Use% Mounted on
/dev/md0                  4.0T      2.7T      1.3T  67% /share/MD0_DATA


14.) Re enable Network Services.

Turn the Network services you want to use back on with the Web Admin interface.

-----------------------------------------------------------------------------------------------------------------------------
Avant de poser votre question, pensez à vérifier si vos disques se trouvent dans la liste de compatibilité
- Besoin d'aide?
- Plugmedia [Alternative de la station multimedia]





1 utilisateur(s) li(sen)t ce sujet

0 membre(s), 1 invité(s), 0 utilisateur(s) anonyme(s)