Xpenology and SAS Controller - HBA


Recommended Posts

Perfect. I have 4.3

So if I manually rezise it should work then?

What exact command should I use so it resize correctly? Hope you can help me last chapter of months of building this up.

Usage: resize2fs [-d debug_flags] [-f] [-F] [-M] [-P] [-p] device [new_size]

Link to post
Share on other sites

I can attach pictures.. not even the smallest ...forum filled up?

You can expand size to about 20452 GB.

File system Ext4

Status: Normal

Capacity: 12.60 TB

Used: 12.50 TB

Available: 102.24 GB

 

Disk Group Info:

Name:

Disk Group 1

 

Allocated: 19.97 TB

Unallocated: 1.81 TB

Capacity: 21.79 TB

 

Please can you send me the correct resize2fs command string using

Usage: resize2fs [-d debug_flags] [-f] [-F] [-M] [-P] [-p] device [new_size]

Thanks in advance. Last step now. :wink:

Link to post
Share on other sites

I have read about this problem on the internet and I have kernel

majorversion="4"

minorversion="3"

buildphase="release"

buildnumber="3810"

smallfixnumber="0"

builddate="2013/11/06"

 

Will this mean that I CAN resize in live mode or do I need to dismount volume or whatever and the resize....bla bla.

I have no clue how to do this because its linux. But I learn a few steps every day.

 

I would be very appreciated if someone could build a package for this issue that is absolutely needed for XPEsynology builds.

I now just have this step left and need full assistance to get this resizing to work without loosing the data.

Can someone of you help me out here..private mail can also be sent and later we could add the solution here.

Thanks so far for all help.

Sit and wait again for response. :geek:

Link to post
Share on other sites

This is the messages in the log I get when trying normally to expand from DSM 4.3.

So what I want to do is to resize now by the prompt. But would like to do it the correct way.

Is this the correct way to type these commands below or do I need to think about anything else?

unmount -f /volume1

e2fsck -f /dev/volume_1

resize2fs /dev/volume_1

 

Will this work... do I dare to try?

Link to post
Share on other sites

Nope does not work as I would like to....

 

lrwxrwxrwx 1 root root 37 Mar 8 09:59 syno_vg_reserved_area -> /dev/mapper/vg1-syno_vg_reserved_area

lrwxrwxrwx 1 root root 24 Mar 8 09:59 volume_1 -> /dev/mapper/vg1-volume_1

Nasse> resize2fs -fpF /dev/vg1/volume_1

resize2fs 1.42.6 (21-Sep-2012)

resize2fs: Device or resource busy while trying to open /dev/vg1/volume_1

Couldn't find valid filesystem superblock.

Nasse> resize2fs /dev/vg1/volume_1

resize2fs 1.42.6 (21-Sep-2012)

resize2fs: Device or resource busy while trying to open /dev/vg1/volume_1

Couldn't find valid filesystem superblock.

Nasse>

Link to post
Share on other sites

Find the solution yesterday....it was easy I needed to totally stop all processes. These are the commands to get the expanding to work....its not ready but at least working fine.

Will take a few days. :razz:

 

A brief summary of the full procedure is as follows:

 

Be aware that my volume is named "volume_1" your name can be different.

 

Volume Checking and Repair

==========================

1. Telnet to "Your NAS IP" using Putty.

2. Login as "root"

3. Password is same as "admin" account.

4. Turn of all tasks using:

syno_poweroff_task

Note: Once you perform syno_poweroff_task, it only allows to access through Telnet/SSH.

 

5. Make all volumes active using:

vgchange -ay

 

6. Do a full check/repair of the file system using:

fsck.ext4 -yvf -C 0 /dev/vg1/volume_1

 

7. Manually expand the volume using:

resize2fs -fpF /dev/vg1/volume_1

 

8. Restart the DS software using:

reboot

Link to post
Share on other sites

After resizing according to the procedure above and even after reboot the system says crashed. Pictures cant be uploaded I do not know why....

Is there anything I can fix this with? I can still reach all data.

 

The Volume is status: Crashed....any tip how to fix this error and get it go away?

At this point I have started the data scrubbing and it will take a long time.

but that is the only thing I can do before I get more tips. :oops:

 

Ok. noone dare to answer...I do now backup all data and make a totally new installation and copy all data back in a fresh environment

then it will be perfect and no messing around and test any more.

The DSM 5.0 I wait to install due to to early ....for XPEnology version.

Link to post
Share on other sites

Hey guys,

 

