Author Topic: FlexRAID tRAID 1.1 Final (new release 2017-11-24)  (Read 1586 times)

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« on: November 27, 2017, 02:35:22 am »
FlexRAID tRAID 1.1 Final (new release 2017-11-24)




Fixed:
Code: [Select]
- Fixed bugs as reported on http://bug.flexraid.com:
0000447 Starting of storage pool end-up in a blocking loop if regular expression for landing-disk is invalid
0000441 Mercurial still not working correctly (Permission denied)
0000442 Cannot delete Log-Raid fhd file
0000440 File statistics broken after applying Mercurial fix
0000433 Cannot create a Shortcut on a Storage Pool with T-Raid...
0000434 Mercurial push does not work
0000417 tRAID crashes when writing a file that over flows the first drive in the array.
0000416 Raid monitoring plugin, file statistics, and forensic give errors
0000418 Failed File and RAID statistics
0000423 Raid Monitoring Tab has no Data - ErrorCode=31
0000436 No individual file statistics for old drives in Dashboard
0000407 Issue with Physical Drives List
0000425 Recycle bin feature can cause non-empty folders to be deleted
- Fixed defect whereas storage pool would in some merge cases move data to a hidden folder when URB is enabled

Improvements:
Quote
- Lots of performance and stability improvements
- New performance features: SIMT & Write Chatter (http://forum.flexraid.com/index.php/topic,49418.0.html)

Linux kernel support:
Quote
Supported distributions are (*):
  • Ubuntu Linux 14 LTS and its derivatives (including Linux Mint): kernel 3.19.0-80-generic or ABI compatible
  • Ubuntu Linux 16 LTS and its derivatives (including Linux Mint): kernel 4.10.0-40-generic or ABI compatible
  • Redhat Enterprise Linux (RHEL) 7/7.x and its derivatives (including CentOS 7/7.x): kernel 3.10 lts
(*) Note that the host package requires a 64 bit OS. However, the Web Client can be installed on both 64 bit and 32 bit systems.


« Last Edit: November 30, 2017, 05:04:23 am by Brahim »

Offline cogliostrio

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +2/-0
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #1 on: December 01, 2017, 03:05:58 pm »
Ive been trying out the new release, but Ive got some trouble with it.

This is on a fresh install of Ubuntu 16 with linux-image-4.10.0-40-generic kernel.

Isnt the kernel/broker supposed to be matching?
Code: [Select]
OS: Linux MEGADRIVE 4.10.0-40-generic #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Broker: 1.1.0 2017.11.25
Kernel: 1.0.0 2017.11.25

Code: [Select]
[2017-12-01 21:13:46.190558][2695141248]Software termination signal received... exiting...
[2017-12-01 21:13:46.190649][2695141248][INFO]:[NZFS Service Broker] Exiting...

[2017-12-01 21:45:24.885134][2665531264]Software termination signal received... exiting...
[2017-12-01 21:45:24.885230][2665531264][INFO]:[NZFS Service Broker] Exiting...


Code: [Select]
[2017-12-01 21:45:25,171] ERROR explore(248) - Connection refused
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.class)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.class)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.class)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.class)
        at java.net.Socket.connect(Socket.class)
        at com.tchegbe.nzfs.ui.server.net.NZFSSocketClient.init(NZFSSocketClient.java:225)
        at com.tchegbe.nzfs.ui.server.net.NZFSSocketClient.execute(NZFSSocketClient.java:225)
        at com.tchegbe.nzfs.ui.server.util.NZFSHostHelper.getResponse(NZFSHostHelper.java:107)
        at com.tchegbe.nzfs.ui.server.util.NZFSHostHelper.getLogicalDrives(NZFSHostHelper.java:107)
        at com.tchegbe.nzfs.ui.server.op.NZFSExplorerOperations.getLogicalDrives(NZFSExplorerOperations.java:757)
        at com.tchegbe.nzfs.ui.server.op.NZFSExplorerOperations.explore(NZFSExplorerOperations.java:757)
        at com.tchegbe.nzfs.ui.server.rpc.NZFSServiceImpl.explore(NZFSServiceImpl.java:248)
        at com.google.gwt.user.server.rpc.RPC.invoke(Method.class)
        at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
        at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
        at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1359)
        at com.tchegbe.lib.gwt.server.servlet.SecurityFilter.doFilter(SecurityFilter.java:30)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1330)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:478)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:47)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
        at org.eclipse.jetty.server.Server.handle(Server.java:349)
        at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
        at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224)
        at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:50)
        at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector$.java:245)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1359)
        at com.tchegbe.lib.gwt.server.servlet.SecurityFilter.doFilter(SecurityFilter.java:30)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1330)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:478)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:47)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
        at org.eclipse.jetty.server.Server.handle(Server.java:349)
        at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
        at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224)
        at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:50)
        at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector$.java:245)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
        at java.lang.Thread.run(Thread.class)
