Click here to Skip to main content
13,735,471 members
Click here to Skip to main content
Add your own
alternative version

Tagged as


Posted 1 Nov 2011
Licenced CPOL

Infrastructure: Replacing a Dead RAID 5 Drive in QNAP NAS

, 1 Nov 2011
Rate this:
Please Sign up or sign in to vote.
Replacing a Dead RAID 5 Drive in QNAP NAS

It’s been a while since I last posted – it’s been crazy busy at work – and this is a completely non-.NET related post (sorry). However, like many of you (I’m sure) I’ve got a personal SVN repository (where I keep my .NET code, so there is a tenuous link!) which is hosted on my QNAP 419P NAS Drive on a RAID5 volume across 4 Hot Swappable Disks.

For the non-technical, this is a little whizzy box with tonnes of space and can withstand a single complete hard disk failure without loosing data.

Recently one of the disk drives failed in the volume (completely dead) and whilst my data’s intact and everything carried on as best as it could, I needed to replace the drive. I was completely under the impression that this operation went along the lines of:

  1. Remove Dead Drive
  2. Insert New Disk
  3. Click ‘Repair’ on RAID volume in config
  4. Wait for repair to complete
  5. PROFIT!!

And with most corporate RAID solutions, that’s exactly what happens. However, after completing Step 2 of my plan, I discovered that the QNAP didn’t recognise the new disk at all and the Repair button was greyed out.


Well, it turns out the QNAP’s software raid manager can’t automatically recover from actual dead disks, only disks incorrectly flagged as faulty. Genius.

After a bit of Googling, I found that ‘all’ I needed to do was duplicate the partition table from one of the remaining live disks to the new disk and hopefully the low-level raid manager will then automatically rebuild the array.

So the actual steps are:

  1. Replace disk with new one
  2. SSH into QNAP box with Administrator privileges
  3. Get the partition settings from fdisk (type: fdisk –l)
  4. Identify a live disk in the output, in my case these were /dev/sda, /dev/sdb, /dev/sdc (there should also have been /dev/sdd – but that was the dead one):
       Device Boot      Start         End      Blocks   Id  System          
    /dev/sdc1   *           1          66      530113+  83  Linux           
    /dev/sdc2              67         132      530145   82  Linux swap / Solaris           
    /dev/sdc3             133      243138  1951945695   83  Linux           
    /dev/sdc4          243139      243200      498015   83  Linux           
  5. Now to replicate this config to the new drive (/dev/sdd). My commands are in bold italics:
    [~] # fdisk /dev/sdd              Device contains neither a valid DOS partition table, 
                                      nor Sun, SGI or OSF disklabel           
    Building a new DOS disklabel. Changes will remain in memory only,           
    until you decide to write them. After that, of course, the previous           
    content won't be recoverable.
    The number of cylinders for this disk is set to 243201.          
    There is nothing wrong with that, but this is larger than 1024,           
    and could in certain setups cause problems with:           
    1) software that runs at boot time (e.g., old versions of LILO)           
    2) booting and partitioning software from other OSs           
       (e.g., DOS FDISK, OS/2 FDISK)           
    Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
    Command (m for help): n              Command action           
       e   extended           
       p   primary partition (1-4)           
    p              Partition number (1-4): 
    1              First cylinder (1-243201, default 1):
    1             Using default value 1           
    Last cylinder or +size or +sizeM or +sizeK (1-243201, default 243201): 66
    Command (m for help): n              Command action           
       e   extended           
       p   primary partition (1-4)           
    p              Partition number (1-4): 
    2              First cylinder (67-243201, default 67):
    67              Using default value 67           
    Last cylinder or +size or +sizeM or +sizeK (67-243201, default 243201): 132
    Command (m for help): n              Command action           
       e   extended           
       p   primary partition (1-4)           
    p              Partition number (1-4): 
    3              First cylinder (133-243201, default 133):133           
    Using default value 133           
    Last cylinder or +size or +sizeM or +sizeK (133-243201, default 243201): 243138
    Command (m for help): n          
    Command action           
       e   extended           
       p   primary partition (1-4)           
    Selected partition 
    4              First cylinder (243139-243201, default 243139):243139           
    Using default value 243139           
    Last cylinder or +size or +sizeM or +sizeK (243139-243201, default 243201): 243200
  6. Next to mark /dev/sdd1 as bootable Command (m for help): a Partition number (1-4): 1
  7. Then change partition 2 to ‘Linux Swap / Solaris’ format Command (m for help): t Partition number (1-4): 2 Hex code (type L to list codes): 82 Changed system type of partition 2 to 82 (Linux swap / Solaris)
  8. Finally, save the new partition table Command (m for help): w The partition table has been altered!
  9. Ctrl-C to exit fdisk
  10. Eject the new disk and reinsert
  11. The new disk is recognized and rebuilding begins
  12. Wait for rebuild to complete
  13. PROFIT!!

I’m aware that on a full linux distribution, there are better approaches than this, but on the QNAP with its subset of commands, this gets the job done reasonably well.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Martin Jarvis
Software Developer (Senior) Freestyle Interactive Ltd
United Kingdom United Kingdom
I'm a lead developer for Freestyle Interactive Ltd where we create many wonderful websites built on Microsofts ASP.Net and Ektron CMS.

I've been developing .Net applications (both Windows and Web) since 2002.

You may also be interested in...

Comments and Discussions

GeneralOr just reboot..... Pin
DaveAuld5-Mar-14 3:13
protectorDaveAuld5-Mar-14 3:13 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web06-2016 | 2.8.180920.1 | Last Updated 1 Nov 2011
Article Copyright 2011 by Martin Jarvis
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid