Error creating Raid 5

[b1gnas]

Code: Select all

00 - Create a temporary copy of the current NAS database file: OK
10 - Lists which servers are installed or running and stops them
15 - Stop the common servers
Samba: stopped
20 - Save the new selected addons volume
30 - Restore the file system fvdw share
Move fvdw (be patient) ... OK
40 - Restore some file system symlinks
70 - Restore technical shares
80 - Restart servers
restart Samba server
99 - Backup the original nas database file: OK


[Jocko]

Note: in version 16.1, fvdw can be created only on the addons volume even if you select another one ;)

Currently, what is the raid status ?

---see your last post ---
Why do you select another addons volume? If I understand well, the addons volume was already the raid5 :thinking

now to share the same information level, post

Code: Select all

ls -l /direct-usb
ls -l /direct-usb/fvdw
cat /etc/nas_conf_db.xml|grep addonsvolume
cat /etc/nas_conf_db.xml|grep fvdw

[b1gnas]

The raid is recovering
I thought that i had to set addons volume back to sda and to rd5-0 again.
Now is set on rd5-0

Code: Select all

root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [                                 raid5] [raid4] [raid10]
md0 : active raid5 sdc8[4] sdb8[0] sde8[3                                 ] sdd8[2]
      2920423872 blocks level 5, 64k chun                                 k, algorithm 2 [4/3] [U_UU]
      [===========>.........]  recovery =                                  56.3% (548889920/973474624) finish=439.5                                 min speed=16100K/sec

unused devices: <none>

root@fvdwsl-base:/ # ls -l /direct-usb
lrwxrwxrwx  1 root root 11 2015-09-24 17:02 /direct-usb -> /share/1100

root@fvdwsl-base:/ # ls -l /direct-usb/fvdw
total 12
drwxrwxrwx  2 root root 4096 2015-09-24 16:57 addons
drwxrwxrwx  2 root root 4096 2015-09-24 16:26 cron-boot
drwxrwxrwx  2 root root 4096 2015-09-24 17:01 mydictionary

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

root@fvdwsl-base:/ # cat /etc/nas_conf_db.xml|grep fvdw
                <hostname>fvdwsl-base</hostname>
                <netbiosname>fvdwsl-base</netbiosname>
                <serverdesc>fvdw-sl NAS</serverdesc>
                        <sharename>fvdw</sharename>
root@fvdwsl-base:/ #


[Jocko]

Thank b1gnas.

When synchronize job will stop, try to restart the nas and see if the addons volume is still your raid5.

If yes, tomorrow we will try to add sda8 in the raid5 and check if you have still a slow speed :?

[b1gnas]

Code: Select all

root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdc8[1] sdb8[0] sde8[3] sdd8[2]
      2920423872 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

unused devices: <none>
root@fvdwsl-base:/ #


Hi Jocko,
After reboot, from the webinterface rd5-0 is selected in the addons-volume tab

[Jocko]

Hi b1gnas,

ok, so now all seems to be ok except for the controller issue (we will see this point later)

to include a new member in a raid, you need to do this sequence,

- first, I'd rather you work with the raid umounted (we go to resize its fs)

Code: Select all

umount /dev/md0

Note: fvdw content is now no longer available

- Unmount sda8

Code: Select all

umount /dev/sda8

- Change the fs type on sda8 fd instead of 83 (use fdisk and the command you well known now ;) )
fdisk /dev/sda -> t -> 8 -> fd ->w

- To add the 5th disk, after making the raid5 with 4 devices, in a root terminal do :
Note: include only sda8 if all disks are active in the raid5 otherwise mdadm will replace a faulty disk by sda8 and you won't be able to increase the raid (It is the purpose of yesterday step).
*Include the device in the raid array

Code: Select all

mdadm --manage /dev/md0 --add /dev/sda8

(sda8 is then a spare device)
* Increase the raid size

Code: Select all

mdadm --grow /dev/md0 --raid-devices=5

Post the outputs of

Code: Select all

cat /proc/mdstat
mdadm --detail /dev/md0

* extend the file system

Code: Select all

resize2fs /dev/md0

* save the new raid configuration

Code: Select all

cat /etc/mdadm.0 > /etc/mdadm.conf
mdadm --detail --scan >> /etc/mdadm.conf