I've been running the v1.0 for a short while and am being very happy with it. The VAAI support for VMWare is awesome (and the mainreason for running xpenology for me).

However, I have a need to connect a few more disks to the NAS than the motherboard supports, so I have an LSI 2008 card lying around. (MPT 2 Fusion)

 

Now, unfortunately due to the broken iSCSI/VAAI in beta7 I cannot use the HBA version.

Is there a possibility/process for getting this card work in the V1.0?

 

I've been looking for some info in this thread, and it seems it can be done, but being a bit of a Linux beginner, can someone shed some more light on the correct process?

 

Thanks!

Link to post
Share on other sites
After resizing according to the procedure above and even after reboot the system says crashed. Pictures cant be uploaded I do not know why....

Is there anything I can fix this with? I can still reach all data.

 

The Volume is status: Crashed....any tip how to fix this error and get it go away?

At this point I have started the data scrubbing and it will take a long time.

but that is the only thing I can do before I get more tips. :oops:

 

Ok. noone dare to answer...I do now backup all data and make a totally new installation and copy all data back in a fresh environment

then it will be perfect and no messing around and test any more.

The DSM 5.0 I wait to install due to to early ....for XPEnology version.

 

I don't have an answer on what to do for you, but I'm going to guess that DSM is saying your array is crashed is because the volume group config doesn't match your array anymore.

 

Again, not sure I know what I am talking about :oops: But when I was expanding my array (swapping in bigger disks one by one) within DSM, and letting it do it's thing, it messed up on the last disk and said my array was crashed. To fix it I had to manually restore a previous vg1000 config from /etc/lvm/archives/ that matched the setup of 3/4 disks when the system last worked correctly. Once I did that I booted into degraded array, and could add my 4th disk to repair.

 

But I dunno if you'd have the correct backup config since you did things manually from shell, as I'm not sure what process creates the backups (DSM?). best bet is to do what you're doing, backup your data and start fresh.

Link to post
Share on other sites
Hey guys,

 

I've been running the v1.0 for a short while and am being very happy with it. The VAAI support for VMWare is awesome (and the mainreason for running xpenology for me).

However, I have a need to connect a few more disks to the NAS than the motherboard supports, so I have an LSI 2008 card lying around. (MPT 2 Fusion)

 

Now, unfortunately due to the broken iSCSI/VAAI in beta7 I cannot use the HBA version.

Is there a possibility/process for getting this card work in the V1.0?

 

I've been looking for some info in this thread, and it seems it can be done, but being a bit of a Linux beginner, can someone shed some more light on the correct process?

 

Thanks!

 

Try Trantor 4.3-3810 v1.4 ??

Link to post
Share on other sites

That is correct, but I could do that with the HBA Beta7 version as well.

The problem there being that with IET mode there's no VMware VAAI support, whch kinda is the entire point of me using xpenology :sad:

 

So I'm still wondering how I could add the necessary driver and fixes for just the mpt2sas cards myself to trantor's v1.0 :s

Link to post
Share on other sites
That is correct, but I could do that with the HBA Beta7 version as well.

The problem there being that with IET mode there's no VMware VAAI support, whch kinda is the entire point of me using xpenology :sad:

 

So I'm still wondering how I could add the necessary driver and fixes for just the mpt2sas cards myself to trantor's v1.0 :s

 

The same reason why I tried XPEnology, but LIO iSCSI is not fully functional. Got it working eventually (file & block backend)!

 

I'm working on fixing mpt2sas iSCSI issue with my boot image. Here's my test results:

 


IET+noop vt-d - Raid0 block level (2 SSDs)  
-----------------------------------------------------------------------
CrystalDiskMark 3.0.3 x64 (C) 2007-2013 hiyohiyo
                          Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [sATA/300 = 300,000,000 byte/s]

          Sequential Read :    74.706 MB/s
         Sequential Write :    96.323 MB/s
        Random Read 512KB :    66.134 MB/s
       Random Write 512KB :    85.864 MB/s
   Random Read 4KB (QD=1) :     5.925 MB/s [  1446.7 IOPS]
  Random Write 4KB (QD=1) :     6.490 MB/s [  1584.4 IOPS]
  Random Read 4KB (QD=32) :    63.203 MB/s [ 15430.4 IOPS]
 Random Write 4KB (QD=32) :    89.203 MB/s [ 21778.0 IOPS]

 Test : 1000 MB [i: 0.3% (0.0/10.0 GB)] (x5)
 Date : 2014/03/18 20:09:15
   OS : Windows 7 Ultimate [6.1 Build 7600] (x64)