[2017-12-01 21:45:24,903] INFO  run(757) - Stopping all stoppable threads on shutdown hook...
[2017-12-01 21:46:41,923] INFO  start(56) - Overriding locale to en_US

[2017-12-01 21:46:42,086] INFO  start(56) - Setting Http port to 8080
[2017-12-01 21:46:42,086] INFO  start(56) - Https port not set. Https requests will not be serviced...
[2017-12-01 21:46:43,071] INFO  init(248) - Build date: 2017.11.22
[2017-12-01 21:46:43,071] INFO  init(248) - Session UUID: d99cd830-b926-4fdc-a919-5208994ae959
[2017-12-01 21:46:48,278] WARN  init(248) - Connection refused

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #2 on: December 01, 2017, 04:41:36 pm »
...
Isnt the kernel/broker supposed to be matching?
Code: [Select]
OS: Linux MEGADRIVE 4.10.0-40-generic #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Broker: 1.1.0 2017.11.25
Kernel: 1.0.0 2017.11.25
...
There is indeed a typo in the Linux Kernel version.

As far as your issues, try to see what dmesg says (sudo dmesg > /tmp/dmesg.txt).

If anything, it would be a problem at the broker level. I would give strace a go (sudo strace -p pid). Of course you would get the PID from grep (ps -aux | grep NZFSB).
« Last Edit: December 01, 2017, 04:49:04 pm by Brahim »

Offline cogliostrio

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +2/-0
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #3 on: December 02, 2017, 02:53:10 am »
This is the same hardware I have been running on for years (apart from a few new HDDs). I was running Ubuntu 14 LTS prior to upgrading.

Here is the output requested. This is with the array and pool set to manual start. If I set the array and pool to autostart. The array starts, but not the pool. The physical drives and mounted volumes does not load in the UI if I do set both array and pool to autostart.



ps -aux | grep NZFSB
Code: [Select]
root      1275  0.0  0.0 1872380 4552 ?        Sl   10:12   0:00 NZFSB
coglios+  2018  0.0  0.0  14228   936 pts/0    S+   10:13   0:00 grep --color=auto NZFSB