Note: if you included previously sda8 in a raid you need to clear its superblok before adding it. (but this should not be the case as you have reformatted sda

Code: Select all

mdadm --zero-superblock /dev/sda8

Then after rebooting you should have a raid5 with 5 members

[b1gnas]

Long wait for e2fsck command

Code: Select all

root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sda8[4] sdb8[0] sde8[3] sdd8[2] sdc8[1]
      2920423872 blocks super 0.91 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
      [>....................]  reshape =  0.1% (1309760/973474624) finish=2207.9min speed=7338K/sec

unused devices: <none>
root@fvdwsl-base:/ # mdadm --detail /dev/
md0
/dev/md0:
        Version : 00.91.03
  Creation Time : Wed Nov 16 13:22:21 2011
     Raid Level : raid5
     Array Size : 2920423872 (2785.13 GiB 2990.51 GB)
    Device Size : 973474624 (928.38 GiB 996.84 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Sep 25 10:48:43 2015
          State : clean, recovering
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

 Reshape Status : 0% complete
  Delta Devices : 1, (4->5)

           UUID : fa58a2b1:a56fc1c1:2a5b9325:5626151a
         Events : 0.412

    Number   Major   Minor   RaidDevice State
       0       8       56        0      active sync   /dev/sdb8
       1       8       40        1      active sync   /dev/sdc8
       2       8       24        2      active sync   /dev/sdd8
       3       8        8        3      active sync   /dev/sde8
       4       8       72        4      active sync   /dev/sda8
root@fvdwsl-base:/ # resize2fs /dev/md0
resize2fs 1.42.11 (09-Jul-2014)
Please run 'e2fsck -f /dev/md0' first.

root@fvdwsl-base:/ # e2fsck -f /dev/md0
e2fsck 1.42.11 (09-Jul-2014)
Pass 1: Checking inodes, blocks, and sizes
^@Pass 2: Checking directory structure   Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary informatio
/dev/md0: 17/182534144 files (0.0% non-cocks
root@fvdwsl-base:/ # resize2fs /dev/md0
resize2fs 1.42.11 (09-Jul-2014)
The filesystem is already 730105968 blocks long.  Nothing to do!

root@fvdwsl-base:/ # cat /etc/mdadm.0 > /
etc/mdadm.conf
root@fvdwsl-base:/ # mdadm --detail --sca
n >> /etc/mdadm.conf
root@fvdwsl-base:/ #

Now can i reboot or i have to wait for reshape to be completed?

[Jocko]

[>....................] reshape = 0.1% (1309760/973474624) finish=2207.9min speed=7338K/sec

:woohoo
So that' would mean that the misaligned end block on sda8 was the issue... :thumbup

It seems that you need to wait for ending the array reshaping before updating the fs on md0 currently you still have a raid size ~3TB

So wait and retry to do

Code: Select all

resize2fs /dev/md0

and then you will be able to restart the NAS.

But can you post again

Code: Select all

mdadm --detail /dev/md0

[b1gnas]

Yes!! It seems it's working finally!! :-)

So let's wait and fingers crossed!

Code: Select all

root@fvdwsl-base:/ # mdadm --detail /dev/
md0
/dev/md0:
        Version : 00.91.03
  Creation Time : Wed Nov 16 13:22:21 2011
     Raid Level : raid5
     Array Size : 2920423872 (2785.13 GiB 2990.51 GB)
    Device Size : 973474624 (928.38 GiB 996.84 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Sep 25 14:43:30 2015
          State : clean, recovering
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

 Reshape Status : 7% complete
  Delta Devices : 1, (4->5)

           UUID : fa58a2b1:a56fc1c1:2a5b9325:5626151a
         Events : 0.1521

    Number   Major   Minor   RaidDevice State
       0       8       56        0      active sync   /dev/sdb8
       1       8       40        1      active sync   /dev/sdc8
       2       8       24        2      active sync   /dev/sdd8
       3       8        8        3      active sync   /dev/sde8
       4       8       72        4      active sync   /dev/sda8
root@fvdwsl-base:/ #

[b1gnas]

Reshape done, but resize error

Code: Select all

root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sda8[4] sdb8[0] sde8[3] sdd8[2] sdc8[1]
      3893898496 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>
root@fvdwsl-base:/ # resize2fs /dev/md0
resize2fs 1.42.11 (09-Jul-2014)
Resizing the filesystem on /dev/md0 to 973474624 (4k) blocks.
resize2fs: Memory allocation failed while trying to resize /dev/md0
Please run 'e2fsck -fy /dev/md0' to fix the filesystem
after the aborted resize operation.
root@fvdwsl-base:/ #