Error creating Raid 5

[Jocko]

Sorry we posted in the same time...
and it is ok :-D
So now you must wait up to get a synchronized raid... As the next step you will need to restart the nas.

But now you can try to select the raid as new addons volume and posts

Code: Select all

cat /etc/nas_conf_db.xml| grep '<vol>' -C 11
cat /etc/nas_conf_db.xml| grep 'addonsvolume'
cat /rw_fs/etc/nas_conf_db.xml| grep '<vol>' -C 11
cat /rw_fs/etc/nas_conf_db.xml| grep 'addonsvolume'

[b1gnas]

Code: Select all

root@fvdwsl-base:/ # cat /etc/nas_conf_db.xml| grep '<vol>' -C 11
                                <partition>
                                        <lvname>/dev/sde8</lvname>
                                        <color>#8c81ba</color>
                                        <volid>1100</volid>
                                        <index>0</index>
                                        <size>928.377857208</size>
                                </partition>
                        </partitions>
                </disk>
        </disks>
        <vols>
                <vol>
                        <volid>1000</volid>
                        <md>/dev/sda8</md>
                        <fs>1000</fs>
                        <lastindex>1</lastindex>
                        <name>Vol-A</name>
                        <devices/>
                        <raidtype>single</raidtype>
                        <color>#aca72b</color>
                        <formatting>0</formatting>
                        <size>928.377857208</size>
                </vol>
                <vol>
                        <volid>1100</volid>
                        <md>/dev/md0</md>
                        <fs>1100</fs>
                        <lastindex>1</lastindex>
                        <name>RD5-0</name>
                        <devices>/dev/sdb8 missing /dev/sdd8 /dev/sde8 </devices>
                        <raidtype>raid5</raidtype>
                        <color>#31f4e4</color>
                        <formatting>0</formatting>
                        <size>2785.13323975</size>
                </vol>
root@fvdwsl-base:/ # cat /rw_fs/etc/nas_conf_db.xml| grep '<vol>' -C 11
                                <partition>
                                        <lvname>/dev/sde8</lvname>
                                        <color>#8c81ba</color>
                                        <volid>1100</volid>
                                        <index>0</index>
                                        <size>928.377857208</size>
                                </partition>
                        </partitions>
                </disk>
        </disks>
        <vols>
                <vol>
                        <volid>1000</volid>
                        <md>/dev/sda8</md>
                        <fs>1000</fs>
                        <lastindex>1</lastindex>
                        <name>Vol-A</name>
                        <devices/>
                        <raidtype>single</raidtype>
                        <color>#aca72b</color>
                        <formatting>0</formatting>
                        <size>928.377857208</size>
                </vol>
                <vol>
                        <volid>1100</volid>
                        <md>/dev/md0</md>
                        <fs>1100</fs>
                        <lastindex>1</lastindex>
                        <name>RD5-0</name>
                        <devices>/dev/sdb8 missing /dev/sdd8 /dev/sde8 </devices>
                        <raidtype>raid5</raidtype>
                        <color>#31f4e4</color>
                        <formatting>0</formatting>
                        <size>2785.13323975</size>
                </vol>
root@fvdwsl-base:/ #


[b1gnas]

Code: Select all

root@fvdwsl-base:/ # cat /etc/nas_conf_db.xml| grep 'addonsvolume'
                <addonsvolume>1100</addonsvolume>
root@fvdwsl-base:/ # cat /rw_fs/etc/nas_conf_db.xml| grep 'addonsvolume'
                <addonsvolume>1100</addonsvolume>
root@fvdwsl-base:/ #


[Jocko]

Ok
Now, we must wait for getting a clean raid
For my knowledge, if you do

Code: Select all

echo 100000 > /proc/sys/dev/raid/speed_limit_max

do you get a faster speed?

[b1gnas]

umh no... Always near 16000k/s

When recovey is finished, how can i add sda8? And do you think the speed will be the same or will fall down as always?

[Jocko]

So it is a CPU limit.

I give you later the command, need before to fix this addonsvolume resetting after reboot.

[b1gnas]

Ok... so let's wait

meanwhile... thanks for your precious support :hail

[Jocko]

I understand why the boot script resets the selected addons volume and it is a firmware bug :mrgreen:

Indeed with your posted new-addons.vol file, I see no technical share is moved on the new addons volume.
Technical shares are: plex-prog;pyload;tr-daemon;minidlna;twonkymedia;mt-daapd;mp3;tflux;oxylbox;cronjobs;mediatomb;motion-webcam;btsync;mldonkey;nzbget;owncloud;netatalk
Only two cases can explain this :
- You do not select the option 'Move the technical shares on the new volume'
- These shares are not yet created

The issue is the boot script keeps the selected add-ons volume only if it finds at least one technical share stored on the add-ons volume else it selects the system volume as add-on volume.

As there is no technical share on the raid volume the boot script selects again sda8. So it is a bad behaviour.

I go to send you a patch to fix it.

[Jocko]

In fact on your nas, there is no technical share and also you don't have yet created the share 'fvdw' (you lost it when you rewrote sda)

if fvdw share existed you would not have your issue :scratch

So attached a patch to fix it (and so you need to create the share fvdw...)

[Jocko]

I reloaded the patch file (I made a small change)