Jump to content

Add new drive with data to existing system


seanant

Recommended Posts

I have the software up and working great.  I just got done with the parity check for my largest drive.  I want to add a large drive with quite a bit if data on it now as part of the array.  What is the procedure to add another drive to the array while keeping all of the data intact?

Thanks -SEAN

Link to comment

How is the drive currently partitioned? What filesystem does the drive have?

 

If it's not partitioned into a single partition starting at sector 63 extending the entire size of the disk with a REISER FileSystem on it, there's no way to add it preserving data.

Link to comment

I figured out a way!!!!  Takes time but works.

1.  Take identical size drive and format as the parity drive.

2.  Remove drive and place in a separate Linux box, in my case FC7, and mount.  If you need help here please let me know.

3.  Copy data over to drive.  I used rsync and it worked like a champ.

4.  Place this drive and the drive that will be your new parity drive in the unRAID box.

5.  Build array with new parity drive and select the old parity drive from step #1 as Disk1.

6.  Add additional drives as needed.

7.  Start and let the array build.  unRAID detected the existing data and made shares.

The key is formatting the drive for reiserfs.

 

Link to comment

The same as any other Linux distro since unRAID is built on top of Slackware. Unfortunately, not all filesystem drivers like ext3 are compiled into the kernel. Fortunately ext3 can be mounted as read-only as an ext2 type.

 

mount -r -t ext2 <device> <dir>

 

Replace device and dir as appropriate.

 

mkdir -p /mnt/data
mount -r -t ext2 /dev/sdd1 /mnt/data

 

Link to comment

I am trying to mount another drive and copy more data over.  It is hda1.  This is the error I am getting:

 

root@Tower:/# mount -r -t ext2 /dev/hda1 /mnt/data/

mount: wrong fs type, bad option, bad superblock on /dev/hda1,

      missing codepage or helper program, or other error

      In some cases useful info is found in syslog - try

      dmesg | tail  or so

 

root@Tower:/#

 

What does this mean?  Thank You -Sean

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...