sudo strace -p 1275
Code: [Select]
strace: Process 1275 attached
accept(4, {sa_family=AF_INET, sin_port=htons(41266), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41268), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41270), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41272), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41274), sin_addr=inet_addr("192.168.1.110")}, [16]) = 6
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41276), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41278), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41280), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41282), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41284), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41286), sin_addr=inet_addr("192.168.1.110")}, [16]) = 6
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4, {sa_family=AF_INET, sin_port=htons(41288), sin_addr=inet_addr("192.168.1.110")}, [16]) = 5
futex(0x7fffc4b0897c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7fffc4b08978, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7fffc4b08950, FUTEX_WAKE_PRIVATE, 1) = 1
accept(4,

sudo strace -p 2018
Code: [Select]
strace: attach: ptrace(PTRACE_ATTACH, ...): No such process


Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #4 on: December 02, 2017, 06:58:55 am »
Okay, so the issue is isolated to the service broker (NZFSB). The kernel component is functioning just fine.

Try this:
  • Disable the pool auto-start option
  • Start the array but not the pool
  • Set the host to log in TRACE mode. In the Web UI, select to edit the host and you will see the option to set the log level for the host.
  • Do another sudo strace -p pid >> /tmp/strace.txt
  • Finally, try to start the pool. It will fail, but we want to see the extra logs.
  • Attach both /tmp/strace.txt and /var/log/NZFSB.log here

Offline cogliostrio

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +2/-0
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #5 on: December 02, 2017, 08:21:40 am »
Host set to trace. Autostart for array and pool is turned off.

sudo strace -p 1304 >> /tmp/strace.txt

Starting array.
This does not seem to complete, just keeps loading. After doing a refresh of the page, it appears to have started. Start button is now greyed out, and physical drives and mounted volumes does not load (spinning circle indicating they are loading).

Starting pool.
This keeps loading, without appearing to complete. Reloading the page does not work for this (times out).

As a side note, the command "sudo strace -p pid >> /tmp/strace.txt" did not save anny text. So I copied the output from terminal window.

Offline cogliostrio

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +2/-0
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #6 on: December 02, 2017, 08:22:42 am »
Can only add one attachment to a post?

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #7 on: December 02, 2017, 08:39:31 am »
The array must be up for the collected logs to be relevant. Basically, this needs to go one step at a time.

If the array is not starting properly, then that needs to be investigated and resolved as a first step.

So, going back to the basics.
  • Let's test with both the array and pool not mounted.
    • Are you able to use the Web UI and browse whatever mounts you see?
    • Are you able to query for SMART? Etc.
    • Are you able to do the above after 5/10/30 minutes of the tRAID services being up?
  • Test whether the array (without) pool mounts successfully.
    • With the array online, are you able to run a small range (1GB) Verify?
    • Are you able to use the Web UI to get SMART while the array is up?
    • Are you able to do the above after 5/10/30 minutes of the tRAID services being up?

Once the above is fully resolved, then we can investigate the pool.

Offline cogliostrio

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +2/-0
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #8 on: December 02, 2017, 09:53:56 am »

Your the expert, just trying to do what Im told  ;)
Please see my replies in green below. As you can see, not much luck so far. Any other suggestions?
  • Let's test with both the array and pool not mounted.
    • Are you able to use the Web UI and browse whatever mounts you see?
      Yes, all drives have been added.
    • Are you able to query for SMART? Etc.
      Yes, works for all registered HDDs
    • Are you able to do the above after 5/10/30 minutes of the tRAID services being up?
      Yes, this does not appear to be time limited.
  • Test whether the array (without) pool mounts successfully.
    • With the array online, are you able to run a small range (1GB) Verify?
      Running 0-1GB verify. UI keeps loading. After reload of of UI, there is nothing under tasks. No updates in logs either.
    • Are you able to use the Web UI to get SMART while the array is up?
      As for the step above, the start button for array is grayed out, but it does not appear to be running.
    • Are you able to do the above after 5/10/30 minutes of the tRAID services being up?
      I dont think time is a factor here. Attaching pic of interface after having started the array and reloaded UI.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #9 on: December 02, 2017, 01:55:05 pm »
Your the expert, just trying to do what Im told  ;)
...
No one is "telling" you anything. You are merely being given some inputs to consider. I.e., this is not paid support. ;)

From your above descriptions, it seems to me that the broker is failing as soon as the array is started. You should verify that by checking if the broker service is up or not once the UI becomes unresponsive.
So, the steps need to be modified to:
Quote
1. Disable the pool auto-start option
2. Set the host to log in TRACE mode. In the Web UI, select to edit the host and you will see the option to set the log level for the host.
3. Do another sudo strace -p pid >> /tmp/strace.txt
4. Finally, start the array but not the pool.
5. Attach both /tmp/strace.txt and /var/log/NZFSB.log here

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #10 on: December 02, 2017, 02:10:38 pm »
Also, do post a screenshot of your RAID options.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #11 on: December 02, 2017, 04:42:36 pm »
Update
Looks like you have stumbled upon a Linux kernel bug. The kernel was the culprit all along. There is a message in the dmesg that I had overlooked.
I will look into how to work around this Linux bug and push out a new release.
This is also specific to kernel 4.10 as kernel 3.19 works just fine.
« Last Edit: December 02, 2017, 04:46:58 pm by Brahim »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #12 on: December 03, 2017, 01:25:23 pm »
Update
The issue is now fixed and a new build has been push out. You can now update your installation to the latest using the installation manager.

Offline cogliostrio

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +2/-0
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #13 on: December 03, 2017, 03:04:36 pm »
Can confirm that it now works with ubuntu 16 and 4.10.0-40-generic. Array and pool now autostarts.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: FlexRAID tRAID 1.1 Final (new release 2017-11-24)
« Reply #14 on: December 04, 2017, 09:09:40 am »
Can confirm that it now works with ubuntu 16 and 4.10.0-40-generic. Array and pool now autostarts.
Great. Thanks for confirming the fix.