ReadyNAS RN102 Inode Limit

The space used is irrelevant. You would need another 3TB disk:

readysecure1985 wrote:

Here is a simple guide to quickly recover a failed drive using dd_rescue. I often have to deal with pesky failed drives, so here is a quick simple guide how to achieve this with a free Linux Live CD and a PC with two SATA connections. I will be using a Knoppix 6.2 Live CD for this guide. Can be found at http://www.knoppix.net Using dd_rescue command allows you to copy data from one drive to another block for block. This is especially useful for recovering a failed drive. Often when a drive fails, the drive is still accessible, it has just surpassed the S.M.A.R.T. error threshold. dd_rescue allows you to ignore the bad sectors and continue cloning the bad drive to a new healthy drive. 1) Connect your old drive and new drive to your PC 2) Boot up using your Linux live CD 3) Launch a terminal window. 4) Run fdisk -l to make sure the system sees both of the hard drives. 5) Run hdparm -i /dev/sdx on both of the drives to find which drive is your source drive and which drive is your destination drive 6) Once you know which drive is which you can start the clone process. dd_rescue /dev/sdx(source disk) /dev/sdx(destination drive) 7) You will see the process start, just keep an eye on it, it might take a few hours for the clone job to finish, depending on the size of the drive. Once the process is complete, there will be no notification, the transfer will just stop and you will see the terminal prompt again. If you see a lot of errors or see that there is no more data being shown as succxfer: it means the drive got marked faulty by the kernel. At this point reboot the system and make sure you know which drive is which again, as it is possible they lettering might switch. Run the dd-rescue command again but this time with -r option. This will start the cloning again but this time will start from the back of the drive and will make sure to get the data that has not been cloned yet.

Once the disk is cloned you could try repairing the partition table etc. if you know what you're doing. If you do attempt to recover it yourself it is at your own risk.