IET+cfq vt-d - Raid0 block level (2 SSDs) 
-----------------------------------------------------------------------
CrystalDiskMark 3.0.3 x64 (C) 2007-2013 hiyohiyo
                          Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [sATA/300 = 300,000,000 byte/s]

          Sequential Read :    77.226 MB/s
         Sequential Write :    95.568 MB/s
        Random Read 512KB :    64.591 MB/s
       Random Write 512KB :    85.319 MB/s
   Random Read 4KB (QD=1) :     5.907 MB/s [  1442.2 IOPS]
  Random Write 4KB (QD=1) :     6.841 MB/s [  1670.2 IOPS]
  Random Read 4KB (QD=32) :    60.185 MB/s [ 14693.6 IOPS]
 Random Write 4KB (QD=32) :    78.320 MB/s [ 19121.0 IOPS]

 Test : 1000 MB [i: 0.3% (0.0/10.0 GB)] (x5)
 Date : 2014/03/18 20:17:23
   OS : Windows 7 Ultimate [6.1 Build 7600] (x64)

LIO+noop vt-d - Raid0 file level (2 SSDs)
-----------------------------------------------------------------------
CrystalDiskMark 3.0.3 x64 (C) 2007-2013 hiyohiyo
                          Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [sATA/300 = 300,000,000 byte/s]

          Sequential Read :    69.090 MB/s
         Sequential Write :    88.915 MB/s
        Random Read 512KB :    53.987 MB/s
       Random Write 512KB :    77.443 MB/s
   Random Read 4KB (QD=1) :     6.942 MB/s [  1694.8 IOPS]
  Random Write 4KB (QD=1) :     2.786 MB/s [   680.1 IOPS]
  Random Read 4KB (QD=32) :    48.489 MB/s [ 11838.2 IOPS]
 Random Write 4KB (QD=32) :    38.899 MB/s [  9496.8 IOPS]

 Test : 1000 MB [G: 0.8% (0.1/10.0 GB)] (x5)
 Date : 2014/03/19 19:21:37
   OS : Windows 7 Ultimate [6.1 Build 7600] (x64)

LIO+cfq vt-d - Raid0 file level (2 SSDs)
-----------------------------------------------------------------------
CrystalDiskMark 3.0.3 x64 (C) 2007-2013 hiyohiyo
                          Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [sATA/300 = 300,000,000 byte/s]

          Sequential Read :    63.148 MB/s
         Sequential Write :    87.762 MB/s
        Random Read 512KB :    67.471 MB/s
       Random Write 512KB :    75.709 MB/s
   Random Read 4KB (QD=1) :     6.395 MB/s [  1561.4 IOPS]
  Random Write 4KB (QD=1) :     2.576 MB/s [   628.9 IOPS]
  Random Read 4KB (QD=32) :    43.786 MB/s [ 10690.0 IOPS]
 Random Write 4KB (QD=32) :    39.534 MB/s [  9652.0 IOPS]

 Test : 1000 MB [G: 0.8% (0.1/10.0 GB)] (x5)
 Date : 2014/03/19 19:30:53
   OS : Windows 7 Ultimate [6.1 Build 7600] (x64)

Link to post
Share on other sites

Fixed!

 

LIO+noop vt-d - Raid0 block level (2 SSDs)
-----------------------------------------------------------------------
CrystalDiskMark 3.0.3 x64 (C) 2007-2013 hiyohiyo
                          Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [sATA/300 = 300,000,000 byte/s]

          Sequential Read :    67.032 MB/s
         Sequential Write :    73.512 MB/s
        Random Read 512KB :    39.569 MB/s
       Random Write 512KB :    84.716 MB/s
   Random Read 4KB (QD=1) :     5.331 MB/s [  1301.4 IOPS]
  Random Write 4KB (QD=1) :     3.458 MB/s [   844.2 IOPS]
  Random Read 4KB (QD=32) :    54.260 MB/s [ 13247.0 IOPS]
 Random Write 4KB (QD=32) :    44.853 MB/s [ 10950.5 IOPS]

 Test : 1000 MB [G: 0.8% (0.1/10.0 GB)] (x5)
 Date : 2014/03/19 21:57:42
   OS : Windows 7 Ultimate [6.1 Build 7600] (x64)

 

[spoiler=]29xgbpg.jpg

osvocz.jpg

 

Link to post
Share on other sites

I have now worked with the 4.3 releases since new year and I have almost got all working.

BUT...for all of you. There is for me no secured way to expand the volume in Raid 6 SHR-2 when using 14 or more disks.

