Hi!
I had the same problem with formatting new disks with ffp installed, but i find the way how to fix it.
I have 4 HDDs not in raid.
When you need to add new HDD to NAS, you can use this step-by-step solution:
0. You need ffp plug installed;
1. Take out all HDDs from NAS;
2. Insert new HDD into drive bay 1;
3. Boot NAS, login into web admin site and format HDD;
4. Take out new HDD and insert old HDDs into their bays (disk with ffp installed must be in 1-st bay), then insert new HDD into free bay;
5. Boot NAS and login into it using ssh or telnet;
6. Run hd_verify. In output search for mtd_smagic value (something like 079e9865cf36a576c91......). Write it out somewhere. Also you need write out serials of all HDDs (in the begining of output of hd_verify). Write out serials in pairs: sda - serial, sdb - serial, etc.
7. Go into /mnt/HD_a4, there is file with name starting with dot, something like .x37c9E.
Structure of this file looks like:
magic: 079e9865cf36a576c91.............
mac: <mac address of nas>
node: sda
p2: NORMAL * <hdd serial1> * <hdd serial2> * <hdd serial3>
I have 4 HDD installed, so there is 3 serials. If you have less HDD, you'll get less serials (qty of HDDs - 1)
You need edit this file next way:
a) replace old magic with new one;
b) replace <hdd serials> with serials of all disks, except serial of current disk(in this case sda).
i.e.:
p2: NORMAL * <hdd serial1(sdb)> * <hdd serial2(sdc)> * <hdd serial3(sdd)>
8. Repeat step 7 for the same file on another disks (/mnt/HD_b4, c4, d4).
9. I'm not sure it's necessary, but in last step I execute write_hdverify.
10. Reboot NAS or simply mount all unmounted disks (mount /dev/sda2 /mnt/HD_a2, sdb2 -> HD_b2, etc.)
11. Check result of hd_verify.
That's all. Quite easy 
I had also some experiences with the installation of a new drive (Samsung F3 2TB HD203WI) into my DNS343 (2x HD103UJ 1TB and 2x HD154UI 1.5TB).
My plan was to replace the 1TB drive in slot 2. So I pulled the drives from slot 3&4 out and inserted the new 2TB in slot 2. Powered up, formatted the new drive in slot 2 and restarted the DNS343.
Silly but reality, both drives in slot 1&2 were formatted!

(I had saved my data from slot 1, before I began)

The second bad thing was that the system shows me only Volume_1 available.

So I started again and formatted both drives in slot 1&2 completely. Then added my old 1.5TB drives in slot 3&4 and rebooted. Now the DNS343 wants to format the drives in slot 3&4 – I skipped!
With the informations from this post it was clear what to do ...
OK, but still after restart of my DNS343 only Volume_1 was available in the network.
Here is the solution for my problem. Both later inserted drives in slot3&4 were not correctly configured – missed in the configuration files.
You should check in the directory /mnt/HD_a4, b4, c4, d4 of each drive also the following files with this structure for non RAID configuration:
1. File "ChkSCSI"
SCSI0 1
SCSI1 2
SCSI2 3
SCSI3 4
2. File "dsk_mapping"
sda
sdb
sdc
sdd
3. File "raidtab2web"
status,0
filesystem,ext3
nonraid,sda2,sdb2,sdc2,sdd2
md0,null,null,null,null,null,null,null
md1,null,null,null,null,null,null,null
md2,null,null,null,null,null,null,null
md3,null,null,null,null,null,null,null
After a restart the Volume_1 - 4 were available and the DNS343 is not asking to format any drives - great!
This is the quickest and safest way (for me) to add a new drive to the DNS343 before I spend days of copying data from one to another storage.
Big Thanks to xatus!