When I added a 2TB disk extra to my volume so it will be 14 disks in the volume I got it into the volume but it do not

have the possibility to expand the volume inside the DSM.

 

I had same problem a couple of weeks ago also doing the same but added 2 disks at the same time.

Then I tried following all guides to manually expand the volume and it did worked to expand the volume but

the volume was crashed somehow and could not write to the volume all files read only. I had to backup all data

again and made a totally new installation.

Now again I am at the same situation and added 1 disk and that worked ok but cant be expanding the volume in DSM.

Now is my question if anyone have used more than 14 disks in a volume. If so...I am pretty sure it worked to create it

and have all capabilities to use the data environment as when you created it, but the problem is that IF a disk crashes

you will be able to fix the volume due to expanding not working with so many disks. Even if you typed in 16 as amount of disk

in the synoinfo.conf files.

 

Do anyone have got a working system with 14 disks and tried to replaced one disk???

If not then I suggest that I would be for sure super happy if this wonderful system could be added to work with lot of more disks.

I guess to start building it on another kernel for the larger Synology stations.

I even pay for it.

 

thanks all for all contributing of info and questions that helped me a lot these months....but I have now to start making backup again

but I did not move over so much data this time so I will start over again with fewer disks so I get this system up and running and

start over when I got response on this question. any tip or trick is wormly appreciated.

Link to post
Share on other sites

I have now worked with the 4.3 releases since new year and I have almost got all working.

BUT...for all of you. There is for me no secured way to expand the volume in Raid 6 SHR-2 when using 14 or more disks.

When I added a 2TB disk extra to my volume so it will be 14 disks in the volume I got it into the volume but it do not

have the possibility to expand the volume inside the DSM.

 

I had same problem a couple of weeks ago also doing the same but added 2 disks at the same time.

Then I tried following all guides to manually expand the volume and it did worked to expand the volume but

the volume was crashed somehow and could not write to the volume all files read only. I had to backup all data

again and made a totally new installation.

Now again I am at the same situation and added 1 disk and that worked ok but cant be expanding the volume in DSM.

Now is my question if anyone have used more than 14 disks in a volume. If so...I am pretty sure it worked to create it

and have all capabilities to use the data environment as when you created it, but the problem is that IF a disk crashes

you will be able to fix the volume due to expanding not working with so many disks. Even if you typed in 16 as amount of disk

in the synoinfo.conf files.

 

Do anyone have got a working system with 14 disks and tried to replaced one disk?

If not then I suggest that I would be for sure super happy if this wonderful system could be added to work with lot of more disks.

I guess to start building it on another kernel for the larger Synology stations.

I even pay for it.

 

thanks all for all contributing of info and questions that helped me a lot these months....but I have now to start making backup again

but I did not move over so much data this time so I will start over again with fewer disks so I get this system up and running and

start over when I got response on this question. any tip or trick is wormly appreciated.

Link to post
Share on other sites
  • 4 months later...

I actually find myself doing this now

 

I do not create a volume....

 

1st I create a DISK GROUP...

 

Then Create volumes on top of the DISK GROUP

 

saves any 16TB volume problems and having to work around them

 

eg

 

15 x 2TB Drives

 

Create DISK GROUP of Multiple Volumes on Raid

Choose Raid 6

 

Disk Group gets Created = Size of 13 x 2TB Drives (2 of the 15 Drives lost to Raid 6 double parity)

26TB Disk Group

 

Then Create Volume 1 say 12TB

Then Create Volume 2 say 3TB for NFS Share to Virtuals

Then Create Volume 3 say 6TB for Rsync Backups of Linux Hosts

 

Remaining "Free Space" of the Disk Group can later be used to expand any Volume 1,2 or 3 if I need more space on either

 

.

Link to post
Share on other sites
  • 4 months later...

hello,

 

as of now, i am running dam 5.0 latest version with update 2.

i have an lei controller which you worked with and it is recognised. i am trying to do the hex calculation and that is exactly where it starts to get a little bit confusing.

in total i have 8 sata ports on the controller and 6 sata ports on the main board, plus one msata and one esata port. totalling 16 ports. the msata port is recognised and works perfectly fine.

with usb, i am a little confused. there is a total of 14 usb ports on the mainbors, however it show a lot more here, i guess one controller is duplicated or so.

how do i setup the hex calculation for the esata port?

does it work at all or should i just leave it out and consider it internal? how about the usb ports? i think i can deactivate each single usb port in bios.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.